Skip to main content

Command Palette

Search for a command to run...

Release Notes

Cursor web release notes

Weekly changes to Cursor on the web, from integrations and admin settings to automations, the APIs, security and approval agents, and models. Each entry covers one week and is labeled with the Monday that starts it. Cloud Agents and Bugbot have their own pages.

AllAgents WindowIDECursor CLICursor SDK

Integrations

Bitbucket

  • Bugbot and @cursor work on every repository in a linked Bitbucket workspace. When the Cursor app is linked to your team, Cursor now handles pull request events from any repository in that Bitbucket Cloud workspace, including new repositories and ones nobody has opened in the Cursor dashboard. Before, those events were ignored. Picking Cursor from Bitbucket's mention autocomplete in a pull request comment now runs the command the same as typing @cursor.
  • Fixes to Bitbucket Cloud connections. Bitbucket Cloud accounts no longer get disconnected when a token refresh coincides with a failed account lookup. The connection stays linked instead of showing as not connected.

Slack

  • Admin Slack settings in one place. A new Slack page under Integrations in the dashboard lets you connect, reconnect, or unlink your Slack workspace, turn Slack notifications on or off, and pick which team runs agents started from Slack. It links to your routing rules, and the Manage rules button and rule links in Slack now open the right rule in the right team or personal workspace.
  • Clearer Slack errors when a cloud agent can't verify repository access. When a cloud agent started from Slack fails because Cursor can't verify access to a repository in its environment, the failure message now names each affected repository and the reason, such as missing write access, missing read access, or a Git remote that is rewritten to another URL.

GitLab

  • Admin Cloud agents only get GitLab write access to submodules and dependencies you can push to. When a cloud agent works on a GitLab project, it now gets credentials for the project's submodules and dependency repositories only where you have Developer access or above, or are an instance admin. Repositories you can't push to are left off the agent, and Cursor creates no project access token for them.
  • Admin Sync GitLab repositories with a team API key. A team API key with Cloud Agents access can now start the same GitLab repository sync as Sync Repos in the dashboard, so automations pick up new GitLab projects without anyone opening the dashboard. The sync runs as the admin who created the key. If that admin is no longer a team admin or hasn't connected the GitLab instance, the request fails with an error that says what to fix. Syncs are rate limited per team and recorded in the team audit log.

GitHub

  • Admin Fixes to GitHub repository access and GitHub Enterprise Server connections. Team admins who haven't connected a personal GitHub account now see the team's GitHub organizations and repositories instead of a prompt to connect GitHub. GitHub Enterprise Server connections no longer break when the server redirects to a URL with a different scheme.

Integrations page

  • Fixes to the Integrations page. Source-control cards such as GitLab Self-Hosted now load at their final size instead of growing when their status arrives. Menus show the full reason an action is disabled, and buttons that open a new tab show an outward arrow.

Dashboard and admin

API keys

  • Admin See every kind of API key in one list. The API keys page now shows all your keys in one table with a Type column, and admins who manage keys see team and personal keys together with each key's owner. Create lets you pick the key type in one dialog, with a Team key switch to pick who owns the new key, and a Filter menu narrows the list by type and status.
  • Admin Find keys created by people who left your team. Admins who manage API keys now see a Created by people no longer on this team section on the API keys page. It lists the API keys and service accounts that former members created, so you can revoke the ones you no longer need.
  • Admin Give team API keys access to automations. When you create a team API key, the permission picker now offers View automations and Manage automations. View lets a key read the team's shared automations, including their prompts, triggers, and repository settings, and Manage lets it change shared automations the team allows others to edit. Neither covers members' private automations.
  • Admin SSH keys moved to My settings and Origin. Your personal SSH keys now live in the SSH and signing keys section of My settings. Team SSH certificate authorities and the IP allowlist moved to the Security section of the Origin page, and old links to the SSH tab on the API keys page redirect.

Security and audit logs

  • Admin Edit each Network access list in its own dialog. In workspace settings, Network access now shows the sandbox allowlist and blocked destinations as rows with a destination count, each with its own edit dialog. The Cloud agent egress uses the sandbox allowlist switch is on by default; turn it off to give cloud agents their own allowlist row. Saving other team settings no longer overwrites your network lists. See network access settings.
  • Admin Clearer audit logs, and a record of a removed member's keys. When you remove a member, the credentials revoked event in your audit log stream now lists the team API keys, fine-grained keys, and service accounts they created that still work. The audit log table shows separate Date and Time columns with sentence-case event names, and you can filter for Origin namespace access policy events. See audit logs.
  • Admin Protect an organization from one dialog. Admins now protect an organization or group from a single Protect organization dialog that takes its URL. With nothing protected yet, the card shows a Protect organization button, or a prompt to connect GitHub or GitLab first. See Protected Git Scopes.

Plugins and MCP

  • Admin Limit which MCP servers each cloud agent environment can use. A cloud agent environment's page now has an MCP servers section where you list the allowed servers one per line as a URL, hostname pattern, or command, or turn on Disable all MCP servers. Agents in that environment then get only those servers from the ones your team allows. This is now available to everyone.
  • Admin Set a team plugin's distribution with switches. A team plugin's details dialog on the Plugins page now has Required for the team and On by default switches that apply when you click Save. In the plugin variables dialog, leaving a saved secret blank keeps its value, and Clear variables removes them.
  • Admin Import a team marketplace from a specific branch. When importing a team plugin marketplace from a repository, admins can now enter a Branch instead of using the repository's default branch. The Manage marketplace dialog also shows the reason when a save or delete is refused. See adding a team marketplace.

Cloud Agents

  • Admin Repository routing rules moved to Cloud Agents preferences. Manage the rules that pick a repository or environment for requests from Slack, Jira, Linear, or the API in a Routing rules panel on the Cloud Agents preferences page, for your team or your personal workspace. Older routing links and Manage rules in the Slack integration open that panel with the linked rule highlighted. See routing rules.
  • Admin Cloud Agents PR creation is an on/off switch. The Create PRs dropdown in Cloud Agents preferences is now an Always create PRs switch in team and personal settings. Teams that had "for single model runs" selected now get a pull request for every run, and in personal settings, leaving it unset follows your team's choice.
  • Pick a default model and its options in one menu. The Default model setting in Cloud Agents preferences is now a single picker: search for a model, then set options like effort or fast mode in the same menu.
  • Admin Run Approval Agents when a pull request joins a stack. Approval Agent triggers on GitHub-only repositories now include Pull request stacked, which fires when a pull request is added to a GitHub stack, drafts included. See configuring triggers.

Usage, members, and groups

  • Admin See which products used your weekly included usage. The weekly usage meter on your plan card and the Usage page now splits into colored segments by product, with a legend showing each product's share. The Usage chart also shows Cloud Agent spend under its own label instead of Other.
  • Admin Break down usage charts by member. The daily usage chart on team and organization Usage pages has a User option in its group-by menu, so admins who can see members can break spend or tokens down by member.
  • Admin Spend alerts require a recipient. Creating or editing a spend alert now requires at least one recipient, keeps at least one notification channel selected, and lets you search long admin lists.
  • Admin Paste invite lists from your email client. In the Invite members dialog, you can paste addresses in the Name <address> format from an email To line, and Cursor invites only the addresses and flags broken entries. An expired, revoked, or unknown invite link now says "This invite link isn't valid", and an invite sent to a different email than your account explains that and offers to switch accounts.
  • Admin Confirm before changing an admin to a member. On the Members page, changing a team admin's role to Member now opens a confirmation that explains they'll stay on the team but can no longer manage its members, invites, billing, or settings. See changing roles.
  • Admin Group model access saves exactly what you check. Saving a group's model access now keeps exactly the models you checked, and a group's Models page shows whether access is on, with a Turn on or Turn off button that confirms before members fall back to the team policy. You can't delete a group until its members are removed, and the dialog says how many remain. See group model access.

Personal settings and navigation

  • Your dashboard theme follows your account. Choosing Light, Dark, or System on the dashboard now saves to your account, so the same mode appears in every browser you sign in from.
  • Manage cookie preferences from My settings. A new Cookies section under Privacy & security in My settings lets you turn optional cookie categories on or off, or use Accept all or Reject all. Necessary cookies stay on.
  • Settings search shows the exact setting. Searching settings now keeps only the matching rows and highlights the matched words. The Cmd+K command palette also finds individual settings in My settings, such as Theme or Home team, and opens the page scrolled to that setting.
  • Resize the dashboard sidebar. Drag the sidebar's edge to make it wider or narrower, or past its minimum width to collapse it. The width is remembered across visits, and the handle works with the keyboard.

Fixes

  • Admin Saving settings no longer undoes other settings. Saving one section of team settings no longer resets unrelated admin settings such as network allow and deny lists, model lists, or browser origins, and saving MCP allowlist rules no longer flips the Enable Team MCP Allowlist switch. Saving quick actions in one team no longer removes the ones in your other teams.
  • Admin Fixes to usage and members. Usage alerts no longer arrive twice for the same threshold, and daily usage charts include usage from merged teams. Role, seat, and Over limit filters on the Members page now match across up to 5,000 members, with a warning when a longer roster is cut off.
  • Admin Fixes to API keys, MCP connectors, and Cloud Agents settings. The dialog showing a new or rotated API key secret now stays open until you click Done. MCP connectors whose sign-in keeps failing show a Reconnect button, and Cloud Agents settings load and save for the team you have selected.
  • Fixes and polish. Amount fields no longer misread a decimal comma like 10,50 as 1,050, and the Overview, Integrations, and My settings pages no longer jump around while they load. Links to Cloud Agents, billing, and workspace settings open in your team or personal workspace instead of the organization overview.

Automations

Tools

  • Automations can open pull requests ready for review. When an automation opens a pull request, it can now open it ready for review when your prompt asks for it. Pull requests still open as drafts by default. A subagent working in another repository now opens its pull request on that repository, instead of failing or opening it on the repository of the agent that started it.

Automation runs

  • Test runs now tell you why an automation didn't start. When you test an automation and the run is refused, you now see the reason, such as no prompts configured, missing repository access or environment secrets, or a rate limit with "Too many automation runs right now. Wait a moment and try again." Runs that fail because Cursor couldn't check your privacy mode now show as temporarily unavailable instead of as a privacy setting problem.
  • Saving an automation now catches repositories it can't use. When you add a repository, or an environment with repositories, to a cloud automation, Cursor checks that you can access each new one before it saves. Saves with a repository you can't reach or an unsupported repository URL fail with a clear message, so you don't end up with an automation that fails on every run. Repositories already on the automation aren't checked again. See Repositories.

Automations page

  • Retry failed follow-ups in the automation builder. When you describe an automation in plain language and a follow-up message fails, the automation builder now shows the error above the Follow up input with a Retry button. Retry resends your last message, and the draft you already have stays in the form.

Integrations

  • Project automations skip the run-finished reaction in Slack. Slack-triggered automations that a Project sets up no longer add the default run-finished reaction to the triggering message. This applies to new ones, and to existing ones once their instructions, trigger, or destination change. A custom completion emoji still applies.

Fixes

  • Template repositories stay selected while repositories load. When you create an automation from a template on the web, the template's repository is now filled in right away and stays selected while your repository list is still loading. Before, it was left empty if the template opened before your repositories finished loading.

Security and approval agents

Security agents

  • Vulnerability findings show their OWASP Top 10 category. Each finding from a Vulnerability Scanner is tagged with its OWASP Top 10:2025 category, so you can see the class of issue at a glance. The category appears as a badge on findings in the dashboard and in Slack finding replies, and the new OWASP category filter in Reviewing findings narrows the list to one category.
  • Vulnerability findings lead with their impact. When you open a vulnerability finding, its impact appears in a highlighted callout at the top, so you see why it matters first. Reports also have clearer descriptions and labeled evidence, and the scanner rates findings high or critical only when they're tied to a concrete business consequence.
  • Fixed docs links on security dashboard pages. The Learn more link on Security Review and Vulnerability Remediation pages, including each agent's page, opens the docs for that kind of agent instead of a generic page. When a scan fails because the default branch has no commits, the notice links to the Vulnerability Remediation docs.

Approval agents

  • Admin Name your approval policies. On Origin repositories, a PR Routing & Approval policy can set an optional name, such as Public API contract, so two rules with the same owners no longer read the same. A name is one line of up to 80 characters, unique within its policy file, and titles the rule on the pull request page, in origin pr requirements, and in approval comments. Policies without a name look the same as before.

Integrations

GitLab

  • Admin Advanced setup for GitLab Self-Hosted instances. Admins can now open an Advanced section for each registered GitLab Self-Hosted instance on the Integrations page in the dashboard. From there, admins can save or reset a service account token, copy the webhook URL and secret for manual webhook setup, rotate the webhook secret, and see which webhook triggers are required. This is now available to everyone.
  • Fixes to GitLab.com token recovery. Starting an agent on many GitLab.com repositories no longer fails because one token expired or was revoked. Cursor now refreshes or re-creates the token and retries, even when GitLab.com reports the problem as a rate limit.

Microsoft Teams

  • Clearer messages for older Microsoft Teams link cards. In Microsoft Teams, only the most recent Link Account card can link your Cursor account. Opening an older card now shows that a newer card replaced it, or that your account is already linked, instead of a "linking expired" error.

Slack

  • A Slack workspace with a removed app shows Needs reconnect. In the dashboard, a linked Slack workspace where the Cursor Slack app was removed or its access was revoked now shows Needs reconnect instead of Connected, so you know to reinstall the app.
  • Fixes to Slack account linking. Linking your Slack account to Cursor no longer fails as already linked when the previous link belongs to a Cursor account on a blocked team. The new account takes over the link instead.

