[BUG] /remote-control fails with "failed to connect: /login" on Pro account, desktop app v1.8555.2

[jmkubr]

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

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Remote Control auto-attach not honored on new Claude Code sessions (macOS desktop) #62105
2. Remote Control fails with "/login" — embedded claude.ai webview stuck logged out, IndexedDB corruption, cookie wipe does not recover #60606
3. Bug: Remote Control initialization fails with "Remote Control failed to connect: Remote Control initialization failed" #57286

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.