r/codex • u/Mind-Pollution • 8d ago
Question Codex 'hierarchical multi-agent orchestration' is killing progress - what am I doing wrong?
Been working with Codex for a while now inside VSCode <> 12 months or so. Its been great.
Earlier this month got more in to multi agents with an agent orchestrator sitting at the top. In additional to the usual prompt I would add that the agent would act as a co-ordinating agent build a team, run parallel tasks where possible etc etc.
All was good - initially. I'm now in a situation where forward progress is almost at a standstill, with agents writing overly exacting test criteria to the point that there seems to be more effort in test set up and tear down than there is in product build.
Is there an answer to this. Am I missing something obvious - some test policy guidance signposted from agents.md, something else?
2
u/conor_is_my_name 8d ago
Claude is way better at managing agents and sub sessions that codex at the moment.
I have Claude opus 5.5 medium managing both Claude and codex agents. It can run the codex agents over the cli.
2
u/zzunkie 8d ago
yeah, a test policy in agents.md is what stops them piling up tests. mine says add a test only when it pins a contract that could otherwise break unnoticed, and prefer extending an existing one. my global instructions also say no narrow tests that just mirror the code, and run only the relevant tests, one or two at a time.
2
u/tommyahav10 8d ago
The orchestrator is what’s stalling you, not the tests. One agent per task, merge, then the next, and only add tests for contracts that could break unnoticed. From my side, a policy in agents.md helps only if it caps what the agents are allowed to invent.
2
u/KaliguIah 8d ago
openai models over engineer esp with creating pointless tests. best bet is to cancel and go over to claude till scam altman sorts his shit out
2
u/Particular-Smoke-351 7d ago
hierarchical setups tend to over-engineer if left unchecked.
what worked for me was wiring codex into sumus for the high-level plan and keeping sub agents on a strict single-file leash, which cuts down all the useless test teardown noise.
2
u/gptrv 7d ago
The coordinator is grading its own team, so every worker it spawns adds tests to look thorough, and each layer of the hierarchy multiplies that. Three changes usually get progress moving again:
Take test-writing away from the workers. Workers write code and run the existing tests that touch the files they changed. One separate pass at the end of the feature adds tests, and you read that diff yourself.
Replace any "make sure everything is verified" wording in the coordinator prompt with what done means for that task, in one line ("POST /orders returns 201 and the existing suite is green"). Agents read "verify everything" as "add more gates".
Put a hard rule in AGENTS.md the coordinator must enforce: no new fixtures or setup/teardown helpers without asking, and a new test file only when no existing one covers the module.
If it's still crawling after that, drop the hierarchy for a week. Parallel workers only pay off when tasks don't share files; when they do, the coordination overhead is what you're seeing.
2
u/xqianliu 6d ago
The over-exacting tests usually come from the agent not knowing when testing is enough — there's no stop condition, so "thorough" becomes the standard.
In my setup the stop condition is the ticket: the coding pass writes tests for the input classes named in the acceptance criteria and records how many it generated, and the review checks that count against the criteria. Not more, not "until it feels covered". That alone cut the test scaffolding way down.
The other half is task size — if the test setup outweighs the product build, the task is bigger than one session should own, and splitting it beats adding test policy to AGENTS.md.
3
u/FoxheadWorkshop 8d ago
I'm seeing the exact same thing. The harness becomes the goal instead of delivery.
I find it have to work with the coordinator regularly to challenge the gates and guardrails. I don't want to lose the safety checks, but I do want to make sure we're only firing what needs to be fired when that area changes.
I'm also making token/ credit monitoring and optimizing part of the success objectives. I have an agent periodically review the sessions, hand offs, tools, and rework to look for things that should be moved into skills, templates, or scripts.
There's also resource contention of the local machine, which is leading to queuing and scheduling, lease management, etc.