Summary
Selecting a message in the session fork modal has no effect. The message is not selected and the modal remains unchanged, preventing the session from being forked at an earlier point in its history.
Environment
- opencode version: OpenCode v2
0.0.0-next-15311
- OS: Darwin 25.3.0, arm64
- Terminal: Ghostty,
TERM=xterm-256color, COLORTERM=truecolor
- Shell:
/bin/zsh
- Install/channel: v2 next
- Active plugins:
./plugins/cmux-session.js./plugins/cmux-feed.js
Reproduction
- Open an existing conversation with multiple messages.
- Open the session fork modal.
- Navigate through the conversation history.
- Select a message using the keyboard.
- Repeat by selecting a message with the mouse.
Expected Behavior
The selected message should be visibly selected and the session should be forked from that point in the conversation history.
Actual Behavior
Selecting a message has no effect. The message is not selected, no fork is created, and the modal remains in the same state.
The behavior occurs with both keyboard and mouse input.
Additional Context
The goal was to fork the session before an issue-reporting exchange so that the reporting content would not remain in the code-review context.
The problem has only been observed in this session so far, so it is not yet known whether it affects every session or depends on this session's history or state.
No workaround has been found.
Summary
Selecting a message in the session fork modal has no effect. The message is not selected and the modal remains unchanged, preventing the session from being forked at an earlier point in its history.
Environment
0.0.0-next-15311TERM=xterm-256color,COLORTERM=truecolor/bin/zsh./plugins/cmux-session.js./plugins/cmux-feed.jsReproduction
Expected Behavior
The selected message should be visibly selected and the session should be forked from that point in the conversation history.
Actual Behavior
Selecting a message has no effect. The message is not selected, no fork is created, and the modal remains in the same state.
The behavior occurs with both keyboard and mouse input.
Additional Context
The goal was to fork the session before an issue-reporting exchange so that the reporting content would not remain in the code-review context.
The problem has only been observed in this session so far, so it is not yet known whether it affects every session or depends on this session's history or state.
No workaround has been found.