What it is
The remote-control bridge now reconnects project-thread sessions when it restarts
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.271.
Presence across releases
1Build by build
8One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.273 read on another version | Not enough to say | no value returned | no value returned | on |
| v2.1.271 read on another version | Not enough to say | no value returned | no value returned | on |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Names beside it
Every feature flag in the inventory starting tengu_bridge_rc_child, up to twelve of them.
tengu_bridge_rc_child_artifactRemote Control child sessions gain two new optional capabilities: artifact behavior and inherited machine settings v2.1.269
tengu_bridge_rc_child_idle_exit_msMore conditions now trigger a session-tag prefetch before spawning a Remote Control bridge worker v2.1.273
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.