Code Editors and IDEs Release Notes

Release notes for code editors and integrated development environments

Get this feed:

Products (8)

Latest Code Editors and IDEs Updates

Jun 4, 2026
- Date parsed from source:
  Jun 4, 2026
- First seen by Releasebot:
  Jun 4, 2026
IntelliJ IDEA by JetBrains

IntelliJ IDEA 2026.1.3 Is Out!

IntelliJ IDEA releases 2026.1.3 with usability fixes for tmux terminal cursor rendering, Markdown image previews, Database tool window colors, and WSL shell integration, improving the overall IDE experience.
We’ve just released IntelliJ IDEA 2026.1.3. You can update to this version from inside the IDE, using the Toolbox App, or using snaps if you are a Ubuntu user. You can also download it from our website.

The latest update brings the following improvements:

In tmux, the terminal cursor is no longer rendered above the current line. [IJPL-102697]

The Markdown preview now correctly displays images when referencing files outside the project directory. [IJPL-171896]

Custom colors are rendered correctly in various UI components in the Database tool window. [DBE-25711]

Launching WSL via wsl.exe -d <distribution> no longer causes shell integration and process detection issues. [IJPL-236576]

For a comprehensive overview of the fixes, see the release notes. If you spot any issues, let us know via the issue tracker.

Happy developing!
Original source
Jun 4, 2026
- Date parsed from source:
  Jun 4, 2026
- First seen by Releasebot:
  Jun 4, 2026
Windsurf

Added a new command for Devin Desktop to rerun the migration from Windsurf

Windsurf adds a reset migration command in Devin Desktop to rerun imports and restore settings.

Added a new command for Devin Desktop to rerun the migration from Windsurf. This will reset Devin Desktop settings and give you a second chance to import extensions and other settings from Windsurf. The “Reset migration from Windsurf” command can be found in the command palette.

If you are logged out of your account after migrating from Windsurf, we recommend opening the command palette via ctrl+shift+p (cmd+shift+p on macOS) and running the reset migration command.
Original source
All of your release notes in one feed

Join Releasebot and get updates from JetBrains and hundreds of other software products.

Create account
Get updates with:
Jun 3, 2026
- Date parsed from source:
  Jun 3, 2026
- First seen by Releasebot:
  Jun 4, 2026
Cursor

Organizations for Cursor Enterprise

Cursor adds organization-level controls for Enterprise customers, letting admins manage multiple teams from one place with separate security, governance, budget, and feature settings. It also introduces Groups for flexible access, spend limits, and permissions across teams.

Enterprise customers can now manage multiple Cursor teams from one place, with different security, governance, budget, and feature controls for each. These capabilities are now generally available to all Enterprise customers.

Organizations

An organization is the top-level container for your company's identity, administration, and membership. It gives admins one place to view and manage their entire Cursor setup, including a rollup of spend and token usage across every team.

Teams

Teams are the operating unit for a department, region, or subsidiary. This is what admins manage as their Cursor org today. We've moved that unit under an organization, so you can run multiple teams, each with its own security, governance, spend, and feature settings.

A user can belong to more than one team, with a different role in each. For current customers, your existing team is preserved and becomes the default home for login, routing, and creating new teams.

Groups

Groups are a lightweight collection of users that can sit across or within teams. They give cohorts of users separate model access, spend limits, and agent permissions without standing up a whole new team. When a user belongs to more than one team or group, the most permissive setting wins.

Learn more in our announcement post or docs.
Original source
Jun 3, 2026
- Date parsed from source:
  Jun 3, 2026
- First seen by Releasebot:
  Jun 4, 2026
Visual Studio Code by Microsoft

Visual Studio Code 1.123

Visual Studio Code ships a release that improves agent workflows and the integrated browser with session sync, side-by-side agent sessions, a research agent, favorite pages, richer screenshot capture, and delayed extension auto-updates for added protection.
Welcome to the 1.123 release of Visual Studio Code.

This release improves how you work with agents and the integrated browser.

Session sync: Automatically sync your chat sessions across machines and search your coding history.

Agents window: Open multiple agent sessions side-by-side to compare or review work in parallel.

Research agent: Run deep research on a topic and get a thorough, well-cited Markdown report.

Integrated browser updates: Favorite pages for quick access and more options to capture browser screenshots.

Make sure to join VS Code Live at Build 2026 on June 3!

Happy Coding!

Agents

Session sync and chronicle

Setting: chat.sessionSync.enabled
This setting is managed at the organization level. Contact your administrator to change it.

