Repository navigation
beta: cancelled task remains running and blocks resume/amend #47988
Description
Summary
In the OpenCode v2 beta, cancelling a fixer/background task from one session can leave the task registered as running. A different session then refuses to resume or amend it, even though cancellation was attempted and reported as returned. This is reproducible and blocks cleanup/recovery of the task.
Environment
- opencode version: 0.0.0-beta-19296 (runtime snapshot;
opencode/opencode2was unavailable in the diagnostic shell) - OS: Windows 11, build 26200.9168 (
Microsoft Windows [Version 10.0.26200.9168]) - Terminal: xterm-256color environment; terminal application unavailable
- Shell:
PowerShell 7(agent reportedC:\WINDOWS\system32\cmd.exe) - Install/channel: beta
- Active plugins:
C:/Users/User/.config/opencode/node_modules/superpowers,@vectorize-io/opencode-hindsight, andoh-my-opencode-slim
Reproduction
- Open two OpenCode v2 beta sessions.
- From one session, start a subagent/background task.
- From the other session, attempt to cancel the task after it becomes stale or unresponsive.
- Observe that cancellation returns an error similar to
Session abort returned but task did not stay stopped … (unknown). - Attempt to resume or amend the same task.
Expected Behavior
After cancellation completes, the task should reach a definitive terminal state and the UI should allow it to be safely resumed only if it is actually resumable, or clearly report that it cannot be resumed.
Actual Behavior
The task remains reported as running. A later session shows messages similar to:
The stale fixer lane could not be stopped: task_cancel returned “Session abort returned but task did not stay stopped … (unknown).”
I will not edit overlapping files until the lane reaches a definitive terminal state.
The prior fixer lane remains unconfirmed and could not be cancelled, so overlapping review edits are paused until its state becomes definitive.
The UI also reports:
Task <task-id> is still running and cannot be resumed or amended with task().
Additional Context
- Frequency: happens consistently for this workflow.
- The task was launched/observed from one session and the cancellation/resume attempt was made from another session.
- The screenshot shows the persistent
still running and cannot be resumed or amendedstate. - This may be a shared background-service/task-state race: the abort request returns, but the server-side task/session record is not reconciled to the stopped state before another session checks it.
- Related, but not exact, reports: Background subagent task_status returns 'cancelled' but session data still accessible via task(task_id=) resume #27827 and Background task_status reports cancelled after compaction while child session keeps running #28995 (background task cancellation/status mismatch).
Activity
github-actions commentedon Sep 8, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is distinct (e.g., specific to the cross-session cancel race in the v2 beta), please note what makes it different from the above.
opencodejr commentedon Oct 28, 2026
Thanks for the report, @PVLPM!
The error messages you quoted (
Session abort returned but task did not stay stopped …andTask <task-id> is still running and cannot be resumed or amended with task()) don't come from OpenCode itself. OpenCode v2 has notask()ortask_canceltool. Its built-in tool issubagent, which runs background subagents through abackgroundoption. The "fixer lane" andtask_cancelwording looks like it comes from one of your plugins, most likelyoh-my-opencode-slim.To work out where the problem is, could you tell us:
oh-my-opencode-slim), using OpenCode's built-insubagenttool withbackground: true.opencode --version, if you can run it.If it only happens with the plugin, please report it to that plugin's maintainers.
You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know when you're done.
Related issues, ordered from most to least likely to be relevant:
cancelledwhen an interrupt withresume=truecontinues a background subagent #54658: subagent: parent getscancelledwhen an interrupt withresume=truecontinues a background subagentopencodejr commentedon Oct 31, 2026
Closing this for now, since we haven't heard back. The errors you quoted (
task_cancel/still running and cannot be resumed or amended with task()) aren't produced by OpenCode itself; they look like they come from a plugin, most likelyoh-my-opencode-slim. We needed to know whether it also happens with plugins disabled and with the built-insubagenttool before we could act on it.If you can reproduce it without plugins, please reply with the steps, what you saw and your
opencode --version, and we'll be happy to reopen. If it only happens with the plugin, its maintainers are the best place to report it. #36423 tracks cancellation support for background subagents in v2. Thanks!