[BUG] Dispatch: completely non-functional after incident q5qk1234v205 "Resolved" — Max plan, 48+ hours, no support response

Resolved 💬 10 comments Opened Mar 30, 2026 by jpjogerst-png Closed Jun 3, 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 has been completely non-functional since Saturday, March 28, 2026. Messages sent via Dispatch are received and read by the desktop agent, but responses never appear in the conversation thread. This matches the behavior described in #40178 exactly.

Incident q5qk1234v205 ("Dispatch sessions not responding in Claude Desktop") was marked "Resolved" at 04:44 UTC on March 29, with the fix attributed to Claude Desktop version 1.1.9493. However, Dispatch remains broken on my account despite confirming I am on the latest version.

Environment:

  • macOS (MacBook Air)
  • Claude Desktop (latest version confirmed; installed in /Applications)
  • Max plan ($200/month)

What I've Tried (All Failed):

  1. Deleted ~/Library/Application Support/Claude/bridge-state.json and restarted
  2. Cleared Session Storage and IndexedDB and restarted
  3. Reconnected and re-set up Dispatch from scratch (new pairing)
  4. Confirmed latest version of Claude Desktop is installed
  5. Restarted Claude Desktop multiple times (full quit via Cmd+Q, not just window close)
  6. No firewall or network restrictions on my end
  7. Claude Desktop is installed in /Applications (system-level)

Support Experience:

  • Opened support ticket Sunday, March 29 at ~10:24 AM CDT
  • Received five consecutive AI bot responses with generic troubleshooting steps, none of which applied
  • Received ticket acknowledgment (Conversation ID: 215473686782974) at 10:32 AM CDT Sunday
  • Sent Monday morning follow-up at 7:09 AM CDT
  • Also contacted support via in-app messenger
  • As of this filing: 48+ hours with zero human response despite Max plan's stated "priority response within one US business day"

Critical Data Loss Risk:
My Dispatch conversation history contains significant work product (a full automation workplan developed over multiple sessions). If Dispatch history is not preserved and recoverable, this represents real data loss caused by the platform defect.

See also: #40178 (exact same bug), #37713 (Dispatch session isolation)

What Should Happen?

  1. Dispatch receives messages from mobile, desktop agent processes them, and responses appear in the conversation thread on both desktop and mobile.
  2. A human engineer investigates why Dispatch remains broken on my specific account after the incident was marked "Resolved."
  3. Dispatch conversation history is preserved and recoverable (contains significant work product).
  4. Billing credit for 48+ hours of non-functional Dispatch on a $200/month Max plan.
  5. Transparency on what "Resolved" means when the fix clearly did not apply to all affected accounts.

Error Messages/Logs

Steps to Reproduce

  1. Set up Dispatch between Claude Desktop (macOS, MacBook Air) and mobile device
  2. Send a message via Dispatch from mobile
  3. Observe that the message is received and marked as read on desktop
  4. Wait for a response — none ever appears in the conversation thread
  5. This has been consistent since March 28, 2026, and persists after all troubleshooting steps listed above
  6. The issue matches exactly the behavior described in #40178 (SendUserMessage tool not found; responses generated but never delivered)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Desktop (latest version, Dispatch feature) — not Claude Code CLI

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This is a Claude Desktop / Dispatch issue, not a Claude Code CLI issue. Filing here because this is where the engineering team monitors and because existing Dispatch issues (#40178, #37713) are tracked in this repo.

Support Conversation ID: 215473686782974
Status page incident: q5qk1234v205

Note: This bug is not about Claude Code CLI. It is about the Dispatch feature in Claude Desktop (the Electron app). The Platform and Terminal/Shell dropdowns above do not have options for "Claude Desktop" so defaults were left in place.

View original on GitHub ↗

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