Cursor
Use Cursor CLI-backed agent work inside Proliferate workspaces and workflows.
Cursor runs inside Proliferate through the Cursor Agent CLI, so your team can bring the Cursor account and workflow they already use into shared workspaces and review.
Supported functionality
| Capability | Support |
|---|---|
| Workspace runs | Launch Cursor-backed work in a local checkout, a worktree, or a cloud sandbox. |
| Background tasks | Run Cursor in the background while you keep working elsewhere. |
| Review | Inspect generated diffs, the transcript, and command output before integrating. |
| Credentials | Cursor authenticates with its own sign-in; there is no separate Proliferate credential to manage. |
Authentication
Cursor is the one agent in Proliferate that skips the Local/Cloud
authentication settings other agents use. It signs in with the Cursor CLI's
own login (cursor-agent login) and reuses that session, so it doesn't
support
BYOK (bring your own key)
API keys or the Proliferate Gateway. If cursor-agent is already logged in
on your machine, Proliferate picks that up automatically.
Settings -> Agents overview, Cursor row
The Agents overview list showing Cursor as a plain row with no settings link, alongside its sign-in status badge.
For shared defaults across agents, see advanced agent settings.