We're shipping a new feature in Claude Cowork as a research preview that I'm excited about: Dispatch!
One persistent conversation with Claude that runs on your computer. Message it from your phone. Come back to finished work.
To try it out, download Claude Desktop, then pair your phone.
Because it's Cowork, Claude runs code in a sandbox on your machine. Your files stay local. You approve what Claude touches before it acts.
It feels pretty magical to give Claude a mission on my computer and getting occasional updates, like creating reports from internal dashboards or finding me a better seat on my next flight.
Everything Claude can do on your computer - files, browser, tools - are reachable from wherever you are.
Your desktop has to be running. Like Cowork itself, we’re shipping an early version - you can expect more to come here within the next few days and weeks.
Rolling out now to Max subscribers, with Pro coming in the next few days. Try it and let me know what you think.
Download the mobile app and pair it with your desktop app: claude.com/download
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Claude gets its own sandboxed Linux VM: An environment separate from your machine where Claude can write code and run commands without touching your actual system. Under the hood, we're using the same Hyper-V virtualization technology that powers WSL2.
On macOS, the VM runs in user space and inside our app's process. On Windows, Hyper-V requires SYSTEM privileges. So we built a separate Go service that runs as LocalSystem and manages the VM. The app talks to it over a Windows named pipe.
The connection between Claude and VM is secured with Authenticode certificate pinning: on startup, the service extracts its own signing certificate's thumbprint.
When any process connects, it looks up the client's exe path, verifies its signature, and checks that the thumbprints match. Only binaries signed with the same Anthropic certificate can control VMs.