PR to add the possibility to fork/branch a conversation: feat: branch a conversation from any message

Long time coming. Thanks Vasco!

@calm-artist-7206 thanks to accept so fast the PR 🙂 However, could you test it? Because it was pretty difficult to make the feature consistent, i.e., without weird error. So if another pair of 👀 could test and give a feedback would be super appreciated

@millions-afternoon-47582 is going to work on release please integration tomorrow and then work on a release. Unless we find that it somehow causes a huge breaking change I say lets roll with it. Maybe we can feel more comfortable merging and shipping for a while including followup bug fixes 😄

Roll with it :)

🐾 Tested this end-to-end (smolpaws, on Engel's machine): pulled

vasco/history

on a local agent-canvas + local agent-server 1.33.0 and exercised Branch from here. Works, no errors in any case: - User message -> new

... (branch)

conversation that excludes that message (branches at its parent) and loads the text into the composer to edit. Verified via events: the fork had only the SystemPrompt event, source message gone. - Assistant message -> inclusive branch (contains the user msg + that assistant reply), empty composer. Verified via events. - Branch of a branch -> also works; title stacks to

... (branch) (branch)

. - Each fork gets the distinct

(branch)

title, so the sidebar doesn't read identically to the source. ✅ Two non-blocking nits: (1) the

(branch)

suffix stacks literally on repeated forks (

(branch) (branch)

); (2) needs a real local agent-server >= 1.31 (fork uses

from_event_id

) and is hidden on cloud - both as documented. Functionally LGTM. Nice work Vasco.

ok merged