Cursor Bridge

cursor-bridge

One binary. Claude Code on Cursor's backend. Zero config.

Why does this exist?

You have a Cursor subscription. You want to use Claude Code (the CLI).
Cursor's Auto model is included with your subscription — free, unlimited, no extra per-token cost.

Without cursor-bridge, you'd pay separately for Anthropic API credits or a Claude Pro plan.
With cursor-bridge, you just run cursor-bridge and it works — Claude Code runs on your Cursor backend.

Use cases:
- You're already paying for Cursor → get Claude Code for free on top
- You want Claude Code's agent capabilities (file editing, shell commands, tool use) without Anthropic billing
- Cursor's Auto model is free and unlimited with subscription — Claude Code becomes effectively free to run

That's it. No proxy management. No env vars. Everything automatic.

How it works

You don't see the proxy. You don't manage it. It's there and gone.

Install

Or download a binary from Releases.

Requirements

- macOS or Linux
- Cursor subscription (with agent CLI in PATH)
- Claude Code CLI (claude in PATH)
- macOS: token auto-read from keychain
- Linux: set CURSOR_TOKEN env var (no keychain fallback)

How it differs from other proxies

All other solutions are background servers you manage. cursor-bridge is a command you run.

Existing proxies (cursor-api-proxy, cursor-composer-in-claude, cursor-proxy) are Node.js servers that live in your process list, occupy a port, and need manual env var wiring. They don't ship with Claude Code — they sit between you and it, adding ceremony.

cursor-bridge is the opposite. There is nothing to start, stop, or configure. It *is* the session:

No daemon. No npm install. No env vars. No port hunting. No cleanup. Just a single binary that works.

cursor-bridge replaces claude entirely —…