[BUG] Dispatch on Windows desktop cannot pair with iPhone — mobile shows "Can't reach my desktop"

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?

The Claude iOS app cannot connect to Dispatch on my Windows desktop. The mobile app shows "Can't reach your desktop. Check that your computer is online and desktop app is open." The desktop app is running, the Dispatch toggle is ON, and the computer is online.

Environment

• OS: Windows 11 x64
• CPU: Intel Core Ultra 7 265K
• Claude Desktop version: 1.19367.0 (1a5be1)
• iOS Claude app version: 1.260702.2
• Account: Same Anthropic account on both devices

Steps to reproduce

1. Open Claude Desktop on Windows, ensure the Dispatch toggle is enabled in Cowork settings.
2. Open the Claude iOS app and navigate to Dispatch.
3. Error appears: "Can't reach your desktop. Check that your computer is online and desktop app is open."

Troubleshooting already attempted (none resolved the issue)

• Restarted both applications and both devices.
• Completely disabled Norton Antivirus and Windows Firewall to rule out local network/port blocking.
• Performed a clean reinstall by manually deleting all cached folders (%USERPROFILE%\.claude, %LOCALAPPDATA%\Claude, %LOCALAPPDATA%\Claude Nest-3p, %LOCALAPPDATA%\Claude-3p, %LOCALAPPDATA%\claude-cli-nodejs) and ensuring background chrome-native-host processes were killed.
• Unlinked and relinked: Logged out completely on both the Windows Desktop App and the iOS App, toggled the Dispatch switch off/on, and signed back in.
• Verified that the underlying API and Anthropic authentication are working perfectly on this exact machine using the claude-code CLI (v2.1.203).

Expected behavior

Dispatch should pair with the desktop, establish the local WebSocket connection, and allow remote task assignment from the iPhone.

Technical Note / Suspected Cause

My Windows user profile path contains a space (C:\Users\Soon Ming). It is highly likely that the Dispatch local forwarding server fails to parse file paths or network bridge paths with spaces on Windows 11. This may be related to issue #46391, suggesting the problem lies in the Dispatch pairing/websocket channel rather than platform-specific code.

What Should Happen?

Dispatch should successfully pair with the Windows desktop app, establish the local connection, and allow remote task assignment from the iPhone.

Error Messages/Logs

Steps to Reproduce

1. Open Claude Desktop on Windows, ensure the Dispatch toggle is enabled in Cowork settings.
2. Open the Claude iOS app and navigate to Dispatch.
3. Error appears: "Can't reach your desktop" or gets permanently stuck on "Asleep".

Troubleshooting already attempted (none resolved the issue)

• Restarted both applications and both devices.
• Completely disabled Norton Antivirus and Windows Firewall to rule out local network/port blocking.
• Performed a clean reinstall by manually deleting all cached folders (%USERPROFILE%\.claude, %LOCALAPPDATA%\Claude, %LOCALAPPDATA%\Claude Nest-3p, %LOCALAPPDATA%\Claude-3p, %LOCALAPPDATA%\claude-cli-nodejs) and ensuring background chrome-native-host processes were killed.
• Unlinked and relinked: Logged out completely on both the Windows Desktop App and the iOS App, toggled the Dispatch switch off/on, and signed back in.
• Verified that the underlying API and Anthropic authentication are working perfectly on this exact machine using the claude-code CLI (v2.1.203), isolating the issue to the Dispatch local WebSocket bridge.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.203

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Note: My Windows user profile path contains a space. I highly suspect the Dispatch local WebSocket server fails to parse file paths or network bridge paths with spaces correctly on Windows 11, causing the pairing to permanently stick on "Asleep".