[FEATURE] Multi-device Cowork: Allow concurrent Cowork agents on multiple machines under a single account
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement Cowork currently enforces a single-device lock per account. If a Cowork agent is running on Machine A, attempting to start Cowork on Machine B (same account) presents: > **"Another device is connected"** > A Cowork agent is already running on [Machine A]. Quit the Claude app on that device, then restart this one to take over. The only option is "Disconnect all and retry" — a destructive action that kills the session on Machine A. This is a hard blocker for users who operate across a stationary workstation and a portable laptop — a common setup for remote-first professionals, consultants, and anyone doing substantive knowledge work. **My setup:** I run an AI consulting practice and have built an agentic operating system on top of Claude's ecosystem (Claude Code, Cowork, Dispatch, MCP connectors). My infrastructure spans two machines: - **Cynapse4eva** (home workstation, always-on) — runs Cowork as the primary command center with Dispatch, scheduled tasks, and full MCP connector access. - - **CynapsePro** (Surface Pro laptop, travel/on-the-go) — currently locked out of Cowork entirely because the workstation holds the agent lock. The workstation is the right home for Dispatch and scheduled tasks.
Posted by cnapz on Apr 5, 2026, 12:13 AM
Tags
Related issues
- Qt is fully of bugs on Wayland, some of which are unfixable because the API makes guarantees that are impossible to uphold.
- I took the plunge into GrapheneOS a week ago.
- [BUG] Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use
- Those cheap Bluetooth Tesla coils on AliExpress use A2DP audio as their control signal - a comparator converts the audio into spark pulses.
- [Prisma 7.0.0] TypeScript TS2742 errors with pnpm monorepo - cannot resolve @prisma/client-runtime-utils types
- I built a routine management app for my kids (7 and 10) called "Oh Yah!" after their constant "Oh yah!
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
onboarding (SaaS)
Qt is fully of bugs on Wayland, some of which are unfixable because the API makes guarantees that are impossible to uphold.
I took the plunge into GrapheneOS a week ago.
[FEATURE] Multi-device Cowork: Allow concurrent Cowork agents on multiple machines under a single account
[BUG] Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use
Those cheap Bluetooth Tesla coils on AliExpress use A2DP audio as their control signal - a comparator converts the audio into spark pulses.
[Prisma 7.0.0] TypeScript TS2742 errors with pnpm monorepo - cannot resolve @prisma/client-runtime-utils types
I built a routine management app for my kids (7 and 10) called "Oh Yah!" after their constant "Oh yah!
> If it is open source, then I can build and install it myself.
[FEATURE] Multi-device Cowork: Allow concurrent Cowork agents on multiple machines under a single account
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement Cowork currently enforces a single-device lock per account. If a Cowork agent is running on Machine A, attempting to start Cowork on Machine B (same account) presents: > **"Another device is connected"** > A Cowork agent is already running on [Machine A]. Quit the Claude app on that device, then restart this one to take over. The only option is "Disconnect all and retry" — a destructive action that kills the session on Machine A. This is a hard blocker for users who operate across a stationary workstation and a portable laptop — a common setup for remote-first professionals, consultants, and anyone doing substantive knowledge work. **My setup:** I run an AI consulting practice and have built an agentic operating system on top of Claude's ecosystem (Claude Code, Cowork, Dispatch, MCP connectors). My infrastructure spans two machines: - **Cynapse4eva** (home workstation, always-on) — runs Cowork as the primary command center with Dispatch, scheduled tasks, and full MCP connector access. - - **CynapsePro** (Surface Pro laptop, travel/on-the-go) — currently locked out of Cowork entirely because the workstation holds the agent lock. The workstation is the right home for Dispatch and scheduled tasks.
Comments (0)
No comments yet. Start the discussion.