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

Claude Code v2.1.225 ·

Remote Control re-arms itself after a re-login

Remote Control now turns itself back on after you log in again, instead of staying dead.

You'll notice Notable New Features
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
New FeaturesKind: in v2.1.225,
What probably matters to youSection of the release
What

A watcher now runs while a REPL bridge session sits in the "auth" failure state and turns Remote Control back on once valid credentials reappear, instead of leaving the session dead until manual intervention.

Details
  • Re-checks credentials every 300000 ms; on finding a fresh credential for the same account it clears replBridgeError, flips replBridgeEnabled back on and fires telemetry tengu_bridge_repl_auth_revive.
  • Refuses to revive across accounts, logging "credential belongs to a different account — disarming".
  • In non-interactive sessions a brake applies unless an in-process /login bumps the new authChangeGeneration counter.
  • Close code 4094 (worker credential expired) is treated as auth-recoverable only when this gate is on.
  • Gated on tengu_bridge_auth_revive, fallback true absent a server value; with the gate off the code still logs "kill switch off — still polling, no unattended revive".
  • authChangeGeneration and the "\x00baseline-pending" sentinel are new in this build.
Evidence

[bridge:repl] Auth-revive watcher: fresh same-account credential — re-enabling Remote Control

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/login
Feature flag
tengu_bridge_auth_revive On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.225: 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.225. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_bridge_auth_revive, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_bridge_auth_revive, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_bridge_auth_revive

See this entry in the whole of v2.1.225 →

Feedback