/fork
what do you think about having a /fork function, that will /compact and then create a new session containing only the summary message or something?
long sessions tend to be VERY long to re-render and that can make it nicer to "continue" work.
That being said, I'm not sure I want this solution[1]--but wanted to put it here for discussions purposes anyway.
[1] I think that a better approach will be to actually render quicker, or in the background, or cache it, or all the above.
yes can confirm that longer sessions get very unstable and laggy
yes! fork command is very nice ux. But i think it should not compact by default, and if you want you can run /compact and then /fork.
Or maybe just adding a command to fork from the last user message would be good enough. I know we can jump to the user messages and then fork from there, but it might be worth adding a shortcut command for fork the previous message.
You can currently fork by clicking a message and then selecting fork but we should prolly make it more discoverable