Cursor 3.5 Brings Automations Into the Agents Window, Plus Multi-Repo and No-Repo Automations
Cursor 3.5, released May 20, 2026, put Automations in the Agents Window, let one automation attach multiple repos or none, and added five no-repo Marketplace templates. As of October 2026, automations run as cloud agents billed at cloud agent rates; the launch week's 50% discount on new automations has ended.
Cursor 3.5, released May 20, 2026, moved Automations into the Agents Window and let an automation attach several repositories or none at all, so always-on agents can watch tools like Slack or Stripe as well as code. As of October 9, 2026, you can create automations from the Agents Window, cursor.com/automations, the /automate skill, or a Marketplace template, and they bill as cloud agent usage (Cursor docs).
Key Takeaways
- Agents Window: automations live beside your interactive agents, in addition to
cursor.com/automations(Cursor changelog). - Multi-repo: one automation can attach several repositories and work across them.
- No-repo: automations can run with no repository, for workflows that monitor tools and act on signals outside code.
- Five no-repo templates shipped to the Cursor Marketplace: Slack digest, product analytics, product FAQ, product finance, and customer health agents.
- Billing today: automations create cloud agents and bill at cloud agent rates. The launch week's 50% discount ended in late May 2026.
What's New in 3.5
Cursor says this release:
- Brings Cursor Automations to the Agents Window (in addition to
cursor.com/automations) (Cursor changelog) - Lets you configure automations with multiple attached repos (Cursor changelog)
- Adds no-repo automations for workflows that monitor tools and act on signals outside of code (Cursor changelog)
New No-Repo Templates
Cursor also added five no-repo templates to the Marketplace:
- Slack digest agent: summarizes unread DMs + key channels and prioritizes them by importance (Cursor changelog)
- Product analytics agent: weekly digest of key metrics from a data warehouse like Databricks (Cursor changelog)
- Product FAQ agent: watches a Slack channel for questions and drafts a first response based on docs, codebase context, and past threads (Cursor changelog)
- Product finance agent: pulls billing data from a provider like Stripe for recurring revenue reports (Cursor changelog)
- Customer health agent: monitors systems like Granola, Slack, and Databricks and flags accounts where health signals are shifting (Cursor changelog)
How Automations Work Now
Cursor's Automations docs describe the setup the same way on every creation path:
- Choose a trigger, such as every hour or when a pull request is opened.
- Write a prompt with instructions for the automation.
- Choose optional tools, such as Send to Slack, Comment on Pull Request, or tools from MCP.
- Choose whether the automation needs a repository, multiple repositories, or no repository at all.
- Save and activate it.
Triggers. Schedules use presets or a cron expression; event triggers cover GitHub, GitLab, Bitbucket Cloud, Slack, webhooks, Linear, and more. An automation can carry several triggers and runs when any one fires. For Slack and cron triggers Cursor defaults to no repository; source control triggers require at least one repo.
Billing. "Automations create cloud agents and are billed based on cloud agent usage." On team accounts, Run as Me bills the creator and Run as Service account bills the team's usage pool through a dedicated service account, so it draws on no member's personal usage.
Cursor-managed agents. The Automations page also hosts three agents Cursor runs for you: Bugbot, Security Agents, and PR Routing & Approval. Bugbot's review settings, including effort levels, are configured there.
Why It Matters
Automations are Cursor's "always-on agent" surface area. Moving them into the Agents Window makes it more likely teams actually maintain them -- because you can build, run, and supervise both interactive and scheduled/event-driven agents in one place. No-repo automations widen the audience beyond engineers: the five templates target product, finance, and customer success work.
For how Cursor Automations compare with Claude Code Routines, Codex, and other schedulers, see our scheduled agents comparison. For the cloud agent features automations build on, see Cursor Cloud Agents add event triggers, goals, and subagents.
Corrections and Updates
- October 9, 2026: This page described a 50% discount on agent runs for newly created automations as current; that 7-day launch offer ended in late May 2026, and automations now bill at standard cloud agent rates.
Sources
- Cursor changelog 3.5, "Improvements to Cursor Automations" (May 20, 2026), read 2026-10-09: https://cursor.com/changelog/05-20-26
- Cursor docs, "Automations" (getting started, billing, triggers), read 2026-10-09: https://cursor.com/docs/cloud-agent/automations
Read next
Related coverage- Claude Code
Scheduled AI Coding Agents in 2026: Claude Code Routines vs Cursor Automations vs Codex vs Warp vs Gemini CLI
Claude Code Routines and Cursor Automations both ship schedules, API calls and native source-control events, and Cursor's trigger set is widest. ChatGPT scheduled tasks add Gmail, Slack and GitHub pull-request triggers but no API or webhook. Warp orchestrates other vendors' agents. Gemini CLI has no scheduler and lost its free individual tier on June 18, 2026.
- Cursor
Cursor Cloud Agents Add Event Triggers, Long-Lived Goals, and Isolated Subagents
Cursor says Cloud Agents can now pick up work from events, keep working toward a long-lived goal, monitor pull requests, watch Slack threads, run scheduled tasks, and launch subagents in isolated virtual machines. The same update adds skill-based Custom Modes and less disruptive steering while an agent is working.
- Cursor
Cursor Bugbot Effort Levels: Low, Default, High, and Smart (Usage-Based Billing Required)
As of October 2026, Cursor Bugbot offers four effort levels: Low, Default, High, and Smart. Cursor launched Default, High, and Custom on May 11, 2026. Effort control requires usage-based billing, which replaced Bugbot's $40 per seat plan at each customer's first renewal after June 8, 2026. Repos can now set effort in a YAML file.
Frequently Asked Questions
What did Cursor 3.5 change about Automations?
Cursor 3.5, released May 20, 2026, made Automations available in the Agents Window in addition to cursor.com/automations, let you attach multiple repositories to one automation, and added no-repo automations for work outside code, with five new templates in the Cursor Marketplace.
Is the 50% discount on Cursor automations still running?
No. The May 20, 2026 changelog said all agent runs for newly created automations were 50% off for the next 7 days, so the offer ended in late May 2026. Automations now bill as cloud agent usage at standard cloud agent pricing.
How are Cursor automations billed?
Automations create cloud agents and are billed on cloud agent usage. On team accounts, Run as Me bills the creator, while Run as Service account bills the team's usage pool through a dedicated service account. Personal accounts always bill to the owner.
What can trigger a Cursor automation?
Cursor's docs list schedules (presets or a cron expression) and events from GitHub, GitLab, Bitbucket Cloud, Slack, webhooks, Linear, and more. An automation can have several triggers and runs when any of them fires. Slack and cron triggers default to no repository.