[BUG] `claude remote-control` shows misleading "Contact your administrator" error for personal (Pro/Max) accounts

@claude Please assist the anthropic team to resolve this ASAP.

Hitting the same error on macOS (v2.1.51, personal account).

Through binary analysis of the CLI, the root cause is a GrowthBook feature flag called tengu_ccr_bridge that defaults to false:

function isBridgeEnabled() { return R9("tengu_ccr_bridge", false) }
function R9(key, defaultVal) {
  let val = settings.cachedGrowthBookFeatures?.[key];
  return val !== undefined ? val : defaultVal;
}

The flag is evaluated server-side and cached locally — there is no local override path. The remoteControlAtStartup setting also gates on this flag before attempting to start the bridge, so even setting it manually in settings.json just produces the same error on every session start.

This suggests the feature _can_ be enabled per-account (it's a flag flip, not a code path that's missing), but it's unclear whether it's intentionally restricted to a specific plan tier or just not yet rolled out broadly. Clarification on which plans/tiers have tengu_ccr_bridge enabled would help resolve the ambiguity in the changelog ("for all users").

Keen to use this, same error about contact administrator

Same here

@claude indeed, would love to finish working between office and home!

In the meantime you could try https://yepanywhere.com/ which would let your easily resume work from your phone or another laptop etc.

https://yepanywhere.com/claude-code-remote-control.html

+1

Same issue here. Max plan, macOS. claude remote-control returns "Remote Control is not enabled for your account."

Same issue here.. I tried claude remote-control and got the same error: "Remote Control is not enabled for your account."

after log out and log in started to work for me

@margusre123 that works 💯

This is further than I got. I am using the latest native install (v2.1.52) but keep getting Unknown skill: remote-control. I tried /login to re-authenticate and it did not make a difference.

Do I need to configure claude, install from npm or build from source?

This is further than I got. I am using the latest native install (v2.1.52) but keep getting Unknown skill: remote-control. I tried /login to re-authenticate and it did not make a difference. Do I need to configure claude, install from npm or build from source?

Same issue here, Max plan, macOS, native v2.1.52. Re-authentication didn't help either. Looks like a server-side rollout issue...

I got it working by Starting the CLI first then doing /rc command.

<img width="1491" height="512" alt="Image" src="https://github.com/user-attachments/assets/e236b4d2-4d53-480b-96b6-37bc73403f5c" />

after log out and log in started to work for me

This worked for me as well. Sign out, then back in on CLI and run /remote-control

Error exists on 2.1.53 as well.

All good now. I guess just needed to be more patient. :)

_Yep, no luck resetting oauth._

Error exists on 2.1.53 as well.

+1

after log out and log in started to work for me

I’ve already logged out of Claude and then logged back in using /login, but it still shows:

claude remote-control
Error: Remote Control is not enabled for your account. Contact your administrator.

This worked for me as well.

Do you have a personal Max or Teams account?

> This worked for me as well. Do you have a personal Max or Teams account?

yes Max

<img width="910" height="232" alt="Image" src="https://github.com/user-attachments/assets/a2b3972b-d62d-4392-8d39-28ac8fc95eae" />

> > This worked for me as well. > > > Do you have a personal Max or Teams account? yes Max <img alt="Image" width="910" height="232" src="https://private-user-images.githubusercontent.com/205518630/554477286-a2b3972b-d62d-4392-8d39-28ac8fc95eae.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzE5ODUwODAsIm5iZiI6MTc3MTk4NDc4MCwicGF0aCI6Ii8yMDU1MTg2MzAvNTU0NDc3Mjg2LWEyYjM5NzJiLWQ2MmQtNDM5Mi04ZDM5LTI4YWM4ZmM5NWVhZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIyNVQwMTU5NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZDQyMzBhNjFlYTg1M2ZkMDRkMDEwOGVhNDcyOGNjNzMyM2FlOTg0NzQyY2RlZGMzMjAxOTJhMDhlNzhjMmI3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.vWOcBGD5dPhuQ6ONf4m6wfPZ-ZsMLiV2QKFMwO5mvO0">

I think the feature is rolling out gradually. It now works for me, and it didn't yesterday. I logged out of my session, logged back in, and /remote-control was available. I'd just be patient.

