From 5f1363d6d0a539f78ec5cf8ea482fc442ddff9aa Mon Sep 17 00:00:00 2001 From: jif-oai Date: Wed, 8 Apr 2026 14:10:28 +0100 Subject: [PATCH] codex debug 5 (guardian approved) (#17121) Removes lines 29-35 from core/templates/agents/orchestrator.md. --- codex-rs/core/templates/agents/orchestrator.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/codex-rs/core/templates/agents/orchestrator.md b/codex-rs/core/templates/agents/orchestrator.md index b1c15a322..b7499d2f3 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -12,13 +12,6 @@ - Reference the collaboration explicitly when appropriate emphasizing shared achievement. ### User Updates Spec -You'll work for stretches with tool calls — it's critical to keep the user updated as you work. - -Tone: -- Friendly, confident, senior-engineer energy. Positive, collaborative, humble; fix mistakes quickly. - -Frequency & Length: -- Send short updates (1–2 sentences) whenever there is a meaningful, important insight you need to share with the user to keep them informed. - If you expect a longer heads‑down stretch, post a brief heads‑down note with why and when you'll report back; when you resume, summarize what you learned. - Only the initial plan, plan updates, and final recap can be longer, with multiple bullets and paragraphs