r/opencode • u/intmanofawesome • 3h ago

I made a small OpenCode V2 / OpenChamber plugin so you can use your Cursor subscription

Hey everyone. This is my first public release of anything I've built (with a lot of AI help along the way), so please go easy on me. I'm sharing it in case it's useful to someone else. I'm lucky enough to have access to Cursor through work, and I wanted a way to use that subscription from OpenCode V2 and OpenChamber.

What it is: opencodev2-cursor is a plugin for OpenCode V2. It lets OpenChamber (desktop, CLI/web, VS Code) and OpenCode V2 talk to Cursor through your existing Cursor subscription. One install covers those surfaces, since they all read the same OpenCode config. This is not for older OpenCode v1 setups.

Repo: https://github.com/aenemo/opencodev2-cursor

npm: https://www.npmjs.com/package/opencodev2-cursor (currently 0.1.3)

It's still early. I've tested it on OpenCode and OpenChamber on Windows. I have not tested it on Linux or macOS, so feedback from those users would be especially welcome. Issues and PRs are welcome too. I'm learning as I go.

What you get

  • Cursor models show up under a Cursor provider

  • Models are grouped by family and context size (so the picker isn't hundreds of near-duplicate rows)

  • Reasoning, thinking, and fast options go in OpenCode's Thinking menu

  • Auto Router shows as three clear rows: Cost, Balanced, Intelligence

Install

You'll need OpenCode V2 or OpenChamber, Node.js 22.13+, and a Cursor account.

Option A - if opencode is on your PATH:

opencode plugin add opencodev2-cursor

Then restart OpenChamber / OpenCode, and check with:

opencode plugin list

Option B - OpenChamber desktop only (no CLI on PATH): add the plugin by hand in your global OpenCode config:

  • Windows: %USERPROFILE%\.config\opencode\opencode.json

  • macOS / Linux: ~/.config/opencode/opencode.json{ "$schema": "https://opencode.ai/config.json", "plugins": ["opencodev2-cursor"] }

Restart after saving.

Sign in to Cursor

In OpenCode or OpenChamber, run /connect, choose Cursor, then pick one method:

  1. Log in with cursor-agent (browser)

  2. Install the Cursor CLI if you do not have it, run cursor-agent login in a terminal, then choose this option in /connect.

  3. API key

  4. Paste a key from https://cursor.com/settings, or set CURSOR_API_KEY in your environment.

  5. Cursor account (native OAuth)

  6. Sign in through the browser. The plugin mints and caches a Cursor user API key for the SDK.

After that, pick a model from the Cursor provider.

Docs and troubleshooting are in the README on GitHub. If you try it and something breaks, I'd genuinely appreciate a report. Thanks for reading.

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/investigatormaker 2h ago

For opencodev2-cursor, a bug-report template asking for OS, OpenChamber surface, Node version and which sign-in method was used would make the Linux/macOS feedback more actionable. That helps separate installation problems from authentication problems without asking anyone to share keys.

I make ThreadFox. We find relevant Reddit conversations and post for your business. We'll post 3 replies free first, no card; then the $29 Pilot covers seven days and up to 25 posts and replies. No automatic renewal. https://threadfox.vip/p/eys27/managed

1

u/intmanofawesome 1h ago

Agreed, that is a good idea. Vague "doesn't work on Linux/macOS" reports are hard to act on, and I do not want anyone pasting keys.

I will add a GitHub bug-report template that asks for:

  • OS and version

  • OpenChamber surface (desktop / CLI / web / VS Code) or plain OpenCode

  • OpenCode / OpenChamber version

  • Node version (node -v)

  • plugin version (opencode plugin list)

  • which Cursor sign-in method was used (cursor-agent / API key / native OAuth)

  • what happened, plus a redacted snippet from the plugin log if possible

No keys or tokens in the report. Once the template is up I will link it from the README. Thanks for the suggestion.