Every error message Claude Code produces for Remote Control, what actually causes it, and how to clear it. Run /status to see your login method and subscription, and claude doctor to see which eligibility check failed. Those two answer most questions before you read any further.
Find your error
Every documented Remote Control error message, with its actual cause and fix. Type any part of what you saw and this narrows the list. The whole table is on this page, so the sections below still work if you would rather read them in order.
“Remote Control requires a claude.ai subscription”
You are 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. An API key cannot establish a Remote Control session.
Before v2.1.206, running /remote-control while signed out reported Unknown command: /remote-control instead of this message. If you are seeing the unknown-command error, you are on an older version and signed out.
“Remote Control requires a full-scope login token”
You are authenticated with a long-lived token from claude setup-token or the CLAUDE_CODE_OAUTH_TOKEN environment variable. These tokens can only make model requests, so they cannot establish Remote Control sessions. Run claude auth login to authenticate with a full-scope session token instead.
“Remote Control is not yet enabled for your account”
The rollout has not reached your account, or your cached entitlements are stale. If you recently changed plans, run claude auth logout then claude auth login to refresh them. claude doctor shows which check failed.
On versions before v2.1.154, a variable that disables feature-flag evaluation (such as DISABLE_TELEMETRY) produced this same message. If you are on an older build, check those variables too. See the feature-flag section below.
“Couldn’t verify Remote Control eligibility”
Claude Code could not reach the feature-flag service to check whether Remote Control is enabled for your account, usually because you are offline or a proxy is blocking the request. Retry once you have network access, or run claude doctor for details.
“Couldn’t verify your organization’s Remote Control policy” has the same cause and the same fix. Both messages were added in v2.1.178.
“Remote Control requires feature-flag evaluation”
One of these environment variables is set, and each one disables the feature-flag evaluation Remote Control depends on:
DISABLE_TELEMETRYDO_NOT_TRACKCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICDISABLE_GROWTHBOOK
The full message names which variable Claude Code found. Unset it wherever it is set: your shell environment, or the env block of a settings.json file. Project-level settings files are easy to forget here.
“Remote Control is only available when using Claude via api.anthropic.com”
The session is not talking to the Anthropic API directly, so there is no claude.ai backend to pair with. This happens on Amazon Bedrock, Google Cloud Agent Platform, and Microsoft Foundry.
From v2.1.196 it also happens when ANTHROPIC_BASE_URL points at a host other than api.anthropic.com (an LLM gateway or proxy), even if you signed in with claude.ai.
From v2.1.219 the message names what routed the session away, such as CLAUDE_CODE_USE_BEDROCK or a custom ANTHROPIC_BASE_URL. Unset the named variable, remove it from the env key in settings if you put it there, and restart. On older versions, check your environment yourself for CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_VERTEX, and ANTHROPIC_BASE_URL.
“Remote Control is disabled by your organization’s policy”
This one message has four distinct causes. Run /status first to see your login method and subscription.
| Cause | Fix |
|---|---|
| Authenticated with an API key or Console account | Remote Control requires claude.ai OAuth. Run /login and choose claude.ai. Unset ANTHROPIC_API_KEY if set. |
| An Owner has not enabled it for your organization | Remote Control is off by default on Team and Enterprise. An Owner turns on the Remote Control toggle in Claude Code admin settings. It is a server-side organization setting. |
| The admin toggle is greyed out | Your organization has a data-retention or compliance configuration incompatible with Remote Control. This cannot be changed from the admin panel. Contact Anthropic support. |
The error mentions disableRemoteControl | Your IT administrator disabled Remote Control on this device through managed settings, independent of the organization-wide toggle. |
“Remote credentials fetch failed”
Claude Code could not obtain a short-lived credential from the Anthropic API. Re-run with --verbose to see the full error:
claude remote-control --verboseCommon causes:
- Not signed in. Run
claudeand use/login. API key authentication is not supported. - Network or proxy issue. A firewall or proxy may be blocking the outbound HTTPS request. Remote Control needs access to the Anthropic API on port 443.
- Session creation failed. If you also see
Session creation failed — see debug log, the failure happened earlier in setup. Check that your subscription is active.
“Couldn’t reconnect to your Remote Control session”
When you resume with claude --resume or claude --continue, Claude Code tries to reconnect to the Remote Control session recorded in that conversation. This message means reconnection failed for a possibly temporary reason (a network interruption or server error), so Claude Code cannot confirm whether the remote session still exists.
Your local session keeps running without Remote Control. Run /remote-control to retry, or start Claude Code without --resume to create a new session.
Before v2.1.200, a reconnection failure silently created a new session instead, which left duplicate entries piling up in the session list at claude.ai/code.
Trusted Devices errors
“Your organization requires Trusted Devices for Remote Control, but this device is not enrolled”
Your organization has Trusted Devices enabled and this machine has not enrolled. Run /login in Claude Code. Enrollment happens as part of sign-in. There is no separate enrollment command.
“session expired for trusted-device check”
Your sign-in is more than 18 hours old. Run /login, or confirm with Face ID, Touch ID, Windows Hello, or a passkey when claude.ai or the mobile app prompts you.
Remote Control errors that are really teleport
--teleport connects through the same session infrastructure Remote Control uses, so pulling a cloud session into your terminal can fail with Remote Control wording even though you never started Remote Control. If you hit one of these while teleporting, the problem is cloud session access, not Remote Control.
Remote Control session expiredandAccess denied: the connection token is short-lived and scoped to your account. Run/loginlocally to refresh credentials, then reconnect, and confirm you are signed in to the account that owns the session.Remote Control may not be available for this organization: an Owner has not enabled cloud sessions for your organization. That is a separate setting from the Remote Control toggle covered on the Team and Enterprise page.
Full detail in Claude Code on the web.
Problems that are not error messages
The /rc active indicator disappeared
Two possibilities. Either the connection genuinely dropped, in which case a notification will say why and re-running /remote-control retries, or your terminal window is simply too narrow. Claude Code hides the indicator when it will not fit. Widen the window and check again before assuming a failure.
My session died while I was away
If your machine is awake but cannot reach the network for more than roughly ten minutes, the session times out and the process exits. Short interruptions like a laptop sleeping or a brief Wi-Fi drop reconnect automatically. For a longer outage you need to run claude remote-control again.
If you closed the terminal or quit VS Code, that also ends the session, because Remote Control is a local process. Use tmux or screen on machines you reach over SSH.
Remote Control disconnected when I started an ultraplan
This no longer applies. The Ultraplan research preview was removed in Claude Code v2.1.224, along with the /ultraplan command. Use plan mode or Claude Code on the web instead. On builds from before that release the conflict was real: both features occupied the claude.ai/code interface, so starting an ultraplan disconnected any active Remote Control session. If you are seeing this on a current build, something else is disconnecting you, so work through the errors above.
A slash command does nothing from my phone
Commands tied to the terminal interface, such as /plugin and /resume, are local-only whether or not you pass an argument. See the command reference for the full list of what works remotely.
Push notifications are not arriving
- If
/configshows No mobile registered, open the Claude app on your phone so it can refresh its push token. The warning clears the next time Remote Control connects. - On iOS, Focus modes and notification summaries can suppress or delay pushes. Check Settings, Notifications, Claude.
- On Android, aggressive battery optimization delays delivery. Exempt the Claude app from battery optimization.
- Claude Code deliberately skips push notifications while you are typing in or focused on the connected terminal.