Launch Cursor Automations in the Agents Window
TL;DR
Manage Cursor Automations directly within the Agents Window. This update also introduces support for multi-repo automations to reason across codebases, and no-repo automations with pre-built templates for Slack, analytics, and finance tasks.
What changed
Cursor added Automations management inside the Agents Window on May 20, 2026. Users can now create and edit automations in the same interface as their agents instead of switching to cursor.com/automations. The update also added multi-repo support so one automation can pull context from several codebases at once.
No-repo automations arrived too, along with five Marketplace templates for Slack digests, product analytics from Databricks, FAQ responses, Stripe finance reports, and customer health monitoring. New automations receive 50 percent off agent runs for the first seven days.
Why it matters
Solo builders gain a single place to run both one-off agent tasks and recurring automations. Multi-repo support reduces the need to maintain separate scripts when work spans multiple repositories. No-repo options open the door to agents that watch Slack, billing data, or analytics without any code attachment.
The bet is that Cursor can become the default layer for both coding assistance and light operational monitoring. This directly competes with custom Zapier or Make setups that many Vibe Builders already run for the same signals.
How to use it
Open the Agents Window in Cursor and select the automations tab to create or edit flows. Templates live in the Cursor Marketplace at cursor.com/marketplace. Attach multiple repos during setup or choose the no-repo option and pick a pre-built template.
Access requires a Cursor account with cloud agent credits. Runs stay discounted for seven days after creation. Full configuration steps appear in the docs at cursor.com/docs/cloud-agent/automations.
Watch for
Confirm the bet if teams start replacing daily Slack summaries and metric reports with these agents. Watch for repeated failures on multi-repo context or delayed responses on no-repo triggers. The next expected move is deeper connections to additional data sources beyond the current five templates.
Who this matters for
- Vibe Builders: Use no-repo templates to monitor Stripe and Slack without writing or hosting custom scripts.
- Developers: Connect multiple repositories to a single automation to sync logic and context across your stack.
Harsh’s take
Cursor is aggressively moving into the operational automation space, positioning itself as a central hub for more than just code. By integrating multi-repo support and no-repo templates for Slack and Stripe, they are attacking the territory of Zapier and Make. This is a smart play for developer retention: if your monitoring and billing alerts live inside your IDE, you never have to leave the environment.
The 50 percent discount on agent runs for new automations is a clear incentive to migrate existing external workflows into Cursor. Operators should view this as a consolidation opportunity. Instead of maintaining a fragmented stack of glue-code scripts and third-party connectors, you can now centralize cross-codebase reasoning and business logic in one window.
It is a high-utility update that turns the IDE into a proactive operations center.
by Harsh Desai
About Cursor
View the full Cursor page →All Cursor updatesMore from Cursor
- App UpdateIntroduce full-screen tabs and compact chat in Agents Window
Maximize your workspace with full-screen tabs for files, terminals, and canvases in the Agents Window. This release also adds compact chat responses with customizable tool call density, alongside various performance improvements and bug fixes.
- IntegrationIntegrate Cursor with Jira to automate work items
Connect Cursor to Jira to assign work items or trigger cloud agents directly from comments using @Cursor. The agent uses ticket context to fix bugs, write tests, or implement features, automatically linking back to the resulting pull request.
- FeatureNew PR Review Experience and Parallel Building
Introduces a unified PR review interface with inline threads and commit history. New 'Build in Parallel' feature allows Cursor to execute independent plan tasks simultaneously using async subagents to speed up development.