claude-code - 💡(How to fix) Fix [BUG] /remote-control slash command not registered for Max account — server-side disableRemoteControl flag suspected [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#57770Fetched 2026-05-11 03:25:52
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Root Cause

/remote-control is not available in Claude Code on a Max account that meets all documented requirements. The Mobile app's Code section is functional but no session can be registered, because the slash command is missing entirely on the desktop side.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this is distinct (closest match: #29796 reports "Unknown skill: remote-control"; this issue reports the command is not registered at all)
  • This is a single bug report
  • I am using the latest version of Claude Code

What's Wrong?

/remote-control is not available in Claude Code on a Max account that meets all documented requirements. The Mobile app's Code section is functional but no session can be registered, because the slash command is missing entirely on the desktop side.

The string /remote-control exists in the Claude Code binary, but the command is not registered for this account at runtime — it does not appear in /help autocomplete and returns "command not found" when invoked.

Anthropic Support's Fin AI agent confirmed via email that the most likely cause is that disableRemoteControl is set at the account/org level server-side and that resolution requires Anthropic to remove the flag. Multiple requests for human escalation in the support thread have looped back to automated responses.

Filing here in the hope that maintainers with account-config access can either resolve directly or route to the right internal team.

Account / Subscription

  • Subscription: Max
  • Auth method: claude.ai OAuth (apiProvider: firstParty, no API key set)
  • Org ID (partial, full available on request): 3b3cd989-…
  • Account email and full org ID can be shared privately with maintainers — not posting full PII in a public issue

Environment

  • Claude Code version: 2.1.138 (latest stable)
  • Platform: macOS 15 (Darwin 24.5.0)
  • Install: native install only (npm-global previously removed)

Symptom

  • Mobile app → Code shows the standard empty state asking the user to run /remote-control from Claude Code to register a session
  • Running /remote-control in any Claude Code session returns "command not found" (not "Unknown skill" — distinct from #29796)
  • The slash command does not appear in /help autocomplete
  • The string /remote-control exists in the Claude Code binary, but the command is not registered at runtime for this account

Troubleshooting Already Performed (over several months)

  • Many claude auth logout / claude auth login cycles
  • claude update to latest stable and claude install latest for the bleeding-edge channel — no change
  • Removed leftover npm-global installation; only native install remains
  • Confirmed ANTHROPIC_API_KEY is not set in the environment
  • Confirmed CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC and DISABLE_TELEMETRY env vars are unset (per fix in #29796 comments)
  • Confirmed claude.ai OAuth login is active
  • Other Max users have the feature working with the same setup, so this appears to be account- or org-specific gating

What Should Happen?

/remote-control should be available on a Max account with claude.ai OAuth, allowing a session to be registered with the mobile app.

Existing Support Conversation IDs

For maintainer reference (Trust & Safety / account-config can look these up):

  • 215474242200631
  • 215474242232169
  • 215474242262431

The Fin AI agent in those threads explicitly identified disableRemoteControl as the suspected gate and acknowledged that human-engineer access is needed to remove it.

Request

If this is a remediable account-config flag, please remove it for the org above and we will verify with /remote-control and report back. Happy to provide additional diagnostic output, debug logs, or run specific commands.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] /remote-control slash command not registered for Max account — server-side disableRemoteControl flag suspected [1 comments, 2 participants]