Launch, monitor, and manage Cursor cloud agents from inside your chat. Send follow-up instructions, check status, create PRs — all with natural language.
We already have PowerCode for reading your codebase and Blackbox Cloud for multi-agent dispatch. Cursor Cloud Agents adds a third superpower: iterative, conversational coding agents that you can refine with follow-up instructions — all from the same chat interface.
Describe what you want in plain English inside the chat. The AI launches a Cursor cloud agent, monitors progress, and reports back — no context switching to another platform.
Unlike one-shot agents, Cursor supports full conversation threads. Send follow-up instructions to refine the work, add tests, or adjust the implementation — all from chat.
Launch agents, check status, send follow-ups, stop, resume, delete — all without leaving the conversation. Your chat history becomes a log of every agent dispatched.
Bring your own Cursor API key. The integration is fully optional — if you don't add a key, the AI has no idea these tools exist. Remove the key any time to turn it off.
The integration adds seven tools to LeemerChat's AI assistant. These tools are only visible when you've added your Cursor API key in Settings → API Keys. No key, no tools — the AI has zero knowledge of Cursor otherwise.
cursor_launch_agentLaunch a new cloud agent on any GitHub repository. Supports custom models, auto-PR creation, and custom branch names.
"Use Cursor to add rate limiting to github.com/myorg/api"
cursor_check_agentCheck the current status, summary, branch, and PR URL of a running or completed Cursor agent.
"What's the status of my Cursor agent?"
cursor_stop_agentStop a running agent. The agent is paused but not deleted — send a follow-up to resume.
"Stop the Cursor agent"
cursor_followup_agentSend a follow-up instruction to an existing agent. If the agent was stopped, this resumes it.
"Tell the Cursor agent to also add unit tests"
cursor_list_agentsList all your Cursor cloud agents with their names, statuses, repos, and PR links.
"Show me all my Cursor agents"
cursor_delete_agentPermanently delete a cloud agent. This action cannot be undone.
"Delete my old Cursor agent bc_abc123"
cursor_list_reposList GitHub repositories accessible to your Cursor account to find the right repo before launching an agent.
"List my repos on Cursor"
Here's what a typical Cursor agent workflow looks like, entirely inside the chat:
"Use Cursor to add authentication middleware to github.com/myorg/api on the main branch, and auto-create a PR"
AI calls cursor_launch_agent with repository, ref, and autoCreatePr. Returns agentId: bc_abc123.
"How's the agent doing?"
AI calls cursor_check_agent(bc_abc123). Reports: status "RUNNING", branch: cursor/add-auth-1234.
"Also add rate limiting to the auth endpoints"
AI calls cursor_followup_agent(bc_abc123, prompt). The agent continues working with the new instruction.
Agent finishes. Status: "FINISHED". PR created at github.com/myorg/api/pull/42. Summary: "Added JWT auth middleware with rate limiting."
Three tools in LeemerChat. They solve different problems and work great together.
| Feature | PowerCode | Blackbox Cloud | Cursor Cloud |
|---|---|---|---|
| Where it runs | Inside LeemerChat's chat interface | Remote Blackbox Cloud sandboxes | Cursor Cloud infrastructure |
| How it works | Browse & read files via GitHub API | Clone repo, make changes, commit & push | Clone repo, make changes, create branch & optional PR |
| Output | In-chat code suggestions & analysis | New branch with committed changes + PR | New branch with changes + optional auto-PR |
| Agent count | Single model at a time | Up to 4 agents simultaneously (multi-launch) | Single agent with follow-up conversation support |
| Best for | Code exploration, Q&A, quick fixes | Full implementations, refactors, features | Iterative coding tasks with follow-up refinement |
| Cost model | Included in LeemerChat plan | Credits on your Blackbox account (BYOK) | Billed via Cursor subscription (BYOK) |
Visit cursor.com/settings (Cursor Dashboard) and generate an API key. The key uses Basic Authentication to authenticate your requests.
Open Settings, then API Keys, and paste your Cursor API key. Once saved, the seven Cursor tools become available to the AI assistant.
Just ask in chat: "Use Cursor to refactor the auth module in github.com/myorg/api and create a PR". The AI handles the rest — launching, monitoring, and reporting.
Your Cursor API key is stored only in your browser's localStorage — never on our servers.
API calls to Cursor go through our authenticated server proxy — your key never appears in browser network logs.
If you remove the key, all Cursor tools disappear from the AI instantly.
We do not store, log, or share any data from your Cursor agents. Usage is billed via your Cursor subscription.
Add your Cursor API key, pick a repo, describe what you want, and let the agent handle the rest — all from inside LeemerChat.