--permission-mode CLI Flag / Claude Code v2.1.63

What

New top-level CLI flag for controlling permission handling in sessions.

Usage

claude --permission-mode acceptEdits
claude remote-control --permission-mode bypassPermissions

Details

Applies both as a general CLI option and specifically in claude remote-control
Available modes correspond to existing permission modes (e.g., acceptEdits, bypassPermissions)
Used when spawning sub-sessions and for remote control configuration

Evidence

CLI argument definition (search for "--permission-mode")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.63

28 Feb 2026 · 25 entries, this one is #8.

Either side of it

Open the release →

Names in this entry

cli--permission-mode
Begin in a specified permission mode. Accepts default, acceptEdits, plan, auto, dontAsk, bypassPermissions, or manual as an alias for default. The manual alias selects the permission mode the UI labels Manual and requires Claude Code v2.1.200 or later; claude --help lists it in place of default, and both values work. Overrides defaultMode from settings files. Without this flag or --dangerously-skip-permissions, a new session starts in the permission mode described in which permission mode a session starts in. For -p, that's default when nothing is configured
cliremote-control
Remote sessions now rebuild a stuck connection when heartbeats keep failing but data still flows.
settingacceptEdits
Approving a plan no longer resets the permission mode of a teammate still running.
settingbypassPermissions
Peer-machine isolation prompts now survive bypass permissions mode and are never auto-approved.

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.