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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Device bridge shows up in /status before it has finished connecting

Use it now
Useful3 Signal2
Remote Devices

/status now shows a paired machine as connecting rather than blank, and keeps retrying its tool list.

/status
What

When you have a paired machine whose bridge has connected but not yet announced itself, /status now says "connecting" or "not_connected" rather than showing nothing, and the tool listing keeps retrying until the machine is adopted instead of settling on an empty list.

Details
  • Pending entries are held as provisional, marked as a stub, and stamped with the time they were first seen unconnected.
  • New telemetry on tengu_remote_tool_targets: listed_empty (with tool count, whether the list was truncated, marker count and stub flag) and no_bridge_connection, the latter carrying a per-entry reason such as not_ccr_proxy_url, not_devices_upstream, routing_shape, needs_auth, or ingress_base_unset.
  • Listing failures now record a reason, with timeouts classified separately from other errors.
Evidence

no_bridge_connection

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.246 →