Cursor Cloud
Set up Cursor Cloud agents for ticket runs, project chat, and workflow automations.
Cursor Cloud
Cursor Cloud runs async repo-backed agents on Cursor's infrastructure. ArxDeck launches runs from ticket automations, @mentions, task templates, scheduled tasks, and project chat. Branch and pull request metadata sync back to tickets.
ArxDeck Helper can propose Cursor Cloud agent configuration through project chat. Describe the agent you need and approve proposals in the Proposals inbox. See ArxDeck Helper.
Prerequisites
| Requirement | Who configures |
|---|---|
Organization API keys — CURSOR_API_KEY (or platform default) | Organization admin at Organization → API keys |
| Linked GitHub repository with Agent starting ref | Project admin at Settings → GitHub (optional when Allow repo-less is enabled on the agent) |
| Cursor account with GitHub access for the linked repo | Your Cursor organization |
| Unrestricted Cursor API key for Allow repo-less agents | Organization admin — repository-scoped keys cannot create repo-less agents |
See GitHub integration for repository binding and Organizations for credential resolution (organization overrides platform defaults).
Setup & configuration
| Step | Action |
|---|---|
| 1 | Connect the project repository and set Agent starting ref under Settings → GitHub |
| 2 | Open Settings → Agents and create or edit an agent with provider Cursor Cloud |
| 3 | Enable capabilities: worker (ticket runs), chat (project chat), and/or automation (workflow actions) |
| 4 | Optionally enable Allow repo-less to run before GitHub is connected (requires an unrestricted API key). When you connect or change the repository, ArxDeck records a bind timestamp; the next launch that would reuse a pre-bind provider agent starts fresh on the repo with full prior history in chat. |
| 5 | Optionally pick a model and parameters from the Cursor model catalog |
| 6 | Enable ArxDeck MCP and select allowed tool groups — inline MCP is injected automatically on launch |
| 7 | Optionally attach external MCP servers registered at Organization → MCP servers |
| 8 | Attach the agent to workflow automations, task templates, or enable Use in project chat |
MCP on launch
When MCP is enabled on a Cursor Cloud agent, ArxDeck auto-injects an inline arxdeck MCP server pointing at your deployment's MCP endpoint with a run-scoped Bearer token. You do not configure MCP manually in the Cursor dashboard for ticket automations or chat turns.
Your deployment administrator registers the Cursor webhook URL {APP_URL}/api/agent-runs/webhooks/cursor in the Cursor console for faster status updates. This is operator-side configuration — not part of the project settings UI.
Ticket runs
- Runs start from the project's Agent starting ref (falls back to the repo default branch when invalid)
- Branch names and PR URLs sync to the ticket as the run progresses
- Sync status, Cancel run, and Retry agent are available on ticket detail
- Costs appear as Estimated from token usage and platform pricing rates (project admins)
- Transient Cursor API errors (429/502/503/504) retry automatically with backoff
Project chat
Cursor Cloud chat streams assistant text via SSE. If the stream ends while Cursor is still running, the UI shows Waiting for Cursor to finish and reconciles in the background. Reload result can pick up a late terminal answer without resending your message.
With Allow repo-less enabled, you can start setup conversations before GitHub is connected. When a repository is linked or changed, a banner appears in chat and the next eligible launch continues in that repository (ticket automations and scheduled follow-ups use the same timestamp-based handoff rule).