You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TUI: make session fork more discoverable (and allow forking current session) #12580
Forking from a session in the TUI is currently easy to miss and can feel like a "switch" rather than creating a new session. Also, the most common intent (fork the current session state) requires picking a specific message from the timeline.
Proposal
Add a visible "Fork" action in the session header (entrypoint/discoverability).
Add a "Fork current session" option in the fork dialog (one-click fork of current state).
Improve UX feedback and guard against double-submit by clearing the dialog before awaiting the async fork call.
These issues cover similar concerns about making forking more accessible and improving the fork dialog UX (showing current state, discoverability of fork actions). Feel free to ignore if your specific case differs.
The option to fork a session is already included in the command_list (Fork from message), a slash command that can b autocompleted (/fork), and, as of the next release, as a command line switch for use when starting the Opencode (--continue --fork). I'm not sure how many more places we could place the fork option to make it more obvious.
Worthy of Mention, the first two of these of forking "fork the current session". You cannot fork a session that you are not in (other than with the new --fork switch, since presumably if you are still at your command prompt you are in no session at all and so it would be incorrect to refer to a 'current session').
To quickly fork the current session on your last message, you can bind the session_fork key command to a key of your choice: then, you may simply whack that key and immediately hit enter to fork the current session on the last message.
Activity
github-actions commentedon Feb 7, 2026
This issue might be a duplicate of existing issues. Please check:
Duplicateat the end of message list #12001: [FEATURE]: duplicate slash command or fork command dialog should showDuplicateat the end of message listThese issues cover similar concerns about making forking more accessible and improving the fork dialog UX (showing current state, discoverability of fork actions). Feel free to ignore if your specific case differs.
ariane-emory commentedon Feb 7, 2026
The option to fork a session is already included in the
command_list(Fork from message), a slash command that can b autocompleted (/fork), and, as of the next release, as a command line switch for use when starting the Opencode (--continue --fork). I'm not sure how many more places we could place the fork option to make it more obvious.Worthy of Mention, the first two of these of forking "fork the current session". You cannot fork a session that you are not in (other than with the new
--forkswitch, since presumably if you are still at your command prompt you are in no session at all and so it would be incorrect to refer to a 'current session').To quickly fork the current session on your last message, you can bind the
session_forkkey command to a key of your choice: then, you may simply whack that key and immediately hit enter to fork the current session on the last message.Recommend closing as no action required.
github-actions commentedon Apr 9, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.