The two-paragraph answer (the TL;DR)
Claude Dispatch only works when there is a live Claude Desktop process somewhere — Windows or macOS — that the phone app can reach over the internet. If that machine sleeps, restarts unexpectedly, or loses its network, Dispatch can't talk to Claude until the host is back up. So the entire problem reduces to: pick a host that never goes dark.
Four hosting options work, ranked by setup cost: (1) a Mac mini or small Windows PC you keep plugged in at home, (2) a managed Windows cloud desktop like Standby ($29/mo, 10-minute setup), (3) a DIY Windows VPS at Kamatera or Vultr (~$15/mo, 2-hour setup), or (4) AWS WorkSpaces / Azure Virtual Desktop (overkill for personal use, $50+/mo, 4-hour setup). Linux servers do not work — Claude Desktop is Windows and macOS only. The cheapest reliable path for someone without spare hardware is option 2.
What you're really asking
You probably want one or both of these:
- Always-on phone access: you want to text or speak to Claude from your phone at any hour and have it act through Claude Desktop's tools — Chrome, MCP servers, your local files — without first having to wake your laptop.
- Scheduled or autonomous workflows: you want Claude to keep running a long task overnight, or wake up to a "morning briefing" agent that has been working since 6 AM, or have a Telegram/WhatsApp bot reply to messages while you sleep.
Both use cases share one root requirement: a Claude Desktop session that doesn't go away. Anthropic's own docs make this explicit — your computer must stay on. Everything else in this guide is just how to satisfy that one constraint.
The 10-minute setup (the recommended path)
If you want the shortest path to a working 24/7 Dispatch setup, follow these six steps. They assume you're using a managed Windows cloud desktop — but they work on any Windows or macOS host with minor adjustments noted inline.
- Choose an always-on host. The minimum spec for Claude Desktop + Cowork is 2 vCPU and 4 GB RAM; 4 vCPU and 8 GB is comfortable; 8+ GB is right if you'll run multiple MCP servers or browser sessions. The host needs Windows 10/11 or macOS, an internet connection, and a static IP or a reachable DNS name.
- Install Claude Desktop. Download the official build at claude.com/download. Run the installer. Don't open it yet.
- Configure power policy and auto-launch. On Windows: Control Panel → Power Options → High Performance, set "Never" for sleep and display. Add Claude Desktop to
shell:startupso it launches at login. Enable automatic login (so the machine returns to a working state after any restart). On macOS: System Settings → Battery → "Prevent automatic sleeping when display is off"; set "Login Items" to include Claude Desktop; installcaffeinatefrom a Brew package or use the built-in command. Schedule Windows Updates / macOS Updates to a fixed maintenance window so they don't auto-restart at 3 AM. - Sign into your Anthropic account. Open Claude Desktop. Sign in with your own Claude Pro, Max, or Team account. Run a test prompt to confirm the connection is healthy.
- Pair Dispatch from your phone. Open the Claude phone app → Settings → Dispatch → "Pair a new desktop." Claude Desktop on the host will display a QR code; scan it. The pairing is durable — the host can reboot and the pairing persists.
- Walk away. Close the RDP or remote-control window. Leave the host alone. Test by sending a Dispatch message from your phone. Claude on the host should respond as if you were sitting at the desk.
That's it. Total setup time, on a fresh cloud desktop: about 10 minutes. On your own hardware: 30 minutes if you've never set up auto-launch and power policies before.
The four hosting options, compared honestly
Here is what each option actually costs and how reliable it is in practice. The "uptime" column reflects realistic expectations — including OS updates, residential power and internet outages, and the inevitable forgotten lid-close.
| Option | Setup time | Up-front cost | Monthly cost | Realistic uptime | Best for |
|---|---|---|---|---|---|
| Existing laptop + caffeinate | 10 min | $0 | $5–10 elec. | 85–92% | Trying it once before committing |
| Mac mini at home | 1 hr | $599+ | $5–8 elec. | 95–97% | Long-term, low marginal cost, you don't mind sysadmin |
| DIY Windows VPS (Kamatera, Vultr) | 2 hr | $0 | $14–28 | 99.5% | Technical user who wants control and lowest cloud cost |
| Standby (managed) | 10 min | $0 | $29–119 | 99.9% | Non-technical user who wants it to just work |
| AWS WorkSpaces / Azure VD | 4 hr | $0 | $50–120 | 99.9% | Existing AWS/Azure shop with compliance needs |
The two questions that determine which row is right for you: do you already own suitable hardware? and do you want to be your own sysadmin? If you answer no to both, the managed cloud-desktop path saves you the most time per dollar — even if it isn't the cheapest dollar amount. If you answer yes to both, the Mac mini path wins long-term.
Common mistakes (and the fixes)
Most "my Dispatch keeps dying" complaints come from one of these:
- Forgetting power policy. Default Windows and macOS settings put the machine to sleep after 15–30 minutes. Override in the OS power settings, not just by jiggling the mouse.
- Forgetting auto-launch. Claude Desktop must restart automatically after a reboot, otherwise a 3 AM Windows Update kills your Dispatch and you don't notice until 9 AM.
- Trying to use Linux. Claude Desktop has no Linux build. Linux works for the API, but not for Cowork or Dispatch. There is no workaround short of a virtualized macOS or Windows guest, which is a worse experience than just renting Windows directly.
- Closing the laptop lid. macOS clamshell mode requires an external display and power. Windows requires the lid-close action to be set to "Do nothing" in Power Options. The single most common Dispatch outage is a lid that closed automatically.
- Home internet outages. Residential Wi-Fi runs at ~95% uptime in real conditions. If your internet dies for an hour, Dispatch is dead until it returns. A cloud desktop lives on data-center networking and avoids this entirely.
- Pairing Dispatch with the wrong account. The Claude account you sign into on the desktop must match the account you use on your phone. Cross-account pairings fail silently.
The managed path — what Standby actually does
Disclosure: this guide is published by Standby. Below is the unvarnished pitch — including weaknesses.
Standby is a managed Windows cloud desktop pre-configured for Claude Desktop, Cowork, and Dispatch. We provision the VM, install Claude Desktop and Chrome, set the power policy, configure auto-launch, and email you the credentials. You sign in with your own Anthropic account — we never resell Claude subscriptions — and pair Dispatch from your phone. Total time from purchase to working Dispatch: about 10 minutes.
Pricing starts at $29/month for a 2 vCPU / 4 GB RAM / 60 GB NVMe spec. Pro ($59) adds Telegram and WhatsApp MCP bridges. Business ($119) adds 8 vCPU / 16 GB RAM and priority support. We're an Illinois LLC; we are not affiliated with Anthropic.
What Standby is good at: non-technical users who want Dispatch on 24/7 without learning Windows administration. The setup is genuinely 10 minutes from purchase to working Dispatch on your phone.
What Standby isn't good at: if you already own a Mac mini and don't mind being your own sysadmin, the math doesn't favor us — the Mac mini wins on long-term cost. If you need GPUs (you usually don't for Dispatch), you'd want a different provider. If you're an existing AWS or Azure customer with compliance requirements, your IT team probably wants you on WorkSpaces or AVD.
FAQ
Will Claude Dispatch work if my laptop sleeps?
No. Dispatch is a remote control for a live Claude Desktop process. If the host sleeps, hibernates, or loses its network, Dispatch goes dark until the host comes back. This is the original problem this guide solves.
Can I run Claude Desktop on a Linux server?
No. Claude Desktop is published for Windows x64 and macOS only — there is no Linux build, official or otherwise. If you need an always-on Claude session, you need a Windows or macOS host. If you just need Claude's API for headless agents, that's a different product (and Linux works fine there) — but it doesn't give you Cowork or Dispatch.
What's the cheapest way to keep Dispatch on 24/7?
If you already own a Mac mini or small PC, leaving it on with Claude Desktop running is free except for ~$5/month in electricity. If you don't have hardware, the cheapest reliable cloud option is a managed Windows cloud desktop starting at $29/month. Doing it on your own with a raw Windows VPS at Kamatera or Vultr can run as low as $14/month, but you do all the setup yourself.
Does my home internet uptime matter?
Yes. Dispatch needs the host to be reachable from the internet. Residential internet runs at 95–97% uptime in real conditions — outages of an hour or more are common (especially during storms, ISP maintenance windows, or your kids unplugging the router). A cloud desktop runs on data-center networking with 99.9% SLAs and avoids this entirely.
Can I pair Dispatch with multiple phones?
Yes. One Claude Desktop session supports multiple paired phones. Each phone runs the standard pairing flow (Settings → Dispatch → Pair a new desktop) against the same QR code shown on the host.
What about Windows Update auto-restarts?
Configure Windows Update to defer restarts to a maintenance window you control, or pause updates while you're using Dispatch. Auto-restart at 3 AM is the most common reason a self-hosted Windows desktop loses Dispatch overnight. On a managed service like Standby this is handled for you.
Does Claude Dispatch work on iPad?
Yes. The Claude phone app runs on iPad too, and Dispatch pairing works the same way. Some users also remote-control their cloud desktop directly from iPad via Microsoft Remote Desktop — useful for occasional administrative work alongside the Dispatch experience.
What if I want to run multiple Claude agents at once?
Each Windows or macOS host runs a single Claude Desktop session, paired to that host. To run multiple parallel Claude agents, you need multiple hosts. Some power users run 2–3 cloud desktops side-by-side for this reason.
Sources and further reading
- claude.com/download — official Claude Desktop installers for Windows and macOS
- Microsoft Remote Desktop client documentation
- Apple — Keep your Mac from going to sleep
- Standby guide — Cheapest way to run Claude Cowork always-on
- Standby guide — Connect Claude to Telegram