{"version":"2.1.290","anchor":"background-worker-bypass-permission-mode-requires-consent-in","canonical_anchor":"background-worker-bypass-permission-mode-requires-consent-in","heading":"Background workers only keep bypassPermissions mode with consent in your user settings","tier":"notice","area":"Permissions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/background-worker-bypass-permission-mode-requires-consent-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Background workers only keep bypassPermissions mode with consent in your user settings\n\nA background worker in bypassPermissions mode falls back to default unless skipDangerousModePermissionPrompt is true in ~\/.claude\/settings.json\n\n**Unclear.** It is not clear whether this fallback is newly enforced or whether only the message is new.\n\n**What**\n\nbypassPermissions mode lets Claude Code act without asking for permission first. When a background worker (a copy of Claude Code doing work out of sight) is set to that mode, it now drops back to the default permission mode and says Permission mode downgraded to default, unless you have agreed to it in a specific place.\n\nThe agreement only counts if `\"skipDangerousModePermissionPrompt\": true` is in `~\/.claude\/settings.json`. These do not count:\n\n- The same setting in `settings.local.json`\n\n- The same setting passed with `--settings`\n\n**Why**\n\nIf you run background agents in bypassPermissions mode, they may quietly fall back to asking for permission unless the consent is in your user settings file.\n\n- Area: Permissions\n- Names: `bypassPermissions`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}