[FEATURE] Support using Dispatch in Claude Desktop
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I use multiple computer workstations in my life. Currently, it's only possible to issue Dispatch commands via the mobile app -- visiting the Dispatch page on a computer when another computer was already paired prompts the user to disconnect the other computer to set this one up for Dispatch.
Replication steps:
- Download Claude Desktop on two computers and mobile phone, sign in on all
- Set up Dispatch on PC 1
- Commands can be sent via mobile as expected
- Open Dispatch on PC 2
- Observe error "Another device is connected. A cowork agent is already running on <Mac>. Quit the Claude app on that device, then restart this one to take over."
- Desired behavior: Allow issuing Dispatch commands from the desktop app similar to existing Mobile and local Claude Code UXes
Thank you for your consideration,
Natalie
---
PS: Usecase context: I'm trying to adopt Claude native apps to replace my OpenClaw workflow where my Laptop serves as my coding/executive assistant's home base. I do most of my development via the openclaw Slack connection on my Windows PC as a result.
Proposed Solution
When I open "Dispatch" on a computer and I already have Dispatch enabled on another computer, I want to see the ongoing Dispatch session and be able to interact with it in the same UX as on the hosting computer.
A small warning banner should be displayed across the top, "You're dispatching Claude sessions to <hostname>", and the settings configurator should be greyed-out -- on hover, it instructs the user to "To edit Dispatch settings, you'll need to use <hostname> directly".
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
Most usecases for using Dispatch via phone, but for computers:
- Anyone who uses multiple computers: People with work+personal laptop, some have a small laptop and a more powerful desktop PC, some people use multiple operating systems for different tasks
- I'm running my "Claude homebase" on a homelab server, but interact with it on a separate PC
Additional Context
_No response_
4 Comments
"Another device is connected" stuck on single PC — Dispatch completely broken
I'm experiencing this exact issue on a single Windows PC. The Dispatch page shows "Another device is connected — A Cowork agent is already running on [hostname]" even though there is no other device or session active.
Environment: Claude for Windows v1.2773.0, Android mobile app (latest)
What I've tried (none resolved it): Killed all Claude processes via Task Manager, completely uninstalled and reinstalled Claude Desktop, logged out and back in, attempted to pair via mobile app — gets "Pairing failed" and cannot find the desktop.
Mobile app behavior: Shows "Looking for your desktop..." indefinitely, then fails with "Pairing failed." The checklist confirms Dispatch should be set up, correct account is signed in, and desktop is open with latest version.
Conclusion: This appears to be a stale server-side session that is not being cleaned up, even after full reinstall and re-authentication.
Request: Please add a way to force-disconnect/reset Dispatch sessions, either from the desktop app settings or from the mobile app. Currently there is no recovery path for users stuck in this state.
+1 — this is exactly my situation. I split my work between a corporate laptop and a personal laptop, and Dispatch's single-pairing model forces me to quit Claude on one machine and re-pair to the other every time I switch contexts. That friction is enough that I've stopped using Dispatch on the secondary machine entirely.
The ideal UX from my side: pair the mobile app with N desktops, and let me pick the target either explicitly ("@work", "@personal") or via a target selector in the Dispatch thread. Same model many remote-access and MDM tools already use.
Would happily beta-test this.
+1, a mobile device isn't always the best or most convenient thing to use to monitor and carry out complex tasks on a desktop.
+1
<img width="689" height="496" alt="Image" src="https://github.com/user-attachments/assets/8e210363-73df-4b23-8e9f-2260a2d3715d" />