Summary
After the computer restarted, reopening an existing V2 session still showed in-progress spinners for work that had been interrupted by the restart. The transcript retained a pending shell call (bun ops prod health) and Writing command..., and the composer still offered ctrl+b to background the supposedly running work.
Interrupted work should be reconciled to a durable terminal/interrupted state after process or machine restart, not projected as still running.
Environment
- OpenCode version: V2 development build; exact build unavailable from the report
- OS: macOS
- Terminal: Unavailable
- Shell: Unavailable
- Install/channel:
opencode2 development channel
- Active plugins: Unavailable
- Model: Little Frank (
anomaly / OpenAI), medium variant
Reproduction
- Start a V2 session that is actively thinking and running a shell tool.
- Restart the computer while the step/tool is still active.
- Reopen
opencode2 and return to the session.
- Observe the interrupted step and tool state.
Expected Behavior
On restart/replay, any work that cannot still be executing is settled as interrupted or failed. Spinners stop, pending tool state is reconciled, and controls do not claim the stale work can be moved to the background.
Actual Behavior
The restored session still showed active spinners for:
Thought: Investigating issues
- shell command
bun ops prod health
Writing command...
The UI also displayed Press ctrl+b to move running work to the background, despite the machine having restarted.
Additional Context
Summary
After the computer restarted, reopening an existing V2 session still showed in-progress spinners for work that had been interrupted by the restart. The transcript retained a pending shell call (
bun ops prod health) andWriting command..., and the composer still offeredctrl+bto background the supposedly running work.Interrupted work should be reconciled to a durable terminal/interrupted state after process or machine restart, not projected as still running.
Environment
opencode2development channelanomaly/ OpenAI), medium variantReproduction
opencode2and return to the session.Expected Behavior
On restart/replay, any work that cannot still be executing is settled as interrupted or failed. Spinners stop, pending tool state is reconciled, and controls do not claim the stale work can be moved to the background.
Actual Behavior
The restored session still showed active spinners for:
Thought: Investigating issuesbun ops prod healthWriting command...The UI also displayed
Press ctrl+b to move running work to the background, despite the machine having restarted.Additional Context