Dispatch QR pairing fails on Linux

[FeroxShark]

Dispatch QR code pairing with mobile does not work on Linux.
After scanning the QR code, the mobile app accepts it but the
pairing never completes in the desktop app.

Environment:

• OS: Arch Linux (Hyprland/Wayland)
• Build: AppImage 1.1.9493
• Backend: host (auto-detected)

Steps to reproduce:

1. Open Cowork tab
2. Click Dispatch
3. Scan QR code with Claude mobile app
4. Pairing never completes

Expected: Desktop and mobile connect successfully
Actual: QR scan accepted on mobile but desktop stays on pairing screen

[github-actions]

I've traced the pairing handshake through the source. The flow is entirely network-based — no platform APIs involved.

Here's how it works: desktop connects to wss://bridge.claudeusercontent.com, authenticates with your OAuth token, gets back a bridge_secret, and encodes that as the QR. Mobile scans it, connects to the bridge with the secret, and the bridge sends a pairing_response back to desktop. Since your phone is successfully scanning the QR, the bridge connection and QR generation are working. The pairing_response is either not arriving or being silently dropped.

There are two likely culprits. First, the pairing_response handler requires pendingPairingRequestId to match the response's request_id — a mismatch causes a silent no-op with no error. Second, shouldEnableSessionsBridge() returns false for non-Claude.ai accounts (e.g., Claude for Work with a custom SSO provider), which gates the whole feature. This project has no patches touching any of this code path, so we can't fix it on our end, but it helps narrow down where to look upstream.

A few things that would help diagnose this:

• Check ~/.config/Claude/logs/ for any errors around the time you attempted pairing
• Confirm you're logging in with a personal Claude.ai account (not a workspace/SSO account)
• Try running with --enable-logging to capture WebSocket traffic: ./claude-desktop.AppImage --enable-logging 2>&1 | tee ~/claude-pair.log

If the logs show the bridge connecting but no pairing_response ever arriving, that points to an upstream server-side issue worth reporting to Anthropic directly.

---

This is an automated triage comment. A maintainer will review this issue and may provide further guidance.

Written by Claude Sonnet via Claude Code