Quick Start
Available Modes
| Mode | Value | Safety | Description |
|---|---|---|---|
DEFAULT | default | ✅ Safe | Standard permission checking - prompts for each operation |
ACCEPT_EDITS | accept_edits | ⚠️ Moderate | Auto-accepts file edit operations without prompting |
DONT_ASK | dont_ask | ⚠️ Moderate | Auto-denies all permission prompts |
BYPASS | bypass_permissions | 🔴 Dangerous | Skips all permission checks entirely |
PLAN | plan | ✅ Safe | Read-only exploration mode - no modifications allowed |
Mode Details
DEFAULT - Standard Permission Checking
DEFAULT - Standard Permission Checking
The default mode prompts for permission on each operation that requires approval.Behavior:
- Prompts user for each permission request
- Follows configured permission rules
- Safest mode for production use
ACCEPT_EDITS - Auto-Accept File Edits
ACCEPT_EDITS - Auto-Accept File Edits
Automatically accepts file edit operations without user confirmation.Behavior:
- Auto-approves file write operations
- Still prompts for other operations
- Useful for automated refactoring tasks
DONT_ASK - Auto-Deny Prompts
DONT_ASK - Auto-Deny Prompts
Automatically denies all permission prompts without user interaction.Behavior:
- Auto-denies all permission requests
- Agent continues with read-only operations
- Useful for safe exploration tasks
BYPASS - Skip All Checks
BYPASS - Skip All Checks
Bypasses all permission checks entirely.Behavior:
- No permission checks performed
- All operations allowed
- Maximum agent autonomy
Security Risk: Only use in fully trusted environments. Agent can perform any operation without restriction.
PLAN - Read-Only Exploration
PLAN - Read-Only Exploration
Restricts agent to read-only operations for safe exploration.Behavior:
- Only read operations allowed
- Write/modify operations blocked
- Perfect for codebase exploration
Usage with Subagents
Default Mode for All Subagents
Per-Call Override
Combined with Model Selection
Best Practices
Use PLAN mode for exploration
Use PLAN mode for exploration
When subagents only need to read and analyze code, use
plan mode to prevent accidental modifications.Avoid BYPASS in production
Avoid BYPASS in production
The
bypass_permissions mode should only be used in controlled development environments, never in production.Match mode to task
Match mode to task
Choose the permission mode that matches the task requirements:
- Exploration tasks →
plan - Refactoring tasks →
accept_edits - Interactive tasks →
default
Log permission decisions
Log permission decisions
When using non-default modes, log the permission mode being used for audit purposes.

