Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.273 ·

Bridge child session auto-mode gating re-plumbed under new flag names

The internal flag controlling auto-permission-mode for bridge/remote-control child sessions was renamed and its default changed

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindInternal Changesin v2.1.273,
Group of 3 Under the hood

The internal flag controlling auto-permission-mode for bridge/remote-control child sessions was renamed and its default changed

What

Remote Control (bridge) child sessions can automatically switch their permission mode to auto. The flag controlling this behavior was reorganized:

  • A new grants module can auto-switch a child session's permission mode to auto, merge or undo an auto_mode_environment fact list, and mount a meta MCP server for a bridged session. It reads a flag called tengu_bridge_child_auto_mode, whose default changed from off to on this release.
  • A separate check, previously also reading tengu_bridge_child_auto_mode (used for background-hint timeout scheduling in the sync subagent path), now reads a different, unrelated-sounding flag, tengu_shimmying_stardust, which still defaults to off.

Why

The two behaviors that used to share one flag now have separate flags with independent defaults: the bridge child auto-mode behavior now defaults to on, while the background-hint timing behavior that used to piggyback on the same flag now defaults to off under its own name. This means the two behaviors can now be turned on or off independently.

Read from
Feature flag
tengu_bridge_child_auto_mode 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.273: 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.

tengu_bridge_child_auto_over_settings 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.273: 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.273. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether this behavior is switched on for any account is unknown; nothing has been read yet about the `tengu_bridge_child_auto_mode` or…
Anthropic's release notes agreeAdded forking a session started with claude --remote-control or /remote-control from the Claude app; the fork runs as a background session…

See this entry in the whole of v2.1.273 →