Bug: Tab agent badge shows 'Done' when a subagent finishes, while the main agent is still running

[kikerojasx]

Pre-flight Checks

• I have searched existing issues and this is not a duplicate
• I understand this issue needs a readiness label before a PR can be opened

Bug Description

When a CLI agent (e.g., OpenCode) spawns subagents, Warp's tab badge changes to Done as soon as any subagent finishes, even if the main agent conversation is still active or other subagents are still running. This makes it hard to know when the user actually needs to review the final response.

Steps to Reproduce

1. Open a Warp tab running OpenCode.
2. Ask OpenCode a question that causes it to spawn one or more subagents (e.g., a complex refactor or multi-file task).
3. Observe the tab badge while subagents are running.
4. When one subagent finishes, but the main agent or other subagents are still running, the badge switches to Done.

Expected Behavior

The tab badge should remain In progress until the main agent conversation has fully completed and no subagents are still active. Only then should it show Done.

Actual Behavior

The badge switches to Done as soon as the first subagent finishes, creating a false "ready for review" signal.

Operating System

macOS

Agent / Client

OpenCode

Shell

zsh

Additional Context

I have inspected the open-source codebase and believe the root cause is in CLIAgentSessionsModel, which currently stores one session per pane and transitions to Success on any Stop event from a subagent. There is no tracking of parent/child subagent relationships when computing the badge status.

I would love to contribute a fix. A proper solution would add subagent tracking to CLIAgentSessionsModel so that the pane-level session status considers the whole agent tree (main + subagents) before reporting Success.

Files likely involved:

• app/src/terminal/cli_agent_sessions/mod.rs
• app/src/workspace/view/vertical_tabs.rs
• app/src/ai/agent/conversation.rs

[oz-for-oss]

@kikerojasx

Here's what I found while triaging this issue:

Thanks for the detailed report. This matches a plausible current-client behavior: a completed subagent can cause Warp to mark the tab's agent status as done even though the parent run is still active.

Maintainer details

I concluded that openCode subagent stop events can make Warp show the CLI-agent tab status as Done before the parent agent session has finished..

Triage

This looks like a real CLI-agent status aggregation bug rather than only a vertical-tabs rendering issue. The report provides a clear OpenCode subagent workflow, and the current client code appears to support the failure mode described.

The most likely cause is that the CLI-agent session model is pane-scoped: it stores one session for the terminal view and maps any stop event to Success. The parsed event includes a session_id, but the model does not currently use that to track a parent conversation plus active child/subagent sessions, so a child completion can overwrite the pane-level status while the main run is still active. Vertical-tab status consumers then render that success state as Done.

Duplicate check: I enumerated the repository's open non-PR issues and found related but distinct agent/status issues such as #9868, #9958, #12639, #12688, and #7408. None matched this specific OpenCode subagent stop event causing the tab badge to show Done early, so this does not look like a duplicate.

Suggested routing: CLI agent session tracking plus vertical-tab/agent icon status display.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[MaggieShan]

@kikerojasx Thanks for reporting! I believe the original issue has since been fixed in open code warpdotdev/opencode-warp#22 such that subagent sessions wouldn't send duplicate stop notifications - going to close this issue but let me know if you're still seeing it