Please consider making side conversations either or both:
- persistable first-class as if they were not a /side branch
- mergeable back into the main conversation
- forkable
Currently the agent will mostly fail to do any of those, and only enable inferior workflows like:
- making a tedious handover doc
- try to perform some of those, waste time to only fail and provide similar handover texts as a fallback.
The kick of /side is quick switching among the two (main and side) unlike forking where it’s many operations for opening the fork side-by-side, which suggests extending the /side feature; but alternatively a fork-and-open-both flow might alternatively address the same. Or other quick switching capabilities which the /side keyboard shortcut is an example of.