3.5  · Changelog

Improvements to Cursor Automations

This release brings Cursor Automations to the Agents Window and introduces the ability to configure automations with multiple attached repos or no repos at all.

For the next 7 days, all agent runs for newly created automations are 50% off.

Automations in the Agents Window

Cursor Automations are now available in the Agents Window, in addition to cursor.com/automations. Create and manage your automations in the same workspace as your agents.

Multi-repo automations

A lot of engineering work spans more than one codebase. You can now attach multiple repos to an automation so agents reason across all required context and work across repos to deliver, test, and verify tasks.

No-repo automations

Many useful automations exist apart from code, where agents monitor your tools and act on key signals. You can now create automations without an attached repository.

We've added five new templates for no-repo automations to the Cursor Marketplace to help you get started:

  • Slack digest agent: Summarizes unread DMs and key Slack channels every morning and prioritizes them by importance
  • Product analytics agent: Delivers a weekly digest of key metrics from your data warehouse like Databricks
  • Product FAQ agent: Watches a Slack channel for questions and writes a first response based on docs, codebase context, and past threads
  • Product finance agent: Pulls financial data from a billing provider like Stripe for recurring revenue reports
  • Customer health agent: Monitors key systems like Granola, Slack, and Databricks and flags accounts where health signals are shifting

Read our docs to learn more.

 · Changelog

Cursor in Jira

Cursor is now available in Jira.

Assign work items to Cursor, or mention @Cursor in a comment to kick off a cloud agent. Cursor uses the work item title, description, comments, and your team's repository settings to scope the task.

You can ask Cursor to fix bugs, add features, update tests, or investigate something described in the ticket. When the agent finishes, Jira shows completion updates and includes a link to the pull request.

Install the integration from Cursor integrations. You need Cursor admin access and Jira Commercial Cloud with Rovo enabled. Learn more in our docs.

 · Changelog

Composer 2.5

Composer 2.5 is now available in Cursor.

It's a substantial improvement in intelligence and behavior over Composer 2. It is better at sustained work on long-running tasks, follows complex instructions more reliably, and is more pleasant to collaborate with.

Composer 2.5 benchmark resultsComposer 2.5 benchmark results
  • Standard: $0.50/M input, $2.50/M output tokens
  • Fast (default): $3.00/M input, $15.00/M output tokens

Composer 2.5 includes double usage for the first week. See our model docs for full details.

Read more in our announcement.

3.4  · Changelog

Full-screen Tabs and Compact Chats

This release introduces quality-of-life improvements to the Agents Window.

Full-screen tabs

Full screen maximizes the right panel so you can focus on a single tab.

Files, changes, canvases, PRs, browsers, and terminals can expand to fill the entire working area. This replaces the agent chat with a floating prompt bar.

Enter and exit full screen by clicking on the expand/contract button in the panel header, using the command palette, or pressing Cmd/Ctrl+Shift+M.

Compact chat responses

Compact chats give you a tighter view of your agent conversations so you can read threads more quickly without losing important context.

Customize tool call density to control how much of the agent's tool activity is shown in each response:

  • Compact: shows concise results with minimal tool traces
  • Balanced: includes important intermediate steps
  • Detailed: provides near-complete step-by-step context

  • Improved PR tabs by adding clearer review states, better reviewer/thread visibility, and more predictable PR tab actions.
  • Improved long-chat scrolling to make it smoother, added better undo grouping in prompt input, and improved behavior while streaming.
  • Added clearer status text for background/resumed tasks.
  • Added cleaner environment/repo selection and better persistence when switching contexts.
  • Improved MCP auth token lifecycle handling.
  • Removed noisy in-app terminal notifications and improved shortcut behavior.
  • Clarified model naming and selection behavior in the model picker and added stronger fallback handling.
  • Improved search and navigation to make it faster and more reliable in large workspaces.

  • Fixed PR tab bugs affecting branch lookup, header state, and diff loading.
  • Fixed background task reliability issues like resume failures, interrupt edge cases, and incorrect status scoping on resumed subagents.
  • Fixed cloud agents bugs blocking setup, state merge/persistence bugs, and multi-repo identity issues.
  • Fixed MCP/OAuth reliability bugs like transient 401/stale-token cases and large-token handling edge cases.
  • Fixed edge cases around slash menu + approval regressions, ask-question flow issues, and paste-chunk handling.
  • Fixed keyboard shortcuts bugs in modals, vim/emacs caret style leakage, and other key handling.
  • Fixed hook invocation/path-length issues and Git prompt-related regressions.
  • Fixed model-routing mismatches, proxy body normalization, and thought-chunk forwarding issues.
  • Fixed webhook auth/hostname resolution, GHES installation persistence, and mirrored-repo behavior.

3.4  · Changelog

Development environments for cloud agents

To take engineering tasks from start to finish, agents need a development environment similar to the setup on your laptop: cloned repositories, installed dependencies, credentials for internal toolchains, and access to build systems.

This release introduces new tools for teams to configure development environments for their agents. Cursor also can use these tools to set up and maintain environments for you. Together, this makes it easier for teams to run fleets of parallelized agents that handle tasks from end-to-end, inside development environments you fully control.

Multi-repo environments

Cloud agents and automations now support multi-repo environments, building off our work on multi-root workspaces. You can configure a single environment with all the repositories an agent needs for its work, with re-use across sessions.

Environment configuration as code

To make it easier to change, debug, and review environment definitions, we have improved Dockerfile-based configuration.

This includes support for build secrets, making it easy to securely access private package registries directly from your Dockerfiles. Build secrets are scoped to the build step and aren't passed to the running agent's environment.

Environment configuration as code

We've also upgraded layer caching, so that only the updated layers of your image rebuild when you change the Dockerfile. Builds that hit the cache run 70% faster.

Improved agent-led environment setup

As Cursor configures your environment, it will ask you questions, flag missing credentials, and validate that your environment is set up properly.

Improved agent setup

Cursor will always show you the version of the environment your agent is running in. If your environment configuration fails, it will default to a base image with clear warning signs so that your cloud agents can keep running instead of immediately failing.

Environment governance and security controls

Every development environment now has its own version history that users can review and roll back. Admins can also restrict rollback permissions to admins only. An audit log captures every action team members take on environments, giving security teams full visibility into who changed what.

Egress and secrets can now be scoped at the development environment level. Secrets configured for one environment aren't accessible from any other.

Learn more about agent development environments in our announcement and docs.