Cursor
Bring your Cursor account into Proliferate workspaces, with Cursor's own agent, plan, and ask modes.
Cursor runs through the Cursor Agent CLI, so your team brings the Cursor account, models, and modes it already uses into shared workspaces and review.
Supported functionality
| Capability | Support |
|---|---|
| Where it runs | Local checkouts and worktrees. |
| Modes | Cursor's own agent, plan, and ask modes, switched from the composer. |
| Subagents | Spawn native task agents, or delegate to a separate session. |
| Credentials | Signs in with the Cursor CLI's own login; no separate Proliferate credential. |
Modes
Cursor carries its own mode switch into the composer, separate from the session modes other agents use.
| Mode | What it does |
|---|---|
| Agent | Default. Makes changes directly: edits files and runs commands as it works. |
| Plan | Cursor's own plan mode: it works out an approach before making changes, using Cursor's native planning behavior. |
| Ask | Read-only. Answers questions and explores the codebase without editing anything. |
Subagents
Cursor can spawn its own task agents (cursor/task) inside a session — native
subagents that show up in the session's activity roster. To hand a scoped piece
of work to a separate Proliferate session instead, see
Parallel agents.
Authentication
Cursor signs in with the Cursor CLI's own login (cursor-agent login); if
cursor-agent is already logged in on your machine, Proliferate picks that up
automatically. From Settings -> Agents -> Cursor you can also select API
key and save a Cursor account key instead. Cursor doesn't support the
Proliferate Gateway.
For how routes work on the agents that do support them, see Authentication.
Cursor doesn't appear in an organization's Allowed harnesses checklist, since there's no route to restrict. See Agent policy for what that checklist does control.