[BUG] Desktop app v2.1.108: /remote-control fails with "Remote Control initialization failed" and CLI sessions not shown in sidebar

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] 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.