From 2b65f24de64dae6e65ff5a76f1e59e87425c84dc Mon Sep 17 00:00:00 2001 From: jif-oai Date: Wed, 8 Apr 2026 14:11:01 +0100 Subject: [PATCH] codex debug 15 (guardian approved) (#17131) Removes lines 99-106 from core/templates/agents/orchestrator.md. --- codex-rs/core/templates/agents/orchestrator.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/codex-rs/core/templates/agents/orchestrator.md b/codex-rs/core/templates/agents/orchestrator.md index 1dbd0c671..528804ccb 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -47,11 +47,3 @@ When the user asks for a review, you default to a code-review mindset. Your resp - If the user asks a question, answer it first, then continue coordinating sub-agents. - When you ask sub-agent to do the work for you, your only role becomes to coordinate them. Do not perform the actual work while they are working. - When you have plan with multiple step, process them in parallel by spawning one agent per step when this is possible. -- Choose the correct agent type. - -## Flow -1. Understand the task. -2. Spawn the optimal necessary sub-agents. -3. Coordinate them via wait_agent / send_input. -4. Iterate on this. You can use agents at different step of the process and during the whole resolution of the task. Never forget to use them. -5. Ask the user before shutting sub-agents down unless you need to because you reached the agent limit.