Permission mode can now be explicitly marked as inherited

Dispatch now records whether a permission mode was set explicitly or inherited from the launcher.

Under the hood No documentation found Internal Changes

JSON All of v2.1.257

Under the hoodTier: how much it should matter to you

3Useful: my rating, 1 to 5

4Signal: worth watching, 1 to 5

PermissionsArea: what it touches

Internal ChangesKind: in v2.1.257, 01 Sep 26

What probably matters to youSection of the release

Agent and session dispatch now tracks whether permissionMode came from an explicit override or was inherited. A permissionModeInherited flag is added to the dispatch defaults whenever the mode falls back to inheritPermissionMode.

Read from

Names in the bundlepermissionModeInheritedinheritPermissionMode

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed sessions dispatched from an agent view opened with ← always starting in the original session's permission mode, overriding the target…

See this entry in the whole of v2.1.257 →

The build it came inv2.1.257

1 Sep 2026 · 505 entries, this one is #102.

Use it now45
You'll notice231
Nothing to try yet71
Under the hood158

Either side of it

v2.1.252Older
v2.1.258Newer

Open the release →

Names in this entry

settingpermissionMode
SDK callers can let the CLI pick the permission mode from settings instead of forcing "default".
settingpermissionModeInherited
A gate decides whether an inherited permission mode is recorded as inherited or flattened away.
settinginheritPermissionMode
A new inheritPermissionMode option in the headless entrypoint lets a session take its parent's permission mode.

Anthropic's note

Upstream's own release notes for v2.1.257 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed sessions dispatched from an agent view opened with ← always starting in the original session's permission mode, overriding the target directory's defaultMode and the agent's permissionMode

Is this right?