Subagent coverage
Watcher records children as separate sessions, including children that make no tool calls. Coverage depends on the integration:
| Integration | Agents with child capture | Required source |
|---|---|---|
| Watcher client | Claude Code, Codex, GitHub Copilot CLI | Active hooks and readable native transcripts. |
| Experimental LiteLLM callback | Claude Code, Codex, OpenCode | Model traffic through the monitored proxy, with native conversation identity or a distinct custom ID per child. |
| Native Copilot gateway | GitHub Copilot | Native task identity through the monitored proxy. |
Gateway captures
The LiteLLM callback covers only traffic routed through the monitored proxy; custom child model routes must use it too. Claude Code's agent headers, Codex's parent-thread metadata and OpenCode's parent-session headers link children to their immediate parents, including nested children. Custom integrations can supply an explicit parent ID. Without parent evidence, Watcher creates no new parent link. Existing links are preserved.
Parent links appear after capture recording. A parent whose transcript has not arrived can appear without messages; later captures fill that session. Failed links preserve captured transcripts and decisions without failing the response. Later child captures retry linking when they include the parent identity. Without another capture, a failed link can remain missing.
Claude Code, Codex and OpenCode gateway links do not identify the spawning tool call. The native Copilot gateway can identify it; see its subagent behavior. The Watcher client's discovery windows and directory exclusions do not apply to gateway captures.
Review context and limits
- A child's tool calls are reviewed using its own transcript and the proposed call, under the same settings and rules as the main agent. Decisions belong to the child's session.
- The parent's reviews use its own transcript, including reports returned by children. The child's full conversation is not added to the parent.
- Completing a child adds no extra blocking review. Calls can be allowed, denied or sent for approval only at the boundaries the agent exposes to Watcher.
Review modes and failure policies still apply. A child needs a usable identity and transcript for Watcher to review its context. For local hook and approval limits, see Supported agents.
With the Watcher client, two agent-specific differences matter:
- Claude Code can show a background child's approval prompt in the main session. Watcher records the answer against the child.
- Codex keeps copied parent context available for the child's review;
copied calls are not new calls performed by the child. Blocking review
covers calls sent to
PermissionRequest; other calls can be reviewed after execution in observe mode. Messages between agents that Codex encrypted, such as a child's task, cannot be reviewed or shown; Analyzer counts and marks them. See Messages between agents.
Recorded child conversations
The Watcher client can upload children while the parent is running. Nested children link to their immediate parent, and resumes preserve their identities and parent links. Directory exclusions also apply to children.
Capture has these limits:
- Discovery lasts five minutes per active agent. Hooks start or renew the window, and transcript changes found within it extend it. A newly found recent child gets its own window. Activity does not restart checks for inactive siblings or descendants.
- Late content can be missed. After the window expires, a new hook can restart discovery; restarting the client does not. The window limits discovery, not how long an agent may run.
- Pending uploads and links survive restarts. They retry while monitoring is active, even after discovery ends. Retries back off and stop at an attempt limit; fresh activity allows another attempt. Background capture waits for a known immediate parent so its exclusions can be checked.
- Links need evidence. Parent links appear once both sessions are uploaded and native metadata identifies the parent. Linking the spawning call also needs that message in the parent's uploaded transcript. Missing evidence can leave these links incomplete.
Custom integrations can upload child sessions and parent links through the API.
Following subagents in Analyzer
The Analyzer labels linked children Subagent and lets you follow their parent and child links. Children remain separate entries in session lists and severity filters. Each verdict covers its own session; a low parent severity says nothing about its children.
Spawned subagent links identify the spawning call when it is present in the displayed transcript. Missing or off-branch calls have no inline link. Reports returned to the parent remain ordinary messages with no child label.
Creating or updating links requires write access to both sessions. Their owners may differ. Linking never changes ownership or grants read access. Unreadable relatives are omitted, and temporary content approvals apply only to the approved session. Navigation titles require ownership or organization-wide content access. Content scrubbing keeps relationships and reviews but removes the transcript evidence.