Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ctrlnode.ai/llms.txt

Use this file to discover all available pages before exploring further.

Provider id: cursor · CtrlNode agent type: Cursor Runs Cursor through @cursor/sdk. Because the SDK uses gRPC/HTTP2, the Bridge extracts a Node.js runner (cursor-sdk-runner.mjs) to a temp directory and communicates over JSONL on stdin/stdout.

​
When to use it

  • You have a Cursor API key and want Cursor agents to execute CtrlNode tasks
  • The Bridge host can run Node.js LTS alongside the Bridge binary

​
Prerequisites

​
Node.js

node --version   # LTS recommended
Windows: winget install OpenJS.NodeJS.LTS

​
Cursor API key

  1. Open cursor.com/settings → Integrations → API Keys
  2. Create a key
  3. Set:
CURSOR_API_KEY=crsr_...

​
Environment variables

VariableRequiredDefaultDescription
CURSOR_API_KEYYes—Cursor API key
CURSOR_TIMEOUT_MINUTESNo10Task timeout
AGENTS_FOLDERNoHomeWorkspace root

​
Example .env

PAIRING_TOKEN=...
PROVIDERS=cursor
CURSOR_API_KEY=crsr_...

​
CtrlNode setup

  1. Project agent type Cursor
  2. Register agents in Team
  3. Keep Node.js available to the same user as ctrlnode-bridge
The runner is embedded in the Bridge binary and refreshed on upgrade. You do not install @cursor/sdk manually on the host.

​
Workspace artifacts

Cursor may create node_modules or helper files under the agent workspace during a run. Add them to .gitignore if the workspace is a git repo.

​
Troubleshooting

IssueFix
cursor_api_key_missing at startupSet CURSOR_API_KEY
Runner fails immediatelyInstall Node.js; verify node on PATH
401 on dispatchRegenerate API key in Cursor settings
Task routed to wrong providerAgent type must be Cursor
← All providers