open-cursor
GitHub

open-cursor

open-cursor connects OpenCode to the models available through your Cursor subscription. It translates prompts, streaming responses, and tool calls between OpenCode and cursor-agent.

Getting started

  • Installation sets up the package, OpenCode provider, and current Cursor model list.
  • Authentication covers Cursor CLI login, API keys, and checks for each backend.
  • Quick start runs a first prompt and explains automatic model selection.
  • Troubleshooting maps common symptoms to checks and repair commands.

Guides

  • Choosing a model explains discovered model IDs, auto, variants, and unavailable models.
  • MCP servers connects configured servers and describes tool-name translation.
  • Permissions shows which runtime executes each tool and where approval rules apply.
  • Session resume covers conversation continuity, retry behaviour, and known boundaries.
  • Subagents traces delegated work through OpenCode's task tool.

Reference

  • Configuration lists every supported CURSOR_ACP_* variable.
  • CLI documents the open-cursor commands and flags.
  • opencode.json shows the provider, plugin, model, and MCP configuration written by the installer.
  • Alternatives compares other Cursor and OpenCode integrations by runtime and authentication model.
  • Roadmap separates shipped behaviour, active work, and deferred ideas.

Architecture

  • Overview follows a request across the provider, proxy, Cursor runtime, and response stream.
  • Stream translation explains how Cursor events become OpenAI-compatible streaming output.
  • Tool loop covers tool-call conversion, execution ownership, and result continuation.
  • ACP and MCP distinguishes the provider protocol from external tool-server transport.
  • Cursor-agent tools documents built-in tool handling and the compatibility boundary.

Development

  • Building builds the plugin, library, and CLI from a local checkout.
  • Testing maps test suites to runtime boundaries and useful focused commands.
  • Releasing records versioning, tagging, publication, and post-release checks.
  • Contributing covers project conventions, pull-request checks, and useful bug reports.