GitHub

  • Team repo pickers no longer hide your personal GitHub repositories. Team repo pickers now list repositories from your personal GitHub installation, even if you connected it under a different Cursor team.

Linear

  • Reconnecting Linear takes one step. On the Linear integration card in the dashboard, Reconnect now opens Linear's authorization window right away. The card refreshes when the window closes, even if you don't finish authorizing. If a Linear team can't be found, an All teams button takes you back to the team list.

Dashboard and admin

Security and audit logs

  • Admin Block personal API key creation for your team. Team settings have a new Allow personal API key creation switch under Security & automation. When it's off, nobody on the team, admins included, can create or rotate personal Cursor API keys, including CLI keys, automation webhook keys, and personal service tokens. Existing keys keep working until revoked. See members' API keys.
  • Admin Search your API keys and find fine-grained and legacy keys more easily. The API keys page now has a search box that finds keys by name or masked key, and on the Members tab, by member. Fine-grained and legacy keys appear in separate sections, each with its own sorting and pages. When you can't create a key, Create API key is disabled with a tooltip that explains why. See members' API keys.
  • Admin Track API key creation, revocation, and session exchanges in the audit log. API key create and revoke entries now show the key's name and ID, plus its service account when it has one. Revocations from rotating a key, deleting an automation or service account, disconnecting Jira, deleting an account, or revoking a leaked key now appear with the reason, and a new Session Exchange event records each time an API key or service token is traded for a session. See audit logs.
  • Admin See My Machines activity in the audit log. The audit log now records when a member's personal machine connects to or disconnects from Cloud Agents, and when a Cloud Agent starts on one, with the machine name, the agent, where it was launched from, and the disconnect reason. Filter for these with the new My Machines event type in audit logs.
  • Admin Trust the IP addresses your installed apps declare. Admins can now let installed apps connect from the IP ranges those apps declare, without adding each range to the team's inbound IP allowlist. The inbound IP allowlist settings list each installed app with its IP ranges, and each app's page shows the egress IP ranges it declares.

Plugins and MCP

  • Filter your personal plugins and MCP servers. In a team workspace, the Personal view of the Plugins page has a filter menu for type, category, and status (such as Connected or Disabled by admin). Filters stay in the page URL, so you can share or bookmark a filtered view.
  • Plugins removed from the marketplace are marked as removed. On the Plugins page, an installed plugin the marketplace no longer offers now reads "No longer in the marketplace", with Edit disabled and Disconnect still available. Removed plugins no longer appear in Suggested.
  • Admin See your team's first-party plugin policy at a glance. In workspace settings, the First-Party Plugins row shows whether all first-party plugins are enabled or only an allowlist, with a summary of the allowed plugins. Change opens a dialog to pick the mode and edit the allowlist.

Cloud Agents

  • Admin Track vulnerability findings from the Security Agents page. A new Remediation agents section on the Security Agents page groups vulnerability findings by stage. Open a finding to see its verification and patch timeline or to request verification or a patch, and admins can click Enable all to turn on remediation for every Vulnerability Scanner. See vulnerability remediation.
  • See how long each environment build took. The builds table on a Cloud Agent environment's page now has a Duration column that shows how long each finished build took. See builds.
  • Scope secrets to Origin repositories. When you limit a Cloud Agents secret to specific repositories, the picker now lists your Origin repositories alongside GitHub and other providers, with provider icons to tell same-named repositories apart.

Team settings

  • Admin Turn off voice chat for your team. Team settings have a new Voice chat section with an Enable voice chat switch that hides voice chat for everyone on the team when it's off. Voice settings also let you turn each status chime on or off and preview its sound. See turning voice chat off.
  • Admin Team privacy mode changes apply right away. When an admin changes the team's privacy mode, every member's next request now uses the new mode, instead of the old one for up to several minutes. The same applies when someone joins or leaves a team.
  • Admin Find any team setting from search or the command palette. Search on the Team settings page tolerates typos and matches any text in a section, not only its title. Admins can also type a setting's name in the Cmd+K command palette to open Team settings scrolled to that row.
  • Admin Members can see their team's restricted models. Team members now see the Restricted and early-access models section in Team settings, read-only, with whether the team acknowledged each model's data policy. Only admins can change acknowledgements.
  • Admin Clearer switching between repository blocklist and allowlist. The Blocklist / allowlist card in workspace settings shows which indexing mode is active. Change switches modes in a dialog that warns you before the switch removes the repositories already on your list.

Integrations

  • Admin Manage self-hosted GitLab webhooks and service account tokens. On the Integrations page, Manage instances for GitLab Self-Hosted now has an Advanced view for each instance where admins set or reset its service account token, copy the webhook URL and secret, and rotate the webhook secret. Rotations appear in the audit log. This is now available to everyone. See GitLab.
  • Admin Rollouts records Vercel deploys under their Vercel project. With Use my GitHub deployments on in Rollouts, Production and Staging deployments that Vercel's GitHub integration reports are recorded with the Vercel project as the service, and Vercel preview deploys are ignored. See sending deployment events.

Usage, members, and groups

  • Admin Filter team usage by service account, attribution, and client type. On the Usage page, admins of teams without unified billing can narrow usage to a service account, an attribution such as Cloud Agents, Automations, or Bugbot, or a client type. The chart, usage events, and CSV export follow the filters.
  • Admin Manage SCIM from a group's page. The actions menu on a group's page now includes Manage SCIM, which opens the same SCIM mapping dialog as the Groups list, or says setup is required when SCIM isn't set up. See group management.

Account and dashboard

  • Choose your home team. If you belong to two or more paid teams that aren't linked to an organization, Settings > Profile now has a Home team setting. It shows the team Cursor uses when you sign in and lets you change it or set it to None.
  • Clearer warning before deleting a merged account. If your Cursor account is merged with another account, the delete account confirmation now says that the merged account and its plan are deleted too, immediately and permanently.
  • Shared canvases open on their own page. Opening a published canvas from Shared resources now shows it on its own page with Copy link, Download as PDF, and Open in full screen. Older share links forward to the new page.
  • Switch themes from the command palette. Type "theme", "dark", or another mode name in the Cmd+K command palette to apply Light, Dark, or System, or pick Toggle theme. The palette also hides commands that would do nothing, like your current theme.

Fixes

  • Admin Fixes to MCP allowlists and plugins. A member's group MCP policy can no longer allow MCP servers or tools that the team's Cloud Agent MCP allowlist blocks, and plugins blocked by a team admin show "Disabled by admin".
  • Admin Fixes to members and spending. Organizations using org-level SCIM no longer have members' directory emails overwritten, which could remove them from mapped teams. Reset dates on the Spending page use your local time zone.
  • Admin Fixes to environments, integrations, and team settings. Secrets now appear on the configure page for environments configured from a file in the repository, and the Bedrock IAM role instructions name the correct permissions. Team invite links that carry tracking parameters now redeem, and a failed redemption says why.
  • Admin Fixes to dashboard navigation, old links, and the API keys page. Sidebar items open in a new tab with Cmd-click, Ctrl-click, or middle-click, and old links to Security Agents, Audit log, Data exports, and Deployed Agents open the new dashboard. When a key list fails to load, the API keys page says so and offers Try again when a retry can help, and copy buttons report a failed copy.

Automations

Security agents

  • Vulnerability Scanner can open fix PRs without a verification step. With Open fix PRs for confirmed findings on and Verify new findings off, new Vulnerability Scanner findings now go straight to a patch agent. The agent first writes a test that fails against the unchanged code, and opens no PR if it can't show the finding is real.
  • PR Approver waits longer for automated reviews. The PR Approver automation now waits up to 11 minutes, instead of 8, for configured Bugbot and Security Reviewer checks to finish before it approves or assigns reviewers. Fewer pull requests miss approval because a review check ran long.

Automations page

  • Sign in to an automation's MCP servers from its overview. The MCPs card on an automation's overview now shows the logos of its MCP servers and how many are connected. Click it to see which servers still need sign-in and authenticate each one. The status updates when you come back from the browser.

Tools

  • Images show inline in Origin pull requests opened by automations. When an automation opens a pull request on an Origin repository, screenshots and other images from the agent now appear inline in the description instead of as links to a sign-in page. Teammates who can read the repository and the agent see them without a public share.

Fixes

  • Automations on Origin repositories no longer fail when no branch is set. An automation on an Origin repository with no branch set now finds the repository's default branch and launches, instead of failing every run. This includes scheduled automations and automations owned by service accounts.
  • Fixes to the automation editor's pickers. Choosing an any-repo self-hosted pool no longer clears the repository you already selected. The repository picker in the desktop app now stays responsive with very large repository lists, as it already did on the web.
  • Fixes to vulnerability verification. The Vulnerability Scanner no longer starts a new verification session every minute while one is already running, and a reverify or patch request still starts one within a minute. Findings queued by a scan are now verified for up to 72 hours after they are queued, up from 24.

APIs

  • Admin Look up organization groups by slug, and add members by numeric user ID. In the Admin API, Organization Groups now include a slug, which is null when a group has none, and GET /organizations/groups accepts a slug query parameter that returns the group with that exact slug. When you add or remove group members, userIds also accepts the numeric id that GET /organizations/members returns, as a number or a string, alongside user_ IDs.

Security and approval agents

Security agents

  • Security reviews avoid quoting secret values. When a security review finds an exposed credential, its findings, inline PR comments, and Slack summary refer to the secret by its variable or setting name and point to its file and line instead of repeating the value, including partial, masked, or encoded forms.

Models and Cursor Router

  • Interrupted conversations no longer get stuck. If a response is cut off partway, you can now continue the conversation instead of getting an error. This affected models such as Gemini.

Integrations

GitLab

  • Deploy agents from GitLab Self-Hosted. You can now deploy agents from repositories on a GitLab Self-Hosted instance connected to your team, including instances served under a URL path such as corp.example.com/gitlab. New Deployment lists those repositories, and each deploy checks clone access first. If Cursor can't reach the GitLab host or the project token can't read the repository, the deploy stops with an error that names the problem.
  • Admin Clearer GitLab access errors on the Integrations page. When Cursor can't reach a connected GitLab or GitLab Self-Hosted integration, its row on the Integrations page now explains the problem and how to fix it, with a Try again or Reconnect button, instead of showing a plain connected or disconnected state. On a team's Integrations page, if your own GitLab account is linked but the team's isn't, the GitLab row says so and names the account you're connected as.

GitHub

  • Admin Connect GitHub Enterprise for yourself. On a team's Integrations page, a GitHub Enterprise host now offers Just for me next to Connect, as GitHub already does. Members who can't manage the team's integrations see only Just for me, with a note that a team admin can connect it for the team. Disconnecting GitHub or GitHub Enterprise on a team now explains that only your sign-in is removed and the team's app stays installed, and a signed-out row shows a Sign in button.

Bitbucket

  • Admin Fixes to Bitbucket Data Center. Repository lists on large Bitbucket Data Center instances no longer repeat repositories or miss later ones. Adding a user when the server has no licenses left now reports a seat limit instead of an unexpected error.

Integrations page

  • Open self-hosted integrations by clicking anywhere on the card. On the Integrations page in the dashboard, if you can manage integrations, clicking anywhere on the GitHub Enterprise, GitLab Self-Hosted, or Bitbucket Data Center card now opens its management page. Buttons on the card keep their own actions.

Dashboard and admin

Cloud Agents

  • Admin Manage deployed agents from Cloud Agents. Once your team has deployed an agent, Cloud Agents > Deployed agents lists your team's deployed agents with their status, channels, 7-day usage, source, and last deploy, and New deployment deploys an agent project from a repository at any branch, tag, or commit. Each agent's page shows sessions with step-by-step traces, logs, and deploy history, and lets you roll back, redeploy, stop, or delete the agent. Deployed agents is in beta.
  • Admin Members can cancel draft environment builds when environment edits are admin-only. On teams that limit Cloud Agent environment edits to admins, any member can now cancel an in-progress draft build of a team or repository environment from the builds table or a build's page. Canceling other team builds and activating drafts still need an admin. See managing builds.

Plugins and MCP

  • Admin Browse and install plugins from the Plugins page. Add on the Plugins page now opens a menu with Plugin and Custom MCP. Plugin opens a searchable catalog with Featured and category sections that installs in place, and Custom MCP opens the Add MCP server form, grouped into Where it's added, Connection, and Authentication. See the marketplace.
  • Admin Plugins your team blocks no longer offer Add. In the plugin marketplace on the Plugins page, plugins your team's policies would refuse to install, such as ones whose MCP servers an admin disabled or that aren't on the team's allowlist, now hide Add instead of failing after you click it. This is now available to everyone.

Security and audit logs

  • Admin Stop members from creating personal API keys. Team admins can turn off Allow Personal API Key Creation in the new Personal API Keys card on the API keys page. Members then can't create or rotate personal Cursor API keys, and existing keys keep working until revoked.
  • Admin More audit log events, and a searchable event filter. The audit log now records cloud automations being created, updated, enabled, disabled, or deleted, members setting or leaving a home team, organization API key revocations, Origin repository renames, and commit-signing keys being added or deleted. Login entries name the client and version that signed in, and the event type filter has a search box. See audit logs.

