{"version":"2.1.314","anchor":"background-bypass-consent-error-message-extended","canonical_anchor":"background-bypass-consent-error-message-extended","heading":"Bypass permissions messages now say to relaunch with user settings on","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/background-bypass-consent-error-message-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Bypass permissions messages now say to relaunch with user settings on\n\nMessages about bypass permissions consent now explain that a launch with user settings off ignores skipDangerousModePermissionPrompt and to relaunch with them on\n\n**What**\n\nBypass permissions mode is the mode that skips permission checks. To use it without a confirmation dialog, your user settings file needs `\"skipDangerousModePermissionPrompt\": true`. If Claude Code was launched with user settings turned off, it does not read that file, so the setting has no effect. Two messages now say so:\n\n- The error shown when bypass is used in a background worker without consent now adds: \"A launch with user settings off does not read that file: relaunch with them on\". Before, the message ended at \"which does not count here)\".\n\n- When user settings are off, the hint about the setting now tells you to \"relaunch with user settings on; \" before it says to add `skipDangerousModePermissionPrompt`.\n\n**Why**\n\nBefore, the messages told you to add the setting even when Claude Code would not read it, so following them would not help. They now point to the real fix: relaunch with user settings turned on.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}