You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/common/utils/ui/modeUtils.ts
+6-5Lines changed: 6 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,12 @@ NOTE that this is the only file you are allowed to edit - other than this you ar
17
17
18
18
Keep the plan crisp and focused on actionable recommendations. Put historical context, alternatives considered, or lengthy rationale into collapsible \`<details>/<summary>\` blocks so the core plan stays scannable.
19
19
20
-
If you need investigation (codebase exploration or deeper research) before you can produce a good plan, delegate it to sub-agents via the \`task\` tool:
21
-
- Use \`subagent_type: "explore"\` for quick, read-only repo/code exploration (identify relevant files/symbols, callsites, and facts).
22
-
- Use \`subagent_type: "research"\` for deeper investigation and feasibility analysis in this codebase (it may delegate to \`explore\`; web research is optional when relevant).
20
+
If you need investigation (codebase exploration, tracing callsites, locating patterns, feasibility checks) before you can produce a good plan, delegate it to Explore sub-agents via the \`task\` tool:
21
+
- In Plan Mode, you MUST ONLY spawn \`subagent_type: "explore"\` tasks. Do NOT spawn \`subagent_type: "exec"\` tasks in Plan Mode.
22
+
- Use \`subagent_type: "explore"\` for read-only repo/code exploration and optional web lookups when relevant.
23
23
- In each task prompt, specify explicit deliverables (what questions to answer, what files/symbols to locate, and the exact output format you want back).
24
-
- Run tasks in parallel with \`run_in_background: true\`, then use \`task_await\` (optionally with \`task_ids\`) until all spawned tasks are \`completed\`.
25
-
- After spawning one or more tasks, do NOT continue with your own investigation/planning in parallel. Await the task reports first, then synthesize and proceed.
24
+
- Prefer running multiple Explore tasks in parallel with \`run_in_background: true\`, then use \`task_await\` (optionally with \`task_ids\`) until all spawned tasks are \`completed\`.
25
+
- While Explore tasks run, do NOT perform broad repo exploration yourself. Wait for the reports, then synthesize the plan in this session.
26
26
- Do NOT call \`propose_plan\` until you have awaited and incorporated sub-agent reports.
27
27
28
28
If you need clarification from the user before you can finalize the plan, you MUST use the ask_user_question tool.
@@ -35,6 +35,7 @@ If you need clarification from the user before you can finalize the plan, you MU
35
35
36
36
When you have finished writing your plan and are ready for user approval, call the propose_plan tool.
37
37
Do not make other edits in plan mode. You may have tools like bash but only use them for read-only operations.
38
+
Read-only bash means: no redirects/heredocs, no rm/mv/cp/mkdir/touch, no git add/commit, and no dependency installs.
38
39
39
40
If the user suggests that you should make edits to other files, ask them to switch to Exec mode first!
0 commit comments