Cursor
How Conductor runs Cursor sessions and how Cursor usage is billed
Conductor supports Cursor sessions through Cursor's API key. Cursor sessions run inside Conductor workspaces, so the chat, branch, terminal, diff, checks, pull request, and archive state stay tied to the workspace.
Conductor currently supports Cursor's Composer 2.5 for Cursor sessions.
Cursor
Cursor sessions, including Composer 2.5, running inside Conductor's workspace workflow.
CURSOR_API_KEY in Settings -> Providers -> Cursor, or Conductor environment settings.Models
Use the provider docs for the live model list and pricing.
| Model | Guidance |
|---|---|
| Composer 2.5 | Cursor's agentic coding model for sustained software tasks. Cursor documents composer-2.5 as the model ID for Composer 2.5. |
| Composer 2.5 Fast | Default fast variant of Composer 2.5 for interactive sessions. Cursor documents Fast as a variant of Composer 2.5, not a separate published model ID. |
Capabilities and controls
These notes describe how Conductor wraps the harness and where provider controls still apply.
Composer inside Conductor
Use Cursor's model while Conductor keeps the workspace, branch, terminal, and review path organized.
Cursor owns usage pools
Cursor plan and API usage pools decide how usage is counted and billed.
Editor still available
You can still open the same workspace in the Cursor IDE when manual editing belongs there.
When to use Cursor
Use Cursor when you want Cursor's agent model in Conductor's workspace workflow. Cursor is useful when you want Cursor sessions to run alongside Claude Code or Codex, or when you want Conductor's workspace sidebar, setup scripts, run scripts, diff review, checks, and pull request flow around Cursor work.
If you want Cursor's editor surface for manual editing, open the workspace in Cursor with Open In or Command O. Opening the workspace in Cursor does not replace the Conductor workspace.
Setup
Cursor sessions need a Cursor API key. Add it in Settings -> Providers -> Cursor, or set CURSOR_API_KEY in Conductor's environment settings.
There is no Cursor executable path to configure in Conductor settings. Cursor sessions use Conductor's Cursor integration and your Cursor API key.
Usage and billing
Conductor does not bill or meter Cursor usage. Cursor usage draws from your Cursor plan, API usage pools, API key, and Cursor limits.
Cursor's docs describe usage pools, plan-included API usage, model pricing, Composer pricing, and on-demand usage. Composer 2.5 has its own model page and pricing details. Check Cursor's live docs for current plan limits and rates before planning heavy parallel Cursor work.
Composer 2.5 pricing
Cursor documents Composer 2.5 and Composer 2.5 Fast separately from provider model pricing. Use Cursor's live Composer 2.5 page for the current rate card; Conductor only passes your Cursor session through your configured Cursor API key.