claude-code - 💡(How to fix) Fix Remote Control feature unavailable on Max plan — slash command missing, --remote-control silently ignored, /feedback also fails [1 comments, 2 participants]

Preflight Checklist

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

What's Wrong?

Description

On a Max plan (primary owner, paid personally), the Remote Control feature is completely missing from Claude Code despite meeting all documented requirements. The /feedback slash command also fails, suggesting a shared backend feature-flag issue affecting "non-essential traffic" features on this account.

Expected behavior

• /remote-control should appear in the slash-command autocomplete
• claude --remote-control should start a session that prints a connection URL / QR code
• /feedback should accept bug reports

Actual behavior

• /remote-control does not appear in autocomplete — only /remote-env shows up when typing /rem
• claude --remote-control silently starts a normal session with no URL, no QR code, no Remote Control indicator, even with --verbose
• /feedback fails to submit

Environment

• Plan: Claude Max (primary owner, paid personally)
• Email: [email protected]
• Organization ID: 18045e6a-c75b-48db-9b39-0973ce14770f
• Claude Code version: 2.1.112
• OS: Windows 11
• Authentication: Claude Max OAuth (confirmed via /status, no API key)

Troubleshooting already completed

• Upgraded to latest Claude Code version (v2.1.112)
• Full /logout and OAuth re-login with Claude Max account
• Verified /status shows "Login method: Claude Max Account"
• Confirmed no relevant environment variables are set (checked User, Machine, and Process scopes on Windows):
  • ANTHROPIC_API_KEY — not set
  • CLAUDE_CODE_OAUTH_TOKEN — not set
  • CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC — not set
  • DISABLE_TELEMETRY — not set
  • CLAUDE_CODE_ORGANIZATION_UUID — not set
• /admin-settings/claude-code page redirects to /settings/general (expected for Max, per support)
• No admin toggle exists in user settings, org settings, or Claude Console for Remote Control

Support chat outcome

Support chat (Fin AI Agent) confirmed:

• ZDR does not apply to Max plans, so ZDR is ruled out
• No admin toggle is expected for Max
• This is likely "a backend rollout / feature-flag issue"
• The chat cannot escalate server-side feature flags and loops when human handoff is requested

Request

Please enable the Remote Control feature flag server-side for organization 18045e6a-c75b-48db-9b39-0973ce14770f, or clarify why this Max account is being excluded from the rollout.

What Should Happen?

As a Claude Max subscriber meeting all documented requirements for Remote Control, the feature should be available:

1. /remote-control should appear in the slash-command autocomplete inside Claude Code sessions
2. Running claude --remote-control from the command line should establish a Remote Control session and display a connection URL and/or QR code so the session can be continued from claude.ai/code or the Claude mobile app
3. /feedback should work for submitting bug reports from within Claude Code

Per Anthropic's official documentation (https://code.claude.com/docs/en/remote-control), Remote Control is available on Pro and Max plans without any admin toggle or manual enablement required — it is only admin-gated on Team and Enterprise plans. Anthropic support has confirmed this is the expected behavior for Max subscribers.

Error Messages/Logs

Steps to Reproduce

1. Ensure Claude Code v2.1.112 is installed on Windows 11
2. Authenticate with a Claude Max account that belongs to an organization where you are the primary owner. Verify with /status — should show "Login method: Claude Max Account"
3. Verify no relevant environment variables are set in any scope (User, Machine, Process):
   • ANTHROPIC_API_KEY
   • CLAUDE_CODE_OAUTH_TOKEN
   • CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
   • DISABLE_TELEMETRY
   • CLAUDE_CODE_ORGANIZATION_UUID
4. Open PowerShell and run: claude
5. Inside the Claude Code session, type /rem to trigger slash-command autocomplete
   • Expected: /remote-control appears in the list
   • Actual: Only /remote-env appears; /remote-control is missing entirely
6. Exit the session with /exit
7. In PowerShell, run: claude --remote-control
   • Expected: Session starts and displays a connection URL and/or QR code for mobile/web access
   • Actual: A normal Claude Code session starts silently; no URL, no QR code, no Remote Control indicator anywhere
8. Try with verbose mode: claude --remote-control --verbose
   • Actual: No additional output related to Remote Control is shown; the flag appears to be silently ignored
9. Inside the session, try /feedback to report the bug through the built-in channel
   • Actual: /feedback also fails, suggesting a shared backend feature-flag issue affecting multiple "non-essential traffic" features on this account

Additional context: Attempting to access https://claude.ai/admin-settings/claude-code (the documented admin toggle location) redirects to https://claude.ai/settings/general. Per Anthropic support chat, this redirect is expected for Max plans, because the admin toggle only exists on Team/Enterprise. Support also confirmed ZDR does not apply to Max and is not the cause.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.112

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response