CursorがJetBrains IDEに対応、AI機能を統合提供 Cursor in JetBrains IDEs

Cursor, the AI-first code editor that has rapidly gained traction over the past two years, is now available inside JetBrains IDEs. Developers using IntelliJ IDEA, PyCharm, WebStorm, GoLand, RubyMine and other JetBrains tools can now access Cursor's AI agents and completions without abandoning the IDE they rely on for daily work.

Until now, Cursor has shipped as a standalone editor based on a fork of VS Code. That approach worked well for web and Python developers already comfortable in the VS Code ecosystem, but it created friction for teams entrenched in JetBrains tooling — particularly Java, Kotlin, Scala and large enterprise codebases where JetBrains' deep static analysis, refactoring engine and language-specific intelligence are hard to give up. Bringing Cursor to JetBrains as a plugin removes that switching cost and opens the product to a substantially larger audience.

Functionally, the integration is intended to mirror what Cursor users expect from the native app: agentic coding workflows that can autonomously edit across files, codebase-aware chat that grounds responses in the actual project, and AI completions that go beyond single-line suggestions. These features run alongside JetBrains' own inspections, debugger and indexing, so developers get AI assistance without losing the structural understanding that makes JetBrains IDEs distinctive.

The move arrives in an increasingly crowded AI coding market. GitHub Copilot remains the incumbent, while Windsurf, Cline, Aider and Continue all compete for mindshare among power users. JetBrains itself has been investing heavily, shipping its AI Assistant and more recently Junie, an autonomous coding agent positioned as a direct response to Cursor and Devin. The line between IDE vendor and AI tooling vendor is blurring quickly, and Cursor's decision to expand onto a competitor's platform suggests it wants to be seen as a portable AI layer rather than a single editor.

From a strategic angle, this likely reflects a recognition that locking AI capabilities to a custom editor caps the addressable market. By meeting developers where they already work, Cursor can monetize teams that would never adopt a new IDE wholesale, including regulated enterprises with strict tool standardization. It also pressures JetBrains' own AI offerings, which now have to compete inside their own product surface.

Several details remain worth watching. It is unclear how feature parity will evolve over time — agent capabilities in particular tend to depend on tight editor control, and a plugin architecture may impose limits compared with the native Cursor app. Pricing and how existing Cursor subscriptions transfer to the JetBrains context will also matter for adoption, as will the breadth of supported IDEs and whether Rider, Android Studio and other JetBrains-derived environments are covered. Still, for developers who have wanted Cursor's agent experience without leaving IntelliJ, this is a significant unlock.