Why Use Different Modes?
- Task specialization: Receive assistance tailored to the current task
- Safety controls: Minimize the risk of unintended file modifications
- Focused interactions: Get responses optimized for the activity in progress
- Workflow optimization: Move seamlessly between planning, implementing, debugging, and learning
Switching Between Modes
There are several ways to switch modes:- Dropdown menu: Click the selector next to the chat input to choose a mode
- Slash command: Enter
/architect,/ask,/debug, or/codein the chat input - Keyboard shortcut: Use the following shortcuts to cycle through available modes. After reaching the last mode, the next press returns to the first mode.
| Operating System | Shortcut |
|---|---|
| macOS | ⌘ + . |
| Windows | Ctrl + . |
| Linux | Ctrl + . |
- Suggested mode changes: Click on suggested mode switches offered when relevant
Built-in Modes
Code Mode (Default)
| Aspect | Details |
|---|---|
| Description | A software engineering persona with expertise in programming languages, design patterns, and best practices |
| Tool Access | Full access to all tool groups: read, edit, browser, command, mcp |
| Ideal For | Writing code, implementing features, debugging, and general development |
| Special Features | No tool restrictions; supports all coding tasks |
Ask Mode
| Aspect | Details |
|---|---|
| Description | A technical assistant focused on answering questions without modifying files |
| Tool Access | Limited access: read, browser, mcp only (cannot edit files or run commands) |
| Ideal For | Explaining code, exploring concepts, and learning technical topics |
| Special Features | Delivers informative responses without changing the project |
Architect Mode
| Aspect | Details |
|---|---|
| Description | A planning-focused persona that helps design systems and create implementation plans |
| Tool Access | Read, browser, mcp, and restricted edit (markdown files only) |
| Ideal For | System design, high-level planning, and architecture discussions |
| Special Features | Follows a structured process from information gathering to detailed planning |
Debug Mode
| Aspect | Details |
|---|---|
| Description | A troubleshooting specialist experienced in systematic problem-solving and diagnostics |
| Tool Access | Full access to all tool groups: read, edit, browser, command, mcp |
| Ideal For | Diagnosing errors, tracking bugs, and resolving complex issues |
| Special Features | Applies a methodical approach of analyzing, narrowing possibilities, and fixing problems |
Orchestrator Mode
| Aspect | Details |
|---|---|
| Description | A workflow coordinator that delegates complex tasks to appropriate specialized modes |
| Tool Access | Limited access for creating tasks and managing workflows |
| Ideal For | Breaking down projects into manageable subtasks handled by specialized modes |
| Special Features | Uses delegation tools to assign work to other modes |