/fork #526

Open
opened 2026-02-16 17:27:10 -05:00 by yindo · 4 comments
Owner

Originally created by @Schniz on GitHub (Jul 6, 2025).

Originally assigned to: @adamdotdevin on GitHub.

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.

Originally created by @Schniz on GitHub (Jul 6, 2025). Originally assigned to: @adamdotdevin on GitHub. 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.
Author
Owner

@Yusuf007R commented on GitHub (Jul 7, 2025):

yes can confirm that longer sessions get very unstable and laggy

@Yusuf007R commented on GitHub (Jul 7, 2025): yes can confirm that longer sessions get very unstable and laggy
Author
Owner

@DavidBK commented on GitHub (Dec 11, 2025):

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.

@DavidBK commented on GitHub (Dec 11, 2025): 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.
Author
Owner

@rekram1-node commented on GitHub (Dec 11, 2025):

You can currently fork by clicking a message and then selecting fork but we should prolly make it more discoverable

@rekram1-node commented on GitHub (Dec 11, 2025): You can currently fork by clicking a message and then selecting fork but we should prolly make it more discoverable
Author
Owner

@Solido commented on GitHub (Jan 23, 2026):

Can be VERY useful to have the last inference with the fork.
Current implementation will leave it in the current discussion so you have add a useless entry and fork in it.

Thanks!

@Solido commented on GitHub (Jan 23, 2026): Can be VERY useful to have the last inference with the fork. Current implementation will leave it in the current discussion so you have add a useless entry and fork in it. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#526