[BUG] Cowork Dispatch still offline — main conversation not reachable

Resolved 💬 2 comments Opened May 30, 2026 by StefanoSorr 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?

Bug Description

Cowork Dispatch is still not working. The main Dispatch conversation shows as offline / unreachable, even though the desktop app is open and individual Cowork tasks run fine.

Environment

  • OS: [your OS]
  • Claude Desktop version: [your version]
  • Plan: [Max / Pro / etc.]

Steps to Reproduce

  1. Open Claude Desktop with Dispatch enabled
  2. Dispatch main conversation shows "Desktop appears offline"
  3. Individual Cowork tasks work normally

What I've Tried

  • Deleted ~/.claude/bridge-state.json and restarted
  • Logged out and back in on all devices
  • Toggled Dispatch off/on with hard refresh (Cmd+R)
  • Restarted the app and machine multiple times

Related Issues

  • #45937 — Dispatch main conversation permanently offline despite working Cowork tasks
  • #40283 — Cowork Dispatch not responding on macOS
  • #40179 — Dispatch responses generated but never delivered to clients

Expected Behavior

Main Dispatch conversation should be reachable from desktop and mobile.

Actual Behavior

Dispatch main thread remains permanently offline. No local troubleshooting resolves it — appears to be a server-side relay issue.

What Should Happen?

Dispatch don't work

Error Messages/Logs

Steps to Reproduce

In the descktop and mobile, even offline

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Last, even adg

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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