Videos
Maybe you miss it:
Plan mode is a special operating mode in Claude Code that allows you to research, analyze, and create implementation plans without making any actual changes to your system or codebase.
What Plan Mode Does:
Research & Analysis Only:
-
Read files and examine code
-
Search through codebases
-
Analyze project structure
-
Gather information from web sources
-
Review documentation
No System Changes:
-
Cannot edit files
-
Cannot run bash commands that modify anything
-
Cannot create/delete files
-
Cannot make git commits
-
Cannot install packages or change configurations
When Plan Mode Activates:
Plan mode is typically activated when:
-
You ask for planning or analysis before implementation
-
You want to understand a codebase before making changes
-
You request a detailed implementation strategy
-
The system detects you want to plan before executing
How It Works:
-
Research Phase: I gather all necessary information using read-only tools
-
Plan Creation: I develop a comprehensive implementation plan
-
Plan Presentation: I use the exit_plan_mode tool to present the plan
-
User Approval: You review and approve the plan
-
Execution Phase: After approval, I can proceed with actual implementation
Benefits:
-
Safety: Prevents accidental changes during exploration
-
Thorough Planning: Ensures comprehensive analysis before implementation
-
User Control: You approve exactly what will be done before it happens
-
Better Outcomes: Well-planned implementations tend to be more successful
I'm new to Claude Code. I'm a longtime CursorMax user, and all the tutorials and things that I've seen have talked about plan mode, but I just don't see it anymore. I don't see how to get into it.
What I have done, I've set it to use the model I've set it to use is OpusPlan, or something like that. It's supposedly where it plans using Opus and executes using Sonnet. And I think it's working, but these days when you actually do the /models command, it only gives you two choices. So are they moving away from this?
Now I just tell it, don't do anything. Let's just talk about the task first, et cetera.
Maybe you missed:
To activate PLAN MODE hit Shift + TAB and again Shift + TAB
Plan mode is a special operating mode in Claude Code that allows you to research, analyze, and create implementation plans without making any actual changes to your system or codebase.
What Plan Mode Does:
Research & Analysis Only:
Read files and examine code
Search through codebases
Analyze project structure
Gather information from web sources
Review documentation
No System Changes:
Cannot edit files
Cannot run bash commands that modify anything
Cannot create/delete files
Cannot make git commits
Cannot install packages or change configurations
When Plan Mode Activates:
Plan mode is typically activated when:
You ask for planning or analysis before implementation
You want to understand a codebase before making changes
You request a detailed implementation strategy
The system detects you want to plan before executing
How It Works:
Research Phase: I gather all necessary information using read-only tools
Plan Creation: I develop a comprehensive implementation plan
Plan Presentation: I use the exit_plan_mode tool to present the plan
User Approval: You review and approve the plan
Execution Phase: After approval, I can proceed with actual implementation
Benefits:
Safety: Prevents accidental changes during exploration
Thorough Planning: Ensures comprehensive analysis before implementation
User Control: You approve exactly what will be done before it happens
Better Outcomes: Well-planned implementations tend to be more successful
I've been using the planning mode for a while now. It's actually very very good. I now use it almost exclusively when I start working on a new feature.
Here's my workflow:
Shift + Tab twice to enter the planning mode
Brainstorming the implementation with Claude, provide feedback on the solution, iterate until I am happy with the solution.
I use @ reference to help Claude with additional context so it doesn't spend a lot time exploring
For convenience, I also connect CC to VS Code by using the `/ide` slash command. I open a file in VS, select the lines, and ask CC about the lines.
I iterate with Claude until I am happy with the solution. After that, Shift + Tab twice to enter auto edit mode. CC will complete the implementation with very little intervention.
I find that with this approach, I don't even need to create PLAN.md anymore. I try to keep the feature iterations small, and commit the changes as soon as the code is working.
Do you have similar experience?
Addendum:
To use the /IDE command, see https://docs.anthropic.com/en/docs/claude-code/ide-integrations
https://cuong.io/blog/2025/06/23-claude-code-ide-vs-code
The key for this to be effective is to keep the scope small. Plan what you will do in the next 30 minutes or less.
The workflow It should be
plan > code > debug > commit
plan > code > debug > commit
plan > code > debug > commit
...
This works really well with small and incremental changes.
Pro tip: while waiting for Claude, you can open another terminal and start another Claude. You can have multiple planning sessions at the same time.
For long discussions, you may use the normal mode and just Claude not to make any changes.
Better yet, use the repomix cli to create a dump of your project.
https://github.com/yamadashy/repomix
You then can upload it to ChatGPT or Claude Web UI for long discussions. Chatgpt's project + canvas feature is super neat for this kind of long planning.