Dispatch shows desktop online but leaves requests on read (no response on target)

Resolved 💬 3 comments Opened Apr 14, 2026 by eusha-tulip Closed Apr 18, 2026

Summary

Dispatch feature accepts requests from phone/web but never executes them on the online target. Target shows "online" in sidebar after workarounds but dispatched requests produce no response.

Environment

  • OS: Windows 10 Pro 19045
  • Claude Desktop: 1.2278.0.0 (x64 MSIX)
  • Claude Code CLI: installed via npm global
  • Account: Max subscription

Timeline

  1. Noticed "Desktop appears offline" in phone Dispatch sidebar
  2. Found ~/.claude/.credentials.json OAuth token had expired 2 weeks prior (2026-03-31) with no automatic refresh in that window
  3. Re-authed via claude setup-token — credentials file refreshed, expiresAt updated
  4. Dispatch still showed offline until claude CLI was started in a terminal
  5. After CLI launched, Dispatch flipped to online — but dispatched requests now land without any response on the target

Expected

Token should auto-refresh while idle (or surface a clear failure); Desktop app alone should be a valid dispatch target; dispatched requests should execute on the online target.

Observed

  • Silent refresh failure — no indication token had died
  • Desktop app alone insufficient as dispatch target (CLI needed)
  • Online state reached but dispatches unresponsive
  • request_id: req_011Ca3yfi6e8RcKio546rbRr

Workarounds attempted

  • taskkill /F /IM claude.exe + relaunch
  • Fresh claude CLI session
  • Credential re-auth

View original on GitHub ↗

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