@0reki/pi-cursor

@rahularya01/pi-cursor

Use your Cursor subscription's models — Composer, Claude, GPT, Grok — inside the Pi Coding Agent. pi-cursor plugs in a cursor model provider that talks to Cursor's own backend directly (native Connect/protobuf streaming over HTTP/2), so there's no separate API key to buy and no Cursor CLI process running in the background for every chat turn. If you're already logged into Cursor's app or CLI, it just works — no setup beyond installing the package.

Unofficial integration. This project is not affiliated with or endorsed by Cursor / Anysphere. It uses reverse-engineered wire protocol details shared by community clients (see Attributions). Use it only with an account you are authorized to access, and review its source before granting OAuth permissions. Cursor may change wire protocol endpoints or formats at any time.

Contents

• Requirements
• Install
• Quick start
• Authentication
• Commands
• Models & reasoning effort
• Usage dashboard
• Troubleshooting
• Configuration (advanced)
• Architecture (advanced)
• Development

Requirements

Install

pi install npm:@rahularya01/pi-cursor

Then restart Pi (or run /reload) so the new provider is picked up.

pi install git:github.com/Rahularya01/pi-cursor

pi update npm:@rahularya01/pi-cursor

Quick start

1. Sign in. If Cursor's desktop app or CLI (cursor / agent) is already logged in on this machine, pi-cursor detects it automatically — skip to step 2. Otherwise, run:

   /login cursor
   

   This opens a browser tab to sign in with your Cursor account.

2. Pick a model:

   /model cursor/composer-2
   

3. Start chatting. If anything looks off, run /cursor.doctor — it prints which credential source is active, the current endpoint, and the last error, and is the first thing to check before filing an issue.

Authentication and resolution cascade

pi-cursor automatically resolves credentials using a 4-tier cascade:

1. CURSOR_ACCESS_TOKEN environment variable
2. Pi OAuth credentials store (~/.pi/agent/auth.json via /login cursor)
3. Cursor CLI credentials in macOS Keychain (cursor-access-token / cursor-refresh-token)
4. Cursor IDE local state DB (globalStorage/state.vscdb on macOS, Windows, Linux, or WSL)

/login cursor is preferred over Keychain/IDE harvest so an explicit Pi login is not silently overridden by another Cursor app account on the machine.

Automatic CLI & IDE login detection

If you are logged into the Cursor desktop app or Cursor CLI (cursor / agent), pi-cursor automatically extracts your session credentials so you can start chatting immediately without manual browser login.

On WSL (Windows Subsystem for Linux), pi-cursor reuses the current Windows user's Cursor IDE login (USERPROFILE / USERNAME → /mnt/c/Users/<you>/AppData/...). It does not scan other Windows profiles.

To opt out of Keychain / IDE / WSL credential reuse (OAuth or CURSOR_ACCESS_TOKEN only):

export PI_CURSOR_SYSTEM_CREDENTIALS=0

Deep-link PKCE browser login

When no local credentials exist, running /login cursor initiates browser sign-in:

1. /login cursor opens https://cursor.com/loginDeepControl?...
2. Pi polls https://api2.cursor.sh/auth/poll until authentication completes.
3. Access and refresh tokens are stored in Pi's auth store (~/.pi/agent/auth.json).
4. Tokens are automatically refreshed via https://api2.cursor.sh/auth/exchange_user_api_key.

Use /cursor.doctor to inspect which source is active (tokenSource=cli_keychain, tokenSource=ide_vscdb, tokenSource=pi_oauth, tokenSource=env).

Commands

Models and reasoning effort routing

pi-cursor discovers live account models via GetUsableModels and parameterized metadata. Reasoning effort levels (off, minimal, low, medium, high, xhigh, max) are mapped directly to Cursor's runtime model variants or reasoning parameters.

To restrict which models Pi displays, configure ~/.pi/agent/settings.json:

{
  "enabledModels": ["cursor/composer-2", "cursor/claude-sonnet-5", "cursor/gpt-5.5"]
}

Usage quota and visual TUI dashboard

Running /cursor.usage displays a formatted terminal interface showing your current billing cycle, progress bars for included plan quota, auto/API usage, reset dates, and on-demand spend:

Usage • Pro                                           Resets 5 Aug
Monthly plan and on-demand usage

Category        Current          Usage
Included        13% used         ███░░░░░░░░░░░░░░░░░
  Auto          12% used         ███░░░░░░░░░░░░░░░░░
  API           14% used         ███░░░░░░░░░░░░░░░░░
On-Demand       Disabled
------------------------------------------------------------
On-demand usage is off

View in dashboard: cursor.com/dashboard?tab=usage

