Scheduled AI Coding Agents in 2026: Claude Code Routines vs Cursor Automations vs Codex vs Warp vs Gemini CLI

The April 2026 wave of AI coding tooling brought a new question into every team's planning meeting: which platform should run your unattended agents? In the last six weeks, Claude Code Routines shipped, Cursor Automations launched, Codex added recurring tasks, Warp wrapped four CLI agents under one cloud platform, and Gemini CLI doubled down on headless mode. Five vendors, five different answers. This guide compares all five so you can pick the one that fits your existing stack and the triggers you actually need.

Key Takeaways

• Routines and Cursor Automations are the only "full triple" managed products
• Codex Automations is schedule-only (cloud-trigger expansion on roadmap, not shipped)
• Warp adds scheduling around other vendors' agents (universal wrapper model)
• Gemini CLI offloads scheduling to the OS -- DIY only
• Pick by: trigger types you need, plan you already have, agents you already use

Why Scheduled Agents Matter in 2026

The shift from "agent you start" to "agent that starts itself" is the biggest behavioral change in AI coding tooling this year. A scheduled agent does not need you at the keyboard, so it can sweep stale PRs at 3am, classify issues as they land, verify deploys hourly, and post a digest before standup. Work that used to require a person opening a terminal can now happen on its own and surface only when there is something to look at.

Triggered agents go a step further. An agent wired to a webhook or a GitHub event reacts to the world: a release ships, the agent writes the notes; a PR opens, the agent labels and assigns it; an alert fires, the agent triages and posts a summary. The agent stops being a tool you reach for and becomes a workflow component other systems can call.

The five platforms in this guide reach for that outcome with different shapes. Two ship the full trigger set in one managed product, one ships only schedules, one wraps other agents under its own scheduler, and one provides the agent and leaves scheduling to you. Picking well is mostly about matching the platform to your existing stack and to the triggers you need, not about which has the smartest model.

The Five Contenders

Claude Code Routines is Anthropic's managed scheduler-and-trigger product, launched April 14, 2026 as a research preview. A Routine is a saved Claude Code configuration -- a prompt, one or more repos, and a set of MCP connectors -- that Anthropic runs in the cloud whenever a trigger fires. Routines support cron schedules (1-hour minimum interval), an HTTP API endpoint with a per-routine bearer token, and direct GitHub event subscriptions for pull_request and release with filters. Setup happens at claude.ai/code/routines, in the Claude Desktop app, or through the Claude Code CLI via /schedule. GitHub triggers require the Claude GitHub App. Routines is bundled into Pro, Max, Team, and Enterprise with daily caps of 5, 15, 25, and 25 runs per day. No free tier.

Cursor Automations is Cursor's always-on cloud-agent product, launched March 5, 2026. Each Automation spins up a fresh sandbox per run, follows the prompt, and verifies its own output before reporting back. Triggers cover schedules, a wide event set (Slack message, Linear issue, GitHub PR merge, PagerDuty incident), and custom webhooks. The product is distinct from Cursor's Background Agents (in-editor async tasks) and Remote Agents (control any machine); Automations is the cloud-managed scheduled-trigger surface. Configuration happens in the cursor.com/dashboard automations panel, where you specify the repo, prompt, MCP servers, model, and trigger source. Automations runs on Cursor's paid plans; no free tier for cloud-agent usage.

Codex Automations is OpenAI's recurring scheduled-task feature inside the Codex app. You name a task, attach a project, write a prompt, and pick a cron-style schedule. Local automations require the machine they were created on to be running; cloud automations are set-and-forget on OpenAI's infrastructure and land results in a review queue. The trigger set is narrow: schedule only. There is no native GitHub-event trigger, no general webhook, no API trigger; cloud-trigger expansion ("on GitHub push after midnight") is publicly on the roadmap but has not shipped. Codex Automations is bundled with the Codex tiers inside ChatGPT Plus, Pro, Business, and Enterprise.

Gemini CLI does not ship a scheduler. The CLI is headless-capable through the -p flag, and Google ships built-in templates for summarize-folder, daily-briefing, and file-watcher, but the scheduling primitive is whatever your OS provides. In practice that means a system cron entry running gemini -p "..." and piping output where you need it. The free tier is generous (25 requests per day on Pro, 1500 per day on Flash), so this is the only path on the list that costs nothing if you wire the cron yourself. Note that the Gemini app's scheduled actions and Gemini Enterprise's agent scheduling are separate products; this guide is about the CLI.

