Thread

1. nullbio · 1789610324 · focus · HN ↗

   I just have it write a checklist file in /tmp (or a todo folder if I want to keep it), and check off items as it finishes them. Seems to work fine. Is this really needed?

   1. trollbridge · 1789610520 · focus · HN ↗

      /tmp? What happens when you reboot?

      1. nonethewiser · 1789616287 · focus · HN ↗

         You know
      2. nullbio · 1789644876 · focus · HN ↗

         That's the entire point. Why would I want to keep these files around forever? If you're keeping these files you're just compounding drift onto drift and making it harder for the agent. For everything else, there is git history.
   2. broodbucket · 1789614721 · focus · HN ↗

      If you're writing design documentation to /tmp you're not the target audience for this kind of thing

      1. nullbio · 1789645173 · focus · HN ↗

         No, I write design documentation to a docosaurus folder where it can actually be read as docs nicely.

         Most of the time all you need is a throwaway md file to compensate for context loss and so you can loop on a spec across compaction. Once you have the spec implemented, there's usually no reason to keep it around. The code becomes the spec.

         For hard constraints you have AGENTS.md, or put it in another md file. Why do I need additional software for this?

Unofficial Hacker News client; not affiliated with Y Combinator.