Cursor 3.5 brings multi-repo and no-repo Automations to the IDE's Agents Window

Cursor released version 3.5 on May 20, 2026, centering the update on its Automations feature with two new operating modes, an in-IDE entry point that removes the browser requirement, and five pre-built agent templates on the Cursor Marketplace.

What

Per Cursor's changelog, Automations are now accessible from the Agents Window inside the IDE, where users already manage their agents. Previously, reaching them meant opening the external web interface at cursor.com/automations. With 3.5, you can create and manage Automations from the same workspace as other agent work, without leaving the editor.

Two new configuration modes ship with the release. Multi-repo Automations let a single automation attach to multiple code repositories at once, so an agent can reason across all attached context and deliver, test, and verify work that spans more than one codebase. No-repo Automations go the other way: they drop the repository requirement entirely, allowing agents to run monitoring or reporting tasks that have no direct connection to a codebase.

Five templates landed on the Cursor Marketplace at launch to accompany the no-repo mode, per the changelog:

Slack digest agent: summarizes unread direct messages and key Slack channels each morning and prioritizes them by importance.
Product analytics agent: delivers a weekly digest of key metrics from a data warehouse such as Databricks.
Product FAQ agent: watches a Slack channel for questions and drafts a first response drawing on docs, codebase context, and past threads.
Product finance agent: pulls financial data from a billing provider such as Stripe for recurring revenue reports.
Customer health agent: monitors key systems including Granola, Slack, and Databricks and flags accounts where health signals are shifting.

All agent runs on newly created Automations are 50% off for seven days from the May 20 release date, per the Cursor announcement.

Why it matters

Pulling Automations into the Agents Window removes the context switch between the editor and the browser for teams already using them. Before 3.5, creating or managing an Automation meant navigating to cursor.com/automations in a web browser, which kept the feature at a distance from the moment-to-moment development workflow. Now the full setup and monitoring loop can stay inside the editor.

Multi-repo support closes a specific gap for developers running work across monorepos or service-oriented architectures. A single feature change often touches a shared component library, a backend service, and a frontend application at the same time. Cursor's changelog describes the multi-repo mode as allowing an agent to "reason across all required context and work across repos to deliver, test, and verify tasks." That is a vendor-attributed capability description, not an independently benchmarked result. Still, it addresses a workflow pattern that single-repo automations could not handle without manual coordination across multiple agent sessions.

There is a second signal in the no-repo templates: a direction for the product beyond pure code editing. Four of the five launch templates connect to Slack, Stripe, Databricks, or Granola rather than to a source code repository. The Slack digest agent, the product analytics agent, the product finance agent, and the customer health agent all lean toward recurring business operations tasks. The fifth template, the product FAQ agent, does use codebase context alongside docs and past threads, yet its primary trigger is a Slack channel rather than a code push. In short, Cursor is testing whether the agent infrastructure it built for software development can also serve a broader category of recurring operational work.

One more detail on the promotion: the seven-day 50% discount on newly created Automations applies to agent runs only, per the announcement, and is time-bound from the release date. Developers evaluating the feature have until approximately May 27, 2026, to take advantage of the promotional pricing on new Automations.

Context and reactions

Cursor shipped version 3.0 in early 2026 with the Agents Window as a central organizing surface for background agent work. Introduced as the interface for running persistent, interruptible agents alongside normal editing, that window became the conceptual anchor for longer-horizon tasks in Cursor. Version 3.5 extends it by making Automations, which are scheduled or event-triggered agent runs, a first-class part of the Agents Window rather than a separately hosted product.

Those five new templates are published on the Cursor Marketplace, the distribution channel for agent templates across Cursor's Cloud Agents infrastructure, per cursor.com/marketplace. The announcement does not state the total template count available across all categories in the Marketplace.

Cursor is developed by Anysphere, Inc. In the hours following the release, no independent benchmarking or analysis of the new Automations capabilities had been published.

What to watch next

Will no-repo Automations support additional data-source connectors beyond the integrations shown in the five launch templates? Cursor has not said. The Marketplace template catalog is worth checking weekly for new additions that signal which integration categories Anysphere is prioritizing next. Nor has the company confirmed whether the 50% promotional pricing on newly created Automations will extend beyond the seven-day window or become a standard introductory offer going forward.

For supported configuration options, the most current reference is Cursor's Automations docs page, linked from the changelog.

Sources

Improvements to Cursor Automations -- Cursor official changelog, May 20, 2026