Continuum launches Cursor-backed sessions through the ACP (Agent Control Protocol) harness via cursor-agent.
Requirements
cursor-agent must be installed and your Cursor account must be authenticated. Continuum discovers the available models from your Cursor account; no manual model list configuration is needed.
How it integrates
Continuum spawns cursor-agent and communicates over ACP. The same daemon surface used for Claude and Codex handles send, interrupt, model selection, and plan approval for Cursor sessions.
Cursor sessions appear in the Chat tab, the Code tab session list, and the Usage tab quota panel.
Effort dial
Cursor does not currently expose a programmatic effort control. The effort dial in the session header is set to “Cursor Auto” for Cursor sessions and does not map to a real Cursor parameter. If Cursor adds a reasoning effort API, this will be updated.
File system trust
When the session’s repo is on the autopilot trust list, Continuum advertises fs/read_text_file and fs/write_text_file capabilities to the ACP agent. Untrusted repos advertise no file-system capability and all file requests are refused. All paths are validated through RepoTrustGate before any disk I/O.
Usage analytics
Cursor token events feed the Usage tab. A quota panel appears showing your Cursor account’s rolling usage.
Broadcast
Cursor can participate in the Chat tab’s multi-provider broadcast mode alongside Claude, Codex, Antigravity, Grok, and OpenRouter. 
