Hacker News Reader

Preserve context in the lead chat - let the subagents fill up their own contexts then only return the necessary information.

View on HN

Why not just have an agent that can branch its context?

Forking conversations have been a thing for a long time, and it's not the same thing (e.g. you may have 50% of your context used up at fork time that is carried into "both agents" afterwards)

Also sometimes _not_ having the context is what you want.

Eg when I have the AI do a self-code-review before bothering a human, I also want to the AI to give the draft PR to a sub-agent that only has the publicly available context that a viewer of the final PR would have; and not all the accumulated reasoning that lead to the writing of the code in the PR.

It is exactly the same, you’re just doing it wrong.

So in your mind forking a repo removes the commits from one of the branches?

Reply on news.ycombinator.com