Plan Mode

Investigate and discuss first, review an editable complete plan, then explicitly begin implementation; planning and permissions are independent.

Plan mode is for work that needs agreement on requirements, boundaries, and implementation before execution. Klaus first investigates what it can discover in the working directory, discusses the decisions that need your input, and then presents a complete plan.

Enter and leave Plan mode

Select "Plan" from the + menu beside the composer (or /plan in the quick commands submenu) to toggle the mode. Toggling alone does not send an empty message, and existing draft content is preserved. Select the control again or click the Plan badge to leave.

The mode is saved per conversation and restored when you switch chats or reopen the same thread. A mode change during a running turn applies to the next request; it does not rewrite a request already in flight. Goals remain separate conversation state: entering Plan mode preserves an existing goal and suppresses its automatic continuation while planning.

Plan mode is independent of "Ask every time / Auto-edit / Skip all permissions". Investigation can include reading files and running checks; it must not perform changes that implement the task. Leaving Plan mode retains the conversation's permission rules and sandbox scope. Saving a Klaus-managed plan document does not grant arbitrary project-file write access.

Discussion, questions, and the complete plan

When a decision needs your input, Klaus shows structured questions. Navigate between questions, read the option descriptions, or choose "Other" and write an answer. Selecting an option still requires explicit submission. Questions, answers, and cancellation states stay with the corresponding conversation. Optional questions in ordinary conversation have a different waiting behavior from questions that block planning.

The complete proposal appears as a distinct plan, with "Writing plan" shown while it streams. It should explain the outcome, implementation, error handling, verification, and assumptions. Expand it, copy it, download PLAN.md, or read the rendered full document in the right panel.

Execution progress is separate: update_plan tracks pending, in-progress, and completed steps. That checklist is not the complete proposal for your review and does not replace the final plan.

Edit, give feedback, and implement

  • Opening the right panel displays the rendered document, including headings, lists, and tables. Select "Edit plan" to edit the full source, then use Save or Revert. Switching plans saves the current editor first. Resolve version changes or document conflicts before proceeding; an old draft cannot stand in for the latest reviewed plan.
  • Choose "Yes, implement this plan", or use ⌘/Ctrl+Enter. Klaus reads the current full content, validates the plan identity and revision, leaves Plan mode, and starts implementation. Accepting a plan does not approve subsequent tool operations.
  • The "Implement this plan?" area beside the composer provides one implementation choice and a field for explaining what should change. This continues planning and revision; feedback does not authorize implementation. A complete revised proposal follows when ready.
  • Cancel or Escape dismisses the current implementation request without accepting it. A failed submission keeps the plan and edits available for recovery and retry.

Spec documents and review records in older conversations remain readable. New work uses the planning workflow above. This page keeps its existing URL; see Plan mode and permission prompts for related permission behavior.