ACP in JetBrains IDE — Model Selection, Pricing Clarification, and Enterprise Privacy

To: Cursor Team

We have recently integrated the Cursor ACP (AI Coding Partner) into our JetBrains IntelliJ IDEA environment. While the initial experience is promising, as an enterprise subscriber, we require clarification on the following points to ensure alignment with our internal workflows and compliance standards.


1. Model Selection & Control

Currently, the ACP plugin in IntelliJ IDEA appears to be locked to an “Auto” mode, with no visible option to manually select specific models (e.g., Claude 3.5 Sonnet, GPT-4o).

  • Question: Is this “Auto-only” behavior the intended design for the current stage of ACP?
  • Future Roadmap: Are there concrete plans to introduce manual model switching within JetBrains IDEs, similar to the functionality available in the Cursor Desktop application?

PS: I’m not quite sure, but it seems there is a dropdown box here, but it’s completely blank inside.

2. Clarification on “Free” Usage

The official documentation mentions that ACP is currently “free.” We would like to understand the boundaries of this term:

  • Scope: Does “free” refer only to the plugin’s availability, or does it mean that model invocations/tokens consumed via ACP currently do not count against our Enterprise subscription’s monthly request/token quotas?
  • Policy Duration: Is this a permanent feature of the ACP integration, or is it a temporary promotional/beta period?

3. Enterprise Privacy & Data Training Policy

As an Enterprise customer, we have a strict agreement ensuring our code is not used for model training. We need to confirm that the ACP channel maintains the same rigorous standards:

  • No-Training Guarantee: Does our existing Enterprise privacy agreement (Zero Data Retention / No Training) fully extend to all data processed through the ACP plugin in third-party IDEs?
  • Data Routing: Does the data routing and the use of third-party LLM providers remain consistent with our primary Enterprise contract terms when using ACP?
  • Policy Parity: Can you confirm there are no “policy gaps” between using the native Cursor Desktop app and the ACP integration regarding data handling?

We look forward to your detailed response to help us finalize our internal rollout strategy.

Thank you for your time. Looking forward to your response.

Hey, thanks for the detailed questions. Here’s a point by point answer.

  1. Model Selection in JetBrains ACP

Auto-only isn’t by design. Model selection in ACP should work, see JetBrains docs JetBrains | Cursor Docs which says you can choose from frontier models. But in cursor-agent acp version 2026.05.07 there’s a regression. configOptions and availableModels return an empty list, so the dropdown in JetBrains ends up empty. Details and confirmation from the team here: ACP model selection API removed?

Current workaround is to start the ACP server with --model <model-id> on launch. Switching models at runtime mid-conversation doesn’t work yet. The CLI team is working on a fix, I can’t share an ETA. I’ll follow up once it’s released.

  1. What “free” means for ACP

The ACP plugin and the integration itself don’t cost extra for users on paid plans. But that does not mean requests sent via ACP don’t count. ACP usage is billed the same way as normal Cursor usage, it comes out of your plan quota. There’s no separate free quota for ACP. This isn’t a temporary promo, it’s the built-in pricing model.

  1. Enterprise Privacy via ACP

ACP uses the same backend and the same data routing practices as native Cursor. The no training on Inputs or Suggestions policy applies the same way across all Cursor surfaces, native IDE, CLI, and ACP in JetBrains. There’s no policy gap between the native app and ACP.

That said, if you need strict verification for your specific Enterprise contract terms, like ZDR, model provider list, data residency, and so on, it’s best to reach out via your Enterprise admin or AE at [email protected] so they can confirm coverage for your exact agreement.

Let me know if you want me to dig deeper on any of these points.