[Bug]: Codex child-agent output floods the parent chat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
- Start T3 Code and connect the Codex provider.
- Open a project thread.
- Ask: “Start 3 parallel sub-agents and summarize their results after they finish.”
- Observe the parent chat and Agents panel.
Expected behavior
The parent chat should show only the coordinator’s messages. Child-agent
activity should appear separately in the Agents panel with readable names,
statuses, and token usage.
Actual behavior
Child agents’ narration, reasoning, commands, and tool output appear directly
in the parent chat. The conversation becomes flooded, and the Agents panel may
show no agents or only opaque UUIDs.
Impact
Major degradation or frequent failure
Version or commit
Local source build, based on main @ 02f4ce56
Environment
Fedora Linux, Brave browser, Codex provider, T3 Code source build
Logs or stack traces
Screenshots, recordings, or supporting files
Workaround
No reliable workaround. Reducing the number of parallel agents avoids the issue but defeats the multi-agent workflow.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in apps/server and reproduce the three-parallel-sub-agent scenario with the Codex provider. Trace how child-agent narration, reasoning, commands, and tool output are routed to the parent chat and Agents panel; done means only coordinator messages appear in the parent chat while agents show readable names, statuses, and token usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100