by lysonober ยท v0.0.1
Comprehensive Dify tool provider for managing Cursor Background Agents on GitHub repositories.
This community listing does not yet include every recommended support, privacy, pricing, and permission disclosure. Review the available package permissions before installing.
Available inside your emploidai workspace after installation.
Available inside your emploidai workspace after installation.
A comprehensive Dify tool provider for integrating with Cursor Background Agents API, enabling autonomous AI-powered coding workflows in your applications.
Author: lysonober
Version: 0.0.1
Type: Tool
Cursor Background Agents are autonomous AI-powered coding agents that work independently on your GitHub repositories. Think of them as skilled developers who can:
| Feature | Description |
|---|---|
| Autonomous Code Generation | Agents understand your requirements and implement complete features |
| Repository Integration | Direct GitHub integration with automatic branch management and PR creation |
| Intelligent Problem Solving | Agents can debug, test, and refine their own code |
| Scalable Workflow | Support for up to 256 concurrent agents per API key |
| Follow-up Instructions | Send additional requirements to running agents |
| Environment Awareness | Automatically detects and uses your project's setup (package.json, requirements.txt, etc.) |
This Dify plugin provides a complete interface to manage Cursor Background Agents on no-code canvas, allowing you to:
For Product Teams:
For DevOps & Maintenance:
For Content & Automation:
.cursor/environment.json configurationssk-...)Tool: Launch Agent
Prompt: "Add a comprehensive README.md file with installation instructions and examples"
Repository: "https://github.com/your-username/your-repo"
Model: "claude-4-sonnet" (optional)
Configure Provider Credentials:
Add Tool Categories:
| Tool | Parameters | Description |
|---|---|---|
| List Agents | limit (1-100, optional)cursor (string, optional) | Retrieve paginated list of all background agents |
| Agent Status | agent_id (string, required) | Get current status, progress, and metadata for specific agent |
| Agent Conversation | agent_id (string, required) | Fetch conversation messages and interaction history |
| Tool | Parameters | Description |
|---|---|---|
| Launch Agent | prompt (string, required)repository (string, required)ref (string, optional)model (string, optional)webhook_url (string, optional)webhook_secret (secret, optional) | Create new background agent on specified repository Note: Environment setup via .cursor/environment.json in target repo |
| Add Follow-up | agent_id (string, required)message (string, required) | Send additional instructions to running agent |
| Delete Agent | agent_id (string, required) | Terminate and remove background agent |
| Tool | Parameters | Description |
|---|---|---|
| API Key Info | None | Validate API key and retrieve account metadata |
| List Models | None | Get available Max Mode-compatible models for agents |
| List GitHub Repositories | limit (1-100, optional)cursor (string, optional) | Browse accessible GitHub repositories |
prompt: "Add comprehensive unit tests for the authentication module"
repository: "https://github.com/your-org/your-repo"
ref: "main"
model: "claude-4-sonnet"
agent_id: "bc_abc123"
message: "Also add integration tests for the login flow"
For optimal results, commit .cursor/environment.json directly to your target repository:
Example: In your project repository (https://github.com/your-org/your-repo)
your-repo/
โโโ .cursor/
โ โโโ environment.json
โโโ src/
โโโ package.json
โโโ README.md
Sample .cursor/environment.json:
{
"install": "npm install && npm run build",
"terminals": [
{
"name": "Dev Server",
"command": "npm run dev"
}
]
}
When a background agent is launched on your repository, it will automatically detect and use this environment configuration for proper setup.
You can configure webhooks to receive real-time status updates from Cursor Background Agents.
webhook_url when launching an agent to receive event notifications.webhook_secret for HMAC signature verification to ensure authenticity.statusChange events (including ERROR and FINISHED states).๐ก Tip: Using webhooks in combination with Supabase Edge Functions is highly recommended for secure, scalable, and low-latency event handling.
Each webhook request includes the following HTTP headers:
X-Webhook-Signature: HMAC-SHA256 signature in the format sha256=<hex_digest>X-Webhook-ID: Unique identifier for this webhook deliveryX-Webhook-Event: Event type (currently only statusChange)User-Agent: Always set to Cursor-Agent-Webhook/1.0For issues or feature requests:
This plugin acts as a passthrough to Cursor's API and stores no data locally. Refer to Cursor's Privacy Policy for data handling details.
Made with ๐ for the Dify community