Claude Code v2.1.257 · 1 Sep 2026
A gate decides whether an inherited permission mode is recorded as inherited or flattened away.
Nothing to try yet
No documentation found In Development
Copy link
Copy markdown
JSON
All of v2.1.257
Nothing to try yet Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Permissions Area: what it touches
In Development Kind: in v2.1.257, 01 Sep 26
In Development Section of the release
Read from
Feature flag
tengu_agentview_inherit_mode_demote Not enough to say
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.257: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.257. It isn't a statement about your account. What a flag value here can and cannot tell you
How sure we are
Two sources agree Two things we can check say the same as this entry.
Anthropic's release notes agree Fixed sessions dispatched from an agent view opened with ← always starting in the original session's permission mode, overriding the target…
The name it cites is new in this build New in this build: tengu_agentview_inherit_mode_demote
See this entry in the whole of v2.1.257 →
1 Sep 2026 · 505 entries, this one is #352.
Use it now45 You'll notice231 Nothing to try yet71 Under the hood158
Open the release →
Names in this entry
flag tengu_agentview_inherit_mode_demote A hidden --inherit-permission-mode flag lets a spawned session take its permission mode from whatever launched it.
setting permissionMode SDK callers can let the CLI pick the permission mode from settings instead of forcing "default".
setting permissionModeInherited A gate decides whether an inherited permission mode is recorded as inherited or flattened away.
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?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 351 of 505
Sync-transport auth handshake option (feature-flagged)
Nothing to try yet Artifacts
In v2.1.257 In Development release-page order
Next → · 353 of 505
New gate suppresses commit/PR attribution and bridge-conflict correction
Nothing to try yet Git Integration