Integrations

EGC for OpenHands

Give OpenHands 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.

Community-supported

Installed, registered and tested in CI like every other tool; a vendor change that breaks it waits for a report or a pull request. How support levels work.

Install

One command sets up the engine for OpenHands 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 OpenHands alone with egc install --target openhands --profile full.

What OpenHands gets

Memory

Decisions, session context, working memory and lessons captured in OpenHands 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; OpenHands 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 through a real pre_tool_use hook, project-scoped; no Token Crusher.

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 id	openhands
Files	Skills installed flat under ~/.agents/skills/<name>/SKILL.md; hooks at .openhands/hooks.json in each project.
MCP servers	Not registered: egc init and the installers write the servers into seven tools, and OpenHands is not one of them. If it has an MCP config of its own, you can add them by hand.

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