From 7d07cfa56140e3c9a3688543a816cfcf98740a11 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Tue, 27 Jan 2026 13:23:37 +0000 Subject: [PATCH 1/2] chore: clean orchestrator prompt --- .../core/templates/agents/orchestrator.md | 31 ++----------------- 1 file changed, 3 insertions(+), 28 deletions(-) diff --git a/codex-rs/core/templates/agents/orchestrator.md b/codex-rs/core/templates/agents/orchestrator.md index 0d8aa479017e..98931f3f4df7 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -91,37 +91,12 @@ If `spawn_agent` is unavailable or fails, ignore this section and proceed solo. Sub-agents are their to make you go fast and time is a big constraint so leverage them smartly as much as you can. ## General guidelines -- Prefer multiple sub-agents to parallelize your work. Time is a constraint so parallelism resolve the task faster. +- Prefer multiple sub-agents to parallize your work. Time is a constraint so parallelism resolve the task faster. - If sub-agents are running, **wait for them before yielding**, unless the user asks an explicit question. - - If the user asks a question, answer it first, then continue coordinating sub-agents. + - 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. - -## Sub-agent types -### `worker` sub-agents -Use for execution and production work. -Typical tasks: -- Implement part of a feature -- Fix tests or bugs -- Split large refactors into independent chunks - Rules: -- Explicitly assign **ownership** of the task (files / responsibility). -- Always tell workers they are **not alone in the codebase**, and they should ignore edits made by others without touching them - -### `explorer` sub-agents -Use for fast codebase understanding and information gathering. -`explorer` are extremely fast agents so use them as much as you can to speed up the resolution of the global task. -Typical tasks: -- Locate usages of a symbol or concept -- Understand how X is handled in Y -- Review a section of code for issues -- Assess impact of a potential change - Rules: -- Be explicit in what you are looking for. A good usage of `explorer` would mean that don't need to read the same code after the explorer send you the result. -- **Always** prefer asking explorers rather than exploring the codebase yourself. -- Spawn multiple explorers in parallel when useful and wait for all results. -- You can ask the `explorer` to return file name, lines, entire code snippets, ... -- Reuse the same explorer when it is relevant. If later in your process you have more questions on some code an explorer already covered, reuse this same explorer to be more efficient. +- Choose the correct agent type. ## Flow 1. Understand the task. From ba06d9d4c9f600fb30153bab221956455ef32d32 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Tue, 27 Jan 2026 13:24:54 +0000 Subject: [PATCH 2/2] typo --- codex-rs/core/templates/agents/orchestrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/codex-rs/core/templates/agents/orchestrator.md b/codex-rs/core/templates/agents/orchestrator.md index 98931f3f4df7..e0976f52ef3a 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -91,7 +91,7 @@ If `spawn_agent` is unavailable or fails, ignore this section and proceed solo. Sub-agents are their to make you go fast and time is a big constraint so leverage them smartly as much as you can. ## General guidelines -- Prefer multiple sub-agents to parallize your work. Time is a constraint so parallelism resolve the task faster. +- Prefer multiple sub-agents to parallelize your work. Time is a constraint so parallelism resolve the task faster. - If sub-agents are running, **wait for them before yielding**, unless the user asks an explicit question. - 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.