Claude Code Routines: Run AI Agents 24/7 Without Your Laptop

Key Takeaways

• Routines run on Anthropic's cloud infrastructure (4 vCPUs, 16 GB RAM, 30 GB disk per run) — your laptop does not need to be on or even connected to the internet.
• The most common setup mistake: API keys from your local .env file are gitignored and invisible to the cloud run. Store them in the Cloud Environment's environment variables section and explicitly tell your prompt to read them from the environment, not from .env.
• Three trigger types: schedule (minimum 1-hour interval, set in natural language), API call (send a curl request to fire the routine), and GitHub events (new PR, push, issue, or release).
• Session limits per day: 5 on Pro, 15 on Max, 25 on Team/Enterprise. Hitting the cap triggers metered overage for orgs with that enabled.
• Network access modes: Trusted only allows Anthropic-vetted domains (version control, major cloud providers). Full allows all outbound requests — required for third-party APIs like ClickUp. Understand the tradeoff before switching to Full.
• Each run is stateless — the cloned GitHub repo is destroyed after completion. Commits to your branch persist; local files, browser cookies, and cached credentials do not.

Routines vs. Scheduled Tasks vs. /loop

Nate compares the three Claude automation modes side by side:

• Routines: cloud-based, no machine required, survive restarts, minimum 1-hour interval, stateless (no local file access), fully autonomous.
• Desktop scheduled tasks: local, machine must be on, survive restarts, can run every minute, full local file access, configurable permissions.
• /loop: local, machine must be on, does NOT survive restarts (session-bound), any interval, full local file access.

The right choice depends on your use case. If you need local file access, browser session state, or sub-hour triggers, stick with desktop scheduled tasks. If you need the automation to run while you travel or sleep without leaving a machine on, Routines are the answer.

Setup in Practice: What Actually Works

Based on Nate's live testing, the fastest path to a working routine:

1. Create a dedicated GitHub repo for the routine (not your full project repo — the cloud clones the entire repo, so keep it lean).
2. Add any API keys you need to the Cloud Environment → Environment Variables section in the Claude desktop app or web interface.
3. Write the routine prompt with an explicit instruction like: "My YouTube API key is available as an environment variable. Use it directly from the environment, not from .env."
4. Use Run Now to test before scheduling — you can watch it execute live and inject corrections.
5. If your routine uses a non-standard API (not on Anthropic's trusted list), set Network Access to Full in the Cloud Environment settings.

Related on OpenClawDatabase

• Claude Cowork Setup Guide — getting started with Claude Code and Cowork environments
• Claude Routines vs N8N — Nick Saraev on why Routines replace no-code automation platforms entirely
• Claude Managed Agents Reviewed — Nate's earlier take on managed agents and where Routines fill the gaps