EDIT: The other thing that occurred to me is that it doesn't work on an existing session I have. I definitely had to jump into a new session, log out, log in, and then run /remote-control.

I will also be honest, it's pretty simple right now, but I'm looking forward to seeing future versions (of itself I guess?).

> > > This worked for me as well. > > > > > > Do you have a personal Max or Teams account? > > > yes Max > <img alt="Image" width="910" height="232" src="https://private-user-images.githubusercontent.com/205518630/554477286-a2b3972b-d62d-4392-8d39-28ac8fc95eae.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzE5ODUwODAsIm5iZiI6MTc3MTk4NDc4MCwicGF0aCI6Ii8yMDU1MTg2MzAvNTU0NDc3Mjg2LWEyYjM5NzJiLWQ2MmQtNDM5Mi04ZDM5LTI4YWM4ZmM5NWVhZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwMjI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDIyNVQwMTU5NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZDQyMzBhNjFlYTg1M2ZkMDRkMDEwOGVhNDcyOGNjNzMyM2FlOTg0NzQyY2RlZGMzMjAxOTJhMDhlNzhjMmI3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.vWOcBGD5dPhuQ6ONf4m6wfPZ-ZsMLiV2QKFMwO5mvO0"> I think the feature is rolling out gradually. It now works for me, and it didn't yesterday. I logged out of my session, logged back in, and /remote-control was available. I'd just be patient. EDIT: The other thing that occurred to me is that it doesn't work on an existing session I have. I definitely had to jump into a new session, log out, log in, and then run /remote-control. I will also be honest, it's pretty simple right now, but I'm looking forward to seeing future versions (of itself I guess?).

Guess what? I’ve got some good news — I can finally use it now!

Are there any workarounds for it?

Logout and login doesn't work, reinstalling Claude also doesn't work.

Are there any workarounds for it? Logout and login doesn't work, reinstalling Claude also doesn't work.

Nah, just be patient or use https://sessioncast.io or one of the other suggestions above, which are a bit more feature-rich in any event.

Setting DISABLE_TELEMETRY=1 causes claude remote-control to fail with "Remote Control is not enabled for your account."

Unsetting it fixes it: DISABLE_TELEMETRY= claude remote-control

Same root cause as #27939.

+1

Same issue on v2.1.55

Same issue on v2.1.55, Rocky Linux, Max Plan

Correct method:

1. Start Claude in the directory of a code repository.
2. In a new terminal window, enter claude remote-control.
3. I’ve developed a new website that lets you quickly access Twitter data through an API. If you’re interested, feel free to give it a try. （https://xapis.dev）

Same on version 2.1.56:

Claude Code is up to date (2.1.56)
claude remote-control
Error: Remote Control is not enabled for your account. Contact your administrator.

Same on version 2.1.56

Fixed after updating to v2.1.55. /remote-control now works inside the session.

logout and login back make it work

Same issue on version 2.1.56, Pro plan, Mac OS 26.2

• logout and login not working

Same here, 2.1.56, Windows 98, Ultra subscription

Same issue in 2.1.56, still not working. Logout and login doesn't work.

I'm on Claude Max 5x plan.

<img width="1034" height="725" alt="Image" src="https://github.com/user-attachments/assets/495af480-c099-442b-b7c8-eb66f7f8ef6a" />

people on different versions got this issue and some then got it working after logging out and logging back in, feels like it's being rolled out progressively.

It doesn't work for me on 2.1.56 as well sadly.

worked for me
enable telemetry and nonessential traffic

jq 'del(.env.CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC)' ~/.claude/settings.json > /tmp/settings_tmp.json && mv /tmp/settings_tmp.json ~/.claude/settings.json
jq 'del(.env.DISABLE_TELEMETRY)' ~/.claude/settings.json > /tmp/settings_tmp.json && mv /tmp/settings_tmp.json ~/.claude/settings.json

Not working for me either on 2.1.56 and Max x20

Does not work for me (Max plan) in version 2.1.56 even with DISABLE_TELEMETRY: 0 (or not present). I just did that for testing though, users shouldn't have to enable telemetry to use remote-control, why would statsig have anything to do with remote-control?

