What
Bypass 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:
- 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)".
- 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.
Why
Before, 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
You can't set per-teammate permission modes at spawn time. A new teammate starts with the lead's mode, including `bypassPermissions` mode, which `--dangerously-skip-permissions` turns on. If the lead is in [`dontAsk` mode](https://code.cla…agent-teams see the edit
To make Claude's file tools refuse paths outside the working directories in every permission mode, including `bypassPermissions`, set one or both of these keys to `true`:permissions see the edit
| `skipDangerousModePermissionPrompt` | the Code tab has its own confirmation for [Bypass permissions mode](#choose-a-permission-mode), and this key doesn't skip it |desktop see the edit
Anthropic's documentation has since written up skipDangerousModePermissionPrompt, on Desktop application.