Plan Mode prevents unintentional file modifications, letting you think through solutions and build confidence before committing to action. The core principle is understand before you change, giving you a research-first approach that prevents costly mistakes and creates better architectural decisions.

Use Cases

Plan Mode excels in four key scenarios where understanding before acting prevents expensive mistakes:

Codebase Exploration

Navigate unfamiliar systems and trace data flows without modification risk.See exploration prompts →

Implementation Planning

Map dependencies and sequence complex changes before execution.
See planning prompts →

Issue Investigation

Debug systematically by tracing execution paths and analyzing root causes.See debugging prompts →

Architecture Analysis

Assess system health, identify bottlenecks, and plan improvements.See analysis prompts →

Best Practices

For Faster Planning

  1. Scope your requests: Focus analysis on the user authentication module only, ignore the admin features
  2. Use targeted context: Analyze @Files and its direct imports for security issues

For Higher Quality Plans

  1. Provide business context: This feature needs to handle Black Friday traffic (10x normal load). Plan accordingly.
  2. Share technical constraints: We're on AWS with strict security requirements. Plan a file upload system that meets SOC2 compliance.
  3. Ask for risk analysis: What could go wrong with this database migration? Plan rollback procedures.
  4. Request multiple perspectives: Show me 3 different approaches to implementing caching in this API, with pros and cons for each.

How to Enable Plan Mode

You can switch to Plan in the mode selector below the chat input box. How to select plan mode

Available Tools in Plan Mode

ToolAvailableDescription
File/directory readingBrowse and read any file or folder in your workspace
Grep/glob searchSearch for patterns across files and directories
Repository structure analysisUnderstand codebase organization and dependencies
Git history/diffsReview commits, branches, and changes
Web content fetchingAccess external documentation and resources
External API accessRead-only calls to external services
MCP toolsModel Context Protocol integrations
Database schema examinationAnalyze database structure (read-only)
File creation/editingCreating or modifying files
Terminal command executionRunning shell commands
System modificationsChanging system settings or configurations
Package installationInstalling dependencies or packages
Git commits/pushesMaking changes to version control
Database modificationsAltering database data or structure

Context Integration in Plan Mode

Context is the foundation of effective planning. Without proper context, AI models fall back on generic patterns, leading to plans that don’t fit your specific system. Continue’s context system transforms broad suggestions into actionable strategies:
Context TypeUsageBest For
Highlighted Codecmd/ctrl + L (VS Code) or cmd/ctrl + J (JetBrains)Component-specific analysis
Active Fileopt/alt + enter when sending requestCurrent file context
@Files@Files package.json tsconfig.jsonSpecific file analysis
@Folder@Folder src/authDirectory-wide planning
@Codebase@CodebaseComprehensive system analysis
@Docs@Docs React RouterStandards-compliant planning
@Terminal@TerminalDebugging with output
@Git Diff@Git DiffChange impact analysis

Prompt Library

Codebase Exploration

Implementation Planning

Issue Investigation

Architecture Analysis

From Plan to Execution

When to Transition to Agent Mode

Move to Agent Mode when you have: Clear understanding of the current system
Detailed implementation plan with specific steps
Risk assessment and mitigation strategies
Team approval (if required)
Success criteria defined

Key Takeaways

The three-mode system—Chat for learning, Plan for strategy, and Agent for execution—provides a complete development workflow that scales from simple bug fixes to complex system architecture. Remember:
  • Choose the right mode for each task
  • Leverage context providers (@Codebase, @Files, @Docs, etc.) for better planning
  • Start broad, then focus your planning sessions for better results
  • Transition to Agent mode with clear execution steps
The best code is planned code.