Your chat sessions now sync automatically to your GitHub account, giving you a personal, searchable history of your work across machines and workspaces.

Each session captures the conversation, the files you touched, repository context (repo, branch, timestamps), and any pull requests, issues, or commits referenced along the way.

With the new chronicle commands (/chronicle) in chat, you can put that history to work:

Ask natural-language questions about past sessions

Generate standup reports

Get personalized productivity tips

Search your coding history by topic, file, or PR

To enable session sync, turn on chat.sessionSync.enabled. This setting is managed at the organization level. Contact your administrator to change it. You can view the status of session sync in the Copilot status dashboard in the VS Code Status Bar.

For more details, see the Session Sync and Chronicle documentation.

Retry network-dependent commands in the sandbox

Setting: chat.agent.sandbox.retryWithAllowNetworkRequests

When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.

Agents window (Preview)

The Agents window is a dedicated companion window optimized for exploring, iterating on, and reviewing agent sessions across projects and machines. This release, we focused on letting you work with multiple sessions side by side.
Multiple open sessions
You can now have more than one session open at the same time in the Agents window. In addition to the active session, open another session next to it by:

Selecting Open to the Side in the context menu of a session in the sessions list.

Dragging and dropping a session from the sessions list into the sessions view area.

Holding Alt and selecting a session in the sessions list.

Even though multiple sessions can be visible at once, only one is the active session at any time. The Terminal, Files, and Changes views all operate on the currently active session, so switching the active session updates these views to reflect its state.

By default, selecting a session in the sessions list replaces the active session view with the selected one. To keep a session view from being replaced, pin it with the pin action in the top right of the view. Pinned session views are never replaced—selecting another session opens it in an unpinned view instead. If every session view is pinned, the selected session opens to the side.

Use the maximize action in the top right of a session view to expand it across all open session views, giving you a focused view of a single session without closing the others.

For more details, see the Agents window documentation.

Research agent (Preview)

Note: The research agent is currently in preview and available only in Copilot CLI (local) sessions in Insiders.

When you need to understand unfamiliar code, compare approaches, or learn how a library or API works, a quick chat answer isn't always enough. The research agent runs deep research on a topic and produces a thorough, well-cited Markdown report by gathering and synthesizing information from your codebase, relevant GitHub repositories, and the web.

The research agent is optimized for depth rather than speed and has read-only access, so it investigates and reports instead of changing your code. To run it, type /research followed by your topic in the chat input of a Copilot CLI (local) session.

For more details, see Run deep research with the research agent.

Integrated Browser

Favorite pages

We've remodeled the address bar in the integrated browser into a more versatile experience where you can not only enter URLs but also favorite pages and easily access your favorites and open tabs.

To add a page to your favorites, select the star icon in the browser URL bar.

When you select the URL bar, you can see your list of favorite pages and open tabs.

More ways to capture screenshots

Setting: workbench.browser.experimentalUserTools.enabled

The previous release introduced Add Screenshot to Chat, which lets you attach a screenshot of the current browser viewport to chat as context. This is especially useful for UI-related tasks, such as debugging a layout issue.

This release, we added two related features:

Add Area Screenshot to Chat: Take a screenshot of a rectangular area that you select, and add that screenshot as chat context.

Add Full Page Screenshot to Chat (Experimental): Take a screenshot of the entire web page, even beyond what is shown in the current viewport, and add that screenshot as chat context. This experimental feature requires enabling the workbench.browser.experimentalUserTools.enabled setting.

Editor Experience

Delayed extension auto-updates

VS Code now applies a two-hour delay before automatically updating extensions to a newly published version. When automatic updates are enabled, new versions are auto-updated two hours after they are published, adding an extra layer of protection against problematic or potentially compromised releases.

This never gets in your way, as you can still update any extension immediately at any time by using the Update button. While an update is waiting, the extension's details view explains why it hasn't updated yet and when the automatic update will happen.

Note: This delay does not apply to extensions from trusted publishers such as Microsoft, GitHub, and OpenAI. These extensions continue to update immediately.

Thank you

Contributions to our issue tracking:

@gjsjohnmurray (John Murray)

@RedCMD (RedCMD)

@IllusionMH (Andrii Dieiev)

@albertosantini (Alberto Santini)

Contributions to vscode:

@aaronpowell (Aaron Powell): Add marketplace ref support for plugin marketplaces PR #317901

@goingforstudying-ctrl: fix: add white-space: nowrap to browser-emulation-toolbar-label PR #318935

