JetBrains Fleet Shutdown — when and how should I migrate?

Teams that adopted Fleet need change awareness on whether to migrate to IntelliJ-based IDEs, VS Code, or another editor now that Fleet has been discontinued.

JetBrains IntelliJ-based IDEs if you want the safest Fleet exit; choose VS Code only when cost or extension flexibility matters more than migration ease.

Blockers

Who this is for

Candidates

Migrate to JetBrains IntelliJ-based IDEs

As of 2026-03-28, Fleet's shutdown has already occurred: JetBrains stopped Fleet updates and ended download distribution on December 22, 2025. JetBrains explicitly says the path forward is to strengthen AI workflows in its existing IntelliJ-based IDEs rather than keep Fleet as a standalone editor. JetBrains also changed the IntelliJ IDEA product model in the same period: the unified distribution started with IntelliJ IDEA 2025.3, and license-expiration behavior changed in 2025.2 so expired Ultimate users keep the same IDE with the free feature set. JetBrains announced IDE subscription price increases effective October 1, 2025; check the current buy page for the exact price on your product and billing type.

When to choose

Best for enterprise or small-team setups that already rely on JetBrains language intelligence, inspections, or existing IDE workflows. Choose this when the main goal is the lowest migration friction from Fleet into a supported JetBrains path.

Tradeoffs

Lowest ecosystem-switch cost if your team already uses JetBrains tooling, but most advanced features remain tied to paid subscriptions. IntelliJ IDEA is also converging on a single distribution rather than a separate Community installer, which simplifies rollout but changes how teams think about free versus paid features.

Cautions

Do not plan around Fleet receiving future fixes. JetBrains says already-downloaded Fleet copies may continue to run, but server-side features including AI Assistant may stop working over time. Also note that IntelliJ IDEA Community Edition is no longer distributed separately starting with 2025.3.

Migrate to Visual Studio Code

As of 2026-03-28, VS Code remains a supported mainstream alternative and the editor itself is officially free for private or commercial use. Microsoft positions it as a streamlined code editor rather than a full IDE, which makes it the clearest low-cost landing zone if you are leaving Fleet's lighter-editor model. VS Code's FAQ also confirms Copilot is still licensed separately even though some AI features are built into the product experience, so editor cost and AI cost should be budgeted separately. Current platform caveat: VS Code 1.107, released in November 2025, stopped updating on macOS Big Sur, and 1.106 is the last available release for that OS.

When to choose

Best for cost-sensitive teams or polyglot teams that want a free editor baseline with broad extension coverage. Choose this when you prefer a lighter core editor and are willing to assemble language support, AI, and workflow features through extensions.

Tradeoffs

Lowest base editor cost, but migration usually means rebuilding Fleet workflows from extensions and team conventions. It is more flexible than prescriptive, which can be a strength for mixed stacks and a weakness for standardization.

Cautions

Do not assume built-in AI means zero AI spend: the official FAQ says GitHub Copilot subscriptions are still separate, although a free Copilot plan exists with limits. Verify OS support during rollout, especially if any developers are still on macOS Big Sur.

Facts updated: 2026-03-28
Published: 2026-04-03

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "JetBrains Fleet Shutdown — when and how should I migrate?"
Missing something? Request coverage