Members and groups

  • Admin Move admins who don't use Cursor to a Free seat. On teams with seat tiers, the seat menu on the Members page offers Free for admins who manage the team but don't use Cursor. A confirmation explains that Free admins can't use Cursor and that the change applies right away. See seat tiers.
  • Admin Review seat upgrade requests from the Members page. On teams with seat tiers, admins get an Upgrades tab on the Members page that lists members' pending seat upgrade requests and, on self-serve teams, recommended upgrades. Each row has Upgrade, and a bulk button upgrades all seats or the ones you select. The tab isn't offered during a Teams trial. On these teams, the Members page also shows when member usage resets, in your local time zone. See changing a seat tier.
  • Admin Legacy SCIM groups appear on the Groups tab, and synced groups show their last sync. The Groups tab lists legacy SCIM directory groups with a Legacy badge, including for teams without an organization. Each synced group's page shows when it last synced, and when you add an organization group you can choose Manual or Synced and pick a directory group to sync from. See group management.
  • Admin Clearer spend limit controls. Lowering a member's spend limit warns you when a higher group or team limit still applies, and Cloud Agents blocked by a limit say which team or member limit stopped them.

Team settings and integrations

  • Admin Team members can open Team settings. Every team member now sees Team settings in the dashboard navigation. Members who can't manage settings get a read-only view of the team's name, privacy mode, and Origin review and repo creation providers.
  • Admin Connect GitHub Enterprise just for yourself. On a team's Integrations page, GitHub Enterprise now offers Just for me next to Connect, and members who can't manage integrations see that a team admin can connect it for the team. Disconnect on GitHub and GitHub Enterprise now explains that it removes only your own sign-in while the team's app stays installed. See GitHub.
  • Turn off Slack link previews. A new Slack link previews switch in your pull request settings shows or hides previews of the pull request, code, and artifact links you post in Slack.
  • Filter Insights to weekdays. The Include weekends switch on the Insights page is now a Filter by day dropdown with All days and Weekdays only. Existing links keep their filter. See filtering analytics.

Fixes

  • Admin Fixes to the Members, Usage, and Groups pages. The Members page keeps listing members, with search and sorting, when usage data fails to load. Directory group spend limit overrides on pooled and Enterprise token plans now save to the monthly limit that is enforced, and group pages show clear empty, not-found, and load-failure states with Try again.
  • Admin Fixes and polish. Settings save instantly and offer Try again when a save fails on a temporary network or server error, and team rule globs like *.{ts,tsx} stay as one pattern. Adding or renaming an MCP server can no longer overwrite one with the same name, and long emails in the audit log are truncated, with the full address on hover.

Automations

Automations page

  • A refreshed Automations list with icons, run history, and templates. The Automations list now shows each automation's icon, a 15-day run sparkline, and a count of what you're viewing, with Sort (name, last updated) and Filter (type, creator, status) menus. You can give an automation its own icon and color in the editor, and start from a template in the Templates section with one click on Use. Now available to everyone.
  • Search for a model when editing an automation. The model picker in the automation prompt editor now has a search box, so you can type to filter the list instead of scrolling. Now available to everyone.

Security agents

  • Admin Vulnerability Scanner can verify findings and open fix PRs. Each Vulnerability Scanner automation now has its own Verify new findings and Open fix PRs for confirmed findings remediation settings, now available on Teams and Enterprise plans. Verification agents write tests to confirm each new finding, and patch agents open fix PRs for you to review. Both settings start on when an admin creates a scanner, and only team admins can change them.
  • Security agent pages get clearer names. Under From Cursor in Automations, the Security Reviewer page is now Security Review and the Vulnerability Scanner page is now Vulnerability Remediation, with new page addresses to match. Old links, including links to a specific agent or finding, redirect to the new pages. On the Vulnerability Remediation page, the sections are now Scanner Agents and Remediation Agents, and Remediation Agents sits above Recent Runs.
  • Vulnerability Scanner keeps secret values out of its reports. When the Vulnerability Scanner finds an exposed credential, its findings, Slack reports, and fix pull requests name the secret and point to the file and line where it lives, without repeating the value or any part of it. Fix pull requests that remove a hardcoded secret also remind you to rotate it, since removing it from the code doesn't revoke it.
  • Security Reviewer runs on GitLab merge requests again. Fixed an issue where Security Reviewer automations matched a GitLab merge request, including on self-managed GitLab, but never ran and left Recent Runs empty.

Automation runs

  • Run history shows skipped scheduled runs. When a scheduled automation fires while its previous run is still in progress, run history now records a skipped run that explains why, instead of showing nothing.
  • Clearer messages when a run can't start. When a run fails because your machine was offline, run history now shows Machine offline with the machine's name and the agent worker start command to bring it back. A run whose selected environment was deleted or is no longer accessible shows Environment not available and asks the owner to select an environment and save. Runs blocked by a Cursor-wide rate limit now say there is nothing to change on your side and to trigger the run again shortly.

Fixes

  • Fixes to the automation editor. Adding or renaming an MCP server from an automation's actions no longer overwrites an existing server with the same name, and the repository picker stays responsive with very large repository lists.
  • Fixes to automation runs. Automations that approve pull requests, resolve review threads, or manage check runs no longer fail with an "Unknown action type" error before the agent starts. This applies to CI, scheduled, webhook, and GitHub triggers.

APIs

  • Admin Verify and patch security findings from the API. Use the Vulnerability Remediation API with a team API key to list your team's Vulnerability Scanner findings with GET /security/findings. Start verification agents and fix pull requests with POST /security/verifications. Track them with GET /security/verifications and GET /security/verifications/{verificationId}, which return each verdict, its patch status, and links to the fix pull request and Cloud Agent. Service accounts get two new scopes for these endpoints: View security findings and Verify and patch security findings.

Security and approval agents

Security agents

  • Admin Verify vulnerability findings and open fix PRs automatically. Remediation Agents are now available on Teams and Enterprise plans. Admins can turn on Verify new findings to test each finding a Vulnerability Scanner reports with an exploit test, and Open fix PRs for confirmed findings to get a fix PR, ready for review, for each confirmed issue. Each scanner keeps its own settings, and new scanners created by admins start with both on. Enterprise teams can also request verification and fixes for specific findings through the Vulnerability Remediation API.
  • Admin Security dashboard pages renamed to Security Review and Vulnerability Remediation. Under From Cursor in the dashboard, the Security Reviewer and Vulnerability Scanner pages are now Security Review and Vulnerability Remediation, and old links redirect to them. The Remediation Agents section on Vulnerability Remediation is marked Beta.
  • Fixed duplicate findings and slow repository pickers on the security dashboard. The Remediation Agents section no longer lists the same scanner finding twice. Links to Vulnerability Remediation, such as those from Slack, now scroll to the Remediation Agents section once the dashboard loads. The repository picker on security and approval agent triggers stays responsive with thousands of repositories.
  • Fixed follow-up security reviews skipping fixed issues. When you push to a pull request again, Security Review marks issues you've fixed as fixed instead of skipping them without notice.

Approval agents

  • Fixed approval reviews failing when rules share a prompt. When several matched rules use the same prompt text, PR Routing & Approval now includes that text once, so the repeated text no longer makes the review too large to run.

Integrations

GitHub

  • Admin Connect GitHub just for yourself, then move it to your team. On a team's integrations page, GitHub now offers Just for me next to Connect, so team members who can't manage the team's integrations can still connect GitHub for their own use. After a personal connect, team admins see an offer on the success page to move the installation to the team, and can also move personal installations from the Details dialog on the GitHub row.
  • Admin Clearer GitHub access errors on the Integrations page. When Cursor can't reach a connected GitHub or GitHub Enterprise integration, its row on the Integrations page now shows a warning that explains the problem and how to fix it, with a Try again or Reconnect button, instead of a generic "Reconnect required." You can also disconnect GitHub when Cursor can't read its installations, instead of being stuck on an error row.
  • Clearer GitHub connection errors. If GitHub has an error or times out while Cursor checks your access to a repository, git, pull request creation, and agent tools now say GitHub didn't answer and to try again, instead of saying you don't have access. If your GitHub connection was revoked, Cursor asks you to connect GitHub again instead of showing an internal error. If GitHub won't refresh the connection because your primary email isn't verified, Cursor tells you to verify it.
  • Agents recover from common GitHub errors. When an agent works with GitHub, short rate limits are waited out and retried automatically, and merging a pull request without naming a method uses a method the repository allows. Merging an already-merged pull request, opening a pull request that already exists, or creating a branch that's already at the right commit now succeeds with a note. Errors that remain name the fix, such as a missing branch or label, a pull request with conflicts or blocked by branch protection, or a repository where the account only has read access.
  • GitHub pull request lookup no longer fails on busy branches. Finding the pull requests for a GitHub branch with more than 100 pull requests now returns the newest ones instead of failing, and lookups for other branches in the same request still go through.

Bitbucket

  • Admin Bitbucket Data Center works on hosts without account linking. On a Bitbucket Data Center host where members can't link their own accounts, Cursor now accepts pull request links from repositories your team has connected, and team admins' runs started from Slack, Microsoft Teams, or Jira use the host's connection. Other members, and anyone who comments @cursor on a pull request, now get a reply saying Cursor can't verify their account and asking a team admin to set up account linking, instead of a refusal or no response.
  • Agent commits on Bitbucket Data Center credit you. When a cloud agent you launch commits to a Bitbucket Data Center repository, the commit is authored as your linked Data Center account, so Bitbucket attributes it to you. If your account isn't linked or no longer has access to the repository, commits keep the default Cursor agent author.
  • Admin Switch your team's Bitbucket workspace from the dashboard. If you installed the Cursor app in another Bitbucket Cloud workspace, the Bitbucket Cloud integration now shows it and lets admins switch to it from Switch workspace in the Manage menu. A team uses one workspace at a time, and linking a second workspace now explains how to switch instead of failing with a generic error.
  • Fixes to Bitbucket Data Center pull requests. Cursor now shows diffs for Bitbucket Data Center pull requests, finds a pull request by its source branch, and opens create pull request links on your server's browser URL. Merges use a strategy the repository allows, and pull requests that can be merged no longer show as blocked by branch rules. When creating or merging a pull request fails, Cursor explains why, for example that the branch hasn't been pushed, there are no new commits, or a pull request is already open.
  • Fixes to Bitbucket Data Center. Repositories are now recognized as connected when the URL uses different capitalization, or when the instance is registered on a non-standard port. Agents can clone same-host submodules listed by their /scm/ clone URL, and PR creation no longer fails while a rejected member token stays cached. Members whose Bitbucket user was deleted are asked to reconnect instead of hitting repeated temporary errors.

GitLab

  • GitLab merges run as your GitLab account. Merging a GitLab merge request from Cursor, or turning auto-merge on or off, now uses your connected GitLab account, so protected-branch merge rules apply to your role instead of failing with an unauthenticated error. If GitLab denies the merge, the error says whether to ask a project Maintainer for merge access or to connect your GitLab account to Cursor.
  • Fixes to GitLab. Merge request state, author, and mergeability now update right away after merging, closing, reopening, or renaming instead of showing stale values. Expired GitLab OAuth tokens are refreshed automatically during permission checks, service account tokens no longer rotate repeatedly and break access, and rate limits are reported as rate limits rather than project access errors. Repository access checks also retry after a timeout or dropped connection.

Dashboard and admin

Security and audit logs

  • Admin Review and revoke your members' personal API keys. Enterprise admins can open the new Members tab on the API keys page to see members' personal Cursor API keys, filter by member, and revoke one key or all of a member's keys. The Members page also adds a View API keys action for each member.
  • Admin See which API key acted in the audit log. When an action was made with an API key, the audit log now shows the key under the user, such as a service-account key or Admin API key with its name and ID, plus the delegated user when there is one. Audit log CSV exports add Actor API Key Kind, Actor API Key ID, Actor API Key Name, and Actor Delegated User Email columns. See audit logs.
  • Admin More Origin activity in the audit log. On Enterprise teams using Origin, the audit log now records repository ruleset changes, repository deletions, labels, merge when ready being turned on or off, dismissed reviews, and ownership exemptions. It also logs app signing keys being added or revoked, and members adding or deleting personal SSH keys, with the key name, fingerprint, and algorithm. You can pick each new event in the event type filter.

Deployed agents

  • Admin Control who can view, deploy, and manage each deployed agent. Each deployed agent now has Viewer, Editor, and Owner roles: Viewers see the agent and its logs, Editors can also deploy and stop it, and Owners manage secrets, access, the Slack app, token rotation, and deletion. New agents make the deployer Owner and the rest of the team Viewer, and existing agents keep their current access. The deployed agents page also shows your deployment count against your team's limit, and deploys over a limit are refused with a message explaining which one.

Agent settings

  • Admin Turn off personal secrets for Cloud Agents. Team admins can turn on Disable personal secrets in Cloud Agents in the Cloud Agents security settings. Members then see Add and Edit for personal secrets disabled, with a note explaining why, and can still delete secrets they already added.
  • Admin Pick a default pool for self-hosted Cloud Agents. Team admins can now set a Default pool in the self-hosted machine settings of the Cloud Agents dashboard, so self-hosted Cloud Agents that don't name a pool or machine run there. If the default pool doesn't cover a run's repository, that repository keeps using its own pool. Choose None to keep routing as before. See Self-hosted pools.

Plugins and MCP

  • Manage your personal plugins and MCP servers from a team workspace. In a team workspace, the Plugins and MCP pages now have a Team and Personal switch, so you can view and manage your own plugins and MCP servers without leaving the team. Your MCP servers stay listed even when team policy blocks them, marked "Disabled by admin", and adding or editing your own servers doesn't need team manage permission.
  • Admin Import a team marketplace alongside your default one. On the Plugins & MCPs page, teams without Enterprise can now import a team marketplace even when the team has a default marketplace, because the default no longer counts toward the one-marketplace limit.

