Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.225entry #58

Claude Code v2.1.225 ·

Remote Control: new terminal error reasons and clearer failure surfacing

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

You'll notice Improvements
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
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.

Read from
Names in the bundle/remote-control

See this entry in the whole of v2.1.225 →

Feedback