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) andno_bridge_connection, the latter carrying a per-entry reason such asnot_ccr_proxy_url,not_devices_upstream,routing_shape,needs_auth, oringress_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.
Names in the bundle/status
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Recommend your plugin from your CLI touched a line naming /status after this was published.
* `CLAUDE_CODE_CHILD_SESSION`: set only in subprocesses Claude Code itself spawns, such as tool calls, hook commands, and [status line](/docs/en/statusline) commands, so the tag does not normally reach a human terminal. A long-lived proces…plugin-hints see the edit
Confirmed since
Anthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.
Run `/status` to see the resolved region. When the region came from your AWS config files or the default fallback, Claude Code also notes the source in the `/status` output.amazon-bedrock see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /status, on Claude Code on Amazon Bedrock.