@guomaggie: [Search Subagent] Handle context window limit exceeded error PR #316529

@maruthang (Maruthan G): fix: combine URI flags to prevent Electron argument filtering on Windows PR #308150

@oded-ist (Oded S): Fix read_cell_output incorrectly reporting all outputs as too large PR #318148

@PenguinDOOM (Penguin): Fix BYOK invalid stateful marker retries PR #317292

@rebornix (Peng Lyu): Add mobile multi-diff view PR #318081

@SimonSiefke (Simon Siefke):

fix: memory leak extension actions PR #315054

fix: memory leak in ipc.electron.ts PR #317846

fix: memory leak in search results PR #282309

@SLdragon (rentu): feat: add languageDiagnosticsService option for nes/inline completion provider PR #317678

@Tyriar (Daniel Imms): fix: remove awaits inside Promise.race in shell integration test PR #319068

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.
Original source
Jun 3, 2026
- Date parsed from source:
  Jun 3, 2026
- First seen by Releasebot:
  Jun 4, 2026
Cursor

Introducing organizations for Cursor Enterprise

Cursor introduces organizations for Enterprise customers, giving admins a single dashboard to manage multiple teams, budgets, security, model access, and usage analytics across the company. It also adds groups for flexible cohort-level controls and smoother identity and membership management at scale.

How the structure works

Large enterprises are often made up of many business units, subsidiaries, and functions. We frequently hear from customers that each of these units needs its own budget, security, governance, and feature controls.

To support these requirements, we’re introducing organizations, a new structure that allows enterprises to manage multiple Cursor teams from one place. With it, admins can set separate budgets for different teams, enable different models for different cohorts of users, create sandbox environments to test new features, and view usage analytics across the whole company, all from one dashboard.

These capabilities are now generally available to all Enterprise customers.

An organization is the top-level container for your company’s identity, administration, and membership. This gives admins one place to view and manage their entire Cursor configuration.

Under organizations are teams, the operating unit for a department or subsidiary. Admins previously managed Cursor at this level. We’ve now taken this unit and moved it under the organization so you can run multiple teams, each with its own security, spend, and feature settings. For current customers, your existing team setup is preserved. Admins can create new teams with separate configurations at the organization level.

Groups are a lightweight collection of users that can sit across or within teams. They give cohorts of users separate model access, spend limits, and agent permissions without standing up a whole new team. When a user belongs to multiple teams or groups, the most permissive setting wins.

At Cursor, we've created separate teams for different departments. Engineering and product teams have the most permissive network access and the ability to let agents run commands automatically. Sales, marketing, and finance have tighter security controls, especially when it comes to agents accessing production systems.

Enterprise use cases

There are a few common patterns we've seen from customers using these new capabilities in beta.

Sandboxing to test new features

Many customers with strict security review requirements have set up a staging team that gets early access to new Cursor features. These users test features in a sandboxed environment before they are rolled out more broadly to the full company.

Because a user can belong to more than one team, engineers can work in their production team while retaining testing team capabilities without having to create a second Cursor account.

"We have set up a separate staging team that tries out new Cursor features before they are released broadly to all our engineers. We have another team where agents can run commands on auto-run without manual approval. Keeping those environments distinct under one organization lets us move quickly and adopt new capabilities without sacrificing control."
Wendy Tang
Staff Software Engineer, AI Solutions Engineering, NVIDIA

Segmenting model access, budgets, and agent permissions

Some customers are segmenting model access and budgets across functions. Users in engineering, product, and design functions get access to every frontier model, including more expensive offerings with fast mode, and higher monthly budgets.

Users in non-product functions like marketing or finance have restricted model access, lower budgets, and tighter restrictions on whether agents can run commands without manual approval.

See detailed usage analytics across every team

The organization dashboard rolls up spend and token usage across every team in one view. Filter by team, user, service account, or cloud agent to see where usage comes from. Team admins keep a scoped view of their own team, which supports chargebacks by business unit or cost center.

Manage identity and membership at scale

With this structure, customers set up their identity provider and SCIM directory source once at the organization level. They can then re-use the same cohorts from these tools to create teams and groups in Cursor, ensuring that membership always stays in sync.

Admins can move users between teams through the dashboard, API, or CSV. And when a new user joins a team, settings and permissions apply automatically.

What's next

We’re continuing to add better policy controls, easier onboarding, SCIM-driven assignment, and simpler ways to manage subsets of users without forcing every workflow into separate teams.

