Cursor
Details for running the Cursor Agent harness inside Conductor
Cursor Agent is Cursor's coding harness. Conductor runs Cursor sessions through the Cursor API with the Composer model exposed by Cursor.
Cursor quick facts
| Topic | Cursor |
|---|---|
| Availability | Cursor Agent through the Cursor API. Requires a Cursor API key. |
| Setup | CURSOR_API_KEY in Settings -> Harnesses -> Cursor, or Conductor environment settings. |
| Models | Cursor Agent models exposed by the Cursor API. |
| Billing | Cursor plan, API usage pools, API key, and on-demand usage. |
| Controls | Plan Mode, Fast Mode, skills, and checkpoints are not supported today. |
Setup notes
Cursor Agent sessions use the Cursor API and need a Cursor API key. The key can be added in Settings -> Harnesses -> Cursor, or set as CURSOR_API_KEY in Conductor's environment settings.
There is no Cursor executable path to configure in Conductor settings.
For a setup walkthrough, see Configure model providers: Cursor.
Cursor's editor surface remains available through Open In or Command O. Opening the workspace in Cursor does not replace the Conductor workspace.
MCP
Cursor Composer supports MCP through Cursor's own MCP configuration. Use ~/.cursor/mcp.json for user-level servers or .cursor/mcp.json in the repository root for project-level servers.
When you open a Conductor workspace in Cursor, Cursor reads project-level MCP config from that workspace checkout. Conductor-hosted Cursor sessions do not currently surface Cursor MCP server status in Conductor's MCP status UI.
For the shared reference, see MCP. For a setup flow, see Set up MCP servers.