Background subagent task_status returns 'cancelled' but session data still accessible via task(task_id=) resume

[smithyyang]

Bug Description

When using task(background=true) to launch a background subagent, the task completes successfully and results are visible in the UI. However, when the parent agent polls for results using task_status(task_id="...", wait=true), it returns state: cancelled with empty error.

The session data is not lost — using task(task_id="...", prompt="...") to resume the session retrieves the full completed results.

Steps to Reproduce

1. Set OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true
2. Launch background subagent: task(background=true, ...)
3. The subagent completes its work (results visible in parent session context)
4. Parent agent calls task_status(task_id="...", wait=true) to get results
5. state: cancelled is returned, no result data

Expected Behavior

task_status(wait=true) should return state: completed with the full task result data, matching what is visible in the session UI.

Workaround

Instead of using task_status, use task(task_id="<same_id>", prompt="return your previous result") to resume the session and retrieve results. But this is clunky — the parent agent shouldn't need to know the prompt again.

Environment

• OpenCode version: latest
• Feature flag: OPENCODE_EXPERIMENTAL_BACKGROUND_SUBAGENTS=true
• Plugin: @tarquinen/opencode-dcp@latest (DCP)

---

Re-submitted from #27827 — the original issue was closed due to triage bot not assigning labels/staff.

[github-actions]

This issue might be a duplicate of an existing issue. Please check:

• Background subagent task_status returns 'cancelled' but session data still accessible via task(task_id=) resume #27827: Identical issue — same title, same description, same author. This appears to be a direct re-submission of that closed issue.

If #27827 was closed incorrectly (e.g., by an automated bot without valid reason), please leave a comment on that issue requesting it be reopened, rather than creating a new one. Maintainers can reopen closed issues.

If you believe this is a separate occurrence or the previous issue was closed in error, please clarify the distinction here.

[smithyyang]

just as what i said ,Re-submitted from #27827 — the original issue was closed due to triage bot not assigning labels/staff.