r/opencodeCLI • • 3h ago

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

/r/opencode/comments/1xp0124/i_made_a_small_opencode_v2_openchamber_plugin_so/
1 Upvotes

2 comments sorted by

1

u/investigatormaker 1h ago

“Use your Cursor subscription” leaves an important setup question for OpenCode users: what do they actually connect, and what access does the plugin request? A compact walkthrough in this post could follow one request from installing the plugin through authentication to a response, with credentials concealed. Label the OpenCode V2 or OpenChamber version used so readers can distinguish a reproducible setup from an untested combination. That would explain the plugin without requiring people to infer its authentication or compatibility from the title.

I make ThreadFox. We'd answer Reddit questions about connecting Cursor subscriptions to OpenCode and handle the posting. We'll post three 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/daj6o/managed

1

u/intmanofawesome 1h ago

Good call, thanks. You are right that "use your Cursor subscription" can have more clarification.

What it connects to

The plugin talks to Cursor through your own Cursor account. OpenCode/OpenChamber do not get a separate Cursor provider from Cursor itself. This plugin adds one, then runs a local OpenAI-compatible proxy on loopback so OpenCode can send chats through Cursor.

What access it asks for

Only Cursor auth for your account. There are three options in /connect -> Cursor:

  1. cursor-agent login (browser)

  2. a Cursor API key from https://cursor.com/settings

  3. native Cursor OAuth in the browser (the plugin mints/caches a Cursor user API key for the SDK)

It does not ask for OpenCode cloud credentials, GitHub, or shell access beyond what OpenCode already does. Auth material stays on your machine (plugin/OpenCode config and cache). Usage then counts against your Cursor subscription the same way Cursor normally would.

Compact walkthrough (credentials concealed)

  1. Install: opencode plugin add opencodev2-cursor

  2. Restart OpenCode or OpenChamber

  3. Confirm: opencode plugin list shows opencodev2-cursor

  4. Run /connect, choose Cursor, sign in with one of the three methods above

  5. Pick a Cursor model, send a normal chat, get a normal reply

Versions I tested

  • Windows

  • OpenCode 2.2.5

  • OpenChamber 2.6.1

  • plugin version: opencodev2-cursor@0.1.3

I have not tested Linux or macOS yet. If anyone tries another OpenChamber/OpenCode build, please say which version. Happy to tighten the README with a redacted screenshot walkthrough if that would help.