Activation scenarios
By default, AI Assistant uses models provided through the JetBrains AI service to deliver AI functionality.
However, you can also configure it to use models from third-party providers, authorize integrated agents with their provider account, or connect external agents that support the Agent Client Protocol (ACP).
The following activation scenarios are available:
- JetBrains AI subscription
Use models provided through the JetBrains AI service.
- Bring Your Own Key (BYOK)
Use models from supported third-party AI providers by configuring your own API key.
- OAuth
Authorize supported integrated agents using your provider account.
- ACP-compatible agents
Connect to external agents that provide AI capabilities through the Agent Client Protocol (ACP).
You can use these scenarios independently or configure several of them at the same time. Each option supports different AI capabilities and uses a different billing mechanism.
Feature availability and billing
The selected activation option determines which AI Assistant features are available and how usage is billed:
When using a JetBrains AI subscription, all AI Assistant features are available, and usage is billed through the JetBrains AI service.
When using external providers or agents (BYOK, OAuth, or ACP agents), some AI Assistant features may be unavailable, and usage is billed by the corresponding external provider.
The following table summarizes the differences between the available scenarios.
Activation scenario | Requires JetBrains AI subscription | Available features | Billing |
|---|---|---|---|
JetBrains AI subscription | Yes | All features | Billed through JetBrains AI service subscription |
API Key (BYOK) | No | Most features [1] | Billed by the selected AI provider |
OAuth (currently, Codex only) | No | Specific agent only | Billed by the account provider |
ACP-compatible agent | No | Specific agent only | Billed by the agent provider (if applicable) |
Combined configurations
Multiple activation scenarios can be enabled at the same time. When several scenarios are active, AI Assistant selects the provider according to a predefined priority order.
Active scenarios | Priority order | Behavior |
|---|---|---|
JetBrains AI | JetBrains AI | All AI Assistant features are available because the required models are provided by the JetBrains AI service. |
BYOK | BYOK | AI Assistant features work only if compatible models are available from the configured third-party provider. |
OAuth | OAuth | The OAuth-authorized agent uses the provider account. |
ACP-compatible agent | ACP agent | Requests to the ACP-compatible agent are handled by the agent provider. |
JetBrains AI + BYOK |
|
|
JetBrains AI + OAuth |
|
|
OAuth + BYOK |
|
|
JetBrains AI + BYOK + OAuth |
|
|
How data is handled in different scenarios
Depending on the selected activation scenario, data may be handled differently:
The IDE sends prompts and context to the JetBrains AI service, which coordinates the request but does not store or process the data. The request is then forwarded to the LLM provider, and the response returns along the same path.
Prompts and context are sent directly to the BYOK-configured LLM provider using the user's API key.
If the feature is supported by the models from a third-party provider, prompts and context are sent directly to the BYOK-configured LLM provider.
If the feature is not supported by the models from a third-party provider, prompts and context are sent to the JetBrains AI service, which coordinates the request but does not store or process the data. The request is then forwarded to the LLM provider, and the response returns along the same path.
Prompts and context are sent directly to the agent provider.
Prompts and context are sent directly to the ACP agent provider using the user's API key (if applicable).