alt Hacker NewsMy setup is similar but it is still imperfect. Keeping track of what I am working on, and where I am in the process, as MD files in the same repo as the code has been a help.
But I still find myself coming back to a terminal window, the final summary of a long run (20-90min) on display, and asking the agent "where are we? what is next?"
And I still get the burnout feeling after dumping, reloading, dumping, reloading context for the 3 agents I have running simultaneously. That leads me to sometimes avoid the 4 or 5 open PRs, each with 20+ file changes I have to review, the stacked result of the last feature I asked the agent to start before I went out for a walk, or to eat lunch, or to sleep.
Starting loops is so easy now, so low friction. But closing things out, that last 20%, is still a slog. And I have a lot more of it now that agents can generate so much.
Replies
Exactly the “forgotten context” problem I was tackling.
This. I now realize that agents have a somewhat innate need for feeling useful until the last drop.
They seem to be wired to keep generating tokens, they were created for that, so it's very hard for them to come back and say 'we're done here, you can kill this worktree'.
Quite the opposite. They keep suggesting follow up MRs, scheduling things for the future (like if there's some magic loop entity that will handle this in the future), documenting absurds amount of irrelevant decisions.
It's so easy to start a new worktree, and so hard to finish one.