Hey, thanks for the report. This looks like a region limitation, not an ACP routing bug. In China, OpenAI and Anthropic models aren’t available, and kimi-k2.5 is the only frontier model we can serve to users in CN. So no matter what you pick in the model picker, the request ends up on kimi-k2.5, which matches what you’re seeing in the dashboard. In your screenshot, I can see consecutive idle events going to kimi-k2.5.
The UX here is definitely rough. The ACP or JetBrains picker still shows models that aren’t available in your region instead of filtering the list. We’ve logged this gap, but there’s no ETA for a fix yet.
Hey, thanks for the report. One important detail: you’re in India, so your case is different from the first post in this thread. That one is China, where only kimi-k2.5 is available due to regional restrictions. Your case is different. This is a known issue where the ACP picker in JetBrains doesn’t pass the model selection to the agent, so the request falls back to composer-2.5-fast. The same symptom is discussed in this thread: Model selection in Phpstorm via ACP is not working, which you’ve already checked. The issue is being tracked, but there’s no ETA for a fix yet.
About the “stuck” command, that’s actually expected behavior, not a bug. agent acp or cursor-agent acp is a stdio server that just waits for a client (the IDE) to connect and send protocol messages. So if you run it manually in a terminal, you’ll see “Waiting…” with no output. That’s normal, and there’s no point running it by itself.
To pin a model via a workaround, you need to add the --model flag not to a manual run, but to the ACP agent launch command in JetBrains settings where the IDE starts the Cursor agent. In other words, add --model <model-id> to the agent launch arguments. You can get the list of available IDs with:
agent --list-models
This will lock the model for the session. Runtime switching via the picker in the IDE won’t work until this is fixed. Let me know if you were able to add the flag in the config.
