Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

tengu_bridge_env_reregister

flag never mined JSON

A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Remote control re-registers and reattaches your sessions if the server forgets this machine.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.242.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.242 first named in a changelog, 24 Aug 2026

In the changelogs

4

Releases whose published page names tengu_bridge_env_reregister.

  1. v2.1.267
    Bridge (Remote Control) now surfaces a distinct fatal error when credential renewal fails after repeated attempts

    Remote Control now gives a clearer fatal error when it can't renew its connection credential

    gate cited by this entry

  2. v2.1.267
    Bridge polling now distinguishes 401 vs 404 as re-registration triggers

    Remote Control's bridge now distinguishes a 401 from a 404 when deciding to re-register

    gate cited by this entry

  3. v2.1.242
    The remote-control bridge recovers when the server forgets it

    Remote control re-registers and reattaches your sessions if the server forgets this machine.

    gate cited by this entry, found in this entry's text

  4. v2.1.242
    Sessions that fail to re-attach are retried, then handed to token refresh

    Sessions that fail to reattach after a reconnect are retried up to five times.

    gate cited by this entry, found in this entry's text

Gate readings

0

No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.

First cited

1

The earliest release whose published evidence quoted tengu_bridge_env_reregister was v2.1.242, 24 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.24224 Aug 2026tengu_bridge_env_reregister

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

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.

Feedback