Notable changes in Watcher

The Analyzer connects recorded parent and child sessions so reviewers can follow delegated work.

The Watcher client stores Claude Code children as separate sessions and reviews each child's tool calls using its own transcript.

The Watcher client stores each Codex child's transcript in its own session and reviews the child's tool calls in that context.

What's new?

• Subagent labels identify children in session lists and headers.
• Parent and child links show direct relationships. Child lists show each child's own review result.
• Spawning calls link to their children when identified in the displayed transcript.
• Children inherit their parent's known owner. Temporary content approvals remain session-specific.
• Children retain their own severity. Parent verdicts do not combine child verdicts.
• Text-only children are captured too. Parent transcripts retain the child's returned response. See Subagent coverage.
• Transcript and parent-link retries survive client restarts.
• Local upload state migrates automatically. No manual migration is needed, but downgrading to a release before this upgrade is unsupported. Older clients cannot read the migrated upload state, including after a server rollback. Reinstalling an older client does not undo the migration. Read the restriction in Update Watcher before upgrading clients or planning a rollback.
• Children previously filed under their parent get their own session on the next full transcript upload. Existing records under the parent stay in place; they are not moved or deleted.
• Child transcripts retain inherited parent context. Parent transcripts retain the child's returned response. See Subagent coverage.
• Reuploading an older Codex transcript can add a one-time extra trajectory within the same session. Tool names now include their group where needed to match Codex's hook reports. This changes stored message identifiers and can duplicate history from the first renamed tool onward. Parent sessions can be affected too. Later uploads of the same transcript do not keep adding copies.
• Existing grades stay linked to the original trajectory. If the extra trajectory has no grade on its own message chain, its API response can return a prior session grade as a fallback. That grade still refers to the original trajectory. Both trajectories remain recorded.

No manual reupload or cleanup is required for this change.