Cursor IDE with ACP support

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Cursor currently has to manually add support for individual agents and their models. That means we have to create a feature request and then wait until implementation is done. To short-circuit that, the Cursor IDE should support the Agent Communication Protocol (ACP).

Feature requests like the Mistral Devstral model could have an interim solution of Bring Your Own Agent until Cursor gets to adding the model.

3
4

Hi Colin,

There’s a misunderstanding. The request is not to make Cursor available to other IDEs, but to make other agents available in Cursor via ACP. Basically, what your announcement plugged into should be made available in Cursor.

5

Current Issue
Cursor needs manual support for each agent/model (e.g., Mistral Devstral), creating delays via feature requests.

Proposed Solution
Add ACP support for “Bring Your Own Agent” – let Cursor IDE act as orchestrator.

Scenario

  • Create a feature branch for your agent (Cursor CLI, Codex, Claude, Gemini, Mistral).

  • Cursor IDE gives full repo context to the agent via ACP.

  • IDE supervises progress and waits for PR to main branch (or intermediate steps).

Benefits
Instant access to any ACP agent, unified UX, no waiting for integrations. :rocket:

7

I would further suggest IDE support for ACP isn’t just for “bring your own agent”. It can be used to run cursor’s agent in a container (sandboxed nicely) and interact with it in the non-containerized IDE.

I know we can “devContainer” our way there. But this is simple.
I’ve done so with Kimi and Zed. It would be swell to use Cursor with Cursor :slight_smile: