Cloud agents

The cursor-cloud-agents extension lets an Agent SDK agent hand coding work to Cursor cloud agents. A cloud agent works in a repository checkout and pushes branches and pull requests while your agent keeps talking to the person.

Mount it

// bot/extensions/cloud.ts
import cursorCloudAgents from "@grok/agent-sdk/extensions/cursor-cloud-agents";

export default cursorCloudAgents({
  cloud: {
    repos: [{ url: "https://github.com/acme/api", startingRef: "main" }],
    autoCreatePR: true,
  },
});

Launches run under the host's signed-in account (agent-sdk login, CURSOR_API_KEY, or CURSOR_SERVICE_ACCOUNT_KEY) and spend its cloud-agent budget.

What the agent can do

With the extension mounted, the agent can launch a cloud agent on a repository or pull request, check its status, read its conversation and edits, steer or stop it, and list the agents it launched. A bundled skill teaches the model when to delegate and how to write a brief a cloud agent can act on alone.

Each caller can only see and steer the cloud agents they launched. If every caller uses the same bearer token, the extension treats them all as one person. Use authored auth to keep callers apart.

Configure it

Option	What it controls
cloud	Launch defaults for repositories, environment, and pull request behavior.
cloud.repos	The repositories the agent may hand work to, each with a default branch or pull request. Without it, launches run with no repository, so secrets in cloud.envVars never reach a repository you didn't list.
cloud.teamMcpServers	Up to 50 team MCP server names that launched agents may use, matched case-insensitively. Omit it to allow every team server the account can use. Personal servers and cloud.mcpServers aren't filtered.
model	The model launched agents run. Omit it to use the account default.
apiKey	A Cursor API key to launch with instead of the host's own.

Adjust it

To remove a capability such as sending follow-ups, mount the extension as a directory and disable that tool. See Adjust a mounted extension.