Cursor CLI

Dedicated Cursor CLI plugin support instead of a generic shell wrapper.

Agent guide

Cursor CLI works well for teams already living inside Cursor and wanting that runtime to be a first-class choice in Conductor rather than an unsupported shell fallback.

Binary: cursor-cliAliases: cursor, cursor-agentBest for Cursor-native repos

Primary binary

cursor-cli

Known aliases

cursor, cursor-agent, cursor-agent-cli

Good fit

Cursor-centric teams, agent switching, and dedicated alias normalization.

​

Set up Cursor CLI in Conductor

1. Install the Cursor CLI

   # install cursor-cli or cursor in your environment
   
2. Complete sign-in if required

   Make sure the installed CLI works in your shell before selecting it in a workspace profile.

3. Launch Conductor

   npx --yes --registry=https://registry.npmjs.org conductor-oss@latest
   

   Add the workspace and select Cursor CLI for the repositories that already use Cursor-oriented workflows.

4. Set the project default

   projects:
     my-app:
       agent: cursor-cli
   

​

Model selection in Conductor

Cursor CLI model availability comes from the Cursor environment attached to that machine.

• leave agentConfig.model unset when Cursor should keep using its default or workspace-selected model
• pin a model only when a repository needs a documented exception
• keep the model source of truth in Cursor unless there is a clear operational reason to override it here

​

Why teams pick Cursor CLI

• smoother fit for Cursor-native teams
• keeps aliases normalized across environments
• avoids generic shell dispatch for a supported runtime