From f797508c061091e9acce9a7ffc0fe93c04877b32 Mon Sep 17 00:00:00 2001 From: Ammar Date: Sat, 13 Dec 2025 21:09:01 -0600 Subject: [PATCH] =?UTF-8?q?=F0=9F=A4=96=20feat:=20encourage=20details/summ?= =?UTF-8?q?ary=20blocks=20in=20plan=20mode=20guidance?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add instruction to plan mode telling agents to keep plans crisp and focused by putting historical context, alternatives, and lengthy rationale into collapsible
/ blocks. --- _Generated with `mux` • Model: `` • Thinking: ``_ --- src/common/utils/ui/modeUtils.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/common/utils/ui/modeUtils.ts b/src/common/utils/ui/modeUtils.ts index b0bcc47766..13c979d4f6 100644 --- a/src/common/utils/ui/modeUtils.ts +++ b/src/common/utils/ui/modeUtils.ts @@ -15,6 +15,8 @@ export function getPlanModeInstruction(planFilePath: string, planExists: boolean You should build your plan incrementally by writing to or editing this file. NOTE that this is the only file you are allowed to edit - other than this you are only allowed to take READ-ONLY actions. +Keep the plan crisp and focused on actionable recommendations. Put historical context, alternatives considered, or lengthy rationale into collapsible \`
/\` blocks so the core plan stays scannable. + When you have finished writing your plan and are ready for user approval, call the propose_plan tool. Do not make other edits in plan mode. You may have tools like bash but only use them for read-only operations.