Source Intelligence

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.251 Home All releases olderv2.1.250
Claude Code v2.1.251

Remote Control startup handles an org-policy refusal on its own terms

You'll notice
Useful3 Signal2
Remote Control

Remote Control now says plainly when your organization's policy turned it off.

What

When the Remote Control connection is declined because of organization policy, Claude Code now says so directly with "Remote Control is disabled by your organization's policy. Contact your organization admin for access." and leaves the feature off, instead of counting it as a generic startup failure.

Details
  • Kept separate from the two existing outcomes: the session being held by another local process, and an unexplained empty result.
  • The refusal is logged and shown as a notice; it does not increment the failure counter used for ordinary connection failures.
  • What tells the client the policy denied it is decided outside the build.
Evidence

Remote Control is disabled by your organization's policy. Contact your organization admin for access., Init declined by org policy; leaving Remote Control off

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