OpenCode++ plugin
A Windows plugin for OpenCode Desktop that sets edit boundaries, screens commands and ties test results to the current code.
- 113 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The EXE installer writes files into the OpenCode config directory.
- The plugin only restricts and verifies and does not protect against other applications.
Install
- Works in
Manual install
Download `opencode-plusplus-setup-win-x64.exe` from the repository's GitHub Releases, show me its size and checksum and wait for permission to run it. OpenCode Desktop must be closed before installation.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The EXE installer writes files into the OpenCode config directory.
- The plugin only restricts and verifies and does not protect against other applications.
This is third-party code. Review the repository files before installing.
What it does
OpenCode++ is a user-level plugin inside OpenCode Desktop that adds one selectable mode of the same name. OpenCode still reads files, edits code and runs commands, while the plugin sets context, boundaries and checks around that work. There is no second model or separate process. Through the `prepare`, `retrieve`, `evaluate` and `next` tools the agent first selects relevant files and symbols, then records edit boundaries and required checks, and screens commands and protected paths. Command and CI results are tied to the hash of the current working tree. The final decision suggests the next step: repair, repack context, call a human or finish. Data lives in the repository's `.agent-context/` directory.
Who it is for. OpenCode Desktop users on Windows who need to see which files the agent read, what it blocked and what fresh checks confirmed.
Good fit when
- The agent declared a task done but fresh test results are missing.
- Edits must stay inside directories set in advance, with no drift beyond the task.
- The repository needs a trail of checks to review a disputed diff.
- A command is screened against protected paths before running.
Not a fit when
- Work happens in OpenCode on macOS or Linux.
- An OS-level sandbox that stops another application is needed.
- The task is small and the mode's overhead is not justified.
Example request
Fix the login timeout and add a regression test. Work in OpenCode++ mode and show the verdict based on fresh results.Limitations
The installer targets Windows x64, runs without administrator rights and installs the plugin into OpenCode Desktop only. The plugin does not replace an OS sandbox, cannot prove business logic from an exit code and does not reveal hidden model reasoning. Context is guidance, not permission. Remote context sources and feedback are off by default and are enabled explicitly. Do not switch to Build while working with the mode, or the protection will not apply.
How to disable. Close OpenCode Desktop and delete the four installer files: `plugins/opencode-plusplus.js`, `agents/opencode-plusplus.md` and two files in `opencode-plusplus/` of the config directory. Remove `.agent-context/` in repositories separately.
FAQ
How do I install OpenCode++?
Download `opencode-plusplus-setup-win-x64.exe` from GitHub Releases, close OpenCode Desktop, run the EXE and restart OpenCode. Then pick OpenCode++ in the mode list under the prompt box.
Which files does the installer change?
Four files in the OpenCode config directory: the plugin, the mode definition and two state files. It no longer patches the Desktop bundle and removes old slash command files.
Are slash commands or the CLI required?
No. The mode calls the plugin tools itself. CLI and MCP remain for developers and diagnostics.
Are administrator rights required?
No. The EXE installer works per user on Windows x64 and needs no administrator rights.
Where are verification traces stored?
In the repository's `.agent-context/` directory: `traces/` with command and test results, `runs/` with task boundaries, `loops/` with decisions and the summary in `sidecar/latest.md`.
Discussion
No questions or reviews yet.
Related
PluginsAn OpenCode plugin where hooks on tool and subagent calls are declared in config and command output flows into context.
A Claude Code plugin with seven specialized subagents and approval gates: the agent proposes a plan and waits for confirmation before touching code
OpenCode plugin that turns a session into a team of agents led by an architect and runs the work through plan phases
OCX keeps OpenCode setups in portable profiles and installs agents, skills and commands from registries as ordinary files.
55 skills for Claude Code, Codex, OpenCode and Pi: code review, security audit, feature development, frontend design and Hugging Face
Plugin that builds a codebase knowledge graph of classes, calls and services, which an agent queries through MCP.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| OpenCode++ (this card) | no | 113 | |
| HarnessKit | no | 491 | installs a set of rules and contracts into a project; OpenCode++ runs inside OpenCode Desktop and checks freshness of test results |
| oh-my-opencode-slim | no | 10,207 | extends OpenCode with agents and settings; OpenCode++ adds a mode for verifying edits and evidence |
README in short
The plugin installs through a per-user EXE installer, leaves the OpenCode Desktop build untouched and works offline by default. Documentation is kept in English and Chinese.