JetBrains outlines its 2026 strategy for integrating AI into its IDEs while preserving classic coding workflows. The approach centers on coexistence: developers can use traditional typing/refactoring workflows or AI-assisted/agentic workflows without one compromising the other. Key commitments include avoiding vendor lock-in through multiple AI connection options (JetBrains subscription, BYOK, OAuth, and the new Agent Client Protocol), ensuring AI-generated code is visible, reversible, and reviewable, and treating generated code with the same rigor as human-written code. The Agent Client Protocol (ACP) allows external agents like Cursor to be connected to JetBrains IDEs via a standard interface. The overarching principle is that humans remain responsible for shipped code, and the IDE is the best place to review and own it.
Table of contents
What “AI in the IDE” means without the snake oil or hypeThe AI strategy: Avoid vendor lock‑in and keep workflows compatibleAgent Client Protocol (ACP): “Bring your own agent”“Professional coding with AI” means more responsibilityAI on your terms: our product commitmentsSort: