Cursor
Shanone’s Cursor integration gives your agent 17 tools for controlling Cursor’s own Cloud Agents API: launching agents, monitoring runs, sending follow-ups, and retrieving artifacts.Getting Started
1
Generate a Cursor API Key
In Cursor, go to cursor.com/settings and create an API Key.
2
Add it to Shanone
Open Integrations in the Shanone dashboard, select Cursor, and paste in the API Key.
3
Retry your request
Once saved,
shanone_execute_tool calls for cursor_* tools will succeed.Available Tools
Shanone provides 17 tools for Cursor, organized into these categories:Cloud Agents
Cloud Agents
cursor_list_agents, cursor_get_agent_status, cursor_get_agent_conversation, cursor_launch_agent, cursor_add_followup, cursor_delete_agent, cursor_archive_agent, cursor_unarchive_agentRuns
Runs
cursor_list_runs, cursor_get_run, cursor_create_run, cursor_cancel_runArtifacts
Artifacts
cursor_list_artifacts, cursor_download_artifactAccount Info
Account Info
cursor_get_api_key_info, cursor_list_models, cursor_list_repositoriesCommon Use Cases
Delegate background coding
Launch a Cloud Agent on a repository with a task prompt and poll it to completion
Multi-agent orchestration
Fan out several agents across repos/branches and collect their conversations for review
Follow-up steering
Send a follow-up instruction to a running agent instead of starting a new one from scratch
Artifact retrieval
Pull generated diffs, logs, or build outputs from a completed run
Troubleshooting
cursor_launch_agent fails with a repository access error
cursor_launch_agent fails with a repository access error
The target repository must be listed in
cursor_list_repositories for the connected account — Cursor Cloud Agents can only act on repositories the API Key’s account actually has access to.cursor_get_agent_status stays in a running state indefinitely
cursor_get_agent_status stays in a running state indefinitely
Long-running agents are expected to take minutes; poll
cursor_get_agent_status periodically rather than expecting immediate completion, and check cursor_get_agent_conversation for intermediate progress.cursor_add_followup has no effect
cursor_add_followup has no effect
Follow-ups can only be sent to agents that are still active (not archived, deleted, or already finished) — check
cursor_get_agent_status first, and use cursor_launch_agent to start fresh if the agent has already completed.