Usage statistics are fetched directly from Cursor's native Connect period usage endpoint (POST https://api2.cursor.sh/aiserver.v1.DashboardService/GetCurrentPeriodUsage) using your active access token, with optional fallback to CURSOR_USAGE_SESSION_TOKEN.

Architecture & Wire Protocol

The rest of this README is reference material for troubleshooting, tuning, and contributing — nothing here is required for day-to-day use.

Pi Coding Agent  →  streamSimple (cursor-native)
                      → h2-bridge.mjs (Node.js HTTP/2 child process)
                      → agent.v1.AgentService/Run (Connect + Protobuf over HTTP/2)

• Transport: Native Connect/protobuf streaming over HTTP/2 via h2-bridge.mjs.
• Infrastructure Context Normalization: Side-channel user messages (context-mode routing, post-compaction <session_state>, and explicit [pi-lens automated … not a user request] notices) are safely normalized into the system prompt so Cursor models stay focused on your primary task.
• Context-Efficient Tools: MCP schemas are compacted without changing callable constraints, and exact conversational-only turns (hi, thanks, etc.) omit tools entirely. Actionable prompts always retain tools.
• Cross-Platform: Tested and fully compatible with macOS, Linux, Windows, and WSL.

Configuration

Everything below is optional — pi-cursor works out of the box. These environment variables exist for tuning timeouts, debugging, and edge-case overrides.

Architecture notes

Troubleshooting

• No API provider registered for api: cursor-native: Update to the latest pi-cursor (pi update npm:@rahularya01/pi-cursor) and restart Pi (or /reload). This means the Agent tried to stream via Pi's global streamSimple dispatcher before the Cursor transport was registered there. Current builds register cursor-native on that registry during extension load.
• Not logged in / 401: Ensure Cursor CLI or app is logged in, or run /login cursor again. Check /cursor.doctor to verify your tokenSource. Tokens from CLI/IDE are re-resolved when near expiry; idle stream retries also force-refresh credentials.
• Empty / hung stream: Cursor may have updated wire headers; verify network connectivity or bump PI_CURSOR_CLIENT_VERSION. /cursor.doctor prints the active clientVersion.
• Wire-protocol drift: Cursor can change agent.v1 at any time. Unrecognized server messages and unknown protobuf fields are no longer skipped silently — they are counted, written to the lifecycle log as wire_drift, appended to the failing turn's error message, and listed by /cursor.doctor under wireDrift. wireDriftStranding=yes means an unanswered message could have parked the turn, which is the difference between "our schema is a bit behind" and "this is why it hung". Run CURSOR_ACCESS_TOKEN=... npm run smoke:wire to check the handshake and schema against the live endpoint without starting a chat turn, then see proto/README.md to resync the schema.
• Stuck / dies after a few minutes of work: Cursor InteractionQuery prompts are answered so the stream does not park. Web/search and unnamed proto fields are rejected (use Pi tools instead). Inspect $TMPDIR/pi-cursor-lifecycle.jsonl for interaction_query / bridge_close events, and /cursor.doctor for lastStreamEvent. Full debug: PI_CURSOR_PROVIDER_DEBUG=1.
• Tool continuation lost: The provider now prefers full-history rebuild when checkpoints are stale/mismatched. If recovery still skips, /cursor.doctor shows lastRecoverySkipReason. Retry the turn or start a new chat.
• WSL credential detection: Set USERPROFILE or USERNAME so the Windows home directory is known, and ensure /mnt/c/Users/<you>/AppData/... is readable. Disable with PI_CURSOR_SYSTEM_CREDENTIALS=0 if undesired.
• Slow startup: Activation should be a few milliseconds. /cursor.doctor reports catalogCache (none(using bundled fallback) means every launch is starting cold — check that catalogCacheDir is writable) and unaryTransport. A stale Cursor CLI keychain entry no longer blocks startup: a refresh token that fails is remembered for 10 minutes so it is not retried on the next launch, and any valid locally stored token is always preferred over a network exchange.
• Model list looks stale: It is the last successfully discovered catalog. Open /model to trigger a background refresh, or delete PI_CURSOR_CACHE_DIR to force full rediscovery.

Development

npm install
npm run check

npm run check runs TypeScript typechecking, ESLint, Prettier format verification, security checks, the protobuf staleness check, and unit tests.

Attributions

Wire protocol and authentication patterns adapted from MIT community client lineage:

• ephraimduncan/opencode-cursor
• @pi-stef/cursor

Package structure mirrors pi-antigravity.

Support the project

If pi-cursor is useful to you, consider sponsoring the project on GitHub.

License

MIT