Integrations

  • Admin Connect GitHub just for yourself on a team. On a team's Integrations page, GitHub now offers Just for me next to Connect, so members who aren't admins can connect their own GitHub account. Details on a connected GitHub row lists who owns each GitHub account, and team admins can choose Move to this team to turn a personal connection into a team one. Inactive teams are warned that this needs active seats. See GitHub.
  • Source control connection problems now explain how to fix them. When a GitHub, GitHub Enterprise, or GitLab connection on the Integrations page runs into an access problem, such as a rate limit or expired authorization, the row now says what went wrong and how to fix it, with a Try again or Reconnect action. Environment build failures caused by source control errors use the same wording and link to Integrations, the docs, or the installation settings. A GitHub connection whose installations fail to load still shows as connected and offers Disconnect.
  • Admin Switch the Bitbucket workspace your team uses. If you install the Cursor app in a second Bitbucket workspace, the Bitbucket integration on the Integrations page now says so and offers to switch the team to it. Admins can also choose Switch workspace from the Manage menu, which explains how to move the team to another workspace. Members who aren't admins are told to ask one.

Cloud agent environments

  • Create Cloud Agent environments without a repository. In the dashboard's Environments section and the New environment dialog, you can now skip picking a repository, name the environment, and save it. Repository-free environments then appear in your environment lists and can be configured like any other, with an install script and secrets. See environment management.
  • Set how long a cloud agent environment's install script can run. Environment Build Settings in the dashboard now include an Install Timeout field, so a slow install no longer fails at the fixed default. Enter a whole number of minutes from 5 to 300, or leave it blank to keep the 90-minute default. When an install times out, the build failure message now points you to this setting. See managing Builds.
  • Admin Refreshed secrets tables and safer bulk scope edits. Team Secrets, My Secrets, and the Secrets section on an environment's page now share one secrets table, with new dialogs for adding and editing secrets. When you bulk-edit the repository scope of secrets with different scopes, the picker now starts empty instead of defaulting to all repositories.

Members and groups

  • Admin Set spend limits on automation and agent service accounts. Admins can now use Edit monthly spend limit on the service accounts that run automations and cloud agents, so these accounts get a budget like any other. Key, suspend, and archive actions stay unavailable for these managed accounts.
  • Admin Every member can see whether a group is Synced or Manual, and group rosters sort by usage. The Type column on the Groups tab now shows Synced or Manual for every viewer, not only for admins who manage SCIM. On a group's member list, you can click the usage column header (monthly spend, included spend, or requests) to sort by it if you can see member spend.

Bugbot

  • Admin Choose whether Bugbot reviews outside contributors on public repositories. A new Public repositories switch in Bugbot team settings controls whether Bugbot automatically reviews pull requests from people outside your team on public repositories. It starts on for existing teams and off for new teams. See Bugbot configuration.

Account and navigation

  • Old settings links now open the right place in Settings. Bookmarks and links to the old My Settings and Voice pages now open the matching section of the Settings dialog, including Pull requests preferences. If you're not on a team, a model consent link from the editor opens Settings > Privacy with that model's consent dialog already open.

Fixes

  • Fixes to deployed agents. A deployed agent's page no longer fails to load while its Slack app is waiting for Slack's first request, and now shows that it is pending. Running Slack setup again from the dashboard keeps any extra bot scopes the agent's existing Slack apps already use. The Source value and the egress allowlist domains are now easier to read.
  • Admin Fixes to the Apps pages. When an admin changes access on a teammate's app, the Private and Team options now name the app's owner instead of saying "you." Failed Revoke, Change access, and Unpublish actions now show the reason they failed instead of a raw error code.
  • Admin Fixes to MCP, LLM Gateway, and plugin marketplace settings. Editing an HTTP MCP server no longer drops its custom CA bundle when you save other changes, and long MCP tool names truncate in a single alphabetical list instead of scrolling sideways. The LLM Gateway model test lists your team's published models and says when model discovery returned nothing, instead of showing a misleading provider mismatch. Failed plugin marketplace refreshes now explain the cause, such as missing repository access or rate limiting.
  • Fixes to cloud agent environments. The Trigger build dialog on the Environments page no longer grows past the screen for environments with many repositories. Its branch pickers now scroll inside the dialog.
  • Admin Fixes to usage and analytics. The analytics overview now marks the chats and models widgets as unavailable when part of the date range fails to load, instead of showing those days as zero. On the Usage page, owners of a personal team now see their usage from before the team was created, and chart tooltips show a total for the day. Paginated tables format large counts with thousands separators.
  • Admin Fixes to members and groups. Members with an unlimited spending limit now show a blank in CSV exports instead of a very large dollar amount, and they sort last with other no-limit members. The suggested Increase limit amount no longer jumps to a huge value because of them. A group's Codebase access section now shows that the team has no Codebase namespace instead of failing.
  • Admin Fixes to team invites and the team list. Sending invites or getting an invite link no longer times out on teams with very large numbers of pending invites, and pending invites waiting on a card confirmation now say so, can be revoked, and complete correctly for shared invite links. The Invite members dialog no longer offers a Free seat on teams that can't use one, and the team list no longer shows empty teams left over from abandoned checkouts.
  • Admin Fixes to audit log labels. Source control connection entries in the audit log now show "Bitbucket Cloud" and "Bitbucket Data Center" instead of raw provider IDs. The API keys page and audit logs now label Grok inference keys as "Grok API" keys.
  • Fixes to the account menu, profile, and sign-in. Approving a desktop sign-in now tolerates a slow security check, and the approve button can't be pressed twice. Accounts that signed in by phone no longer see a placeholder email address, and picking or removing a profile photo in Settings now saves right away. The account menu shows your profile photo and lists the same items everywhere.
  • Fixes to dashboard navigation and the Overview page. Switching teams from the team switcher or account menu no longer lands on a "team not found" page, and older dashboard links now keep their section anchor and open the matching Cloud Agents view and team instead of the dashboard home. On the Overview page, clicking the Cursor card opens the desktop app when it's installed and falls back to the download page otherwise.
  • Fixes to automations. Breadcrumbs, Back links, and navigation after deleting an automation now return you to the Mine or Team list you opened it from. The model picker in an automation's prompts section is now searchable.
  • Fixes to dialogs and menus. Pressing Escape or clicking outside a menu inside a dialog now closes just the menu, and menus in side panels are no longer cut off at the panel edge. The Duplicate as Origin dialog now fits on screen, and its list scrolls.
  • Fixes to scrolling in the Changes agent panel. The agent conversation in the dashboard's Changes agent panel scrolls with the mouse wheel and Page Up/Page Down again, instead of only responding to dragging the scrollbar.
  • Fixes to merging accounts. When a merge can't go ahead, the dashboard now says why, for example a merge already in progress or a team or organization that blocks it. The merge banner on Overview appears only when there is an account you can merge, and Profile settings no longer shift while it loads. Merged accounts on a merged team now open the new dashboard instead of the legacy one.

Automations

Triggers

  • Security Reviewer runs on GitHub label changes. Security Reviewer automations with a Pull request label changed trigger now run when a matching label is added to or removed from a GitHub pull request. Before, they never ran. To apply the fix to an existing automation, open it and save it.

Automation runs

  • Admin Automations start on teams with an inbound IP allowlist. Personal automations on teams with an inbound IP allowlist no longer fail with an "IP address is not on this team's inbound IP allowlist" error. Scheduled runs, webhook deliveries, and CI triggers start normally, and Cursor still checks your sign-in and repository access. Manual runs and API-key webhook calls still have to come from an allowed IP address.
  • Clearer failure messages for runs and webhooks. When a webhook-triggered automation fails to start, the webhook response gives the same failure title and reason as run history, instead of a generic error. Rate-limited runs explain that the limit can apply across all of Cursor and suggest trying again after a short wait. Runs whose agent fails to start tell you to retry and to contact support if it keeps happening.
  • Scheduled automations start up to 5 minutes after their set time. Each scheduled run can start up to a fifth of its interval late, capped at 5 minutes. This applies to every schedule, not only hourly and top-of-hour ones. A schedule that runs every 15 minutes can start up to 3 minutes late, and a daily schedule up to 5 minutes late. How often a schedule runs does not change.

Integrations

  • Clearer errors when connecting Linear or linking Jira. If you aren't a team admin, connecting Linear from a Linear trigger tells you only team admins can connect it, instead of showing a generic failure. Linking your Jira account explains when you aren't on the Cursor team connected to that Jira site, or when the site isn't connected to a Cursor team yet.

Fixes

  • Fixes to the repository picker. The repository picker in the automation editor labels partial lists as Recent, shows a spinner while more repositories load, and says clearly when a search fails.
  • Fixes to the PR Approver and pull request creation. The PR Approver automation finds routing policies in .cursor/approval-policies/, including ROUTING.md, and reviewer-specific criteria in .cursor/approvals/. Automations that open GitHub pull requests no longer fail silently when Cursor can't find the repository. The agent gets a clear error instead.

APIs

  • Admin Team admins can list a member's personal environments. The Cloud Agents API's GET /v1/environments accepts a userId query parameter. With a team admin's user API key, pass a member's ID to see their personal environments that list at least one repository, all of which you can read, for example to promote them to team environments. Pages can come back short or empty, so keep requesting until nextCursor is absent.
  • Admin Match team directory groups to the group IDs used elsewhere. Team directory groups in the Admin API now return each group's publicId (grp_…), the ID access grants use for the group. GET /teams/directory-groups/:groupId and its /members route also accept the publicId; write routes still take the team_group_… ID.

Security and approval agents

Security agents

  • More accurate fix detection for earlier findings. When you push to a PR, Security Reviewer now recognizes a fix made outside the flagged file, such as a new check in a caller elsewhere in the PR, and closes the finding. It closes a finding only when the fix appears in the lines your PR changes, and it rechecks every earlier finding before posting results.
  • Security reviews no longer fail at startup when the model list is briefly unavailable. If the model list is rate-limited or temporarily unavailable, the review retries with backoff, honoring the server's requested wait, before giving up.

Approval agents

  • Fixed approvals held by a missing rule rating. Fixed an issue where PR Routing & Approval could hold a PR's approval because a matching rule, or its global override copy, never got a risk rating. A rule and its override copy now share one rating, based on the files that rule governs.

Integrations

GitHub

  • Admin Bugbot reviews pull requests in shared GitHub installations. When another team in your organization shares its GitHub installation with your team, Bugbot runs on pull requests in the shared repositories using your team's Bugbot settings.
  • Admin Connecting GitHub no longer turns on Bugbot for every repository on Enterprise teams. When an Enterprise team or a GitHub Enterprise Server installation connects GitHub, existing repositories stay off until an admin turns Bugbot on for them. New repositories also stay off unless you change the installation's auto-enable setting, and these changes appear in your team's audit log.
  • Admin Clearer GitHub access errors. When an agent can't reach a GitHub repository, the error says why. A repository not granted to the Cursor GitHub App comes with a link to grant access, an organization that requires SAML SSO comes with a link to authorize, and IP allow list blocks are explained. Changing settings for an installation linked to a different Cursor account explains how to uninstall and reinstall it from your team's dashboard.
  • Admin Fixes to the GitHub integration. Admins of merged teams can manage GitHub and Bugbot installations again instead of seeing "Team is not active". Agents with access to more than 500 repositories get a GitHub token instead of failing, and GitHub requests no longer fail when HTTP/2 isn't available. When GitHub rate limits token refreshes, you see a "try again later" message.

Bitbucket

  • Admin Bitbucket Data Center explains a missing permission. If Cursor's application link grants less than Repositories Read, connecting Bitbucket Data Center shows a page asking your Bitbucket admin to raise it before you reconnect, and the setup instructions list that permission.
  • Admin Fixes to Bugbot for Bitbucket. Bitbucket Cloud admins who get admin access through a group or workspace role can turn Bugbot on or off for a repository. Reconnecting a repository no longer fails with 405 errors when Bugbot updates its existing webhook.
  • Fixes to Bitbucket. Repository lists in large Bitbucket workspaces load partially instead of failing, and reading pull request diffs and repositories no longer fails when Bitbucket Cloud redirects. Creating a pull request reuses the open one even when the repository name differs in letter case, and empty secondary repositories are skipped.

GitLab

  • Admin GitLab credentials stay on your GitLab host. When a GitLab instance redirects a request to a different host, Cursor refuses the redirect with an error instead of sending your token or OAuth client secret there. Same-host redirects, such as a moved project or renamed namespace, are still followed.
  • Fixes to the GitLab integration. Empty GitLab repositories added as secondary repositories are skipped instead of making the agent fail. Webhooks with a missing token or unknown registration return an error, so GitLab shows the failure instead of reporting success.

Dashboard and admin

Plugins and MCP

  • Admin See which servers Team list enforcement would block before you turn it on. Team list settings on the Plugins page, and the new Turn On Team List Enforcement dialog, now list the plugins and MCP servers members use that aren't on the Team list, with how many members use each. You can add a plugin to the Team list or allow a remote MCP server in one click, and the dialog warns you when enforcement would block every MCP server. See MCP server trust management.

Integrations

SSO and SCIM

  • Admin Control who can join through SSO. Organization admins can turn off SSO auto-enrollment in organization settings. When it is off, only invited or SCIM-provisioned users can join, while existing members keep signing in with SSO as before. Anyone else who signs in through your SSO connection is told to ask an admin for an invite. See SSO settings.

Members and groups

  • Admin Create team groups that the whole team can see. The New group dialog on the Members Groups tab now has a Visibility switch, so admins can make a group and its members visible to the whole team when they create it instead of editing it afterward. Groups stay visible only to admins unless you turn the switch on.
  • Admin Choose how many members to show per page. The Members page now has a Rows per page control at the bottom of the list, so admins of large teams can show 50, 100, or 250 members at a time. Your choice is kept in the page URL, and changing it takes you back to the first page.

