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
If OpenCode loses the in-memory runner for a session while a task tool call is still persisted as pending or running, aborting the session only marks it idle. The parent assistant message and task part remain unfinished, so the transcript shows a task that never completed.
The TUI startup path for --continue --fork can also briefly route through a placeholder session ID (dummy), which produces an invalid-session error instead of returning to home when no session is available.
Steps to reproduce
Start a session that invokes the task tool.
Interrupt or restart the local runner after the task part is persisted but before it reaches a terminal state.
Abort the parent session.
Observe the task part still shown as pending or running and its assistant message left incomplete.
For the fork path:
Run opencode --continue --fork with no resumable root session.
Observe the placeholder-session validation error.
Expected behavior
Abort should cancel any live runner, then settle orphaned task parts with an aborted error and complete their parent assistant message. --continue --fork should show a loading state and return home with an error when no session can be forked.
fix: orphan sub-sessions not cleaned up when parent aborts #37314 covers the broader lifecycle problem of child sub-sessions surviving a parent abort. This issue is narrower: it settles stale persisted task parts and their parent assistant message after the local runner is gone.
#45482 addresses this — abort now returns success only once the branch is closed and released, and pending tool calls are terminalized rather than left running.
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.
Activity
0xfed commentedon Aug 13, 2026
Related reports:
--continue --fork: Expected a string starting with "ses", got "dummy" #29262 previously reported the--continue --forkstartup request using thedummyplaceholder session ID. This fix avoids entering that route while the fork target is unresolved.taskparts and their parent assistant message after the local runner is gone.NamedIdentity commentedon Aug 27, 2026
#45482 addresses this — abort now returns success only once the branch is closed and released, and pending tool calls are terminalized rather than left running.
Tarquinen commentedon Oct 20, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