Claude Code turned routines into cloud sessions triggered by schedules, HTTP API calls, or GitHub events. My read is simple: Anthropic is not shipping a cute automation add-on here. It is trying to own the always-on runtime layer for coding agents. Once prompts, repos, environments, and connectors are packaged together, and the result can hand back to a local session later, this stops looking like a chat assistant and starts looking like a lightweight CI-plus-agent operator.
I buy the direction because it patches a real weakness in Claude Code’s earlier shape. The local experience was strong, but it effectively went offline when the developer did. Over the last year, OpenAI kept pushing cloud-resident agent behavior through its app and API stack, and GitHub Copilot has long been embedding itself into PRs, reviews, and workflow hooks. Anthropic wiring Claude Code into GitHub events is not novel by itself. The timing is the point. A local-first coding tool without an async execution layer usually caps out as a personal productivity tool instead of a team budget line.
I also have doubts. The article gives capability contours, but not the numbers that decide whether this is production-grade: pricing, concurrency limits, max runtime, secrets handling, network boundaries, supported connectors, rollback behavior. None of that is disclosed. Without those details, routines looks more like a strategic direction than an operationally credible platform feature. And I’m skeptical of the “your computer can be off” framing as the main pitch. Anything that runs shell, touches external services, and gets triggered by HTTP or GitHub events runs straight into security review and cost control. If Anthropic wants this to land beyond power users, the hard sell is auditability and permission isolation, not convenience.