Run Claude Code in the Cloud: Routines vs VPS vs OpenHelm

"Can I run Claude Code in the cloud?" comes up constantly, and it's really a proxy for a more specific problem: your laptop can't be the thing standing between a scheduled job and it actually running. It goes to sleep. It gets closed. It goes on holiday with you while the job you wanted to run stays behind.

There are three genuinely different answers to that problem, and each one gets recommended online as though it's the only sensible choice. It isn't, they suit different people. This is a direct, honest comparison of all three: Anthropic's own cloud Routines, a self-managed VPS, and OpenHelm running locally.

Key Takeaways

• Claude Code Routines (Anthropic's cloud scheduler) is the lowest-effort option, but caps you at 5 runs/day on Pro or 15/day on Max, and only sees your git repository, not your local filesystem. See Anthropic's Claude Code documentation for the current specification.
• A self-managed VPS removes the run cap entirely for roughly $4–8 a month, but you're now responsible for monitoring, retries, and uptime yourself.
• OpenHelm runs locally on macOS with full filesystem access, no run cap, and built-in silence detection and self-correction, at the cost of needing your Mac powered on.
• None of the three are mutually exclusive. Plenty of developers run Routines for simple repo-scoped jobs and a second tool for anything needing local files or tighter reliability.

The Three Ways to Run Claude Code Without Your Laptop Open

Claude Code Routines is Anthropic's native, cloud-hosted way to schedule Claude Code tasks. It clones your git repository into a managed cloud environment and runs your task there, no server of your own required.

A self-managed VPS is a rented Linux server you configure yourself, install Claude Code on it, and keep it running with tmux or systemd. Full control, full responsibility.

OpenHelm is a macOS desktop app (our product) that schedules and monitors Claude Code jobs running locally on your own Mac, against your actual filesystem, while you're away from it.

All three solve "my laptop can't be the bottleneck." They solve it in genuinely different ways, with different trade-offs attached.

Option 1: Claude Code Routines

Routines launched as Anthropic's answer to exactly this problem: scheduled, unattended Claude Code execution without you managing any infrastructure. You define a routine, it clones your repo into a cloud sandbox, runs your task, and reports back.

What's good about it: zero infrastructure. No server to patch, no SSH keys to manage, no monthly VPS bill. It's built by the same team that builds Claude Code, so it's tightly integrated with the product.

What limits it: a daily run cap, five runs a day on the Pro plan, fifteen on Max, and a git-clone model rather than access to your actual local filesystem. If your task needs to read files outside version control, a local database, credentials on disk, cached build artefacts, Routines can't see them. It's built for repository-scoped work, which covers a lot of coding tasks and misses everything that isn't.

Option 2: A Self-Managed VPS

The DIY path: rent a Linux server, install Claude Code, keep a session alive with tmux or systemd, schedule with cron or systemd timers. We cover the full process in our Claude Code VPS setup guide, this is the honest summary for comparison purposes.

What's good about it: no run caps, no vendor lock-in, and it works identically whether you're on macOS, Windows, or Linux day to day, the server doesn't care what you develop on. Cost is genuinely low, $4–8 a month for a basic instance.

What limits it: you're now the systems administrator. Silence detection, retry logic, run history, monitoring, none of that exists unless you build it, on top of the systemd service management most of this relies on. That's not a small omission, it's most of what makes unattended execution actually reliable rather than just technically possible.

Option 3: OpenHelm on a Local Mac

OpenHelm takes a different premise entirely: rather than moving execution to the cloud or to a rented server, it keeps Claude Code running on your own Mac, against your actual project, your actual filesystem, your existing subscription, while you're away from the keyboard.

What's good about it: full local file access (no git-clone limitation), no daily run cap, silence detection that kills hung sessions after ten minutes of no output, and a self-correction loop that retries failed jobs with the failure context passed back to Claude Code. Structured run history means checking last night's jobs is a glance at a dashboard, not a log file archaeology exercise.

What limits it: it's macOS only, and it depends on your Mac being powered on and awake (though not unlocked, or you present) when a job is due to run. If your Mac genuinely goes offline, Routines or a VPS will outperform it.

Head-to-Head Comparison

Which Should You Actually Choose?

Pick Routines if: your task lives entirely inside a git repository, you're comfortable with five to fifteen runs a day, and you want zero infrastructure to think about. It's the lowest-effort option by a wide margin, provided your workload fits inside its constraints.

Pick a VPS if: you're on Linux or Windows day to day, you need more than fifteen runs a day, or you specifically want infrastructure you control end to end. Be honest with yourself about the maintenance commitment, it's real, and it doesn't show up on the invoice.

Pick OpenHelm if: you're on a Mac, your tasks need access to files outside version control, and reliable unattended execution (silence detection, retries, a run history you can actually read) matters more to you than avoiding a native app. It's the closest thing to "set it up once and stop thinking about it" of the three, with the one honest caveat that your Mac needs to stay on.

A reasonable number of developers end up running more than one of these. Routines for pure repo-scoped tasks that fit the run cap, OpenHelm for anything touching local files or needing tighter reliability guarantees. They're not mutually exclusive, they're tools for slightly different jobs wearing the same "run it in the cloud" search query.

"I tried Routines first because it needed zero setup. Hit the run cap within a week once I had more than a couple of scheduled tasks, and half of what I wanted to automate needed local file access anyway. Ended up on OpenHelm for the actual dev work and kept Routines for one simple repo-only job."

>, Developer in the OpenHelm community Slack, July 2026

FAQ

Can I run Claude Code fully in the cloud with no local machine involved?

Yes, via Claude Code Routines. It clones your repository into a cloud sandbox and runs there, no server or local machine required for execution, though you'll trigger and configure it from wherever you normally work.

What's the cheapest way to run Claude Code unattended?

A self-managed VPS is the lowest raw cost, roughly $4–8 a month. Routines is included in your existing Claude Code plan up to the run cap. OpenHelm has a free tier that covers a meaningful number of jobs before you'd need to upgrade.

Why would I choose a VPS over Routines if it's more work?

Two main reasons: no daily run cap, and full control over the environment, useful if your tasks need dependencies, local services, or configuration that a cloud sandbox doesn't support.

Does OpenHelm work on Windows or Linux?

No, OpenHelm is macOS only. For Windows or Linux, Routines or a self-managed VPS are your realistic options, our guide to open source Claude Code schedulers covers cron and community tooling for those platforms specifically.

Which option has the most reliable unattended execution?

On paper, OpenHelm's silence detection and self-correction loop are purpose-built for exactly this problem. A VPS can match that reliability, but only once you've built the monitoring yourself, it isn't there by default. Routines' reliability characteristics for long-running or hung jobs aren't fully published at the time of writing.

There's no universally correct answer here, only the right fit for your platform, your workload, and how much infrastructure you actually want to own. If you're on a Mac and haven't tried the local route yet, OpenHelm's free tier is the fastest way to find out whether it fits before you commit to a VPS bill or hit Routines' run cap. And if local files and a Mac aren't your situation, the VPS setup guide has the full walkthrough for the self-managed path.