Agent settings

  • Admin Project agents now ask before using a new machine, on every plan. The Automatically allow Projects to place their work switch in Cloud Agents security settings now starts off for every team, not only Enterprise teams, so a person approves each new machine, environment, or repository a Project's agents use. Teams that turned the switch on keep auto-allow, and approvals already granted stay in place. See Cloud Agents security settings.
  • Admin Clearer warnings for network allowlist entries that won't match. In the team Network access settings, admins now see which sandbox allowlist entries cloud agent egress ignores, along with explanations for unsupported characters and wildcard patterns. Catch-all entries such as *. and URL paths are no longer accepted for cloud agent egress, so a mistyped entry can't open access to every host. See network access settings.
  • Admin Choose a mode for Approval Agents. Approval Agent settings now include a Mode option under Configuration. Default is the faster choice and fits most teams. Low costs less and runs slower. You need edit access to change it. See PR Routing & Approval.

Rollouts

  • Admin Send Rollouts notices to Slack channels by repository, service, or environment. In Rollouts settings, team admins can subscribe Slack channels to change notices that match a repository, service, or environment, and add an optional message, including @mentions, that's posted in the thread after each new issue. Members can add their own personal subscriptions, and both team and personal subscriptions can be edited later. See Rollouts notifications.
  • Admin Send deployment events to Rollouts from your GitHub deployments. When you set up deployment events in Rollouts, you can choose Use my GitHub deployments to record deployments from your watched repositories, with no CI reporter needed. The manual setup now shows numbered, collapsible steps, and its copyable snippets report a missing or rejected Cursor API key in your CI log without failing the deploy. Deployments from gitlab.com projects now appear on a deployment's page, with Version and Previous version linking to the GitLab commit. See sending deployment events.

Cloud agent environments

  • Find, filter, and rename Cloud Agent environments. The Environments list now marks environments defined by a committed .cursor/environment.json with a Config as code badge, and a Config as code switch shows only those environments. You can rename an environment by clicking its name on the environment's edit page, and the Repo filter has a search box. In the default environment picker, unnamed environments show their repositories, such as "web-app +3", instead of an ID, and you can search for them by repository name. See environment management.
  • Clearer messages when a Cloud Agent environment build can't use its environment.json. When an environment build fails because its tracked environment.json is missing, empty, or can't be read, the build page now says so and tells you to restore or check the file, then rebuild. Agents keep using the last successful build in the meantime. Builds that fail because the GitHub App can't access a repository now list the affected repositories with an Open installation settings button, and teams that require self-hosted workers see a note in place of the Trigger build action. See Cloud Agent Builds.

Usage and analytics

  • Admin Export usage events for your whole organization. Organizations with pooled usage now get a Usage events section on the organization Usage page, with an Export button that downloads event-level usage across the organization's teams for the selected date range and filters. If an export isn't possible, for example when the organization has both merged and unmerged teams, the button is disabled and the page explains why.
  • Reorder usage event columns and read usage labels more easily. On the Usage page, you can drag the usage events table's column headers, or move them with the keyboard, into the order you want. Your browser remembers the order, and Date and User stay in place. Usage types now read "Additional usage" and "Credit grants", Auto requests show as Auto or as the routed model with its Auto option in the chart and model filter, and usage owned by a team rather than a person or API key shows as Team in the table and CSV export.

Security and audit logs

  • Admin More team changes in the audit log. The audit log now records changes to cloud agent network egress and sandbox networking settings, and to your team's repository allowlist and blocklist, including repo patterns. It also records Remote Control events, such as a computer being registered or a device being paired, unpaired, or revoked, with a new Remote Control filter. Pull request takeovers are now logged too, and takeovers show the previous author. See audit logs.

Workspace settings

  • Admin Add an icon to your team or organization. Admins can upload, change, or remove a team icon (PNG, JPEG, or WebP up to 2MB) in the Team profile settings. The icon appears in the workspace switcher, command palette, team selector, and the organization's teams table. Organization owners can also set an organization icon from the organization Overview page.

Automations

  • Admin See more flagged vulnerabilities per page. The flagged vulnerabilities table on the Vulnerability Scanner page now has a rows-per-page selector with 10, 25, 50, or 100 rows. It shows 25 by default instead of 5. Long titles wrap to two lines, and the Prev and Next buttons no longer move when you change pages. See Vulnerability Remediation.

Account and navigation

  • See what you lose before deleting your account. The delete account dialog in Profile settings now lists what will be deleted, starting with your Cursor account's name, email, and member-since date. If your account is merged with a Grok account, it also shows that account under Deleted and your linked X account under Unlinked, since X accounts are unlinked, not deleted. The dialog also notes that payments already made are not eligible for a refund.
  • Reset a saved color palette from Appearance settings. If you saved a colorblind or high-contrast color palette, Settings > Appearance now shows it in a Color palette row with a Reset button. Resetting shows a toast with Undo, so you can restore the palette.

Fixes

  • Admin Fixes to Rollouts setup and issue pages. Rollouts setup now pre-selects your team's existing observability connections, and Rollouts only shows as Enabled once setup is finished. If Rollouts is already on, setup still shows that step, with a link to its settings. Clicking Fix on an issue opened from a direct link now starts from the right rollout, and links to pull requests open on the portal you're using.
  • Fixes to cloud agent environments. Restoring an older team environment version no longer removes your personal override, and the Secrets row now says it includes team and personal secrets, with Manage opening the secrets that match the environment's scope. If the environments list fails to load, the Environments pages, Slack repo routing rules, and the agent environment picker now show the error or fall back instead of loading forever. The Environments section also recognizes any connected source control provider, so it loads faster and no longer shows the Connect Source Control card by mistake.
  • Admin Fixes to usage and analytics. Team usage event tables now load long date ranges, such as 30 days, without timing out on large teams. The usage card shows a member's own spending limit, including a $0 limit, instead of the team limit. The Usage Leaderboard no longer lists service accounts, team API keys, or unauthenticated usage, and no longer merges members who share an email or have none.
  • Admin Fixes to team invites and team selection. Copy invite link now uses the role you pick in the invite form on teams without seat tiers, so an admin link no longer adds people as members. When you belong to several teams, paid teams now come before free ones, so you no longer land on a free team by default.
  • Fixes to integrations and shared pages. Teammates who haven't connected Slack now see a deployed agent's existing Slack apps as read-only rows with a Connect Slack button, not an empty state. Shared canvases now print on white paper without the browser's header and footer, and the disabled Team sharing option explains when your team's admin turned it off.
  • Fixes to dashboard navigation and phone layouts. On phones, tab strips scroll to the screen edges, tap targets are larger, and the members search and setup checklist no longer crowd the layout. The Cmd+K command palette now opens above other dialogs, and closing it leaves the dialog underneath open. Each dashboard tab sets its own browser title, a failed background refresh no longer replaces a loaded workspace with an error screen, and profile settings show your saved first and last name.

Automations

Triggers

  • Label triggers for Origin pull requests. Automations on Origin repositories can now use the Label change trigger, which runs when a label is added to or removed from a pull request, as it does for GitHub.
  • Inline review comments on Origin pull requests now trigger automations. Automations with a pull request review comment trigger now run when someone leaves an inline review comment on an Origin pull request. Before, those comments only reached automations that trigger on top-level pull request comments.

Security agents

  • Admin Vulnerability Scanner caps hourly scans per team. Vulnerability Scanner automations run at most 500 repository scans per team per hour. Scans over the cap are skipped and show in run history as rate limited.
  • Subagents in managed security runs no longer message on their own. Fixed an issue where helper subagents in managed security review, vulnerability scanner, and PR approval runs could send Slack and Teams messages or resolve review threads on their own. Those actions are now refused for subagents in these runs.

Integrations

  • Automations load the MCP servers you named. Automations that pick an MCP server by name, like slack or google-drive, now find it even when the capitalization or spacing doesn't match. Before, these runs could start without the server's tools. If Cursor still can't find a server, the run shows a warning telling you to check the name or reconnect the server under Integrations.
  • Clearer status when GitLab has MCP turned off. When a GitLab MCP server in an MCP action is blocked because GitLab has MCP turned off for your groups, the automation editor now explains that an Owner of your top-level GitLab group must turn on MCP client access, instead of showing a sign-in prompt that can't succeed.
  • Admin Only team admins can connect a team's PagerDuty integration. Connecting, replacing, or moving a team's PagerDuty integration now requires a team admin, the same as disconnecting it. A PagerDuty account connected to one team can't move to another team until an admin disconnects it. The connection page now tells you why a connection failed: your session ended, you aren't a team admin, or the account belongs to another team.

Automation runs

  • Admin Managed automations no longer run on models your team blocks. When your team's model settings block every model a managed automation can use, such as the security reviewer or vulnerability scanner, the run now fails with a "Model blocked" error asking a team admin to allow a model. Before, the automation could fall back to a blocked model.

Automations page

  • The Model column shows the variant your automation actually runs. The Automations list, overview table, and run history now label each automation's model with the effort and Fast settings you saved, instead of the model's default variant. If a saved selection doesn't match a single variant, the column shows the plain model name.

Fixes

  • Fixes to which branch and repository automations launch on. Automations tied to a single-repo environment, including repos saved as SSH URLs, now run on the branch you saved instead of the environment's default branch. Automations that target a specific self-hosted machine fall back to main instead of failing when Cursor can't reach the git host. Runs that fail because the GitHub App was installed under another account now say the repository isn't connected to this team and explain how to reinstall the app.
  • Fixes to the automation editor and integrations. MCP actions now show when a server needs sign-in even if no sign-in link came back, and clicking sign in gets a fresh link. PagerDuty services load faster on accounts with many services, and descriptions over 1,024 characters now show a clear error. Turning off Change Monitor reports a failure instead of looking successful while it keeps running, and the Bugbot MCP tools and installation pages under From Cursor now load.
  • Automations list rows work with the keyboard. You can now reach and open rows in the Automations list with the keyboard. Tab moves focus from row to row.
  • Fixes to long automation runs. Runs that take a very large number of actions no longer fail to save their action history. The oldest entries are compacted so the run keeps recording.

APIs

  • Admin Make directory groups visible to your whole team. Team directory groups in the Admin API now have a visibility field. Set it to team when you create or update a group so every team member can see the group and its members, or team_admin to keep it visible only to admins. If you leave it out on create, the group is visible only to admins.
  • Admin Fixed missing member spend in the team spend endpoint. POST /teams/spend now counts each member's billed usage in full for teams on combined billing, so reported spend no longer comes up short. If spend data can't be read, the endpoint returns a 503 error instead of reporting zero spend.

Security and approval agents

Security agents

  • Vulnerability Scanner findings show in Vulnerability Remediation. Fixed an issue where findings from a Vulnerability Scanner didn't appear in the Vulnerability Remediation section.
  • Show more flagged vulnerabilities per page. The Flagged Vulnerabilities list now has a Rows per page selector (10, 25, 50, or 100) and shows 25 rows by default instead of 5. Long titles wrap to two lines, and the Prev and Next buttons stay in place as you page.
  • Fixed multi-file findings close when you push a fix. When a finding names more than one file, Security Reviewer re-checks each of those files on every push, so a fix in any of them closes the finding. You no longer need to resolve it by hand. Open findings in files you haven't changed now count toward the security check, so the check status matches the open threads.
  • Saving large Security Reviewer configurations works. Saving a Security Reviewer with many selected repositories, exclusions, or Slack channels no longer fails.

Approval agents

  • Approval comments show everyone who can approve. When a PR Routing & Approval policy is waiting on review and more owners can approve than were requested, its comment reads like "Needs 1 approval from any of: @alice, @bob (+2 more)". On Origin repositories, a pending policy that lists bot owners names them and shows how to request their review from the Reviewers list or with origin pr reviewer request.

Models and Cursor Router

  • New model: Gemini 4 Argon. Gemini 4 Argon is now available in Cursor.

Integrations

GitHub

  • Admin Pull request details stay limited to people with GitHub access. Cursor shows pull request details only to people whose GitHub account can read the repository, even when a teammate already loaded them. Everyone else gets an access error.
  • Clearer errors when GitHub blocks a merge method. Merging a GitHub pull request from Cursor with a merge method the repository doesn't allow now fails right away with GitHub's own reason, such as "Squash merges are not allowed on this repository." Before, Cursor retried and then showed a generic can't-merge-yet message.
  • Fixes to GitHub status and setup. Pending commit-status checks now show as running instead of queued, Actions log excerpts no longer hang on redirects, and @cursor commands from people whose GitHub username contains "cursor" are no longer ignored. GitHub Enterprise Server app installs now land on the team that started setup.

GitLab

  • GitLab repository lists and merge request lookups load reliably. The Bugbot repository list for large GitLab groups loads with the projects fetched so far instead of failing on a timeout, and finding the merge request for a branch now works for GitLab instances reached through AWS PrivateLink or an egress proxy.

Linear

  • Full Linear team names on hover. Hover a truncated team name in the teams list on the Linear integration page to see the full name.

Source control

  • Steadier self-hosted source control connections. Cursor retries a read request once when a connection to GitLab self-managed or Azure DevOps drops briefly. Over AWS PrivateLink, GitHub, GitLab, and Bitbucket requests also retry once when the server closes the connection.

Dashboard and admin

