March 26, 2026
Set it and forget the bill?
Schedule Claude Code tasks on the web
Claude runs your code chores while you sleep - but users smell a token trap and a 3-task cap
TLDR: Claude can now run recurring coding chores in the cloud, but commenters are split between hype for hands‑off automation and worry about opaque costs and limits like a 3‑task cap. Fans see a step toward fully automated software, skeptics see “announce here, restrict there” confusion and potential surprise bills.
Claude just rolled out “scheduled tasks” for Claude Code on the web — think a robot assistant that checks pull requests, summarizes test failures, and updates docs on a schedule, even when your computer’s off. You can set it up in the desktop app, web, or via the CLI, choose a cloud environment with network and secrets, and have it clone your repos and push changes on its own. The cloud version runs minimum every hour, local versions can go every minute. Sounds dreamy, right? The comments, however, are spicy.
The loudest chorus: money nerves. One user wonders if this is “just a way to make you forget you’re spending money on tokens,” while another presses for the real compute costs and how long jobs can run. Then there’s the limits drama: a Max-tier user says they hit “only 3 cloud scheduled tasks,” which turned excitement into side-eye. And yes, a separate thread fumed that feature launches show up on the site while usage restrictions trickle out via a team member’s tweet — a classic “announce in blog, limit on X” moment.
Meanwhile, optimists are hyped: one says we’re “one or two steps” from a fully automated software loop — feedback to ticket to pull request to deployment, all by bots. Memes call it “cron with vibes,” a “set-it-and-forget-it coffee machine for code,” and a “to‑do list for bots.” Progress or rug pull? The feed can’t decide.
Key Points
- •Claude Code on the web supports scheduled tasks that run prompts on recurring schedules in the Anthropic cloud or on a user’s machine.
- •Cloud tasks run autonomously without a local machine or open session, are persistent across restarts, and have a 1-hour minimum interval; local tasks can run as frequently as every 1 minute.
- •Tasks are created via the web/desktop form or the CLI (/schedule), with a self-contained prompt, model selection, and optional GitHub repos that are freshly cloned each run.
- •A cloud environment controls network access, environment variables, and setup scripts; a Default environment is available, and custom environments can be precreated.
- •Schedules offer hourly, daily (default 9:00 AM local), weekdays, and weekly options with time zone handling; custom intervals are configured via /schedule update, and each run creates a reviewable session.