Cursor
Everruns integrates with Cursor Cloud Agents so agents can delegate asynchronous coding work to Cursor. A triage agent can inspect a request, split it into focused tasks, launch Cursor agents against GitHub repositories, send follow-ups, and summarize status or results.
What You Get
Section titled “What You Get”- Launch Cloud Agents: Start Cursor agents with repository, base ref, task prompt, optional branch name, and PR behavior.
- Track Progress: Read status, target branch, PR URL, summary, and conversation history.
- Send Follow-ups: Add more instructions to running Cursor agents.
- Connection Prompt: Configure a Cursor Cloud Agents API key in Settings > Connections.
- Seed Agent: Use the built-in Cursor Agent Manager example to triage and delegate work.
Quick Start
Section titled “Quick Start”1. Get a Cursor API Key
Section titled “1. Get a Cursor API Key”- Open Cursor Dashboard
- Go to Cloud Agents > My Settings > API Keys
- Create a Cloud Agents API key
- Make sure Cursor’s GitHub app can access the repositories agents should work on
Use a Cloud Agents API key. A general Cursor dashboard API key may not be enough to create agents.
2. Connect in Everruns
Section titled “2. Connect in Everruns”- Go to Settings > Connections
- Find Cursor
- Click Connect
- Paste the Cloud Agents API key
Operators can also provide CURSOR_API_KEY through Doppler for managed deployments and live tests.
3. Use in Sessions
Section titled “3. Use in Sessions”Agents with the Cursor capability can use these tools:
| Tool | Description |
|---|---|
cursor_launch_agent | Start a Cursor Cloud Agent |
cursor_get_agent | Get one agent’s status and result metadata |
cursor_list_agents | List agents for the connected Cursor account |
cursor_add_followup | Send extra instructions to a running agent |
cursor_get_conversation | Read an agent’s conversation transcript |
cursor_delete_agent | Delete an agent record/resources |
cursor_list_models | List recommended Cursor model ids |
cursor_list_repositories | List GitHub repositories Cursor can access |
cursor_key_info | Check the active Cursor connection |
Delegation Pattern
Section titled “Delegation Pattern”Use Cursor Agent Manager when you want Everruns to triage first and then delegate:
- Provide the repository URL and base branch
- Ask the agent to break the work into scoped tasks
- Let it launch Cursor agents with clear acceptance criteria
- Review returned Cursor links, branches, PR URLs, summaries, and transcripts
Lifecycle
Section titled “Lifecycle”Cursor owns Cloud Agent lifecycle state. Everruns stores no per-agent state beyond normal session messages and tool results. Keep the returned agent_id if you want to poll, send follow-ups, read the conversation, or delete the agent later.
cursor_list_repositories is heavily rate-limited by Cursor and can be slow for large accounts. Prefer passing the repository URL directly.
Security
Section titled “Security”- Cursor API keys are encrypted at rest when stored as Everruns user connections
- Everruns prompts for missing Cursor credentials through the inline connection dialog, not chat text
- Cursor agents run in Cursor-managed remote environments with internet access and command execution
- Repository access is controlled by the Cursor GitHub app and Cursor account settings
- Webhook secrets and image prompt payloads are intentionally not exposed in the first tool surface