Plugins and MCP

  • Admin Control which MCP and plugin tools your team can use. Admins can turn Team list enforcement on or off from the Plugins page and limit a URL MCP server's or plugin's tools from its detail dialog, picking allowed tools from a live preview. The MCPs tab has an Allowlist rules editor that marks rules that apply only while Team list is on, and each server shows its access status, such as Read-only or Cloud only, with a tooltip that explains why the IDE and CLI block it. See MCP server trust management.
  • Admin Browse and add plugins and MCP servers from one list. The Plugins & MCPs page shows installed plugins and MCP servers together in one searchable table, with an Add button for the selected scope. Clicking a plugin opens its details in a dialog instead of a separate page.

Members and groups

  • Admin Set soft or hard spend limits for a group's members. In organization group settings, admins can set a member's monthly spending limit to No limit, Soft limit, or Hard limit. A soft limit doesn't block members and can be paired with pace alerts. A hard limit blocks members once their monthly spend reaches the amount. See group spend limits.
  • Admin Groups show their slugs, label synced groups correctly, and all appear on large teams. Team and organization group lists and group pages show each group's slug under its name. On the team Groups tab, groups synced from your identity provider are labeled Synced instead of Manual, and Move member no longer offers synced groups as destinations. Teams with more than 200 groups now see all of them on the Groups tab, in the Move member list, and in the invite group picker.
  • Admin Pending invites close when someone joins your team. When someone joins your team in any way, such as SSO, domain join, SCIM, or a direct add, their other pending email invites to it close automatically, and an old invite link still takes them to the team. When someone joins through a copied invite link, the audit log records the member who copied the link as the inviter.

SSO and SCIM

  • Admin Turn on SSO auto-enrollment from either SSO page. The SSO auto-enrollment switch now also appears on the older team SSO settings page, and both SSO pages show a newly finished SSO setup as soon as you return to the tab. When your identity provider marks a SCIM user inactive, Cursor removes their team seat but keeps their SSO membership, so reactivating them doesn't require adding them again. See SCIM user management.

Agent settings

  • Admin Control where Project agents can run. The new Automatically allow Projects to place their work switch in Cloud Agents security settings decides whether a Project's agents can start work on any machine, environment, or repository the Project owner can reach without asking first. When it's off, agents ask for approval before they use a new one. It starts off for Enterprise teams and on for other teams. See Cloud Agents security settings.
  • Choose which team your Slack agents run under. If you belong to more than one paid team, the Team for Slack agents setting in Cloud Agents settings picks the team that agents you start from Slack run, bill, and use settings under. The setting is locked when your Slack workspace is restricted to one team. See Team for Slack Agents.

Automations

  • Mine, Team, and Explore tabs on the Automations page. Mine lists the automations you own, Team shows your team's automations alongside agents from Cursor, and Explore holds the template gallery. Team admins open on Team by default, and everyone else opens on Mine.
  • Admin Security Reviewer and Vulnerability Scanner have their own pages. The From Cursor automations list shows separate Security Reviewer and Vulnerability Scanner cards in place of the single Security card. Each page lists only its own agents and recent runs, its New button creates that type directly, and flagged vulnerabilities appear on the Vulnerability Scanner page. Old Security links redirect to Security Reviewer. See Security Review and Vulnerability Remediation.
  • Start Rollouts checks yourself when a deploy isn't recorded. If a merged change goes live without a recorded deployment, select Run checks on the change's page in Rollouts, pick the environment and services, and Rollouts starts checking it. Deferred checks show as Deferred with the reason, and closing an issue now asks for a reason, such as Fixed or Duplicate. See Rollouts.

Usage and integrations

  • Admin Filter usage by SDK. The Usage pages for teams and organizations have an SDK option in the client filter, so you can see spend and requests from agents run through the Cursor SDK on their own. Now available to everyone.
  • Admin Connect SharePoint for your whole team. Admins can connect SharePoint from the Integrations page: choose delegated or application permissions, enter your Microsoft tenant, grant admin consent, and optionally allow write access. If setup stops partway, members who add the SharePoint plugin are told to ask an admin, and admins get a link back to Integrations to finish.

Security and privacy

  • Admin Bitbucket connection changes in the audit log. The audit log records when a Bitbucket Cloud or Bitbucket Server connection is connected, disconnected, registered, or deleted, and when its token is set or cleared, with the provider and host. Filter for them with the new Source Control Connection event type. See audit logs.
  • Admin Clearer privacy mode names. Privacy settings now read "Privacy Mode (no training)" and "Legacy (no storage)". When you invite teammates from a personal plan, a new "Share Cursor Analytics" checkbox sets the new team's privacy setting, and Privacy Mode stays on unless you check it.
  • Admin Control Grok dictation and private chats. Team admins can turn dictation on or off for their members from the Grok tab. Organization admins also get a Features section there with switches that turn off dictation or private (temporary) chats for every team in the organization, so all chats are kept for compliance exports.

Fixes

  • Fixes to dashboard layout and display. Team settings opens on the first click, and plan reset and billing cycle dates show in your local time zone instead of UTC. The Usage page shows how far you are over your monthly limit instead of $0 remaining, and the Overview setup checklist shows the steps that loaded instead of failing the whole card. Long names and emails truncate with the full text on hover, and pages no longer flash stale content or jump while loading.
  • Fixes to the dashboard on phones. The navigation drawer can be swiped left to close, the Members table and Usage filters fit the screen, and the Usage date picker no longer widens the page. The team name editor wraps and stops at 200 characters, and the invite email field no longer autocapitalizes or autocorrects.
  • Fixes to the Automations page layout. The Automations list no longer leaves a gap between each automation's title and author, the "Showing N" count is the right size with proper spacing, the filter tabs line up with the page title, and shared GitHub and GitLab triggers use a generic git icon.
  • Fixes to Rollouts settings. Clicking Authenticate on an MCP tool no longer wipes an existing shared connection, and already-connected servers refresh instead of opening a sign-in window. The data sources list shows every row instead of a small scrolling box, and notification help text wraps on mobile.
  • Fixes to environments and secrets. An environment's page shows history for that environment only. Double-clicking Duplicate creates one copy instead of two, and choosing All repositories in the Edit Secret dialog saves the secret for every repository.
  • Admin Fixes to integrations and MCP authentication. Registering a GitHub Enterprise Server app attaches it to the team you selected, and the existing-apps list shows that team's apps. Authenticating an MCP server for a service account returns you to the settings page you started from, and the private inference assignee picker loads groups from every linked team. Paging through the Origin repositories card no longer hides the card or shows the wrong page when a page change fails.
  • Admin Fixes to account sessions and deletion. When an account's email changes to a different address through your identity provider, SSO, or directory sync, existing Cursor sessions on that account are signed out. Deleting an account that was previously merged with another account no longer fails.

Automations

Automations page

  • Mine, Team, and Explore tabs on the Automations page. The Automations page now opens on Mine, which lists the automations you own across your personal account and teams, alongside popular templates. Team shows your team's automations, and Explore holds the full template gallery. Now available to everyone. Team admins land on Team, and users without a team see Mine and Explore.
  • See each automation's tools at a glance. The Tools column on the Automations page shows each tool as a pill with its icon and name. When a row has more tools than fit, a +N pill shows how many more there are.

Triggers

  • Microsoft Teams automations now fire on every channel post. Automations that listen to a Microsoft Teams channel now run on regular posts in that channel, not only on posts that @mention Cursor.
  • Failed Slack-triggered runs are marked on the trigger message. When an automation started from a Slack message fails, that message now gets a red X reaction in place of the hourglass. Before, the hourglass disappeared and nothing showed that the run had failed. The channel still gets no failure post.

Security agents

  • Vulnerability Scanner follows your custom instructions and files follow-ups. Team Vulnerability Scanner automations now use your custom instructions to shape what they scan. After a scan, they carry out the follow-up actions those instructions ask for, like filing a ticket for each new finding, through the automation's MCP servers, and link what they filed in the finding's Slack report.

Automation runs

  • Clearer reasons when a run fails. Run history now tells you whether to retry or contact your admin when your organization's policy check blocks a model request or is unavailable. Runs that fail because no self-hosted worker matches their labels now name those labels.

Fixes

  • Fixes to the Vulnerability Scanner. Findings recorded by the Vulnerability Scanner show up again instead of appearing empty. Repositories listed as host/owner/name without https:// now scan instead of failing. Teams that turn Security off in their managed automation settings no longer get scheduled scanner runs.
  • Fixes to Change Monitor setup. Turning off Change Monitor now stops its agents, and asks you to try again if they don't stop. Saving repositories the installation can't see, or that are missing a webhook, now shows the specific setup error instead of a generic one. Nested GitLab paths now ask for the full gitlab.com/<group>/<project> form, and fully qualified GitLab projects are watched correctly.
  • Admin Fixes to the automation editor and integrations. Your GitHub or GitLab connection no longer shows as disconnected when you belong to several teams or use self-hosted GitHub Enterprise or GitLab. The editor's MCP server options now list the selected team's servers. Disconnecting a team's PagerDuty integration now removes the team's connection, and "Configure here" links in Security Reviewer comments and Slack messages open that agent's page under From Cursor.
  • Fixes to the Automations page layout on web and mobile. On narrow screens, the Automations list now scrolls sideways instead of cutting off columns, and the row actions stay pinned on the right. Spacing and alignment across the page header, tabs, toolbar, and list rows are fixed.

APIs

  • Admin Clearer error for Azure DevOps repos in the Bugbot repo update endpoint. POST /bugbot/repo/update now returns a 400 for dev.azure.com and visualstudio.com repo URLs, explaining that Azure DevOps repo settings are managed from the Cursor dashboard, instead of telling you to install the Cursor GitHub or GitLab app.

Security and approval agents

Security agents

  • Admin Separate Security Reviewer and Vulnerability Scanner pages. Under From Cursor in the dashboard, the Security card is now two cards, Security Reviewer and Vulnerability Scanner. Each opens a page that lists only that type of security agent and its recent runs, with a New button that creates that type and an icon that shows whether it's enabled. Old Security links redirect to Security Reviewer.
  • Incomplete reviews no longer auto-approve. When part of a security review fails, Security Reviewer no longer treats the result as clean, so it doesn't auto-approve the PR. If no reviewer finishes, it posts no findings and leaves existing threads alone. Earlier findings stay open when their follow-up check times out or fails.
  • Accepted findings aren't posted again on every push. If you resolve a finding without fixing it, for example to accept the risk, a later push that finds the same issue no longer opens a new comment. A different issue on the same lines still gets its own comment, and a fixed issue that comes back is reported again.
  • Failed large reviews finish sooner. When every reviewer on a very large security review fails, the review now stops early instead of retrying until its budget runs out.

Approval agents

  • Clearer approval requirements on pull requests. PR Routing & Approval checks, comments, and the reviewer hovercard now say exactly what clears review, such as "Needs 1 approval from any human reviewer" with suggested reviewers, one approval from any of a set of owners, or approvals from all named owners. Auto-approved low-risk pull requests no longer show a leftover approval requirement.

Models and Cursor Router

  • New model: Claude Haiku 5.5. Claude Haiku 5.5 is now available in Cursor as an opt-in model. Turn it on in Cursor Settings > Models.
  • Fixes for Mistral models. Mistral requests that failed with a validation error now complete, and the model's reasoning shows up as thinking, separate from its answer.
  • Vendor names for Alibaba and Mistral models. The model list now labels these models with their vendor.

Integrations

GitHub

  • All your GitHub installations and accounts load. If you have many GitHub App installations, connecting GitHub and picking repositories now shows all of them instead of missing the ones past the first page. If one of several connected GitHub accounts has an expired token, the others still load instead of failing with "GitHub access token is no longer valid".
  • Newly created repositories. Cursor no longer denies access to a GitHub repository you can write to when GitHub briefly fails to return the repository's details, such as right after it is created.
  • Cloud Agent follow-ups on GitHub Enterprise Server. Cloud Agents started through a GitHub Enterprise Server app now receive pull request and CI updates for the team that owns the app, instead of having those webhook events rejected.
  • GitHub stays connected through GitHub incidents. When GitHub briefly rejects valid refresh tokens, Cursor keeps your GitHub connection instead of deleting it, and removes the token only if it keeps failing, so you don't have to reconnect GitHub.

GitLab

  • Clearer GitLab access errors. Starting work on a GitLab project where you lack Maintainer or Owner access now consistently says GitLab Maintainer access is required instead of asking you to reconnect, and the token cooldown error states the remaining wait in minutes or hours.
  • Connecting GitLab clears token cooldowns. After you connect GitLab, your personal and team repositories are usable right away instead of waiting out a cooldown left by earlier token errors.
  • Organization admins can manage team GitLab and Bitbucket connections. Organization admins who aren't members of a team can now load and manage that team's GitLab and Bitbucket integrations instead of getting an error.

Bitbucket

  • Replies when a comment command can't run. When @cursor can't run a command from a Bitbucket pull request comment, Cursor now replies on the pull request with the reason, such as needing a linked Bitbucket account or write access, instead of ignoring the comment.

Dashboard and admin

Cloud agents

  • Fix failed Cloud Agent environment builds in one click. When an environment build fails during install or on its Dockerfile, the environment and build pages show a Fix Build button that starts an agent to debug it, including for builds whose snapshot has expired. Builds with a deleted snapshot show a Snapshot expired chip and can't be activated, and deactivating the active build warns you when no other build can take over. Builds that fail because your self-hosted source control server is unreachable now say so. See Cloud Agent Builds.

Automations

  • Admin More control over label triggers in Approver Agents. A label-change trigger can now fire when a label is added, removed, or either, and you can limit it to one label name. These settings are now saved when you edit the agent.
  • Admin Vulnerability Scanner runs in Security Agents run history. Recent Runs on the Security Agents page now lists Vulnerability Scanner runs next to security reviewer runs.

