[DOCS] Remote Control troubleshooting missing trusted-device unenrolled failure

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/remote-control

Section/Topic

Troubleshooting section for /remote-control connection failures

Current Documentation

The Remote Control troubleshooting section currently lists subscription, token, eligibility, policy, and credential-fetch failures:

### "Remote Control requires a claude.ai subscription" You're not authenticated with a claude.ai account. Run claude auth login and choose the claude.ai option. If ANTHROPIC_API_KEY is set in your environment, unset it first.

It also covers credential-fetch failures:

### "Remote credentials fetch failed" Claude Code could not obtain a short-lived credential from the Anthropic API to establish the connection. Re-run with --verbose to see the full error:

The page does not mention trusted-device enrollment, unenrolled trusted-device failures, or what a user should do when /remote-control fails before connecting because the current device is not trusted.

What's Wrong or Missing?

Claude Code v2.1.126 changed /remote-control behavior so unenrolled trusted-device failures are caught up-front instead of appearing as repeated "connecting..." retries. The Remote Control docs already have a Troubleshooting section for connection startup failures, but they do not document this newly surfaced failure mode.

Users who see the up-front trusted-device error have no documented recovery path on the Remote Control page. The nearest entries cover claude.ai login, full-scope login tokens, organization eligibility, policy disablement, and generic remote credential fetch failures, but none explain trusted-device enrollment or how to resolve an unenrolled device state.

Suggested Improvement

Add a troubleshooting entry to the Remote Control page for the trusted-device/unenrolled-device failure shown by /remote-control.

Suggested placement: near the other startup failures in the Troubleshooting section, before or after "Remote credentials fetch failed".

Suggested content:

"Trusted device enrollment required"

Claude Code could not start Remote Control because this machine is not enrolled as a trusted device for your claude.ai account or organization. Sign in again with /login or claude auth login using your claude.ai account, complete any trusted-device or device-verification prompts, then retry /remote-control or claude remote-control.

If you are on a Team or Enterprise plan, confirm that your organization allows Remote Control and that your account/device meets any organization-level trusted-device requirements.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/remote-control | 195-236 | Troubleshooting covers Remote Control subscription, full-scope token, eligibility, policy, and credential-fetch failures, but not trusted-device enrollment failures. |
| https://code.claude.com/docs/en/changelog | 42 | v2.1.126 release note says /remote-control now catches unenrolled trusted-device failures up-front. |

Total scope: 1 primary page affected