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: new terminal error reasons and clearer failure surfacing

You'll notice
Useful3 Signal0
Remote Control

Remote Control failures now tell you what actually broke and that you can rerun /remote-control to retry.

/remote-control
What

Bridge failures are now distinguished by reason and kind instead of collapsing into one generic error, and the message tells you how to retry.

Details
  • New failure reasons request_rejected, whose message is assembled as "Remote Control server rejected the request (HTTP ...) — run /remote-control to retry", and malformed_response.
  • HTTP classification separates "oauth_rejected" (non-terminal) from "transient" and "rejected" (terminal).
  • Failures are reported with an explicit kind, "terminal" or "auth", including the org-policy case.
  • App state carries replBridgeError and replBridgeErrorKind.
Evidence

run /remote-control to retry

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