# Planning Mode

Planning mode restricts the agent to read-only operations for research and design before implementation.

## What Changes
- **Allowed**: file_read, file_list, file_search, file_info, db_sql (SELECT only), memory tools, skill tools, plan_read, plan_write, plan_list, chat_list, chat_history, web_search, web_fetch, query_llm, file_versions, approval_list, approval_create, approval_cancel
- **Blocked**: All file writes, code execution, deploys, database mutations, email, and other side-effect tools

## Plan Files
- Use `plan_write` to save plans as timestamped markdown files in the project
- Use `plan_list` to see all saved plans
- Use `plan_read` to review a specific plan

## When to Use
- Researching before building - gather requirements, read existing code, check databases
- Designing architecture - write plans without accidentally modifying anything
- Reviewing work - audit what's in the project without risk of changes
- The user toggles plan mode via the status bar or by asking

## Tips
- Plan mode is a safety net - the agent physically cannot modify files or execute code
- Switch back to normal mode when ready to implement
- Plans persist as files in the project, so they survive mode switches