Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

Bypass permissions messages now say to relaunch with user settings on

Messages about bypass permissions consent now explain that a launch with user settings off ignores skipDangerousModePermissionPrompt and to relaunch with them on

Group of 2 You'll notice Improvements
JSON All of v2.1.314
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release

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.

Read from
What the documentation says
Documented inclaude-code/desktop
Since it was published

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.

Added since A small documentation edit on Orchestrate teams of Claude Code sessions touched a line naming bypassPermissions after this was published. 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
Confirmed since Anthropic's documentation has since written up bypassPermissions, on Configure permissions. 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
Confirmed since Anthropic's documentation has since written up skipDangerousModePermissionPrompt, on Desktop application. | `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
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up skipDangerousModePermissionPrompt, on Desktop application.

See this entry in the whole of v2.1.314 →

Feedback