Skip to content

serve autoresume skips stopped sessions marked as MessageAbortedError #120

@OpenCodeEngineer

Description

@OpenCodeEngineer

Summary

opencode serve startup auto-resume currently only matches sessions with tool error Tool execution was interrupted by server restart.

In practice, many interrupted sessions are persisted as:

  • assistant error MessageAbortedError
  • or tool error Tool execution aborted

These sessions remain stopped after restart even when there is no newer user message.

Repro

  1. Start a long-running session.
  2. Stop/restart server while session is active.
  3. Start opencode serve again.
  4. Observe auto resume complete with resumed=0 and session remains stopped.

Expected

Serve startup should also resume sessions interrupted via abort path when no later user prompt exists.

Notes

Observed local DB state contains multiple recent sessions with MessageAbortedError and no following user message, while auto-resume scanned sessions but resumed none.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions