Skip to Content
ResourcesIntegrationsDeveloper ToolsCursor Agents

Cursor Agents

Cursor Agents icon
Arcade Optimized

Arcade.dev tools for operating Cursor Cloud Agents

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

Cursor Agents Toolkit

Provides Arcade tools for operating Cursor Cloud Agents — launching AI coding agents on GitHub repositories, managing their lifecycle, and inspecting runs and artifacts.

Capabilities

  • Agent lifecycle management: Launch agents on repos or named environments, archive/unarchive, and permanently delete them.
  • Run control and polling: Start follow-up runs, cancel active runs (with async-settle semantics), and retrieve run status, result text, branches, and PRs once terminal.
  • Inspection and listing: List agents, runs, repositories Cursor can reach, available LLM models, and uploaded artifacts; get per-agent token usage summed and per-run.
  • Artifact access: List files a cloud agent explicitly uploaded and obtain time-limited download links for them (distinct from code output, which lands on a run's branch/PR).
  • Account verification: Confirm which Cursor account the API key authenticates as before performing any operations.

Secrets

CURSOR_AGENTS_API_KEY — A Cursor API key that authenticates all calls to the Cursor Cloud Agents API. Obtain it from your Cursor account settings dashboard (Settings → API Keys or equivalent). The key must belong to an account with access to Cursor Cloud Agents; standard Cursor accounts may require an active Pro or Business subscription for cloud agent access. Treat this value as a credential — it grants full control over agents and runs in the associated account.

For configuring secrets in Arcade, see the Arcade secrets guide. You can also manage secret values 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
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
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
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
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
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