Skip to content

Integrations

EGC for OpenCode

Give OpenCode the same persistent memory, guardrails and context as 18 other AI coding tools. One local install, encrypted on your machine, nothing sent to a cloud.

Core-supported

The maintainer or an area steward runs it daily; a regression caused by a vendor change is fixed before the next release. How support levels work.

Install

One command sets up the engine for OpenCode and every other tool it detects. Then run egc init once in each project you want EGC to manage.

npm install -g @egchq/egc && egc install
cd your-project && egc init

The prompt library (agents, skills, commands and rules) is optional and off by default. Add it to every detected tool with egc install --prompt-library, or to OpenCode alone with egc install --target opencode --profile full.

What OpenCode gets

Memory

Decisions, session context, working memory and lessons captured in OpenCode are available in every other tool you open, and the other way around. Encrypted at rest, kept per project and branch, never committed.

Session Mesh

Open sessions announce themselves, claim the files they edit and exchange events on a local bus; OpenCode reads the bus through the memory protocol, and through the MCP tools where they are registered.

Guardian

Command validation and write gating by egc-guardian: through its MCP tools where they are registered, and through the tool's own hooks where it has them. Guardian and Token Crusher run through the native plugin events.

Token Crusher

Shell output is compressed before it reaches the model, with every error and warning kept and a local ledger of what it saved. Where the tool has no hook that rewrites commands, the PATH-level shim (egc crusher-shim) covers git, npm, gh and the rest.

Where EGC installs

Target idopencode
FilesSkills, commands, instructions and prompts under ~/.config/opencode/, next to the EGC plugin (an ES module).
MCP servers~/.config/opencode/opencode.json under the mcp key, in OpenCode's own shape, on every platform.

The full map of how each tool integrates lives in the integration tiers spec.

Share memory between OpenCode and

Every tool below reads and writes the same memory as OpenCode. Open two of them side by side and the second already knows what the first decided.