Remote Control not enabled for Max plan account

Resolved 💬 10 comments Opened Mar 3, 2026 by successldlgo-del Closed Jun 23, 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?

Running claude remote-control returns:

Error: Remote Control is not yet enabled for your account.

According to the official documentation at https://code.claude.com/docs/en/remote-control, this feature should be available for Max subscribers.

I have re-authenticated using /login (selected option 1: Claude account with subscription) and confirmed my account is on the Max plan. /feedback also fails with "Could not submit feedback. Please try again later."

What Should Happen?

claude remote-control should work correctly for Max plan subscribers as documented at https://code.claude.com/docs/en/remote-control. The /feedback command should also be able to submit feedback successfully.

Error Messages/Logs

Error: Remote Control is not yet enabled for your account.

# /feedback also fails:
Could not submit feedback. Please try again later.

Steps to Reproduce

  1. Install Claude Code v2.1.63 via npm globally (npm install -g @anthropic-ai/claude-code)
  2. Run /login and select option 1 (Claude account with subscription - Max plan)
  3. Run /doctor — all checks pass, no issues found
  4. Run claude remote-control
  5. Observe error: "Error: Remote Control is not yet enabled for your account."
  6. Additionally, run /feedback — it fails with "Could not submit feedback. Please try again later."

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

  • Install method: npm-global
  • Login method: Claude subscription (option 1, Max plan)
  • /doctor reports all OK, no issues found
  • The issue also affects /feedback, which fails with "Could not submit feedback. Please try again later."

View original on GitHub ↗

This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