Source Intelligence

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.232 Home All releases olderv2.1.231 v2.1.233newer
Claude Code v2.1.232

Remote Control stops retrying an unreachable server

You'll notice
Useful3 Signal2
Remote Control

Remote Control gives up after 14 reconnect tries and tells you it couldn't reach the server.

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

What

Reconnect attempts after a lost heartbeat now stop after 14 tries instead of looping indefinitely, and report that Claude Code could not reach the Remote Control server for about 30 minutes.

Details
  • Only the heartbeat close case (code 4093) sets a retry cap; other close reasons are unchanged.
  • Giving up emits telemetry carrying the attempt count, elapsed milliseconds, and how many queued writes were dropped.
  • Controlled by a tengu_bridge_recovery_patience gate; nothing in this build sets it, so it falls back to on and the real value comes from remote config.
Evidence

bridge_repl_v2_remint_loop_exhausted

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

See this entry in the whole of v2.1.232 →