SSO and SCIM

  • Admin More reliable SCIM directory sync. For organizations that own their SCIM directory, groups your identity provider pushes for teams linked to that organization now become synced groups instead of legacy directory groups. In directories with at least 10 users, if your identity provider briefly reports every user with no groups, directory sync no longer removes all directory group memberships.

Fixes

  • Fixes to Cloud Agent environment builds. Build logs open at the newest line and keep following new output until you scroll up. When a page of the builds table comes back empty but older builds exist, it now tells you to use Next instead of leaving you stuck, and the Trigger build dialog no longer warns that builds are off.
  • Fixes to Cloud Agents settings and runs. The Run history chart on the Cloud Agents Runs page no longer pushes the page down while it loads. Cloud agent settings refresh while the page is open, and network access entries like *.example.com now also match example.com.
  • Admin Fixes to groups and teams. On a group's Members tab, the row actions menu stays on screen on wide tables. When you create a team in an organization, the team admin list puts you first and selects you by default.
  • Fixes to the dashboard on mobile. On mobile, the navigation menu button now sits at the left of the top bar, and long GitHub Enterprise instance names truncate in settings.
  • Fixes to GitLab and Bitbucket integrations. GitLab and Bitbucket connections on the Integrations page no longer fail to load when the team selected in the dashboard is one you aren't a member of, such as a canceled team. They show as read-only instead.
  • Fixes to Bugbot settings. Old Bugbot license links open Bugbot settings in Automations.

Automations

  • GitLab support in pull request triggers and comments. The Comment on PR action accepts GitLab merge request URLs, including self-hosted GitLab. Git pull request triggers can be saved with a nested GitLab group (group/subgroup) or an organization URL as the org scope, and invalid entries show an error.
  • Clearer run failures. When a run fails because of a configuration problem, such as a missing branch, an inaccessible repository, a model blocked by your team's region, an API key rate limit, or a missing Slack channel, run history shows the specific reason and what to do. Runs whose agent ran out of memory or whose machine stopped responding say so, and a run that later succeeds shows as succeeded.
  • Fixes to automation runs. Automations with more than one schedule now run on every schedule instead of only the first. The open pull request step now opens the PR for runs owned by service accounts and for older team automations. Security Reviewer automations triggered by pull request comments or labels run again instead of being skipped, and automations with Slack access no longer stall on each step while re-listing Slack channels.
  • Fixes to team selection and PR Approver. On cursor.com, automation actions run under the team you have selected instead of your default team. PR Approver reviews no longer say reviewers were assigned when assignment was turned off or failed; they say human review is needed instead.

APIs

  • Skip the no-issues comment. POST /bugbot/review accepts an optional postSuccessComment boolean. Set it to false and a review with no new findings doesn't post the "found no new issues" comment. It defaults to true.
  • Cost for free Bugbot reviews. GET /analytics/team/bugbot-reviews now returns cost_cents for seat-based and free-trial reviews, showing their undiscounted model cost, and adds a billed field. billed is false when your team wasn't charged for the review.

Security and approval agents

  • Admin Only label. If you can't make changes to Security Agents, its pages now show an Admin Only label next to the page title.
  • Save without linking Slack. You can now save edits to a security agent without connecting your own Slack account, as long as its Send to Slack channels are unchanged.
  • More reliable security reviews. Security reviews keep results that finish right at the deadline, retry transient connection errors, and fall back to another model when the selected model is unavailable.

Models and Cursor Router

  • New model: Claude Sonnet 5.5. Claude Sonnet 5.5 is now available in Cursor.
  • New models: GLM 5.3 and GLM 5.3 Flash. GLM 5.3 and GLM 5.3 Flash from Z.ai are now available in Cursor. They're off by default; turn them on in Cursor Settings > Models.

Integrations

GitHub

  • Repository access updates right away. After you connect, reconnect, or disconnect GitHub, changes to which repositories you can access apply immediately instead of after a cache expires.

GitLab

  • Renamed and moved projects. After a GitLab project is renamed or moved, Cursor resolves the current project instead of a stale copy.
  • Disconnecting self-hosted GitLab keeps your GitHub connection. Disconnecting a self-hosted GitLab instance on the Integrations page now disconnects that instance even when your current team can't see it, instead of disconnecting your GitHub account.

Azure DevOps

  • Bugbot repository status. The Azure DevOps Bugbot dashboard no longer shows enabled repositories as disabled.

Dashboard and admin

Cloud agents

  • Clearer Cloud Agent environment build failures. Failed environment builds now explain what went wrong, such as "Git provider isn't connected", "No access to a repository", or "GitHub IP allow list blocked access", instead of a generic error. You can activate a draft build while it is still running, and build logs now include an Ask Agent link. See Cloud Agent Builds.
  • Admin Limit Cloud Agents to selected groups. Enterprise admins can now set Restrict By to Groups in the Cloud Agents access settings and pick which groups can use Cloud Agents, instead of listing members by name.
  • Admin Set spend limits for service accounts. The service accounts list in the dashboard now shows each account's spend limit and current spend. Admins can edit an account's limit per billing period or set it to No limit.

Fixes

  • Admin Fixed the team Groups tab. The Groups tab no longer fails to load with an "invalid int 32" error for some groups.
  • Admin Fixed members and invites. The invite screen now rejects spreadsheets, PDFs, and addresses longer than 255 characters instead of creating broken invites. A newly created invite link now shows up right away instead of appearing missing, and revoking your current session from Active Sessions now signs you out instead of showing an error.
  • Admin Model access settings apply more consistently. Saving a section of the Models page no longer turns a new Cursor model in its 7-day review window on or off by accident. Only an explicit Enable now or Keep disabled choice is saved. Model blocks and release-delay settings for your team now also apply when Auto routes to that model.
  • Admin Clearer Network Access Control settings. The settings now say that the blocklist applies only to the local sandbox, list the patterns each list supports, and warn when an entry, such as an IP address with a port or a path, won't behave as expected in a sandbox list.
  • Admin Fixed GitLab for team-owned instances. On the Integrations page, GitLab repository sync and your personal connection status for a team's GitLab instance now use the team you have selected, so they load and sync correctly.

Automations

  • Fixes to Slack triggers and channel pickers. Slack-triggered automations in private channels shared across workspaces now fire for owners who are members of the channel. Slack channel pickers on large workspaces no longer miss channels after a slow load, and Refresh reloads the full channel list.
  • Fixes to automation runs. Security Reviewer automations triggered by pull request comments or CI completion run again instead of being skipped, and runs whose parent agent is no longer active fail with a clear message instead of retrying.
  • Fixes to the automation editor. Adding or editing a custom MCP server from an automation's actions no longer drops auth settings such as OAuth scopes.
  • Faster branch picker for Origin repositories. When you set a branch for an automation trigger on an Origin repository, the default branch now appears right away instead of after the full branch list loads.

APIs

  • Organization audit logs. Organization API keys can call GET /organizations/audit-logs to read audit events across the organization. Filter by time range, event type, search text, users, or a single linked team, with pagination.
  • Organization API key expiration. When you create an Organization API key, you can now set it to expire after 30, 90, or 180 days, or one year. Once a key expires, it no longer authenticates against organization APIs.
  • Look up many commits at once. The commit lookup endpoint accepts a comma-separated list of up to 100 full commit hashes. Lists with three or more hashes used to return 404; more than 100 now returns 400.

Security and approval agents

  • Smarter follow-ups on findings. Partly fixed findings are treated as addressed, and a failed follow-up check leaves the existing thread as is.
  • Overlapping findings stay visible. A new finding overlapping an acknowledged one is posted as its own comment.
  • Model fallback. Security reviews fall back to the next model when the preferred model is out of capacity.
  • Every run opens. Every run in the Security Agents run history is now clickable. A run opens its session transcript, or a run summary when no transcript is available.

Models and Cursor Router

  • New model: Grok 4.7. Grok 4.7 is now available in Cursor.
  • New model: Claude Opus 5.5. Claude Opus 5.5 is now available in Cursor.
  • Shorter Grok model names. Grok 4.5 and Grok 4.6 now appear by those names in the model picker and its tooltips, without the "Cursor" prefix.
  • Auto follows team model settings. When a team admin blocks a Cursor-served model such as Grok 4.7, or the team's release delay for new models hasn't passed yet, Auto no longer routes that team's requests to it.

Integrations

Slack

  • Full bot alerts in automations. Automations triggered from Slack now read the full content of bot alerts that use attachment blocks, instead of only their one-line fallback text.

GitLab

  • Large GitLab groups and repositories. The GitLab repository picker no longer times out on large organizations, and resolving a branch or tag works on repositories with thousands of branches.

Azure DevOps

  • Reconnect prompt for expired Azure DevOps access. When Microsoft Entra rejects your Azure DevOps refresh token, Cursor stops retrying and the dashboard shows the connect card so you can reconnect.
  • Large Azure DevOps access tokens. The dashboard and Cloud Agent starts no longer fail with a server error when your Azure DevOps access token is larger than 4 KB.
  • Per-organization errors in the Azure DevOps repository picker. When one Azure DevOps organization refuses to list its projects, the repository picker shows an access error on that organization instead of failing the whole picker.

Dashboard and admin

Members and groups

  • Admin Groups pushed from your identity provider now appear as team groups. When your identity provider pushes a directory group through SCIM, Cursor creates a matching team group in the dashboard and keeps its members in sync. Removing a user from the group in your identity provider removes them from the team group, and deleting the group retires it. Groups that synced before this change keep working as they did.
  • Admin Removed members are now signed out everywhere. When you remove a member from a team that isn't connected to SSO, Cursor ends all of their active sessions so they lose access right away. Sessions stay active only if the member still belongs to another team in the same organization. Your audit log stream also gets a new credentials revoked event that records what happened to the member's sessions, repository access, and cloud agent git tokens.
  • Choose your home team in an organization. If you're a direct member of two or more teams in your organization that have billing set up, at least one seat, and a subscription that isn't canceled, pick a home team under My Settings > More while a team in that organization is selected in the dashboard. Cursor uses that team for your account when no team is specified, or you can set it to None.
  • Admin See a group's Codebase access on a new Access tab. Team and organization group pages have an Access tab that shows the group's access to your team's Codebase and any repository-specific access, with Manage links to change it.
  • Admin Organization admins appear in team member lists. Team member lists now include admins of the linked organization, labeled Org Admin.

Workspace settings

  • Admin Turn Projects on or off for your team. Admins can use the Enable Projects switch in Team Settings, under Chat, to control whether team members can use Projects in Cursor. When it's off, Projects is hidden for everyone on the team.
  • Admin Data exports for every team. The Data Exports tab is no longer limited to Enterprise teams. Any team member with permission to read exports can open it and download archives Cursor has prepared and released for the team, including teams whose subscription has ended. Export links open straight to the right team.
  • Admin Team MCP servers on members' machines (since removed from the dashboard). This week added a Run team MCP servers on members' machines switch to the Team MCP Servers section of the Plugins & MCPs tab. The Plugins & MCPs tab no longer shows that switch. Teams and members can also configure up to 1,000 MCP servers each.
  • Admin Connect more than one Jira site to a team. Admins with a connected Jira site now see a Connect another site action on the Jira page in the dashboard. It opens the Atlassian Marketplace to install Cursor on the new site, and the site list refreshes when you come back.
  • Clearer way back to Agents from settings. The settings sidebar header now shows a Back to Agents link next to the Cursor mark.

Usage and cloud agents

  • Admin Security Reviewer spend is easier to track on the Usage page. Security Reviewer usage is now attributed to Security Reviewer, and you can filter usage events by it. When you filter by Security Reviewer, each review run shows as one row, including the reviewer agents it spawns, instead of being split across many rows.
  • See exactly what a cloud agent environment build used. Environment build pages now have a Configuration section that shows the build's source, install and start scripts, terminals, and environment.json. Build logs sit in a collapsible Build output panel with an Ask an agent about these logs button, and they keep streaming past one minute without disconnecting or repeating lines.

Fixes

  • Dashboard pages no longer jump while they load. Overview, Usage, Billing, Cloud Agents, and Integrations pages reserve space for banners, usage tables, and invoices, and the dashboard no longer shifts sideways on first load.
  • Admin Fixed MCP server and secrets settings. The Choose Tools dialog stays on screen with its header and Use Selected Tools button visible, scrolls long tool lists, and trims long tool descriptions to three lines with the full text on hover or click. Editing an MCP server no longer drops extra auth settings such as scopes. The update warning for a new secret now appears only when a secret with that name exists in the same scope.
  • Admin MCP restrictions on team groups now apply. MCP settings saved on a team group are now enforced for the group's members. Editing MCP settings on a SCIM directory group linked to a team group saves them to that team group without dropping its existing restrictions.

Automations

  • Enable Cursor-built agents from a card grid. The From Cursor section of the Automations page shows each agent as a card with an enabled or disabled badge and an Enable or Manage button.
  • Clearer delete confirmation. Deleting an automation from the list or its settings page opens a dialog that names the automation and warns that deletion can't be undone, replacing the browser's confirm popup.
  • Fixes for Security Reviewer. Security Reviewer keeps syncing when a trigger repository is deleted or removed from the GitHub App, covers the repositories in an organization-wide trigger, and retries Origin, GitLab, and Bitbucket repositories that failed to connect.
  • Automations on Origin repositories. Security Reviewer now triggers on pull requests in team Origin repositories. Origin check runs from automations are grouped under the product name, such as Cursor Automation, and each run is named after its automation.

APIs

  • Find groups by ID or name. Organization group objects now include a publicId, and List Organization Groups accepts a name query parameter that returns the group with that exact name.
  • Filter organization members. GET /organizations/members now accepts email, userId, search, organizationRole, and teamId query filters. email and userId each take up to 100 comma-separated values.
  • Team directory groups. The Admin API adds /teams/directory-groups endpoints to list, create, read, update, and delete a team's directory groups, including each group's name and monthly spending limit, and to add or remove members by user ID.

