Cursor becomes cross-IDE agent layer

The key shift is that Cursor no longer has to win by replacing a developer's editor, it can now sell the agent itself wherever developers already work. ACP puts Cursor inside IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs, so a Java or Python team can keep its existing setup and still use Cursor to read the codebase, edit files, and run terminal commands inside the IDE.1 2 3

• This matters because JetBrains is where many enterprise developers already live, especially in Java and Python. JetBrains reported 11.4M plus users across its products, and its 2024 Python survey showed VS Code at 48 percent as the main editor for Python developers versus PyCharm at 25 percent, which is a large installed base Cursor can now reach without forcing migration.1 4 5
• ACP changes the product from a bundled editor into a service layer. In JetBrains, Cursor is installed from the ACP registry and used through the AI Chat panel, with the same paid Cursor account and usage based pricing. That means distribution can shift from getting developers to download a new IDE to adding Cursor as an agent provider inside tools teams already approve.2 3
• Graphite extends the same logic beyond the IDE into code review. Cursor said in December 2025 that Graphite had built a code review platform used by hundreds of thousands of engineers, and that tighter links between local development and pull requests were a core reason for the deal. Together, JetBrains support and Graphite move Cursor from code writing into review and merge workflows.6 7 8

The next step is a broader developer workflow stack where Cursor is present in the editor, in background automations, and in pull requests. If that integration keeps improving, Cursor becomes less like a single app and more like the default agent layer across the everyday tools software teams already use.2 6 8