Been using pi-web for a while and noticed it only supports fork / clone between sessions — every time I want to branch off from a specific message, it creates a brand new session file.
In the TUI, /tree (the branch selector that pops up on double-Esc) actually switches nodes within the same session file without spinning up a new one. That's really handy when you're exploring different approaches — you don't end up cluttering the session list with a bunch of forks.
Just wondering: was this intentionally left out of pi-web, or just hasn't been prioritized yet? If it's on the roadmap, what shape might it take — clicking a node in the left-side tree view to switch, or a separate entry point?
Happy to take a stab at a PR if that helps, though I haven't fully figured out how the web side should wire up to the core navigateTree. Would love to hear your thoughts first.
Been using pi-web for a while and noticed it only supports fork / clone between sessions — every time I want to branch off from a specific message, it creates a brand new session file.
In the TUI,
/tree(the branch selector that pops up on double-Esc) actually switches nodes within the same session file without spinning up a new one. That's really handy when you're exploring different approaches — you don't end up cluttering the session list with a bunch of forks.Just wondering: was this intentionally left out of pi-web, or just hasn't been prioritized yet? If it's on the roadmap, what shape might it take — clicking a node in the left-side tree view to switch, or a separate entry point?
Happy to take a stab at a PR if that helps, though I haven't fully figured out how the web side should wire up to the core
navigateTree. Would love to hear your thoughts first.