Developer Tools
Cortex for JetBrains IDEs
Use Cortex in supported JetBrains IntelliJ-platform IDEs.
Cortex for JetBrains brings the Cortex conversation into a supported IntelliJ-platform project. The tool window lets developers discuss code and security questions alongside their current development work.
Get started
Section titled “Get started”Install the signed Cortex plug-in using the button above or your approved managed plug-in repository, restart the IDE, and open a project. Open the Cortex tool window and sign in.
Project-context assistance
Section titled “Project-context assistance”Cortex uses the current project and explicit selections as context. Ask for an explanation, plan, security review or change, then inspect the diff and validation before applying it. Organization policy can restrict models, connectors, execution targets and file actions.
This supports understanding unfamiliar code, discussing a defect or assessing the security implications of a proposed change. The relevant project context helps keep the conversation tied to the work in the IDE.
Choosing the supported experience
Section titled “Choosing the supported experience”The Marketplace entry lists the compatible IDE products and versions for the published plug-in. The installed tool window exposes its available actions; use those controls when determining the supported review or change workflow.
Developer Tools explains how the editor clients fit into Cortex. DevSecOps provides the broader project-reporting experience, and Account & Billing covers the shared subscription.
Product role in a JetBrains workflow
Section titled “Product role in a JetBrains workflow”The plug-in brings Cortex assistance into the project environment rather than requiring every question to move to an unrelated web chat. Use selected code and supported project context to understand an implementation, investigate a problem or prepare a security-focused discussion while remaining in the IDE.
Make the objective explicit: what behavior should change, what existing behavior must remain and what evidence would establish success? Inspect any proposed changes using the controls available in your installed version and validate them with the project’s normal tests and review process.
Complementary product experiences
Section titled “Complementary product experiences”The public IDE expansion describes Visual Studio Code, Visual Studio and JetBrains IntelliJ IDEA as distinct ways to use Cortex. The Marketplace compatibility list determines which IntelliJ-platform products and versions can install this plug-in; that is not a promise of support for every JetBrains IDE.
Use DevSecOps for broader project reports and AI Code Review for the separate GitHub App or Action. Those integrations complement the IDE conversation but have their own setup, permissions and assessment scope.
Product background
Section titled “Product background”The Cortex expansion across three IDEs explains the role of the JetBrains offering within Developer Tools.
Availability
Section titled “Availability”If a feature shown elsewhere is absent, update the plug-in and check tenant policy; clients advertise capabilities independently and do not assume parity.