Same issue, 2.1.56, Pro plan, Mac OS 26.2

Having the same issue myself. Macbook Pro 2024 - M3 Tahoe 26.2. Ran through terminal via VS Code.

you need to do a /logout and relaunch claude again to make it work

you need to do a /logout and relaunch claude again to make it work

logout and relogin didn't seem to affect the error for me

> you need to do a /logout and relaunch claude again to make it work logout and relogin didn't seem to affect the error for me

https://github.com/anthropics/claude-code/issues/28098#issuecomment-3957015449

Having the same issue myself. Macbook Pro 2024 - M3 Tahoe 26.2. Ran through terminal via VS Code.

https://github.com/anthropics/claude-code/issues/28098#issuecomment-3957015449

Yep. Same issue. Max plan, no dice, tried contacting my administrator (me), didn't help.

Not going to play the login/logout game.

This is a very silly solution but to get this working for me I had to go to https://claude.ai/settings/data-privacy-controls and enable "Help improve Claude". Then running claude remote-control worked as expected.

Funnily enough I then disabled the "Help improve Claude" toggle and it kept working.

I'm a max user. still having the issue. Tried login/logout and toggling "Help improve claude" a few times.

Seemed to work at first, blocked again after a while.

Same issue here — Max plan (20x), v2.1.56, macOS.

Error: Remote Control is not enabled for your account. Contact your administrator.

Diagnostics:

• Plan: max_20x (confirmed in ~/.claude/usage-limits.json)
• Auth: OAuth via claude.ai (not API key), token valid
• Account: personal Gmail (not Team or Enterprise)
• No ANTHROPIC_API_KEY in environment or shell profiles
• Tried claude auth logout → claude auth login to refresh token — same error

Happy to share any additional diagnostics if helpful.

I'm still having the exact same issues as @aaronnam here.

More details:

• Claude Max plan (5x), via Claude.ai, personal account
• using Macbook Air M2 (macOS Tahoe 26.3)
• Claude Code CLI v2.1.56
• Tried logout and login, didn't work

stilll same issue anthropic?????

Same, having a MAX plan

Had this issue, logout, login resolved it.
New issue now. Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url session_01VTQ.....

Hi
I am having the same issue in Ubuntu with pro plan
best,

Tried all steps above.. I am having the same issue.

Same issue in Ubuntu Linux with Max plan

Same here, using Max plan on a mac mini m4... would it be because I use a google workspace account connected to the Max plan??? ok so... had to logout everywhere and then log back in and did what was mentioned above, seems to have worked. (go to https://claude.ai/settings/data-privacy-controls and enable "Help improve Claude". )

Same issue. Restarted computer, did logout/login multiple times, no success. Latest version. Works fine on VPS with same subscription, but not my macbook. Also noticed with previous claude updates I dont get the new features in the latest versions right away.

Reproduces on macOS (darwin arm64), Claude Code v2.1.56, personal Max account. Running ~/.local/bin/claude remote-control returns: Error: Remote Control is not enabled for your account. Contact your administrator. — same error as reported. No workaround found.

worked for me enable telemetry and nonessential traffic jq 'del(.env.CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC)' ~/.claude/settings.json > /tmp/settings_tmp.json && mv /tmp/settings_tmp.json ~/.claude/settings.json jq 'del(.env.DISABLE_TELEMETRY)' ~/.claude/settings.json > /tmp/settings_tmp.json && mv /tmp/settings_tmp.json ~/.claude/settings.json

This was the workaround for me. Remove telemetry blockers in ~/.claude/settings.json file.

Same issue, Max plan on MacOS 🤭

+1 obviates my existing tailscale / termius setup - would love if it actually worked though!

+1

+1

Same with Max plan and wsl Ubuntu

+1

+1

+1

I got it working by removing "CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": 1 from my ~/.claude/settings.json, then logging out, then logging back in.

Thanks folks, appreciate the reports. The team is aware of the issue and is working on a fix.

This should be resolved in tomorrow's release: the expected behavior is that this is not available to Pro/Max subscribers at the moment, and the error message will reflect that.

This was fixed in v2.1.59 — claude remote-control now shows 'not yet available on your plan' for Pro/Max accounts instead of the misleading 'Contact your administrator'. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.