Dispatch: messages received but never executed (ECONNREFUSED 127.0.0.1:3845)

Resolved 💬 2 comments Opened Mar 29, 2026 by SmartConnection-CodeHub Closed Apr 1, 2026

Bug: Dispatch messages received but never executed (ECONNREFUSED 127.0.0.1:3845)

Environment

  • Claude Desktop: v1.1.9310 (latest)
  • OS: macOS Darwin 25.2.0
  • Plan: Max
  • SDK in VM: 2.1.85

Description

Dispatch (mobile → desktop) receives messages and marks them as "Read" (✓ Leído), but never responds or executes them. The Cowork VM boots successfully but the local bridge service on port 3845 fails to start, preventing message execution.

Steps to Reproduce

  1. Open Claude Desktop on Mac
  2. Enable Dispatch: "Mantener activo" ON, "Permitir todas las acciones" ON, "Uso de computadora" ✓
  3. Open Claude mobile app (iOS) → go to "Envío" (Dispatch)
  4. Send any message (e.g., "Hola")
  5. Message shows "✓ Leído" (Read) on mobile but no response ever comes

Expected Behavior

Dispatch should process the message and respond on mobile.

Actual Behavior

  • Messages are received and added to processedMessageUuids in bridge-state.json
  • The Cowork VM boots successfully (7.2s startup, network CONNECTED, SDK 2.1.85 installed)
  • But the bridge service on port 3845 never starts
  • Main log shows repeated ECONNREFUSED 127.0.0.1:3845 errors
  • Session enters is_resume: true state and only sends heartbeats indefinitely

Diagnostic Evidence

main.log errors

[UtilityProcess stderr] [4169] Connection error: TypeError: fetch failed
  [cause]: Error: connect ECONNREFUSED 127.0.0.1:3845
[4169] Fatal error: TypeError: fetch failed
  [cause]: Error: connect ECONNREFUSED 127.0.0.1:3845

main.log session behavior

[sessions-api] Poll received work: id=cse_XXXXX type=session
[sessions-bridge] Session cse_XXXXX already active; refreshing session_ingress_token
[transport:ccr] Heartbeat sent  (repeats indefinitely, no execution)

bridge-state.json

Messages accumulate in processedMessageUuids (16+ messages) but none get responses.

VM logs (cowork_vm_node.log)

VM boots fine: network CONNECTED, API REACHABLE, SDK 2.1.85 installed.

cowork_vm_swift.log

VM startup completes successfully in 7.2s with no errors.

Attempted Fixes (none worked)

  1. Restart Claude Desktop app
  2. Reset bridge-state.json (clear session ID and processed messages) → new session created but same behavior
  3. Toggle "Mantener activo" off/on
  4. Verified lsof -i :3845 → nothing listening on that port

Additional Context

  • Remote Triggers (scheduled tasks) work correctly via API
  • The issue appears to be specifically in the local bridge service that connects Dispatch to the Cowork VM
  • Config shows keepAwakeEnabled: true, allowAllBrowserActions: true, chicagoEnabled: true

View original on GitHub ↗

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