Skip to Content
ResourcesIntegrationsDeveloper ToolsCursor Agents

Cursor Agents

Cursor Agents icon
Arcade Optimized

Arcade.dev tools for operating Cursor Cloud Agents

Author:Arcade
Version:3.0.1
Auth:No authentication required
16tools
16require secrets

Arcade toolkit for operating Cursor Cloud Agents — launch, manage, and monitor AI coding agents programmatically via the Cursor Cloud Agents API.

Capabilities

  • Agent lifecycle management: create/start, archive, restore, and permanently delete cloud agents.
  • Run control and polling: start new runs or follow-up prompts on existing agents, cancel active runs (with async-settle semantics), and poll run status until terminal to retrieve results, branches, and PRs.
  • Artifact and output access: list explicitly uploaded artifact files and generate time-limited download URLs; code output lands on run branches/PRs rather than artifacts.
  • Discovery and introspection: list available agents, runs, GitHub repositories accessible to Cursor, and supported LLM models (Claude, GPT, Gemini families).
  • Usage and account info: retrieve per-agent token usage broken down by run; confirm the authenticated account identity before acting.

Secrets

CURSOR_AGENTS_API_KEY — A Cursor API key that authenticates all requests to the Cursor Cloud Agents API. To obtain one, log in to your Cursor account, navigate to Settings → API Keys (or the equivalent section in your Cursor dashboard), and generate a new key. The key must belong to an account with Cursor Cloud Agents access; verify the authenticated identity with CursorAgents.WhoAmI before launching or managing agents.

For guidance on configuring secrets in Arcade, see the Arcade secrets documentation. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.

Available tools(16)

16 of 16 tools
Operations
Behavior
Tool nameDescriptionSecrets
Archive a cloud agent so it stops accepting new runs (reversible). The archive is committed once accepted; if the follow-up read of the agent fails, the result carries only the agent id with an empty status, and reading the agent again returns the refreshed state.
1
Cancel an active run; cancelling an already-terminal run returns an error. Cancellation is accepted asynchronously: the returned status reflects the run's state at the moment of the call and may still be non-terminal even though the cancel was accepted. Poll the run afterward to confirm it settles to CANCELLED; do not treat a non-terminal status here as a failed cancel. If the post-cancel read of the run fails, the result carries an empty status instead of an error. Upstream failures carry a stable bracketed code before the message when Cursor supplies one (an open set; the most common here is ``[run_not_cancellable]``, returned when the run is already terminal).
1
Permanently delete a cloud agent. This cannot be undone.
1
Get a time-limited download link for one uploaded artifact file. Artifacts are Cursor "background composer" uploads, not an agent's code changes; for code output read the run's branch and PR instead.
1
Get a cloud agent's configuration and latest run pointer.
1
Get token usage for an agent, summed and broken down per run.
1
Get a run's current status, and its result, branches, and PR once terminal.
1
List your cloud agents, newest first.
1
List the artifact files a cloud agent explicitly uploaded. Artifacts are Cursor "background composer" uploads. Code an agent writes to a repo lands on the run's branch and PR (see the run's ``branches``), not here, so this is empty for typical fix-a-repo / open-a-PR tasks.
1
List the LLM models available to launch a cloud agent with. Returns the model ids (e.g. Claude, GPT, and Gemini family models) accepted by the launch tool's model parameter, with display names and aliases.
1
List every GitHub repository Cursor can reach, as repository urls. The upstream returns the full set in one response, so this is always the complete list and never a partial page.
1
List an agent's runs, newest first. Listing omits each run's final result text; read an individual run to get it.
1
Restore an archived cloud agent to active. The restore is committed once accepted; if the follow-up read of the agent fails, the result carries only the agent id with an empty status, and reading the agent again returns the refreshed state.
1
Launch a Cursor cloud agent on a repository or named environment. This single call starts the agent and its first run; follow it to completion with the run tools.
1
Send a follow-up prompt to an existing agent, starting a new run. An agent runs one turn at a time. Upstream failures carry a stable bracketed code before the message when Cursor supplies one (an open set; the most common here is ``[agent_busy]``). If this returns ``[agent_busy]``, the agent already has an active run: poll that run until is_terminal, then resend the follow-up.
1
Return the Cursor account the API key authenticates as. Call this first in a session to confirm which account you are acting on before launching or managing any cloud agents.
1
Last updated on