Warp Skills (Oz) takes a different shape. A Skill is a version-controlled config file that defines a repeatable agent task, and Warp's Oz cloud platform (launched February 10, 2026) orchestrates Skills on a schedule, on a webhook, on a system event, or on a manual run. Crucially, Warp's Universal Agent Support released April 14, 2026 lets a Skill wrap Claude Code, Codex, Gemini CLI, or OpenCode -- but the scheduling layer is Warp's own, not delegated to the wrapped CLI. Triggers cover cron, webhooks, system events like crashes and bug reports, Slack interactions, and manual runs. Pricing is credit-based: CLI and API runs need credits with a 20-credit minimum, and Slack or Linear integrations require the Build, Max, or Business plan.

Trigger Comparison (Schedule, API, Event, Webhook)

The single most important question when picking a platform is: which triggers do you need? Schedule covers cadenced work like nightly sweeps and hourly verifications. API triggers let any system that can POST to a URL fire the agent, covering release scripts, deploy hooks, and cross-tool chains. GitHub event triggers let the agent react to repo activity directly, without you owning the wiring. Custom webhooks give you the same reactivity for anything outside GitHub.

| Tool | Schedule | API | GitHub event | Custom webhook | Free tier | |---|---|---|---|---|---| | Claude Code Routines | Yes | Yes | Yes (PR, Release) | via API | No (Pro+) | | Cursor Automations | Yes | via webhook | Yes | Yes | No | | Codex Automations | Yes | No | No (roadmap) | No | No | | Gemini CLI | Via system cron | DIY | DIY | DIY | Yes | | Warp Skills (Oz) | Yes | Yes | Via webhook | Yes | Credit-based |

The matrix tells the story. Claude Code Routines and Cursor Automations are the only platforms that ship the full triple of schedule, API, and native event triggers in one managed product. Routines covers GitHub directly via the Claude GitHub App; Cursor leans on its broader event source list -- Slack, Linear, PagerDuty, GitHub -- to get there. Codex sits at the narrow end, supporting only schedule today, with cloud-trigger expansion still on the roadmap. Warp covers schedule, API, and webhooks, and reaches GitHub events through a webhook bridge rather than a direct integration. Gemini CLI is the outlier: no scheduler, every trigger on its row wired yourself.

The "via API" cells matter. A platform with a Routine-style HTTP endpoint can be glued to anything via one curl command, which means you can fake a webhook-style trigger by having the upstream system POST to the endpoint. That is how Routines reaches custom webhook use cases without shipping a webhook trigger of its own; the API endpoint is the webhook, just from the agent's side rather than the source's side.

Pricing Comparison

Pricing on this list is unusually messy because four of the five products are bundled into broader subscriptions, and the fifth is credit-based.

Claude Code Routines is bundled into Anthropic's existing paid plans with daily run caps. Pro gets 5 routine runs per day, Max gets 15, Team gets 25, and Enterprise gets 25. There is no separate per-run charge inside those caps and no free tier; if you do not have a paid Claude plan, you do not have access. The cap is enforced at the run level, not at the trigger level, so a Routine wired to a noisy GitHub trigger can blow through the daily cap before lunch on a busy repo.

Cursor Automations runs on Cursor's paid plans as cloud-agent usage. There is no free tier for the Automations surface, and the cost shape mirrors Cursor's broader cloud-agent billing. If you are already paying for Cursor, Automations is incremental usage on the same account rather than a new line item.

Codex Automations is bundled with the Codex feature inside ChatGPT's paid tiers (Plus, Pro, Business, Enterprise). There is no separate SKU. If your team already pays for ChatGPT Plus or higher and uses Codex as the coding surface, Automations is included.

Gemini CLI is free at the Pro tier (25 requests per day) and Flash tier (1500 requests per day), which is enough to run several scheduled scripts a day for free. The pricing tradeoff for "free" is the missing scheduler -- you write the cron, you maintain the host, you handle the failures.

Warp Skills (Oz) uses Warp's credit model. CLI and API runs draw credits with a 20-credit minimum per run, and Slack or Linear integrations are gated to the Build, Max, or Business plan. Warp's free tier covers some credit usage, but heavy parallel use exhausts the budget quickly. The credit shape matters because Warp wraps other vendors' agents -- the credits cover Warp's orchestration, but the underlying LLM calls still draw on whichever agent you wrapped.

