Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Remote Control re-arms itself after a re-login

You'll notice
Useful4 Signal0
Remote Control Notable

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

Feature flag
tengu_bridge_auth_revive Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.225: off

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

/login
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →