Hacker News new | ask | show | jobs
by julesrms 14 days ago
An agent like claude might run a subagent (e.g. to fetch and summarise a web page, or explore a code question) as if it's a tool, so you can't really see what's going on inside it. Juggler makes these sub-threads part of the overall structure, so you can navigate into them.

Another really elegant thing that pops out of subthreads is that to do a compaction, you simply move the entire conversation into a subthread, and let the subthread summarise itself (which they do anyway). So we get compaction as part of the architecture, and you can also dig into that old thread if you need to revisit any of it

1 comments

Ah, ok. Visibility into subagents makes perfect sense. From the "reddit-style" description I was imagining something where the user was conversing non-linearly with the agent at different points in some big tree.
Honestly even just a bookmarking system would go a long way to fix the problem, but getting "off-topic" in LLMs (3 years later and trillions of dollars of investment) still ruins my flow entirely. I end up playing an unwanted game of scrollbar warrior jumping back and forth between two points in chat. Could be that I'm studying a textbook and looking to enhance/check my understanding with Claude, or that I'm working on complicated tasks in my codebase. Side tangents always crop up. LLMs don't handle it well. Blows my mind that it doesn't bother anybody else, perhaps IATAH
You can go off topic and just rewind the context or edit it and delete the off topic messages. Not all harnesses let you do this as easily as you should.

If the off topic messages change files, then it's a bit more complex.

Lol