PROVIDER GUIDE
Cursor
Dispatch tasks to Cursor's background agent API — no IDE window required. The Bridge runs a Node.js runner that communicates with Cursor over gRPC, keeping Bun compatibility intact.
Cursor API key Requires Node.js (gRPC) Headless — no IDE needed
Requirements
- ✓ A Cursor account with an active subscription and API access
- ✓ Node.js 18+ installed — the Bridge spawns a Node.js runner for gRPC (incompatible with Bun's native runtime)
- ✓ CTRL NODE Bridge installed on your machine (GitHub)
Why Node.js? The Cursor SDK uses native gRPC binaries that are incompatible with Bun's runtime. The Bridge embeds a lightweight
cursor-sdk-runner.mjs and executes it with Node.js automatically — you don't need to do anything extra, just have Node.js installed.
Quick start
Run the Bridge
$ PAIRING_TOKEN=your-pairing-token \
CURSOR_API_KEY=cursor_… \
./ctrlnode
CURSOR_API_KEY=cursor_… \
./ctrlnode
.env file
PAIRING_TOKEN=your-pairing-token
CURSOR_API_KEY=cursor_…
Environment variables
| Variable | Required | Description |
|---|---|---|
| CURSOR_API_KEY | Yes | Cursor API key from your account settings. |
How the Bridge dispatches to Cursor
When CTRL NODE dispatches a task to a Cursor agent:
- The Bridge spawns a Node.js child process running the embedded
cursor-sdk-runner.mjs. - The runner connects to Cursor's background agent API over gRPC and submits the task.
- Code edits, terminal output and agent responses stream back through the Bridge WebSocket.
- On completion, task status updates in the CTRL NODE dashboard. The Node.js process exits cleanly.
Note: Cursor may create node_modules artifacts in the workspace during task execution — this is normal behaviour from the SDK.