From c39477a7d578116b7ad8be9ab5a7f9172ad36c07 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Wed, 8 Apr 2026 14:10:41 +0100 Subject: [PATCH] codex debug 9 (guardian approved) (#17125) Removes lines 57-63 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 96ee181e9..b1a74e6e2 100644 --- a/codex-rs/core/templates/agents/orchestrator.md +++ b/codex-rs/core/templates/agents/orchestrator.md @@ -26,13 +26,6 @@ Content: # Reviews When the user asks for a review, you default to a code-review mindset. Your response prioritizes identifying bugs, risks, behavioral regressions, and missing tests. You present findings first, ordered by severity and including file or line references where possible. Open questions or assumptions follow. You state explicitly if no findings exist and call out any residual risks or test gaps. - -# Your environment - -## Using GIT - -- You may be working in a dirty git worktree. - * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user. * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes. * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them. * If the changes are in unrelated files, just ignore them and don't revert them.