Read more detail on how organizations, teams, and groups work in our docs. Please reach out to our team if you'd like to learn more or have questions.
Original source
Jun 3, 2026
- Date parsed from source:
  Jun 3, 2026
- First seen by Releasebot:
  Jun 3, 2026
IntelliJ IDEA by JetBrains

IntelliJ IDEA 2025.3.6 Is Out!

IntelliJ IDEA releases 2025.3.6 with the latest Oracle critical patch update for Java 21, boosting reliability and security.

IntelliJ IDEA 2025.3.6 is now available with the latest Oracle critical patch update for Java 21. The update includes the corresponding JetBrains Runtime changes and fixes the issue [IDEA-389015], providing improved reliability and security.

You can update to this version from inside the IDE, using the Toolbox App, or using snaps if you are a Ubuntu user. You can also download it from our website.

For a comprehensive overview of the fixes, see the release notes. If you spot any issues, let us know via the issue tracker.

Happy developing!
Original source
Jun 3, 2026
- Date parsed from source:
  Jun 3, 2026
- First seen by Releasebot:
  May 22, 2026
- Modified by Releasebot:
  Jun 4, 2026
Zed

1.5.3

Zed releases faster Mermaid diagrams, clickable document links from language servers, and sidebar thread renaming, while also improving Agent, Git, Markdown, remote development, and Helix workflows with new controls, performance gains, and bug fixes.
This week's release includes a new Mermaid renderer with faster and more accurate diagrams, clickable document links provided by language servers, and the ability to rename threads directly in the sidebar.

Features

AI

