{"version":"2.1.232","anchor":"remote-control-stops-retrying-an-unreachable-server","canonical_anchor":"remote-control-stops-retrying-an-unreachable-server","heading":"Remote Control stops retrying an unreachable server","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/remote-control-stops-retrying-an-unreachable-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Remote Control stops retrying an unreachable server\n\nRemote Control gives up after 14 reconnect tries and tells you it couldn't reach the server.\n\n**What**\n\nReconnect 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.\n\n**Details**\n\n- Only the heartbeat close case (code 4093) sets a retry cap; other close reasons are unchanged.\n- Giving up emits telemetry carrying the attempt count, elapsed milliseconds, and how many queued writes were dropped.\n- 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.\n\n**Evidence**\n\n`bridge_repl_v2_remint_loop_exhausted`\n\n- Flag `tengu_bridge_recovery_patience`: Not enough to say (read for one account on one subscription tier against v2.1.232; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}