[BUG] Dispatch messages are marked as read but Claude never responds

Resolved 💬 3 comments Opened Mar 29, 2026 by basabasa-maker Closed Apr 1, 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?

When sending a message via Dispatch, the message is marked as "read" (seen) but Claude never sends a response. The browser-based claude.ai chat and Cowork tasks work correctly. Restarting the app does not resolve the issue. The iOS app is also on the latest version.

Steps to reproduce:

  1. Open Dispatch and send a message to Claude.
  2. The message is marked as read.
  3. Wait for a response — no response is ever received.

Environment:

  • Plan: Max
  • Claude Code version: v2.1.84
  • OS: macOS
  • iOS app: latest version

What Should Happen?

When a message is sent via Dispatch, Claude should respond as expected, just like it does in the browser-based claude.ai chat and Cowork tasks.

Error Messages/Logs

Steps to Reproduce

  1. Open Dispatch in the Claude desktop app or iOS app.
  2. Send a message to Claude via Dispatch.
  3. Observe that the message is marked as "read" (seen).
  4. Wait for a response — no response is ever received from Claude.
  5. Verify that browser-based claude.ai chat and Cowork tasks work normally.
  6. Restart the app — the issue persists.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.84 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Plan: Max
  • The issue occurs on both macOS desktop app and iOS app (latest version).
  • Browser-based claude.ai chat and Cowork tasks function correctly, suggesting the issue is specific to Dispatch.
  • Restarting the app does not resolve the problem.

View original on GitHub ↗

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