Agent: Made the Skill Creator window resizable and its contents scrollable when the window is smaller than the form. (#57754)

Agent: Improved read_file tool output rendering with a line-number gutter. (#56779)

Agent: Improved scrolling smoothness when expanding read_file tool calls with large file outlines. (#57287)

Agent: Improved visibility of pending tool call confirmations when they are scrolled out of view in the Agent Panel. (#57632)

Agent: Added a notification indicator to collapsed project headers in the sidebar when a thread completes. (#57322)

Agent: Added Fast Mode (priority service tier) support to OpenAI models used through the ChatGPT subscription provider. (#57436)

Agent: Added Fast Mode (priority service tier) support to the OpenAI API provider. (#57412)

Agent: Made file paths in backticks clickable in the Agent Panel; clicking opens the referenced file at the given line when present. (#57303)

Agent: Added automatic refreshes for the list of Zed-hosted models, without requiring a restart. (#57528)

Agent: Added the ability to reorder projects by moving them up and down through the sidebar ellipsis menu. (#57448)

Agent: Added support for renaming agent threads directly from the sidebar. (#57656)

OpenCode: Updated the model list, adding Gemini 3.5 Flash and Grok Build 0.1 and removing MiniMax M2.5 Free. (#57556); thanks Vlaaaaaaad

ACP: Added a logout flow for agents that support it. (#57492)

ACP: Allowed external agents that support it to access all working directories in a project. (#57497)

Git

Added a git_commit_buffer_font_size setting and made the in-panel and modal commit message editors zoomable. (#56077)

Added icons for Bitbucket, Codeberg, Forgejo, Gitea, and GitLab remote providers. (#57500); thanks albertbogusz

Improved Git worktree creation by fetching the latest origin/main before creating a worktree. (#57704)

Improved Git Graph commit tooltips. (#57032); thanks aaronang

Improved performance when opening the commit view for files with many diff hunks. (#57330)

Languages

Added support for clickable document links provided by language servers. This is enabled by default and can be disabled with "lsp_document_links": false. (#56011)

C++: Added recognition for HIP files. (#57333); thanks Young-TW

Rust: Improved toolchain compatibility by using the rust-analyzer from a worktree's Rust toolchain when specified. (#57696)

Vim / Helix

Swapped q and Q in Helix mode so they record and replay macros per Helix defaults instead of leaking Vim bindings. (#57622); thanks crazydude123

Remote Development

Added support for local features in dev containers. (#55225); thanks KyleBarton

Other

Improved Mermaid diagram rendering speed and accuracy. (#57644)

Added support for shift+click in Markdown preview to extend text selection. (#57586); thanks cppcoffee

Added a UI control for wrapping and unwrapping Markdown code block contents. (#57312)

Made the Project Panel auto-reveal multi-buffer excerpts for the latest selection. (#57236)

Added the zed: open status page action for opening the Zed status page. (#57316)

Settings UI: Added the setting scope (user or project) to Settings Editor breadcrumbs. (#57437)

Bug Fixes

Agent: Fixed commit message generation not respecting instructions from global AGENTS.md. (#57827)

Agent: Fixed errors not appearing in the UI when an edit tool call failed. (#57722)

Agent: Fixed read_file tool output not re-rendering in restored threads. (#56779)

Agent: Fixed stutters that could occur when interacting with the agent. (#57712)

Agent: Fixed deprecated Rules being automatically included in new agent requests. (#57844)

Agent: Fixed extra link styling on file paths in tool call labels. (#57515)

Agent: Fixed global skill edits appearing without a file path in the changes summary. (#57767)

Agent: Fixed a crash that could occur when adding a crease to the Agent Panel. (#58375)

Agent: Fixed a crash that could occur when searching or configuring tools in agent profile settings. (#58299)

Helix: Fixed g i and g a invoking Vim-mode bindings instead of goto_implementation and goto_last_accessed_file. (#57621); thanks crazydude123

Helix: Fixed g w not targeting words on lines selected with x. (#57565); thanks terror

Helix: Fixed r not replacing multi-character selections in select mode. (#57553); thanks terror

Helix: Fixed a crash that could occur when pasting at the end of a file. (#58373)

Fixed recent-project navigation always activating the main worktree instead of the last active worktree/workspace. (#57321)

Fixed edit prediction previews in the diff popover being occluded by open docks or the right sidebar. (#57519)

Fixed failed branch fetches preventing other Git state from updating. (#57292)

Fixed worktree creation being unavailable when resolving the default branch failed. (#57960)

Fixed branch enumeration when a broken Git ref prevents commit metadata from being read. (#57285); thanks GoldStrikeArch

Fixed incorrect truncation of multi-line text in the UI. (#57450)

Fixed commit modal buttons being hidden for some ui_font_size values. (#56366)

Fixed dot (.) repeat not repeating the last change made by a macro (@register). (#57684); thanks Fanteria

Fixed embedded terminal context menus showing agent actions that could target the wrong item. (#56256); thanks terror

Fixed go to line going to arbitrary lines in multibuffers. (#57700)

Fixed jump-to-definition for file paths wrapped in punctuation, such as backticks, parentheses, or sentence-ending punctuation. (#45457); thanks subtleGradient

Fixed language servers failing to install when the npm registry returns non-string values, such as "unpublished": null, in package time metadata. (#57765); thanks controversial

Fixed a crash when rendering Mermaid diagram flowcharts with deeply nested subgraphs. (#58325)

Fixed a noisy not signed in error being logged on every keystroke when not signed in to Zed. (#57615); thanks seth-wood

Fixed Markdown inline code highlighting in table cells. (#57506); thanks terror

Fixed outline panel hangs during massive project searches. (#57814)

Fixed Project Panel git status indicators showing modified files with a warning color instead of the modified color. (#57716)

Fixed project-local skill creation for remote projects. (#57453)

Fixed rare panic in the open path dialog. (#57290)

Fixed file watcher log flooding and repeated watch attempts after hitting the OS file watch limit. (#57720)

Fixed remote server logs growing unbounded. (#57672)

Fixed the settings window not respecting the server-side window decorations setting. (#57371); thanks hollmmax

Fixed the "About Zed" dialog being a full window instead of a floating window. (#57307); thanks cyyynthia

Fixed the Git Panel branch name staying truncated even when the panel was wide enough to show the full name (#57238). (#57502); thanks mateioprea

Fixed the project section header flickering in the agent threads sidebar when sending a message while the header was partially scrolled off screen. (#57529)

Fixed unnecessary Git state reloading that could occur when editing in linked worktrees. (#57763)

Fixed UTF-8 parsing issues when loading skill frontmatter with multi-codepoint graphemes, such as emoji, crossing file chunk boundaries. (#57466); thanks roboticsdude60

Breaking Changes and Notices

Removed support for ACP extensions. Installed ACP extensions will be migrated to ACP servers provided by the ACP registry, and resources from deprecated extensions will be automatically removed. (#57133)

Removed the retired GPT-5.2 and GPT-5.3 Codex models from the ChatGPT subscription provider. (#58340)

Original source
Jun 2, 2026
- Date parsed from source:
  Jun 2, 2026
- First seen by Releasebot:
  Jun 4, 2026
Windsurf

Windsurf is now Devin Desktop

Windsurf is now Devin Desktop.

Windsurf is now Devin Desktop.
Original source
Jun 1, 2026
- Date parsed from source:
  Jun 1, 2026
- First seen by Releasebot:
  Jun 1, 2026
Cursor

Improvements to Teams Pricing

Cursor increases Teams usage limits, adds a new Premium seat for heavy agent users, and improves spend forecasting and controls. The update splits usage pools, gives Standard seats more included usage, and adds real-time visibility plus smarter alerts to help teams manage costs.
We are increasing our Teams plan usage limits, introducing a Premium seat to support the heaviest agent users, and making it easier for admins to forecast and control spend. We anticipate that these improvements will lower costs for 90% of teams.

These changes will start for all new customers immediately, and renewing customers on billing cycles starting July 1st, 2026.

Increasing limits by adding a Composer-specific usage pool

Model choice is the most important determinant of costs. Until recently, the only way to get frontier performance was to pay frontier prices. Composer 2.5, our latest model, provides frontier performance at a fraction of the cost.

Every Teams seat will now come with two separate pools of included usage:

Composer and Auto: A generous pool reserved for first-party Cursor models.

Third-Party API: Usage consumed by third-party models.

This improvement to the Standard $40 per month seat will give every user significantly more usage, with no change in cost.

Improving cost predictability with a Premium seat for power users

As we showed in our recent Developer Habits Report, a small number of power users on any team tend to drive the majority of spend and unpredictable on-demand costs.

To lower costs and improve predictability for these users, we are introducing a new Premium seat: 5x the included usage of the Standard seat, at only 3x the cost. Teams can mix seat types freely. We expect the Composer pool on our new Premium seat to cover a full month of heavy agent usage for 99% of users.

Updated Teams seats:

Standard: Now includes more total usage. $32 per seat per month for annual plans; $40 per seat per month for monthly plans.

Premium: 5x the usage of Standard. $96 per seat per month for annual plans; $120 per seat per month for monthly plans.

Real-time usage visibility and better spend controls

The Cursor dashboard now shows users how close they are to hitting their limits, split between Auto + Composer and 3rd party API models. When users on your team would benefit from a specific seat type based on their usage behavior, we'll make recommendations to help you get the most value out of your plan.

We've also rebuilt our spend alerting. Admins can configure smart alerts based on dollar thresholds and have them delivered to the right people through Slack or email before a billing surprise happens.

Please let us know if you have any questions! You can check out this help article or email us at [email protected].
Original source
May 29, 2026
- Date parsed from source:
  May 29, 2026
- First seen by Releasebot:
  May 31, 2026
Cursor

Auto-review Run Mode

Cursor adds Auto-review run mode for longer, safer agent runs with fewer approvals.

Auto-review is a new run mode that allows Cursor to work for longer with fewer approval prompts and safer execution.

Auto-review applies to Shell, MCP, and Fetch tool calls. Allowlisted calls run immediately, and calls that can be sandboxed run in the sandbox. All other agent actions go to a classifier subagent that decides whether to allow the call, try a different approach, or ask for your approval.

Configure your run mode in Settings > Cursor Settings > Agents > Run Mode. You can also steer the classifier agent by giving it custom instructions.

Learn more in our docs.
Original source

Code Editors and IDEs Release Notes

Products (8)

Latest Code Editors and IDEs Updates

IntelliJ IDEA 2026.1.3 Is Out!

Added a new command for Devin Desktop to rerun the migration from Windsurf

Organizations for Cursor Enterprise

Organizations

Teams

Groups

Visual Studio Code 1.123

Welcome to the 1.123 release of Visual Studio Code.

Agents

Session sync and chronicle

Retry network-dependent commands in the sandbox

Agents window (Preview)

Research agent (Preview)

Integrated Browser

Favorite pages

More ways to capture screenshots

Editor Experience

Delayed extension auto-updates

Thank you

Introducing organizations for Cursor Enterprise

How the structure works

Enterprise use cases

Sandboxing to test new features

Segmenting model access, budgets, and agent permissions

See detailed usage analytics across every team

Manage identity and membership at scale

What's next

IntelliJ IDEA 2025.3.6 Is Out!

1.5.3

Features

AI

Git

Languages

Vim / Helix

Remote Development

Other

Bug Fixes

Breaking Changes and Notices

Windsurf is now Devin Desktop

Improvements to Teams Pricing

Increasing limits by adding a Composer-specific usage pool

Improving cost predictability with a Premium seat for power users

Real-time usage visibility and better spend controls

Auto-review Run Mode