"Remote Control environments are not available for your account": how to fix it

You run claude remote-control, answer y, and get one line back:

Remote Control environments are not available for your account.

No link, no QR code, and the next run skips the question and prints the same thing. Here is what it means and how to get past it.

The short answer

Claude Code asked Anthropic whether your account can run Remote Control, and the answer was no. The cause is almost always on your side of the check, not a broken install. Work through this list in order:

1. You're signed in with something other than a claude.ai login (an API key, a CLAUDE_CODE_OAUTH_TOKEN, Bedrock or a proxy).
2. Your plan, or the organization your login belongs to, doesn't have Remote Control turned on. On Team and Enterprise an Owner has to switch it on.
3. An environment variable is turning off the feature-flag check (DISABLE_TELEMETRY, DO_NOT_TRACK, DISABLE_GROWTHBOOK, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC).
4. Your cached account info is out of date, usually after a plan change.
5. Your Claude Code version is old.

The fastest single check is claude doctor. It prints a Remote Control eligibility line that names the check that failed.

Who sees this message

This exact string comes from server mode, claude remote-control. It isn't in the error list on Anthropic's Remote Control page, but its documented cousin "Remote Control isn't enabled for this account" has the same fixes. Older versions said "Remote Control is not yet enabled for your account" or "Contact your administrator" for the same states.

You're not alone. #29449 is a Pro user hitting this exact message on v2.1.62 on a Mac, with dozens of "same here" replies from Mac, Windows and WSL. #29980 is the same message on Windows 11 in PowerShell, also on Pro. #29580 shows DISABLE_TELEMETRY=1 alone turning Remote Control off on an eligible account.

Step 1: check what you're signed in with

Remote Control needs a claude.ai subscription login: Pro, Max, Team or Enterprise. The docs are direct about it: "API keys are not supported."

claude auth status --text

Then, inside a session, run /status and look at the plan and organization. Three things to look for:

• An API key or auth token. If ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN is set, these win over your login. Remove them from your shell profile and from the env block of any settings.json.
• A long-lived token. If CLAUDE_CODE_OAUTH_TOKEN is set, that's the long-lived token from claude setup-token. It can only make model requests, so it "can't establish Remote Control sessions." One commenter on #29449 found theirs in a project .env file loaded by autoenv. Unset it.
• Bedrock, Vertex, Foundry or a proxy. That includes a custom ANTHROPIC_BASE_URL. Remote Control only works when Claude Code talks to api.anthropic.com directly.

Quick way to find stray variables:

env | grep -E 'ANTHROPIC|CLAUDE_CODE|DISABLE_|DO_NOT_TRACK'

Step 2: check your plan and organization

Remote Control is available on Pro, Max, Team and Enterprise. Two traps:

• Team or Enterprise: Remote Control is off by default. An Owner of the organization has to turn on the Remote Control toggle at claude.ai/admin-settings/claude-code. Until then nobody in the org can use it, however they sign in. On Enterprise with custom roles, your role also needs the cloud sessions permission and the "Claude Code remote control" permission.
• You're on Pro or Max now, but Claude Code still remembers an old Team login. It then checks that organization's policy instead of yours. /status shows which organization is in use.

Organizations with Zero Data Retention or the HIPAA configuration can't turn Remote Control on at all.

Step 3: unset the variables that turn off flag checks

Remote Control availability is decided by a feature flag, and some privacy variables stop Claude Code from fetching flags. Per the Remote Control docs:

• CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC or DISABLE_GROWTHBOOK: Remote Control is unavailable while either is set.
• DISABLE_TELEMETRY or DO_NOT_TRACK: fine on Claude Code v2.1.283 or later (v2.1.304 or later in the Desktop app), unless your org requires Trusted Devices. On older versions they block it.

unset DISABLE_TELEMETRY DO_NOT_TRACK DISABLE_GROWTHBOOK CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
claude remote-control

If that works, find where the variable is set (~/.zshrc, ~/.bashrc, a settings.json env block) and remove it there for good.

Step 4: refresh your login and update

Cached entitlements go stale, especially right after you upgrade or change plans. Sign out and in again, then update:

claude auth logout
claude auth login
claude update
claude doctor

Choose the claude.ai option at login, not the Console one. If claude doctor now shows Remote Control as eligible, run claude remote-control again.

Step 5: try the in-session command

A few people in #29449 found that server mode kept failing while the in-session command worked. Start a normal session and turn it on from inside:

claude
/remote-control

If this works and claude remote-control doesn't, you can still use Remote Control today. Note the version and post it on the issue, since that difference is useful to Anthropic.

How to confirm it's fixed

• claude remote-control prints a session link, and pressing space shows a QR code.
• In the Claude app, under Code, the session shows a computer icon with a green dot.
• In an interactive session you see /rc active in the footer.

If you've done all five steps, claude doctor says eligible and it still fails, it's account-side. Add your version and claude doctor output to #29449.

Related fixes

• Claude Code Remote Control keeps disconnecting: once it connects, keeping it connected.
• Claude Code login on a headless server: signing in on a box with no browser, without breaking Remote Control.
• Running Claude Code on a server: the full always-on setup.

If you'd rather not keep a machine awake

Remote Control is a window into a claude process on some computer, so that computer has to stay on. Podway is an always-on cloud computer for Claude Code. You sign in with your own Pro or Max plan and open the session from the Claude app via Remote Control. On Team or Enterprise, your org Owner still has to enable Remote Control first; Podway can't skip that check. If the agent crashes, Podway restarts it and reconnects Remote Control, and before your Claude login expires it tells you, with a one-click reconnect.

Your first pod is free, no card needed, and pods start at $4/month. Start a pod, or read more on the agent computer page.