Conversation
|
@vvoland what do you think about the UX? any hard desire for the session not to branch? i think this is safer as a default. Or any other thoughts? :) |
|
UX-wise, there are issues imo:
As for branching itself - no hard opinion, but personally I'm fine with just discarding the conversation after the edited message. I don't think I would have the brain capacity to think about different branches 😅 |
|
For the edit button, i was thinking we could reuse the message selection code that already exists when pressing TAB, which now only selects assistant messages for copying them but could easily extend to user messages where then pressing Totally agree the button can be hard to spot, its not easy to make things both visible and not too ugly in a terminal interface (and font choice also affects what you see) Branching was more something i wanted to have because:
|
|
Consider adding a possibility to branch out without touching a mouse. The tool already supports some of vim style navigation, which I find really convenient. Maybe something like using Tab to switch to messages panel and |
9985a21 to
d0e18ae
Compare
Allows users to edit a previous message, which will cause the session to branch off so no messages in the original session get lost Signed-off-by: Christopher Petito <chrisjpetito@gmail.com>
Signed-off-by: Christopher Petito <chrisjpetito@gmail.com>
d0e18ae to
0e9202a
Compare
|
You can now edit via the keyboard as well, give it a try :) I also fixed/cleanup up some minor details while i was there (e.g. msg selection styling will be restored when exiting the selection mode) |
Allows users to edit a previous message, which will cause the session to branch off on the spot so no messages in the original session get lost
The newly created session gets a parent session id and position of the message it was branched off from, allowing for future features that may be interesting to have (tracing a session tree, branching off a question to multiple different models/agents at the same time, etc.)
Screencast
Screencast.From.2026-02-03.13-45-44.mp4