Supported agents and features

This page lists the AI coding agents JetBrains Central CLI supports, and the features available to you when you use them. JetBrains Central CLI supports command-line agents; running an agent inside an IDE or a desktop application is outside its scope.

The tables below describe what is generally available. To see what applies to your own session — which agents your organization allows, and which ones your login method can use — run central agents.

Supported agents

Agent	Connect with	Routed to	Service accounts	Requirements and limits
Claude Agent	`central add claude`	Anthropic, or Amazon Bedrock when your organization provisions it	Yes	—
Codex	`central add codex`	OpenAI	Yes	—
Gemini CLI	`central add gemini`	Google Vertex	Yes	Trust the folder when Gemini CLI asks. If you decline, Gemini CLI ignores its own configuration files, including the settings JetBrains Central CLI wrote.
Junie CLI	`central add junie`	Several model vendors, through JetBrains' own gateway, on a JetBrains Account login; OpenAI, Anthropic, or Google Vertex on JetBrains Central Server	No	Requires a GA build — EAP builds are not supported. Requires a personal account, so it is unavailable on a service-account session.
Pi	`central add pi`	Anthropic, OpenAI, and Google Vertex, or Amazon Bedrock when your organization provisions it	Yes	—

Available features

Feature	Description	Availability
Routing through the JetBrains AI Platform	A connected agent's requests are authenticated with your JetBrains credentials and billed to your JetBrains AI subscription, so no model-vendor API key is involved	All supported agents
Seat-based login and licensing	Log in once with your JetBrains Account. Your AI access can come from an organization workspace seat or from a license, and you choose which one a machine uses.	All supported agents
Multi-provider routing	One connection reaches Anthropic, OpenAI, and Google Vertex models, and Amazon Bedrock where your organization has provisioned it, without per-vendor setup	Which providers apply depends on the agent — see the table above
Per-developer usage logging and quota visibility	`central limit` reports your AI credit usage against your limit, and `central log` your per-request history. The request log stays on your machine and records metadata only.	All supported agents. Organization-level spend attribution and finance reporting are JetBrains Central features, not JetBrains Central CLI ones.
Agent availability control	Your administrator decides which agents your organization may use. JetBrains Central CLI keeps that list current, refuses to connect an agent that is not on it, and disconnects one that leaves it.	All supported agents. Applies to workspace-backed access only — license-backed access is unrestricted.
Model availability control	Your administrator decides which models your organization may use, and the proxy enforces that for agent traffic	Configured in JetBrains Central, not in JetBrains Central CLI. Applies to workspace-backed access only.
Audit and traceability	Every request a connected agent makes goes through the governed proxy path and is logged, which is what makes it auditable	All supported agents. The audit and reporting views themselves live in JetBrains Central.
Service accounts	A non-personal login for headless and CI use	All supported agents except Junie CLI

18 September 2026