claude-code - 💡(How to fix) Fix [BUG] /remote-control fails with "failed to connect: /login" on Pro account, desktop app v1.8555.2

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…

The /remote-control slash command consistently fails with "Remote Control failed to connect: /login" in the Claude Code desktop app for macOS, despite being signed in to an active Pro account.

Error Message

  1. Error appears: "Remote Control failed to connect: /login" Error: "Remote Control failed to connect: /login"
  • Re-authenticated via claude.ai in iPhone Safari, retried — same error error message referencing /login may be misleading

Error Messages/Logs

  1. Error appears: "Remote Control failed to connect: /login" Error: "Remote Control failed to connect: /login"
  • Re-authenticated via claude.ai in iPhone Safari, retried — same error error message referencing /login may be misleading

Root Cause

The /remote-control slash command consistently fails with "Remote Control failed to connect: /login" in the Claude Code desktop app for macOS, despite being signed in to an active Pro account.

RAW_BUFFERClick to expand / collapse

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?

Summary

The /remote-control slash command consistently fails with "Remote Control failed to connect: /login" in the Claude Code desktop app for macOS, despite being signed in to an active Pro account.

Environment

  • Claude Code desktop app for macOS
  • Version: 1.8555.2 (a476c3), build 2026-05-22T23:04:37.000Z
  • macOS Darwin 25.3.0
  • Account: Pro plan (active), signed in via claude.ai
  • ANTHROPIC_API_KEY: not set (shell or GUI launchctl env)

Steps to reproduce

  1. Open Claude Code desktop app (signed in to Pro)
  2. Start a new session
  3. Type /remote-control
  4. Error appears: "Remote Control failed to connect: /login"

Expected

A session URL and QR code for connecting from other devices.

Actual

Error: "Remote Control failed to connect: /login"

Troubleshooting attempted

  • Full quit (Cmd+Q) and relaunch
  • Sign out via Settings → Account, sign back in
  • Verified ANTHROPIC_API_KEY unset (shell + launchctl + no shell config files reference it)
  • Re-authenticated via claude.ai in iPhone Safari, retried — same error
  • Confirmed claude.ai/code works correctly in iPhone Safari, so account auth is functional end-to-end
  • /login and /status both return "isn't available in this environment" in the desktop app — they appear to be CLI-only, so the error message referencing /login may be misleading

Impact

Cannot connect MacBook session to iPhone Claude app as documented.

What Should Happen?

/login and /remote-control should work but instead i get errors saying "isn't available in this environment"

Error Messages/Logs

Steps to Reproduce

Summary

The /remote-control slash command consistently fails with "Remote Control failed to connect: /login" in the Claude Code desktop app for macOS, despite being signed in to an active Pro account.

Environment

  • Claude Code desktop app for macOS
  • Version: 1.8555.2 (a476c3), build 2026-05-22T23:04:37.000Z
  • macOS Darwin 25.3.0
  • Account: Pro plan (active), signed in via claude.ai
  • ANTHROPIC_API_KEY: not set (shell or GUI launchctl env)

Steps to reproduce

  1. Open Claude Code desktop app (signed in to Pro)
  2. Start a new session
  3. Type /remote-control
  4. Error appears: "Remote Control failed to connect: /login"

Expected

A session URL and QR code for connecting from other devices.

Actual

Error: "Remote Control failed to connect: /login"

Troubleshooting attempted

  • Full quit (Cmd+Q) and relaunch
  • Sign out via Settings → Account, sign back in
  • Verified ANTHROPIC_API_KEY unset (shell + launchctl + no shell config files reference it)
  • Re-authenticated via claude.ai in iPhone Safari, retried — same error
  • Confirmed claude.ai/code works correctly in iPhone Safari, so account auth is functional end-to-end
  • /login and /status both return "isn't available in this environment" in the desktop app — they appear to be CLI-only, so the error message referencing /login may be misleading

Impact

Cannot connect MacBook session to iPhone Claude app as documented.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Version: 1.8555.2 (a476c3), build 2026-05-22T23:04:37.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

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