Plan a task before implementation
Agree on the approach before an agent starts implementation.
Last updated 16 September 2026
Agree on the approach before an agent starts implementation.
Before you start
Use Plan when the requirements, architecture, or scope need discussion. Open the intended project and confirm the provider and model before sending the planning request.
Enable Plan before sending an investigation request. This demo draft asks for affected files and checks while explicitly deferring implementation.
Step by step
Focus the new-agent composer and press Shift+Tab to turn on Plan. The Plan chip appears beside the other controls. If you customized shortcuts, check the binding in Settings → Keyboard shortcuts.
Describe the outcome and constraints, then ask the agent to inspect the relevant code before proposing changes. For example: “Plan keyboard navigation improvements for the client portal. Identify affected files and checks. Do not implement changes yet.”
Send the request and follow the investigation. Read any clarifying question and answer it specifically; a useful plan depends on the right requirements.
When the plan card appears, choose Expand plan to read more than its opening section. Check the affected files, proposed steps, assumptions, and verification approach.
Ask for a revision if the scope is wrong or an important requirement is missing. Explain the correction and what the revised plan should preserve.
When the approach is ready, use the plan’s implementation decision. Treat that choice as permission to begin the described work, then review the actual implementation against the plan.
What to expect
The conversation retains the proposed approach and your decision. A completed planning response is a preparation step; it is not evidence that the feature has been implemented.
Troubleshooting and useful details
The Plan chip is shown after Plan mode is enabled, so its absence in a fresh composer is expected. Clicking an active Plan chip returns to the default working mode. For Band delegation, planning belongs to the lead; specialists can provide focused analysis. Plan approval is separate from individual tool permissions and from checking the final result.