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.
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.
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.
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.
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.
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.
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.
As Cursor configures your environment, it will ask you questions, flag missing credentials, and validate that your environment is set up properly.
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.
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.
Mention @Cursor in any Teams channel to delegate a task to a cloud agent or pull information from Cursor into Teams.
Cursor automatically picks the right repository and model based on your prompt and recent agent activity. It reads the entire thread for context before implementing a solution and creating a PR for your team to review.
Get started by installing the integration in the Cursor dashboard. Learn more in our docs.
Teams admins and Individual plan users can now customize the effort level Bugbot uses for its PR reviews, with three different configurations:
Default: Bugbot continues to use the same effort level as it does today. Optimized for efficiency and speed.
High: Bugbot spends more time reasoning. Reviews are more expensive and take longer, but Bugbot may find more bugs.
Custom: Describe in natural language when Bugbot should use default or high effort. Cursor will dynamically set effort levels based on your instructions.
Customers must be on usage-based billing for Bugbot to customize effort levels. Learn more in our docs and go to your Bugbot dashboard to get started.
With default effort, Bugbot finds 0.7 bugs per run, on average. Over 79% of these bugs are resolved by users at merge time.
With high effort, Bugbot finds 0.95 bugs per run, on average.
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.
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.
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.
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.
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.
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.
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.
As Cursor configures your environment, it will ask you questions, flag missing credentials, and validate that your environment is set up properly.
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.
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.
Mention @Cursor in any Teams channel to delegate a task to a cloud agent or pull information from Cursor into Teams.
Cursor automatically picks the right repository and model based on your prompt and recent agent activity. It reads the entire thread for context before implementing a solution and creating a PR for your team to review.
Get started by installing the integration in the Cursor dashboard. Learn more in our docs.
Teams admins and Individual plan users can now customize the effort level Bugbot uses for its PR reviews, with three different configurations:
Default: Bugbot continues to use the same effort level as it does today. Optimized for efficiency and speed.
High: Bugbot spends more time reasoning. Reviews are more expensive and take longer, but Bugbot may find more bugs.
Custom: Describe in natural language when Bugbot should use default or high effort. Cursor will dynamically set effort levels based on your instructions.
Customers must be on usage-based billing for Bugbot to customize effort levels. Learn more in our docs and go to your Bugbot dashboard to get started.
With default effort, Bugbot finds 0.7 bugs per run, on average. Over 79% of these bugs are resolved by users at merge time.
With high effort, Bugbot finds 0.95 bugs per run, on average.
