You can now share canvases from Cursor with your team.
Canvases are interactive artifacts created by agents, like reports, dashboards, and custom interfaces. Instead of sharing a full chat thread, you can share a link to a live snapshot of a canvas for teammates to open in the browser.
View your team's shared canvases in the Cursor Dashboard with read-only access. Shared canvases are available on Pro, Teams, and Enterprise plans.
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.
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.
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.
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
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.
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.
You can now share canvases from Cursor with your team.
Canvases are interactive artifacts created by agents, like reports, dashboards, and custom interfaces. Instead of sharing a full chat thread, you can share a link to a live snapshot of a canvas for teammates to open in the browser.
View your team's shared canvases in the Cursor Dashboard with read-only access. Shared canvases are available on Pro, Teams, and Enterprise plans.
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.
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.
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.
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
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.
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.