{"version":"2.1.290","anchor":"proactivity-level-can-override-the-starting-permission-mode","canonical_anchor":"proactivity-level-can-override-the-starting-permission-mode","heading":"A proactivity level can set the permission mode a session starts in","tier":"use","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/proactivity-level-can-override-the-starting-permission-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### A proactivity level can set the permission mode a session starts in\n\nWhen a proactivity level other than default is set, Claude Code can choose the starting permission mode from it\n\n**What**\n\nA permission mode decides how often Claude asks before acting. When the session's proactivity level is something other than `default`, Claude Code now picks the starting permission mode from it. The level comes from the hidden `--proactivity` flag, or is handed over when Claude Code restarts itself.\n\n- `ask`: auto mode where auto mode is available, otherwise the default mode\n\n- `proactive`: auto mode where available, otherwise accept-edits mode\n\nBypass permissions is never picked this way. It does not happen when you gave a mode yourself (`--permission-mode`, `--inherit-permission-mode`, `--dangerously-skip-permissions`, or an agent's own permission mode), when the proactivity selector is off ([what turns it off](\/v\/2.1.290\/e\/new-proactivity-startup-level-gated-by-tengu-proactivity)), or when `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB` forces the default mode.\n\n**Why**\n\nA session started with `--proactivity ask` or `--proactivity proactive` can begin in a different permission mode than before, often auto mode.\n\n- Area: Permissions\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}