Skip to content

Render Codex subagents in the feed - #292

Merged
Juliusolsson05 merged 1 commit into
mainfrom
fix/291-codex-subagent-rendering
Jun 18, 2026
Merged

Juliusolsson05 merged 1 commit into
mainfrom
fix/291-codex-subagent-rendering

Conversation

@Juliusolsson05

Copy link
Copy Markdown
Owner

Summary

Closes #291.

This implements the Codex side of the existing Claude-style subagent rendering path:

  • filters Codex <subagent_notification> runtime messages out of normal user prompt rendering
  • builds SubAgentState for Codex by joining parent spawn_agent calls to child rollout files via function_call_output.agent_id
  • routes Codex spawn_agent blocks through TaskSubagentRow, including adjacent spawn grouping
  • suppresses the raw spawn_agent result row because it is just {agent_id,nickname} join metadata
  • adds focused tests for notification filtering and Codex subagent state extraction/building

Evidence

The implementation is based on the saved debug bundle noted as "Not handling codex subagents at all." The parent rollout stores spawn_agent function calls and synthetic user <subagent_notification> messages, while the child rollouts store session_meta.payload.source.subagent.thread_spawn with the parent thread id, nickname, and role.

Verification

  • npm test -- --run src/renderer/src/workspace/codex/rollout.test.ts src/main/subagents/codexSubagentState.test.ts
  • npx tsc --noEmit

npm test and npm run build:app are blocked in this worktree because packages/claude-code-headless/src/... files, including src/proxy/mitmAddon.py, are missing from the worktree checkout. The new targeted suites pass before that unrelated package-source failure is hit.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Codex subagent notifications render as user prompts instead of structured agent state

1 participant