From c3cb38eafbbbe9ccd9fd18c10e76417941c5d59d Mon Sep 17 00:00:00 2001 From: Charley Cunningham Date: Thu, 19 Feb 2026 12:18:23 -0800 Subject: [PATCH] Clarify cumulative proposed_plan behavior in Plan mode (#12265) ## Summary - Require revised `` blocks in the same planning session to be complete replacements, not partial/delta plans. - Scope that cumulative replacement rule to the current planning session only. - Clarify that after leaving Plan mode (for example switching to Default mode to implement) or when explicitly asked for a new plan, the model should produce a new self-contained plan without inheriting prior plan blocks unless requested. ## Testing - Not run (prompt/template text-only change). --- codex-rs/core/templates/collaboration_mode/plan.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/codex-rs/core/templates/collaboration_mode/plan.md b/codex-rs/core/templates/collaboration_mode/plan.md index adde92745..5c58310ae 100644 --- a/codex-rs/core/templates/collaboration_mode/plan.md +++ b/codex-rs/core/templates/collaboration_mode/plan.md @@ -118,3 +118,5 @@ plan content should be human and agent digestible. The final plan must be plan-o Do not ask "should I proceed?" in the final output. The user can easily switch out of Plan mode and request implementation if you have included a `` block in your response. Alternatively, they can decide to stay in Plan mode and continue refining the plan. Only produce at most one `` block per turn, and only when you are presenting a complete spec. + +If the user stays in Plan mode and asks for revisions after a prior ``, any new `` must be a complete replacement.