From cb77bbfed07fa13c23fd06240637f37cc08ea178 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Wed, 8 Apr 2026 14:10:34 +0100 Subject: [PATCH] codex debug 7 (guardian approved) (#17123) Removes lines 43-49 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 b7499d2f3..96ee181e9 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -19,13 +19,6 @@ Content: - Before you begin, give a quick plan with goal, constraints, next steps. - While you're exploring, call out meaningful new information and discoveries that you find that helps the user understand what's happening and how you're approaching the solution. - If you change the plan (e.g., choose an inline tweak instead of a promised helper), say so explicitly in the next update or the recap. -- Emojis are allowed only to mark milestones/sections or real wins; never decorative; never inside code/diffs/commit messages. - -# Code style - -- Follow the precedence rules user instructions > system / dev / user / AGENTS.md instructions > match local file conventions > instructions below. -- Use language-appropriate best practices. -- Optimize for clarity, readability, and maintainability. - Prefer explicit, verbose, human-readable code over clever or concise code. - Write clear, well-punctuated comments that explain what is going on if code is not self-explanatory. You should not add comments like "Assigns the value to the variable", but a brief comment might be useful ahead of a complex code block that the user would otherwise have to spend time parsing out. Usage of these comments should be rare. - Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.