claude-code - 💡(How to fix) Fix [BUG] Desktop app v2.1.108: /remote-control fails with "Remote Control initialization failed" and CLI sessions not shown in sidebar [1 participants]

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…
GitHub stats
anthropics/claude-code#48238Fetched 2026-04-15 06:29:18
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

Error Message

Error Messages/Logs

  1. Observe: error "Remote Control failed to connect: Remote Control initialization failed"

Fix Action

Fix / Workaround

The CLI workaround is to run /remote-control from an external shell session instead of from within the Desktop app. This confirms the issue is isolated to the Desktop app's Remote Control initialization path introduced in the v2.1.108 redesign.

Code Example

Remote Control failed to connect: Remote Control initialization failed

---

Remote Control failed to connect: Remote Control initialization failed
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?

After updating to the redesigned Desktop app v2.1.108 (released April 14, 2026), running /remote-control inside a Desktop app session fails immediately with:

Remote Control failed to connect: Remote Control initialization failed

What Should Happen?

/remote-control in the Desktop app should connect successfully, as it did before v2.1.108.

Error Messages/Logs

Remote Control failed to connect: Remote Control initialization failed

Steps to Reproduce

  1. Launch Claude Code Desktop app v2.1.108
  2. Start a new session from within the Desktop app
  3. Type /remote-control
  4. Observe: error "Remote Control failed to connect: Remote Control initialization failed"

Verification that this is a Desktop-specific regression

  • Running /remote-control from a CLI session (outside Desktop app) works correctly
  • The Remote Control URL is generated and the session is accessible via claude.ai/code
  • Authentication (Claude Max / OAuth) is confirmed working
  • This regression appeared after upgrading to v2.1.108 on April 14, 2026

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.1.101

Claude Code Version

v2.1.108

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

The CLI workaround is to run /remote-control from an external shell session instead of from within the Desktop app. This confirms the issue is isolated to the Desktop app's Remote Control initialization path introduced in the v2.1.108 redesign.

extent analysis

TL;DR

The issue can likely be resolved by identifying and fixing the regression introduced in the Desktop app's Remote Control initialization path in version v2.1.108.

Guidance

  • Verify that the issue is indeed specific to the Desktop app by continuing to test the CLI workaround, which has been confirmed to work.
  • Compare the Remote Control initialization code between versions v2.1.101 and v2.1.108 to identify potential changes that could be causing the regression.
  • Check the authentication flow and ensure that it is correctly implemented in the Desktop app, as the issue might be related to authentication.
  • Test the Remote Control feature with different Claude models, if possible, to see if the issue is model-specific.

Example

No code snippet can be provided without more information about the specific changes made in version v2.1.108.

Notes

The issue seems to be isolated to the Desktop app's Remote Control initialization path, and the CLI workaround suggests that the issue is not with the Remote Control feature itself, but rather with how it is integrated into the Desktop app.

Recommendation

Apply workaround: Run /remote-control from an external shell session instead of from within the Desktop app, as this has been confirmed to work and allows for continued use of the Remote Control feature while the regression is being addressed.

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