The short answer
Claude scheduled tasks only fire when Claude Desktop is alive on a host that's reachable. Your laptop in a carry-on is asleep. Hotel Wi-Fi drops constantly. Your home network at home is fine, but you're not there to babysit it. The reliable fix is to run Claude Desktop on a host that's not in your bag — a Mac mini at home (95% uptime) or a managed cloud desktop (99.9% uptime).
Why this is a real problem for nomads
The promise of Claude scheduled tasks is: set it once, get the result every morning forever. The actual experience for someone traveling is: it works for a week at home, then the moment you fly somewhere, every task silently breaks.
- Laptop in your carry-on — asleep. No tasks fire.
- Laptop on the hotel desk — Wi-Fi is unstable; the task may fire but the result email may not send.
- Laptop in the cafe — the moment you walk to lunch, it sleeps. Same problem.
- Laptop at home — fine, but you're not at home, so you can't fix it when something breaks.
For someone who's actually building workflows around scheduled tasks — morning briefs, daily research scans, automated content drafts — this is the single biggest source of "wait, where's my brief?" frustration.
The four real options
1. Mac mini at home, sleep disabled
If you own a Mac mini and have it set up at home, you can leave it running while you travel. Disable sleep in System Settings → Battery, install Caffeine (free menu-bar app) as belt-and-suspenders, set Claude Desktop to launch at login, and enable auto-login so it returns to a working state after any restart.
Reliability: ~95–97%. Failures come from home Wi-Fi outages (your ISP, not the Mac), power blips, and occasional macOS auto-updates. Cost: free if you own the Mac. ~$2/month in electricity.
Catch: if something breaks at home and you're in Bali, you have nobody to fix it. The 5% downtime tends to come in multi-hour chunks.
2. Windows VPS, DIY (Kamatera / Vultr)
Rent a Windows VPS for ~$14–18/month. Provision a 4 GB RAM box, install Claude Desktop, set the power policy, configure auto-launch, enable RDP. About 2 hours your first time.
Reliability: ~99.5%. Data-center networking is vastly more reliable than home Wi-Fi. You still patch and babysit, but the VM doesn't go to sleep.
Catch: you have to be your own sysadmin. Windows Updates need handling. Firewall configuration is on you. From a hotel room in Lisbon, this is harder.
3. Managed cloud desktop (Standby)
A service like Standby provides a Windows cloud desktop pre-configured for Claude Desktop, Claude Code, Cowork, Dispatch, and scheduled tasks. We patch it, we keep Claude Desktop launched, we monitor uptime. You sign in to your own Anthropic account once and never touch the infrastructure.
Reliability: 99.9%. Cost: $29+/month. Setup: 10 minutes.
Why this is the nomad answer: the desktop lives in a data center. It doesn't care that you're in a different time zone, on a flight, or on hotel Wi-Fi. Your tasks fire. You access them from your phone or iPad via Dispatch or RDP.
Honest disclosure: we publish this guide. If you have a Mac mini at home and don't mind babysitting it, do that. If you don't, Standby is what we built.
4. AWS WorkSpaces / Azure Virtual Desktop
The enterprise-class options. ~$50–80/month for a 4 GB spec, 4 hours of setup, 99.9% reliability. Worth considering only if you're already deep in AWS or Azure for other reasons. For a single nomad's personal use, the price-to-benefit is poor.
Setting it up for nomadic life
If you go with a cloud desktop (path 3 or 4), the actual day-to-day:
- Pre-trip: install Microsoft Remote Desktop on your laptop, iPad, and phone. Free in app stores.
- Pair Dispatch from your Claude phone app so you can prompt the desktop without RDP.
- Schedule your tasks as normal in Claude Desktop. They run on the cloud machine, fire on its clock.
- While traveling: open Microsoft Remote Desktop on your phone or tablet, connect, check that everything looks healthy. Tasks should be showing results in their target inbox / Slack / wherever.
- If something breaks: RDP in, look at Claude Desktop, restart it if needed. Standby's status page (status.trystandby.com) shows infrastructure health.
Timezone edge cases
One subtle thing: your scheduled tasks run on the desktop's clock, not yours. If your scheduled task is "6 AM scan my inbox" and your cloud desktop is in US-East timezone, the task fires at 6 AM Eastern — which is 3 AM Pacific, 11 AM UK, etc. Three options:
- Set the cloud desktop's timezone to match your home base; scheduled tasks fire at "my home morning."
- Set it to UTC and schedule in UTC; predictable everywhere.
- Set it to your current travel timezone; harder because you'd have to change it every time you fly.
Standby asks you about timezone preference at signup. Default is your home timezone — most users want "my morning brief at my home morning, regardless of where I am."
Bonus: phone access for nomadic check-ins
Once your desktop is in the cloud, you have multiple ways to check on it from any device:
- Dispatch in the Claude phone app — pair once, then send Claude any prompt from your phone.
- Microsoft Remote Desktop for iOS and Android — full screen access. Free.
- AnyDesk, Jump Desktop — alternatives if you prefer them.
- Telegram MCP bridge (pre-installed on Pro and Business) — text Claude like a friend, get scheduled-task results via Telegram.
The honest pick for nomads
If you'll be traveling for more than a few weeks at a time, do not rely on a laptop you're carrying or a home machine you can't physically reach. Either move your Claude workflows to a Mac mini at home (cheap, if you own one) or to a managed cloud desktop (hands-off, $29/mo). The cost of debugging a missed scheduled task from a foreign country is higher than the subscription.