Skip to content

Task child session can exist without metadata.sessionId after interruption, leaving web UI unable to show subagent activity #22348

Closed as not planned

Description

@wanyaoluo

Description

When the Task tool spawns a child session, the child can already exist in /session/{parentID}/children, but the parent task part can still finish as interrupted/aborted without preserving metadata.sessionId.

In the Web UI this makes delegated work look silent/frozen, because the parent task card cannot follow the child session even though the child session already exists and may already contain messages.

This seems related to #21802 and #21979, but the specific issue here is the missing parent-child linkage metadata after interruption.

Plugins

None.

OpenCode version

1.4.2

Steps to reproduce

  1. Start a normal Web UI session.
  2. Let the main agent use the task tool to spawn a subagent.
  3. Hit an interrupted/aborted path for that delegated task.
  4. Compare the parent session timeline with GET /session/{parentID}/children.
  5. Observe that the child session exists and may already contain messages, but the parent task part has no metadata.sessionId, so the Web UI cannot surface the delegated activity.

Screenshot and/or share link

No share link yet.

Example parent task state captured from a real session:

{
  "status": "error",
  "error": "Tool execution aborted",
  "metadata": {
    "interrupted": true
  }
}

Operating System

WSL Ubuntu 24.04 / Linux, using the Web UI in a browser

Terminal

Web UI (browser), not TUI / ACP

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 13, 2026
  2. github-actions commented on Apr 13, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • This issue does not use one of the three required issue templates (Bug Report, Feature Request, or Question). Please re-submit or edit the issue using the appropriate template — in this case, the Bug Report template.

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


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

    If you believe this was flagged incorrectly, please let a maintainer know.

  3. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Apr 13, 2026
  4. github-actions commented on Apr 13, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now follows the contributing guidelines and the Bug Report template correctly. The compliance flag has been removed.

  5. removed
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  6. github-actions commented on Jul 4, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions