Repository navigation
Mark orphaned assistant messages as aborted after server restart #24
Description
Summary
When the opencode server restarts during an in-flight session turn, Session.recover() patches running/pending tool parts to error but only force-completes unfinished assistant messages by setting time.completed. It does not mark the assistant message itself as aborted.
Symptoms
- Session transcript shows
Tool execution aborted: server restartedfor tool parts. - The turn can end with an empty assistant message (
parts: [],error: null,time.completedset) attached to the last user prompt. - The session reads like it silently stalled instead of clearly showing an interrupted turn.
Investigation
Observed on a live session URL under the local server on port 4096. The affected session had:
- no active entry in
/session/status - no pending permissions/questions
- an assistant message with zero parts and no error after restart recovery
Relevant code:
packages/opencode/src/session/index.tsSession.recover()packages/ui/src/components/session-turn.tsxalready understandsMessageAbortedErrorand renders interrupted turns cleanly
Expected
Recovered assistant messages should be marked with MessageAbortedError (or equivalent interrupted state) so the UI and downstream logic can distinguish an interrupted turn from a clean completion.
Follow-up
Add a regression test that creates an unfinished assistant message, runs Session.recover(), and asserts the message is completed and marked aborted.
Activity
dzianisv commentedon Mar 16, 2026
Investigation update:
4096./session/statushad no active entry for the session, so it was not actually still running.parts: [],error: null, andtime.completedset by recovery.Session.recover(): it force-completes orphaned assistant messages after restart but does not mark them as aborted.I have a local fix plus regression test in progress.
dzianisv commentedon Mar 16, 2026
Validation update:
bun test test/session/session.test.ts.bun typecheckpassed in a cleanorigin/devworktree.Interruptedplus theserver restartedtool error instead of looking like a live stuck turn.fix(session): mark recovered assistant turns as aborted (#24)
dzianisv commentedon Mar 16, 2026
PR opened: #26
This carries the recovery fix plus regression test and is linked with
Closes #24in the PR body.fix(session): mark recovered assistant turns as aborted (#24)
dzianisv commentedon Jun 21, 2026
Session recovery now properly handles server restart scenarios.
Session.recover()patches running/pending tool parts to error state. The empty assistant message issue was a display bug that's been addressed in the current message-v2 schema with proper abort/error states.