The practical headline: if you already have a paid plan with Anthropic, OpenAI, Cursor, or Warp, you already have access to that vendor's automation product. The interesting question is rarely "which is cheapest" and almost always "which is included in something you already pay for."

Which to Pick (Decision Tree by Scenario)

The fastest way through this is to match your existing stack and your trigger needs against the five contenders, in order:

1. Already on a Claude paid plan and want GitHub-event triggers? Pick Claude Code Routines. This is the case where Routines is the obvious answer -- the GitHub App integration is direct, the API endpoint is per-routine, and the schedule trigger is built in. The 5/15/25 daily caps are the constraint to plan around, but for 2-4 high-value Routines per repo on Max or Team, the budget fits comfortably. See the Routines deep-dive for setup walkthroughs and the five Routines worth building first.

2. Already in Cursor and need richer event sources (Slack, Linear, PagerDuty)? Pick Cursor Automations. Cursor's event coverage is the broadest in the comparison, which makes it the right pick if your incident or product workflow already runs through one of those tools. The cloud-agent shape -- fresh sandbox per run, self-verifying output -- is the same shape you already use elsewhere in the Cursor product family. Webhook support handles anything outside the named integrations.

3. Already in ChatGPT Plus or Pro with Codex and your use case is simple cron? Pick Codex Automations. If all you need is "run this Codex prompt every morning at 8am on this project," and you do not need to react to GitHub or external systems, Codex Automations is bundled and ready. The schedule-only constraint is real -- if you need event triggers later, you will have to migrate, since the cloud-trigger expansion is still on the roadmap. For pure cron use, the simplicity wins.

4. Already in Warp and want a scheduling layer over your existing agent of choice? Pick Warp Skills/Oz. Warp's universal wrapper model is unique in this list. If you have settled on Claude Code, Codex, Gemini CLI, or OpenCode for interactive work and you want one scheduling layer on top of all of them, Warp is the only platform that gives you that. The Skill-as-config-file shape also means your scheduled agents live in version control next to your codebase, which is a fit for teams that want change history on their agent definitions.

5. Want free and willing to wire it yourself? Pick Gemini CLI plus system cron. This is the path for solo developers and homelab tinkerers who do not want to add another paid SaaS. Write a cron entry that runs gemini -p "...", pipe the output to a log or to Slack via curl, and you have a scheduled agent for $0 of vendor cost. The tradeoff is everything in the "DIY" column of the matrix -- you own the host, the scheduler, the failure handling, and the secrets. For one or two scripts that just need to run on a timer, this is a very reasonable choice.

A note on MCP. Four of the five platforms support MCP connectors at runtime, so the agent can talk to Slack, Linear, GitHub, Google Drive, and the rest of your stack without you wiring REST calls by hand. Pick from the MCP servers worth plugging in today before you build the first scheduled agent; the connector list is what turns "the agent runs" into "the agent does something useful."

What Is Coming Next

Three concrete shifts are visible on the published roadmaps and recent launches.

Codex cloud-trigger expansion. OpenAI has stated publicly that cloud-trigger support -- the "on GitHub push after midnight" example they have used -- is on the Codex Automations roadmap. When it ships, Codex will move from schedule-only into the same trigger band as Routines and Cursor Automations. Until then, Codex remains the schedule-only option.

Convergence on the trigger triple. Routines and Cursor Automations both shipping schedule plus API plus events suggests the industry is settling on that triple as the baseline for a "complete" automation product. Expect Codex to close the gap, expect Warp to keep adding direct integrations alongside its webhook bridge, and expect any new entrant in this space to ship the full triple from day one rather than start narrow.

Universal wrapping versus native integration. Warp's bet that one cloud platform can schedule any agent is genuinely different from the other four, which bet that you pick a vendor and live in their automation surface. Which one wins is downstream of whether teams standardize on one agent (favoring native integration) or multi-source their agents by task (favoring universal wrapping). Both shapes coexist on current trends; the question for your team is which side of that split you sit on.

The five platforms here will not be the final list. The interesting six-month question is not "which one wins" but "what does the trigger set look like once Codex catches up and the next vendor enters." For now, pick by stack fit, trigger fit, and plan fit, in that order. The right answer is usually the one already included in something you already pay for.