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'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.
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 ↗
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.