/remote-control fails silently with "remote control failed" — Cloudflare cf-mitigated: challenge blocking CLI connection

Resolved 💬 3 comments Opened Mar 5, 2026 by Jerry-712 Closed Mar 8, 2026

Description

The /remote-control (or /rc) command always fails with "remote control failed" after showing "Remote Control connecting…". No QR code is displayed and no additional error information is provided.

Environment

  • OS: macOS (Darwin 25.3.0)
  • Terminal: macOS built-in Terminal.app
  • Claude Code version: Latest
  • Auth status: Logged in via claude.ai, Pro subscription
  • Network: VPN (proxy mode), reachable to claude.ai

Steps to Reproduce

  1. Run /remote-control or /rc in Claude Code
  2. See "Remote Control connecting…"
  3. See "remote control failed" — no QR code, no URL, no additional output

Investigation

Running curl -I https://claude.ai through the same network confirms connectivity, but Cloudflare returns:

HTTP/2 403
cf-mitigated: challenge

This indicates Cloudflare is applying a JS Challenge to non-browser requests. The Claude Code CLI cannot complete this challenge, causing the remote control connection to fail silently.

Browsers can pass the JS challenge and access claude.ai normally, but the CLI cannot.

Expected Behavior

  • Either display a QR code / URL for remote control
  • Or provide a meaningful error message explaining the connection failure

Suggested Fix

  • Use an API endpoint for remote control that bypasses Cloudflare's browser-only JS challenge (e.g., an api.claude.ai or api.anthropic.com subdomain)
  • Or improve error messaging to indicate the specific connection failure reason

View original on GitHub ↗

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