Cursor agents inside JetBrains IDEs

ACP turns Cursor from a packaged editor into a service layer that can ride on top of the IDEs many professional teams already refuse to leave. That matters most in Java, Kotlin, and large enterprise codebases, where IntelliJ and its siblings are the default home. Instead of asking those teams to switch editors, Cursor can now sell its agent while JetBrains keeps the editing surface, language tooling, and project setup developers already trust.1 2 3 4

• The practical workflow is simple. A developer stays inside IntelliJ IDEA, PyCharm, or WebStorm, opens JetBrains AI Assistant, and connects Cursor as the agent through ACP. Cursor handles planning, file edits, and terminal style actions, while JetBrains keeps native language support, inspections, and project awareness.1 2 3
• This changes Cursor's competitive position. As a VS Code fork, it had to win both the editor choice and the AI choice at once. ACP separates those decisions. Cursor can now compete more like a model powered agent backend, similar to how cloud services plug into existing developer workflows instead of replacing them outright.2 3 4
• It also fits Cursor's broader expansion beyond code writing. Automations pushes agents into Slack, GitHub, Linear, and PagerDuty. Graphite adds the pull request and review surface after the December 19, 2025 signed deal. The pattern is clear, Cursor is trying to own the agent across writing, testing, review, and merge points, not just inside one editor window.4 5 6

The next step is a world where the IDE matters less than the agent account. If ACP keeps spreading, Cursor can become the portable worker that follows developers across JetBrains, terminals, mobile, cloud sandboxes, and code review, which makes distribution less dependent on winning the editor and more dependent on owning the best autonomous coding loop.1 2 4 5 6