What
Claude Code can hand over a session that was started in advance to the user who claims it. On internal builds, claiming such a session in bypassPermissions mode used to be refused. That is the permission mode in which Claude does not stop to ask before acting. The error told the user to start the session cold, meaning start it fresh. That check has been removed.
Why
This most likely matters only to people running internal builds. They can now claim a pre-started session in that mode instead of starting over.
Names in the bundlebypassPermissions
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 Configure permissions touched a line naming bypassPermissions after this was published.
In the TypeScript SDK, if you set `allowDangerouslySkipPermissions: true` alongside `permissionMode: 'plan'`, file edits and shell commands that modify files still reach your `canUseTool` callback. The option lets you switch to `bypassPerm…agent-sdk/permissions see the edit
Confirmed since
Anthropic's documentation has since written up bypassPermissions, on Interactive mode.
| `Shift+Tab`, or `Alt+M` on Windows when the Node or Bun runtime doesn't enable VT input mode | Cycle permission modes | Cycle through `default` (labeled Manual in the mode indicator), `acceptEdits`, `plan`, and, when available, `bypassPe…interactive-mode see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear whether the same restriction is now enforced somewhere else.
Anthropic's documentation agrees
Anthropic's documentation has since written up bypassPermissions, on Interactive mode.