In a move that has sent ripples through the developer community, JetBrains announced on December 8, 2025, the discontinuation of Fleet, their ambitious next-generation integrated development environment (IDE). After four years in public preview, Fleet—once heralded as a modern, lightweight challenger to both traditional JetBrains tools and competitors like Visual Studio Code—will cease to be available for download starting December 22, 2025. No further updates will be released, marking the quiet sunset of a project that promised to redefine how developers interact with code.
The Birth of Fleet: A Bold Experiment
JetBrains first unveiled Fleet in November 2021 as a “next-generation IDE” built entirely from scratch. Unlike the company’s longstanding IntelliJ platform—which powers flagship products like IntelliJ IDEA, PyCharm, WebStorm, and Rider—Fleet featured a distributed architecture, a sleek modern UI, and a focus on performance and flexibility. It aimed to shed decades of legacy code, offering faster startup times, built-in collaboration features (integrated with JetBrains Space), and a polyglot approach supporting multiple languages out of the box.
The vision was clear: create a lightweight yet powerful tool that could serve as an editor for quick tasks or scale into a full IDE with “Smart Mode” for advanced code assistance. Fleet leveraged the IntelliJ code-processing engine for intelligence while introducing innovations like remote development, plugin extensibility, and AI integration.
Over the years, Fleet received regular updates, reaching version 1.47 earlier in 2025 with features like multiline comment folding and enhanced AI chat. It experimented with ideas like “Islands UI” for a more modular workspace and support for emerging languages like Zig. Yet, despite these advancements, Fleet never transitioned out of preview status.
Why Fleet Failed to Launch
In their official blog post “The Future of Fleet”, JetBrains was candid about the reasons for discontinuation. Product leads Aleksey Stukalov (IntelliJ IDEA) and Ekaterina Prigara explained that maintaining two general-purpose IDE families caused significant confusion among users. Developers frequently asked, “Should I use Fleet or IntelliJ IDEA?”—and there was no concise, compelling answer.
Key issues included:
- Overlap with Existing Tools: Rebuilding IntelliJ-level features in Fleet didn’t add enough unique value. Positioning it as “just another editor” couldn’t justify the resource split.
- Diluted Focus: Supporting parallel product lines spread JetBrains’ engineering efforts thin.
- Market Positioning: Fleet struggled to carve a niche against the dominant Visual Studio Code (with its vast extension ecosystem) or JetBrains’ own mature, feature-rich IDEs.
Early warning signs appeared in February 2025 when JetBrains abandoned plans for a dedicated Kotlin Multiplatform IDE based on Fleet, opting instead to enhance IntelliJ support. Adoption remained limited, with many developers sticking to familiar tools.
While Fleet was a “worthwhile experiment” technically—yielding reusable components and UI concepts now integrated into other JetBrains products—it didn’t succeed commercially as a standalone offering.
For comparison, here’s how Fleet stacked up against its siblings:
| Feature | Fleet | IntelliJ IDEA Ultimate |
|---|---|---|
| Architecture | Distributed, built from scratch | IntelliJ Platform (legacy-rich) |
| Startup Time | Very fast | Moderate |
| Full IDE Capabilities | Partial (Smart Mode) | Comprehensive |
| Plugin Ecosystem | Growing but limited | Extensive Marketplace |
| AI Integration | Built-in chat and assistance | AI Assistant plugin |
| Remote Development | Native support | Via Gateway or plugins |
| Status (as of Dec 2025) | Discontinued | Actively developed |
Impact on Users and What Happens Next
Existing Fleet installations will continue to function, but server-dependent features (like AI Assistant) may degrade as backend support ends. JetBrains recommends migrating to IntelliJ-based IDEs for heavy workloads or lighter alternatives like VS Code.
The Fleet team isn’t disbanding; they’re pivoting to a new frontier: agentic development. This emerging paradigm shifts from traditional synchronous IDE workflows to AI-driven, asynchronous processes—defining structured tasks, assembling context, running agents in isolation, and reviewing results first.
JetBrains is channeling Fleet’s technology into JetBrains Air, an agentic development environment (ADE) currently in preview at air.dev. Air allows developers to delegate complex coding tasks to AI agents working in parallel, with full human oversight. It builds on Fleet’s platform but targets workflows suited to tools like Cursor, Claude Code, or emerging competitors.
This aligns with JetBrains’ broader AI push, including Junie (their in-IDE coding agent) and integrations like Claude Agent.
Community Reactions and Broader Context
Reactions have been mixed. Many expressed disappointment on forums, Reddit, and X, lamenting lost potential in competing with VS Code’s lightness and ecosystem. Critics noted JetBrains’ recent pattern of sunsetting products (e.g., Aqua in 2025, SpaceCode, Writerside), questioning resource allocation amid AI hype.
Others praised the honesty and legacy: Fleet’s innovations live on in refreshed IntelliJ UIs and components. As one developer put it, “Fleet was an experiment that paid off—even if not as a product.”
In an industry racing toward AI-augmented development, JetBrains’ decision reflects pragmatic focus: strengthen core strengths (IntelliJ ecosystem) while exploring agentic tools separately.
Conclusion: Lessons from Fleet’s Journey
Fleet’s discontinuation underscores the challenges of innovation in a mature market. Bold rewrites risk overlapping with proven tools, and finding a “killer niche” is harder than building impressive tech. Yet, JetBrains emerges stronger, with Fleet’s DNA enhancing their lineup and fueling Air’s agentic future.
If you’re a Fleet user, grab the latest version before December 22. For everyone else, watch JetBrains Air—it may represent the next evolution in how we code.
As of December 13, 2025, the Fleet website redirects to the announcement, signaling the end. But in software development, endings often prelude exciting new beginnings.