[BUG] Remote Control returns "disabled by your organization's policy" on Team plan despite admin toggle being ON

Status Closed — not planned
Reported on v2.1.90
Maintainer reply None cached
Activity 14 comments · opened Apr 2, 2026 · closed Jun 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description

Remote Control fails with "disabled by your organization's policy" on a Team plan, even though:

  • The Remote Control toggle is enabled in admin settings (claude.ai/admin-settings/claude-code)
  • Authentication is via OAuth (claude.ai), not API key
  • Managed settings (settings.json) contains only {"channelsEnabled": true}
  • No telemetry-disabling environment variables are set

Both claude --remote-control and the /remote-control slash command produce the same error.

Environment

  • Claude Code version: v2.1.90
  • Plan: Team
  • Auth method: OAuth / claude.ai
  • OS: macOS (Darwin 25.4.0)
  • Shell: zsh

Steps to reproduce

  1. Confirm Remote Control toggle is ON in claude.ai/admin-settings/claude-code
  2. Run claude auth status — confirms authMethod: "claude.ai", subscriptionType: "team"
  3. Run claude --remote-control or /remote-control in a session
  4. Result: "Remote Control failed · disabled by your organization's policy"

Admin settings state

All toggles on the Claude Code admin page:

  • Code in the desktop: ON
  • Remote Control: ON
  • Claude Code analytics: ON
  • Allow channel notifications: ON
  • Code in the web: OFF
  • Allow bypass permissions mode: OFF
  • Allow auto permissions mode: OFF
  • Fast mode: OFF
  • GitHub analytics: OFF

Managed settings (settings.json): {"channelsEnabled": true}

Additional context

  • No CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC or DISABLE_TELEMETRY env vars set
  • Possibly related to #29685, #33327, #38272

What Should Happen?

The remote control should activate successfully.

Error Messages/Logs

Remote control is disabled by your organization's policy.

Steps to Reproduce

See above.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.90

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

13 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/33327
  2. https://github.com/anthropics/claude-code/issues/37608
  3. https://github.com/anthropics/claude-code/issues/33182

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

dholowack · 5 months ago

This was working for the past few weeks but suddenly stopped working a few days ago.

krzakov · 4 months ago

I have the same issue in "Team" license. Org switch toggled, oauth auth, no stale session, newest Claude Code cli version, same error every time: "Remote Control is disabled by your organization's policy." - looks like anthropic bug

Shahid-Fahad · 4 months ago

I am also facing the same issue.

SerhiiMaksymiv · 4 months ago

same issue

elopezdata · 4 months ago

same issue

rtheil-growlink · 4 months ago

I had this same issue.

My solution was to log in with claude /login. Yes, our org had the option disabled, but once I authenticated everything started working fine.

arifulislamat · 4 months ago

I am facing same issue in our team plan for our organization.

SumitPopat · 3 months ago

Facing the same issue in my team plan. Claude Code version 2.1.126.

joecrop · 3 months ago

TLDR: Reboot VSCode

This was fixed for me by doing the following:

  1. Update team settings in claud code web UI to enable remote control.
  2. VSCode -> Developer: Reload Window
  3. In Claud Code extension enter the command: /remote-control
khaledalarja · 3 months ago

i managed to fix the issue,
tldr, even tho you can have a max plan with your personal user, but if you had a pay-per-use before with your organization then it's so probable that Claude Code can be authenticated to that old organization pay-per-use settings,

i have prompted /update-config to debug the issue, and asked him literally "please understand that when i activate it using /remote-control it gives me error "Remote Control failed to connect: disabled by your organization's policy" ", and he will give you the commands to correct the local settings to use your max plan login details and not your organization details

tbertini · 3 months ago

What fixed it for me

The following file had these settings:

~/.claude/policy-limits.json (on macOS/Linux):

{
  "restrictions": {
    "allow_remote_control": { "allowed": false },
    "allow_quick_web_setup": { "allowed": false }
  }
}
Step by step
  1. Change ~/.claude/policy-limits.json to:

``json
{
"restrictions": {
"allow_remote_control": { "allowed": true },
"allow_quick_web_setup": { "allowed": true }
}
}
``

  1. Fully restart Claude Code
  2. Run /remote-control.
github-actions[bot] · 2 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

Showing cached comments. Read the full discussion on GitHub ↗