[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. Runclaude auth loginand choose the claude.ai option. IfANTHROPIC_API_KEYis 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
4 Comments
Still relevant as of 2026-05-18. This documentation gap has not been addressed in the docs yet.
Verified against the latest docs; this still appears unresolved.
Issue #55196 Verification
Title: [DOCS] Remote Control troubleshooting missing trusted-device unenrolled failure
Issue Date: 2026-05-01
Verification Date: 2026-06-27
Status: RESOLVED
---
Issue Summary
The issue reports that the Remote Control troubleshooting section does not include an entry for the unenrolled trusted-device failure that Claude Code v2.1.126 began surfacing up-front (instead of as repeated "connecting..." retries). The reporter asks for a new troubleshooting entry, suggested title "Trusted device enrollment required", placed near the other startup failures such as "Remote credentials fetch failed", explaining how to recover via
/loginand noting any Team/Enterprise caveats.---
Verification Results
Claim 1: The Remote Control troubleshooting section lacks a trusted-device / unenrolled-device entry.
Status: RESOLVED
The current Remote Control troubleshooting section includes an entry that matches the request. At https://code.claude.com/docs/en/remote-control, line 306:
The entry is placed exactly where the issue suggested, immediately after the "Remote credentials fetch failed" entry (line 292). It uses the recovery path (
/loginin Claude Code) and notes that enrollment happens as part of sign-in, which is the substantive guidance the issue asked for.Verdict: The missing entry the issue reported has been added to the troubleshooting section, and the wording matches the suggested content (recovery via
/login, enrollment happens as part of sign-in, no separate enrollment command).---
Claim 2: There is no documented recovery path for users who hit the up-front trusted-device error.
Status: RESOLVED
The Trusted Devices concept is now explained in the same page. At https://code.claude.com/docs/en/remote-control, line 163:
The page also documents unenrolled-device behavior at line 194:
And it provides a per-device management entry point at line 202:
A complementary troubleshooting entry, "session expired for trusted-device check", also exists at line 310:
Verdict: Users who hit the unenrolled-device failure now have a clear recovery path: run
/loginso enrollment happens during sign-in. The page also explains what Trusted Devices are, what unenrolled devices can and cannot do, and where to manage enrolled devices.---
Claim 3: The issue was filed against Claude Code v2.1.126 behavior change.
Status: RESOLVED
The changelog no longer lists this as a separate v2.1.126 line item — the trusted-device / Remote Control improvement has been folded into the user-facing documentation. The current Remote Control page treats the failure as a documented troubleshooting path rather than calling out the v2.1.126 catch-up-front change. The
changelogdoes still mention a later related fix at line 940:Verdict: The user's request — to surface the unenrolled trusted-device failure in the Remote Control troubleshooting section — is satisfied by the current docs. The failure mode is now documented in the place users will actually look for it.
---
Current State
| Claim | Status |
|-------|--------|
| Troubleshooting entry for trusted-device / unenrolled failure missing | RESOLVED |
| No documented recovery path for the up-front trusted-device error | RESOLVED |
| v2.1.126 behavior change referenced as missing | RESOLVED |
---
Suggested Fix
N/A — issue has been resolved. The Remote Control page now contains a dedicated troubleshooting entry at https://code.claude.com/docs/en/remote-control (line 306) that documents the unenrolled trusted-device failure and points users to
/loginto enroll during sign-in. A complementary entry for the related "session expired for trusted-device check" case is included at line 310.---
References
"Your organization requires Trusted Devices for Remote Control, but this device is not enrolled"entry that addresses the issue."session expired for trusted-device check"entry.Manage enrolled devicessection./login".---
Conclusion & Recommendation
Primary Concern: The Remote Control troubleshooting section did not include an entry for the unenrolled trusted-device failure introduced in v2.1.126, so affected users had no documented recovery path on the page.
Resolution Status: RESOLVED
Recommendation: CLOSE
The exact troubleshooting entry the issue asked for — placed near the other startup failures and explaining the
/loginrecovery path — is now present in the current docs.This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.