Skip to main content
Plan Mode is a “think first, act second” conversation approach. When activated, the Expert will first create a structured plan document and discuss it with you iteratively before starting execution — rather than jumping straight into action.

​
Why Use Plan Mode

In the following scenarios, planning before executing can significantly improve delivery quality:

Complex Tasks

Multi-step, cross-module tasks, such as “refactor the entire payment system” or “build a complete blog website”

Architecture Decisions

When technology choices or architectural trade-offs are involved, such as “add a caching layer to the app” or “design the database schema”

Comparing Alternatives

When multiple viable paths exist, let the Expert analyze the pros and cons of each before choosing the optimal approach

Risk Management

For irreversible operations (data migrations, environment changes, etc.), first outline the risk points and rollback strategies

​
How to Use

1

Activate Plan Mode

Click the ”+” menu in the input box and toggle on “Plan Mode.” An indicator will appear in the input box showing you are in plan mode.
2

Describe Your Requirements

Describe the task you want to accomplish just as you normally would. The Expert will first conduct research (reading code, searching for information, etc.), then generate a plan document.
3

Review the Plan

The plan document will be displayed as a card in the conversation, typically including:
  • Current state: The current project status and your requirements
  • Approach: The chosen technical approach with comparisons to alternatives
  • Risks: Potential risk points and corresponding mitigation measures
  • Breakdown: Specific execution steps, with each step indicating the files and operations involved
4

Iterate and Refine

Not satisfied with the plan? Just tell the Expert your suggested changes. For example:
  • “Use a different implementation approach for step three”
  • “Add a rollback strategy”
  • “Merge these two steps into one”
The Expert will update the plan document based on your feedback.
5

Confirm and Execute

Once you’re satisfied with the plan, click the “Build” button on the plan card. The Expert will exit plan mode and begin executing the plan step by step.

​
Plan Mode Constraints

In plan mode, the Expert’s behavior is strictly limited to ensure no side effects are produced:
In plan mode, the Expert cannot perform the following operations:
  • Create, modify, or delete files
  • Run command-line instructions
  • Generate images or videos
  • Deploy or publish content
The Expert can only perform read-only research (reading code, searching for information) and write the plan document.
This means you can safely let the Expert explore freely in plan mode — it won’t make any actual changes to your project.

​
FAQ

In a normal conversation, the Expert thinks and executes simultaneously. Plan mode separates “thinking” and “execution” into two phases — first producing a complete plan, then executing after confirmation. This helps avoid “realizing halfway through that the direction is wrong” in complex tasks.
The plan document is saved in the current session’s working directory (plan.md), and you can view it in the workspace’s file panel. Each plan update overwrites the previous version.
Yes. Simply toggle off plan mode in the ”+” menu to return to normal conversation mode. Previously generated plan documents will not be lost.
After clicking Build, the Expert enters execution mode and follows the plan step by step. If adjustments are needed midway, you can tell the Expert directly in the conversation about the changes you want.
Usually not. For simple tasks like “change one line of code” or “add a button,” direct conversation is more efficient. Plan mode is primarily for complex tasks that involve multiple steps, carry risks, or have multiple possible approaches.

​
Best Practices

Provide ample context — Before activating plan mode, tell the Expert about the project background, your goals, and constraints. The richer the context, the higher the plan quality.
  • Describe “why” rather than “how”: Tell the Expert the problem you want to solve rather than specifying the implementation approach directly. Let the Expert suggest the optimal solution after conducting research.
  • Break down large tasks into phases: If the task is very large (e.g., “rewrite the entire backend”), consider splitting it into multiple sub-plans and executing them separately, focusing on one clear objective at a time.
  • Pay attention to the risk section: The “Risks” section of the plan is worth careful review to ensure every risk point has a clear mitigation strategy.