Nobody really knows how to product-ize any of these LLM interfaces beyond just chat.
They don't want a traditional UI with buttons and forms and labels because they want the interface to be "chat". The problem is that "chat" is tedious. And the turn-based, linear nature of the chat interaction model makes it even more tedious and unproductive.
One thing I would like is a tree-like chat structure like reddit / HN. Many times I abandon the direction things have gone but would like to resume at some ancestor or sibling response.
I solved this with task management and got work trees.
The downside of course is branching in got, but I usually don’t go of course more then a handful of tasks.
I had to engineer my own ticket management to keep opus on target. It’s been great for managing work, history, audit trails and commits are tagged with the task id.
I implemented subtasks to deal with the way Claude likes to stage its own objectives.
Then I made enforcement logic in the task manager so tasks can’t be closed out until reviewers have consensus on the same sha.
The adhd that is Anthropic demanded I build it and now I’m knocking out issues faster than Batman.
I'm not affiliated, and did not actually try it, but your comment reminded me of the juggler coding agent, discussed here: <a href="https://news.ycombinator.com/item?id=48883305">https://news.ycombinator.com/item?id=48883305
>Each conversation is a Yjs CRDT tree. It can branch into sub-threads (recursively), and you can drill down, backtrack, edit, undo/redo, and inspect everything: tool calls, approvals, and the raw context JSON going to the model, etc.
Gemini has something kind of like this. In a chat, click on the "..." icon next to one of Gemini's responses and select "Branch in new chat".
It creates a new chat which has the conversation up to that point and a link to the conversation you branched it from.
The UI isn't tree-like, though. It's more like Git where each branch name is just mixed in with the rest of the soup of references.
petcat · · focus · HN ↗
They don't want a traditional UI with buttons and forms and labels because they want the interface to be "chat". The problem is that "chat" is tedious. And the turn-based, linear nature of the chat interaction model makes it even more tedious and unproductive.
clumsysmurf · · focus · HN ↗
BikiniPrince · · focus · HN ↗
The downside of course is branching in got, but I usually don’t go of course more then a handful of tasks.
I had to engineer my own ticket management to keep opus on target. It’s been great for managing work, history, audit trails and commits are tagged with the task id.
I implemented subtasks to deal with the way Claude likes to stage its own objectives.
Then I made enforcement logic in the task manager so tasks can’t be closed out until reviewers have consensus on the same sha.
The adhd that is Anthropic demanded I build it and now I’m knocking out issues faster than Batman.
drivebyhooting · · focus · HN ↗
Often times I just sort of wish to undo.
whythismatters · · focus · HN ↗
>Each conversation is a Yjs CRDT tree. It can branch into sub-threads (recursively), and you can drill down, backtrack, edit, undo/redo, and inspect everything: tool calls, approvals, and the raw context JSON going to the model, etc.
jobigoud · · focus · HN ↗
adrianmonk · · focus · HN ↗
It creates a new chat which has the conversation up to that point and a link to the conversation you branched it from.
The UI isn't tree-like, though. It's more like Git where each branch name is just mixed in with the rest of the soup of references.
AshleyGrant · · focus · HN ↗