Security and approval agents

  • MCP actions after a review. When a review finishes, Security Reviewer carries out the actions your custom instructions ask for, using the agent's configured MCP servers.
  • Redesigned run transcripts. Opening a Security Reviewer run that ran on Cursor-managed hosting shows a transcript styled like Cloud Agents.

Models and Cursor Router

  • 1M context kept on Cloud Agent follow-ups. A Cloud Agent started on the 1M-context variant of GPT-5.6 Terra now shows 1M in the web follow-up model picker, and follow-ups run at 1M instead of 272K.

Integrations

GitHub

  • Accurate GitHub connect errors. If connecting GitHub fails, the callback page now says whether you were rate limited, hit an authorization problem, or are missing an installation, and shows an error code and request ID instead of a generic rate-limit message.
  • Clear error past the repository limit. When a request needs access to more repositories than GitHub allows in one installation token, Cursor now explains the limit instead of asking you to reinstall the GitHub App.
  • Team marketplaces refresh from private repositories. Plugin marketplace refresh can now authenticate through a GitHub App installation owned by another team in the same organization, so marketplaces on child teams pick up updates from private repositories.

GitLab

  • Connect self-hosted GitLab to the right team. Connecting a self-hosted GitLab instance from the Integrations page now links the selected team, and its repositories populate there, instead of your default team.
  • Reliable host removal. Deleting a GitLab host now removes all of its repositories, even when webhook cleanup fails for some of them.

Bitbucket

  • Complete Bitbucket Cloud pull request lists. Listing closed or all Bitbucket Cloud pull requests now includes merged, declined, and superseded ones.
  • Faster Data Center registration errors. Registering a Bitbucket Data Center instance now fails within seconds when the host is unreachable instead of hanging through retries.
  • Bitbucket Cloud pull request diffs. Pull request diffs from Bitbucket Cloud now load when Bitbucket redirects the request.

Dashboard and admin

Admin

  • Admin Download team data exports from the dashboard. Enterprise admins now have a Data exports tab that lists the exports prepared for their team, with a download link for each archive. The tab stays available after a subscription ends, so you can still retrieve your team's data. Available on Enterprise plans.
  • Admin Confirm before turning off Security Agents or Approval Agents. Turning off Security Agents or Approval Agents in team settings now opens a confirmation dialog, where you can optionally share why you're turning it off.
  • Admin Build the MCP allowlist from your configured servers. In team MCP Configuration, the MCP Allowlist's Add Rule menu lets you enter a custom rule or pick one of your team's configured MCP servers, each marked Allowed by default, Already allowed, or Blocked by allowlist. For a URL MCP server, Choose Tools lists the server's tools, after you sign in if needed, so you can pick the tools the policy allows instead of typing their names.
  • Admin Confirm decisions on new Cursor models. On the Models page, choosing Enable now or Keep disabled (previously Block) for a new Cursor model in its 7-day review window now asks you to confirm. Pending rows show the date the model will be enabled automatically and no longer carry a New model label.

Analytics

  • Admin Redesigned team Analytics charts. The Active Users chart on the Analytics page now stacks CLI, Cloud Agents, and Bugbot activity with an All line. Every chart shares one color palette with a clickable legend below it. Hover a chart to download its data or copy the matching API curl command.

Members

  • Admin Team Admin and Org Admin are now labeled separately. Member lists, role pickers, CSV exports, and the organization member detail page now show team admins as Team Admin and organization admins as Org Admin.
  • Admin Members > Set Cap now warns when a higher limit still applies. If you set a member's spend cap below a higher group or team limit, the dashboard tells you to lower that limit instead. Before, the save went through with no message and the member's limit stayed the same.

SSO and SCIM

  • Admin SCIM keeps team-owned groups and organization access in sync with your identity provider. When a directory group maps to a group owned by a team, SCIM now adds its members to that team, including existing members who were missing from it.

Fixes

  • Fixed several issues in the Automations editor. User MCP servers are now dimmed in the tool picker, with a tooltip, when an automation runs as a service account. The model picker no longer shows raw model IDs while models load, and the remove button on MCP server rows is always visible.
  • Admin Fixed SCIM group mappings that changed the wrong memberships. Mappings no longer add users to extra teams or refill the root team when a directory group already maps elsewhere, and no longer remove members still covered by another mapped group. Full syncs now defer removals when directory data is incomplete.
  • Fixed issues with cloud agent environments. Members who can't create team environments can no longer save a new environment with Team scope. When an environment build fails because the repository's GitHub App belongs to another team, the builds page now shows a warning saying so.

Automations

  • Auto tier now saves in automations. Choosing Cost, Balance, or Intelligence for Auto in an automation's model picker now saves correctly, and cloud runs launch with the tier you picked. Before, every tier reopened and ran as Balance.
  • Model pickers no longer flash raw model IDs. The model pickers in the automation prompt editor wait for the model list to load instead of briefly showing internal model IDs.
  • Fixes to automation saves. Saving an automation on a self-hosted GitLab repository whose host uses a host-level service account no longer fails while setting up webhooks.

Security and approval agents

  • GitLab and Bitbucket reviews. Security Reviewer now reviews GitLab merge requests and Bitbucket pull requests, posting a summary comment and a status check on the change.
  • More runs in run history. The Security Agents run history now includes Security Reviewer runs that ran on Cursor-managed hosting. Click one to open its session view.
  • Confirm before turning off. Turning off Security Agents or PR Routing & Approval for your team now asks you to confirm, and you can optionally say why.

Models and Cursor Router

  • New model: Muse Spark 1.3. Muse Spark 1.3 from Meta is now available in Cursor.
  • Cursor Grok 4.6 sees images directly. Cursor Grok 4.6 now receives images you attach and images returned by tools as images, instead of working from text descriptions of them.

Integrations

GitHub

  • Clearer error for suspended GitHub App installations. When the Cursor GitHub App installation is suspended, Cursor now says so and points you to the app status in your GitHub organization settings.
  • Stale Bugbot comments are cleared. When Bugbot clears reviews from a previous run on a GitHub pull request, their bodies are replaced with a short "Stale Bugbot comment from a previous run." note. Comments from anyone else are left alone.
  • Correct GitHub Enterprise installation. When installation IDs from different GitHub Enterprise Server instances collide, Cursor now picks the installation of the GitHub Enterprise app your team or account owns.

Azure DevOps

  • Bugbot works with spaces in names. Bugbot no longer fails silently on Azure DevOps repositories whose organization, project, or repository name contains spaces.

Dashboard and admin

Cloud agents

  • Admin Manage Self-hosted Machines pools from the Cloud Agents dashboard. Team Pools is now called Self-hosted Machines. The All Self-hosted Machines page lists each pool with its repository, active and idle machines, total machines, and a Sessions column. Admins can set a pool's Reconnect Window or delete a pool without taking its connected machines offline. See Self-hosted pools.
  • Admin See Cloud Agent activity at a glance, with full run history on a new Runs page. The Cloud Agents page now opens with Total runs, Success rate, and Recent runs cards for the date range you pick. Select All Runs to open the Runs page, with a run history chart, a runs table, and filters for trigger, status, and creator. Team admins see runs across the team, and personal users see their own.

Members, groups, and SSO

  • Admin Remove members from your organization. Organization admins can now choose Remove from Organization from a member's row menu on the organization Members page. After you confirm, the person loses access to every team in the organization and can move to an individual Cursor plan. You can't remove yourself this way.
  • Admin Copy settings from an existing team when you create an organization team. A new step when you create a team in an organization lets you pick a source team and choose which settings to copy: models, security, rules and commands, hooks, MCP and plugin policy, spending limits, and team access defaults. A preview shows what each category will copy and lists connections, such as the GitHub App or MCP servers, that you'll need to set up again.
  • Admin Directory groups move into groups without losing spend limits. SCIM directory groups that have moved into organization groups no longer appear twice on the Groups page or in directory settings, and ones not yet moved show a Legacy badge. Filtering analytics or members by a moved directory group includes its new group's members. Members with a lower individual spend limit keep it instead of getting the group's higher limit.
  • Admin Sort group members by usage and spending limit. On the Members tab of a group synced from your identity provider, click the Username, usage, On-Demand Spend, or Limit column header to sort, and click again to reverse the order. When you sort by limit, members with no limit appear last.
  • Admin Warning before SCIM sync removes team members. When you switch a team or group to Synced, or change which directory groups it syncs from, the dashboard now asks you to confirm before saving. The warning explains that members outside the selected groups are removed, and that switching back to Manual doesn't restore them. Read more about SCIM provisioning.

Analytics

  • Admin Refreshed Analytics charts. Charts on the Analytics page and the dashboard overview share one color palette, a more compact layout, and a two-column tile grid on mobile and tablet. The AI commits chart labels the editor series Desktop and replaces Primary Branch Only with a Primary Branch checkbox. See team analytics.

Settings and navigation

  • Admin More models in admin model settings, and simpler Fable data-retention consent. Newer models now appear in admin model settings, so admins can enable, disable, or restrict them, and Muse Spark models appear under Meta on the Models page. Teams that accepted the data-retention consent for Claude Fable 5 don't need to accept it again for Fable 5.1. In organization and group settings, the exemption section is now called "Anthropic: Claude Fable Data Retention Exemption" and links to Organization Groups for organizations that include contractors or other third parties.
  • Admin Clearer Origin switch in team settings. The Origin section of team settings now has an Enable Origin switch: on means your team can create Origin repositories. It replaces the old "Disable creating Origin repositories" switch, and your current setting is unchanged. The description explains that turning Origin off makes existing repositories read-only and hides the Codebase tab.
  • Shared organization links open your own organization. Links to cursor.com/organization now open the same page in your organization's dashboard, keeping the rest of the path and any query string. If your account isn't part of an organization, you see a not-found page.
  • Easier navigation on mobile and clearer page titles. On a phone, tap a dashboard page title to jump to another section from a dropdown, and open your account from the avatar in the header. The Overview, Analytics, and Usage pages now show a title at the top.

Fixes

  • Admin Fixed SCIM group sync. Members provisioned through SCIM are now added to organization groups and passed on to mapped teams instead of being skipped, and synced groups no longer get stuck in an errored state. Adding a group-to-team mapping no longer removes existing team members. Creating a group with a duplicate name, or deleting a group that still has SCIM mappings, now explains what went wrong.
  • Admin Fixed the Integrations page for multi-team organizations. Disconnecting GitLab now disconnects the team you have selected, and GitHub Enterprise, GitLab Self-Hosted, and Bitbucket Data Center rows load installations for that team. Self-hosted GitLab connections no longer fail when another team in the organization already registered the same host. Long instance names now end with an ellipsis, and integration rows lay out correctly on mobile.
  • Admin Cloud Agent secrets no longer show another team's secrets. When you switch teams, the secrets list now shows the selected team's secrets, and creating, editing, and deleting secrets applies to that team instead of your default team.
  • Cloud Agents settings pages keep their header while you scroll. Environment detail pages, Repository Routing, Team Secrets, and My Secrets now have a sticky breadcrumb header in place of the old back links. The Environments list has a compact Repo filter, and Edit is now the primary action on an environment's page.
  • Fixed tooltip and diff glitches in settings and admin pages. The Billable Seats tooltip on the Members page now opens below its label instead of hiding behind the header, and Audit Log value diffs no longer show stray "No newline at end of file" markers. The API Keys and Protected Git Scopes sections also have more consistent layouts.

Automations

  • Search remote machines when picking an environment. The Remote Machines menu in an automation's environment picker is now searchable by machine name, path, repo, or pool, and groups your own machines under My Machines. Pools show how many workers are active and whether they are busy.
  • Approval Agents only offer supported repositories. When you set up an Approval Agent, the trigger menu and the org and repository pickers only offer repositories Approval Agents support, so you can no longer pick a GitLab or Bitbucket repository. If an unsupported repository is still selected, saving shows an error asking you to remove it.
  • Fixes to automation launches and runs. Automations on GitLab repos no longer fail to launch when a repo needs re-linking, and automations owned by removed team members are reliably disabled.
  • Teammates can manage team automations. Deleting a team automation now works from the team you have selected instead of failing access checks, and teammates other than the creator can save Slack channels on managed review agents such as Security Reviewer.

APIs

  • Manage organization groups from the API. The Organization API can now create, rename, and delete groups, and set or clear a group's monthly spending limit. Group responses include memberCount and monthlySpendingLimitDollars.
  • Model access covers every configurable model. The model access routes now list and accept every model you can configure, including hidden models and all of their parameters. Models that are unavailable, end-of-life, or internal no longer appear and are rejected.
  • Set spend limits in bulk. The Admin API adds POST /teams/user-spend-limits, in preview, to set or clear spend limits for up to 100 team members in one request. The response reports each member as updated, unchanged, or failed.

Security and approval agents

  • Search your security agents. The Security Agents list has a search box that filters agents by name.

Models and Cursor Router

  • New model: Claude Fable 5.1. Claude Fable 5.1 is now available in Cursor. With Privacy Mode on, or on an Enterprise plan, Anthropic's data retention terms must be accepted before it can be used.
  • New model: Gemini 3.8 Flash. Gemini 3.8 Flash is now available in Cursor.
  • Fast mode in Max Mode for GPT-5.6. You can now turn on Fast for GPT-5.6 Sol, GPT-5.6 Terra, and GPT-5.6 Luna in Max Mode. Previously, turning on Fast switched these models out of Max Mode's long context.