Integrate Cursor Cloud Agents as synchronized remote sessions

[felipeorlando]

Problem

MonoCode's Cursor harness runs local Cursor CLI/ACP sessions only. Cursor Cloud Agents started from cursor.com, Cursor desktop/mobile, Slack, GitHub, Linear, or the API do not appear in MonoCode, and MonoCode cannot start or continue them.

Proposed behavior

• Add Cursor Cloud credentials/settings separately from the local Cursor CLI login.
• Start a Cloud Agent from a MonoCode project, choosing repository, starting ref, prompt, and supported model/options.
• List Cloud Agents created elsewhere and represent them in the session sidebar with their remote identity and current run status.
• Refresh active/idle/archived state and allow supported follow-up/cancel/archive actions.
• Open the canonical Cursor agent URL for capabilities MonoCode cannot render.
• Avoid duplicate local records when the same cloud agent is discovered again.

For a first slice, “sync” can mean durable identity, status, links, and supported actions. Full transcript/artifact parity should only be included if the public API exposes it cleanly.

Existing work checked

There is no Cursor Cloud code or matching upstream issue/PR. The current cursor harness is local-only. Cursor's public beta Cloud Agents API supports create, list, get, runs/follow-ups, and lifecycle status:

• https://cursor.com/docs/cloud-agent
• https://prod.cursor.com/docs/cloud-agent/api/endpoints

This is a product integration for an existing provider, not a new local harness.

Acceptance criteria

• A user can create a Cursor Cloud Agent from MonoCode.
• Agents started outside MonoCode appear after refresh without duplicate sessions.
• MonoCode shows truthful remote lifecycle state and retains the Cursor agent URL.
• Follow-ups and lifecycle actions use documented API endpoints and handle beta API errors/rate limits.
• Local Cursor sessions continue to work unchanged.