Setup
Cursor uses an API key. There is no OAuth flow like Claude Code or Codex.- Generate a user API key from Cursor Dashboard → Integrations, or a service account API key from Team Settings if your org uses Cursor Enterprise.
- Paste the key in Preferences → Organization → Coding Agents during onboarding or anytime later.
- Set org-level credentials for the whole team, or add a personal key in Account settings (Preferences → Account) that takes priority over org defaults.
User API keys bill to that user’s Cursor plan. Service account keys bill to the team that owns the service account.
Models
Cursor proxies many underlying models (Composer, Claude, GPT, Gemini, Grok, and more). The models available in Replicas depend on whether your organization has a connected Cursor API key. When an organization Cursor API key is connected, Replicas loads the live model catalog from Cursor and lets admins enable any returned model ID in Preferences → Organization → Coding Agents → Cursor → Models. The checklist is searchable and paginated so large Cursor catalogs stay manageable. If no organization Cursor API key is connected, Replicas falls back to its default Cursor model list. See Credentials for organization and personal key behavior. Set the org default model under Preferences → Organization → Settings → Defaults. Each workspace remembers the model used on its Cursor chat tab.Using Cursor in Workspaces
Every workspace can have multiple chats, one per agent. Open the Cursor chat tab to start or continue a Cursor session. Cursor agents can:- Read and edit files in the cloned repository
- Run shell commands in the workspace VM
- Create branches, commits, and pull requests
- Attach and interpret images in the composer (screenshots, diagrams)
- Use Plan Mode to propose a plan before changing code
/goal). The composer uses the selected model directly without a separate fast tier.
Plan Mode
Start a message with/plan or toggle plan mode in the composer. Cursor runs in plan mode and returns a structured plan you can review in the Canvas tab before asking it to implement.
Chat history
Cursor chat history persists across turns and survives workspace sleep. Usereplicas read from the CLI to inspect transcript history from your terminal.
Programmatic Use
Select Cursor anywhere Replicas accepts a coding agent:| Surface | How to choose Cursor |
|---|---|
| CLI | -a cursor on replicas create and replicas send |
| API | "coding_agent": "cursor" on create and message requests |
| MCP | "coding_agent": "cursor" on create_replica and send_replica_message |
| Automations | Set Coding agent to Cursor in the automation editor |
| Slack, Linear, GitHub, GitLab | Set Cursor as the default coding agent |
When to Use Cursor
Cursor is a strong fit when:- Your team already uses Cursor and has API access configured
- You want Composer’s agent loop for multi-file edits and terminal work
- You prefer API-key auth over OAuth for automated or shared workflows (especially with service accounts)