You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release
What
--allow-dangerously-skip-permissions adds bypassPermissions, the mode that skips permission prompts, to the modes you can switch to. In a background session, Claude Code now ignores this flag unless your consent to bypass mode is on record. Interactive sessions are not affected. The flag is ignored when all of these hold:
the session is a background worker (CLAUDE_CODE_SESSION_KIND=bg), such as one the agents view dispatches
bypass mode is not disabled by policy and not blocked by the host
no consent is on record
Consent means "skipDangerousModePermissionPrompt": true in your user settings (~/.claude/settings.json) or in managed policy settings. Accepting the bypass-mode disclaimer writes the same key. The same key in .claude/settings.local.json or passed with --settings does not count here, even though it still skips the disclaimer.
When the flag is ignored you see a warning starting "--allow-dangerously-skip-permissions ignored:" that names the fix. Before, the flag always made bypass mode available.
Why
A background session runs with nobody watching, so bypass mode there now needs consent from your own user settings or from policy, not from a project's files or a launch flag.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed background workers honoring --allow-dangerously-skip-permissions on respawn without the bypass-permissions disclaimer having been…
