Requirements

Before using Remote Control, confirm that your environment meets these conditions:

• Subscription: available on Pro, Max, Team, and Enterprise plans. API keys are not supported. On Team and Enterprise, an Owner must first enable the Remote Control toggle in Claude Code admin settings.
• Authentication: run claude and use /login to sign in through claude.ai if you haven't already. Without an eligible login, claude remote-control exits with an error, while claude --remote-control still starts an interactive session and shows a Remote Control failure notification shortly after launch.
• API endpoint: not available in any of these configurations:
  • You use Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry.
  • You point ANTHROPIC_BASE_URL at a host other than api.anthropic.com, such as an LLM gateway or proxy. Unset the variable to use Remote Control. Before v2.1.196, Claude Code allowed Remote Control with a custom ANTHROPIC_BASE_URL.
  • You sign in through an enterprise Claude apps gateway.
• Feature-flag evaluation: DISABLE_TELEMETRY, DO_NOT_TRACK, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, and DISABLE_GROWTHBOOK each disable the feature-flag evaluation that Remote Control availability depends on. Unset the variable wherever it's set, in your shell environment or in the env block of a settings.json file, to use Remote Control.
• Workspace trust: run claude in your project directory at least once to accept the workspace trust dialog. The startup trust dialog never saves trust for your home directory, so start Remote Control from a project directory.