[BUG] Dispatch paired/online but prompts never execute on desktop

Resolved 💬 3 comments Opened Apr 14, 2026 by srinitude Closed Apr 18, 2026

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?

Dispatch pairing completes successfully and mobile shows "online" status, but prompts sent from the phone never trigger execution on the desktop. No spinner, no "Brewing..." indicator, no response — just silence. Regular Cowork sessions work fine.

Actual Behavior

Prompt is sent and appears delivered, but desktop never picks it up. No activity, no error, no timeout.

Troubleshooting Already Attempted

  • Deleted ~/.claude/bridge-state.json, logged out both devices, re-paired (desktop first, then phone)
  • - Toggled Dispatch off → Cmd+R hard refresh → Dispatch back on
  • - - Full uninstall and reinstall of Claude Desktop app
  • - - - Re-scanned QR code and re-toggled file access + keep-awake permissions
  • - - - - Started fresh Dispatch conversations

None of these resolved the issue.

Environment

  • Plan: Claude Max
  • - Claude Desktop: latest version
  • - - Mobile app: latest version
  • - - - Related issues: #45937, #46391, #40283

What Should Happen?

Prompt should be received by desktop and executed, with results returned to mobile.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Desktop, navigate to Cowork → Dispatch
  2. Pair with mobile app via QR code (succeeds, shows online)
  3. Send any prompt from mobile Dispatch (e.g., "List files in my Documents folder")
  4. Observe: no execution on desktop, no response returned to mobile

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.104

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Warp

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