Dispatch messages show as read but never execute after rate limit (macOS, v1.1.9493)

Resolved 💬 6 comments Opened Mar 29, 2026 by irvcassio Closed May 31, 2026

Bug Description

Claude Dispatch marks messages as read but never responds or executes any actions. The conversation shows the message was received, but Claude produces no output — it silently drops the task.

This persists across app restarts and a full reinstall.

Root Cause Hypothesis

The bridge-state.json file retains a stale remoteSessionId and localSessionId after the local agent process dies or is cleaned up. The bridge continues polling the remote session and marking messages as "processed" (triggering the "read" indicator) but has no local agent process to actually execute them. The pendingProcessedAcks array is empty, confirming no work is being dispatched locally.

Relevant bridge state observed:

{
  "enabled": true,
  "userConsented": true,
  "remoteSessionId": "cse_01HaSsk25xLALTJNzezkcUUy",
  "localSessionId": "local_ditto_...",
  "processedMessageUuids": ["... 20 UUIDs ..."],
  "pendingProcessedAcks": []
}

Environment

  • App version: 1.1.9493
  • OS: macOS Sequoia (Darwin 25.4.0), Apple Silicon
  • Claude Code CLI version: 2.1.87 (bundled)

Steps to Reproduce

  1. Open Claude Desktop, enable Dispatch/Cowork
  2. Send a message via Dispatch (e.g., from claude.ai mobile or another device)
  3. Message shows as "read" in the sender's UI
  4. No response is ever generated — Dispatch appears completely unresponsive

Expected Behavior

Dispatch should receive the message, spin up a local agent session, execute the task, and reply.

Workaround

Resetting the bridge state forces the app to create a fresh Dispatch session:

osascript -e 'quit app "Claude"'
pkill -x Claude
echo '{}' > ~/Library/Application\ Support/Claude/bridge-state.json
open -a Claude

After relaunch, re-enable Dispatch from the Cowork tab. A new session will be established.

Possibly Related

  • #40283 — Cowork Dispatch not responding on macOS
  • #40358 — Dispatch foreground chat shows no replies while background session works
  • #40257 — Dispatch stops replying; instructions are read but completely ignored
  • #40575 — Dispatch session timeout causes silent message loss
  • #40585 — Code tab shows Cowork content (same app version, same session)

View original on GitHub ↗

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