Integrations

EGC for Kilo Code CLI

Give Kilo Code CLI the same persistent memory, guardrails and context as 27 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 Kilo Code CLI 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 Kilo Code CLI alone with egc install --target kilo --profile full.

What Kilo Code CLI gets

Memory

Decisions, session context, working memory and lessons captured in Kilo Code CLI 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; Kilo Code CLI 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, Token Crusher and session restoration through the same in-process plugin as OpenCode, opencode-egc-plugin.js under ~/.config/kilo/plugins/, on tool.execute.before.

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	kilo
Files	Kilo CLI is a fork of OpenCode and reads the same layout from its own config directory, ~/.config/kilo/ (XDG_CONFIG_HOME moves it): skills flat under skills/<name>/SKILL.md, agents under agents/ in OpenCode's agent shape, commands under commands/ and rules as a library folder under egc/library/rules/; the root AGENTS.md installs as the global instructions file Kilo reads, where the cognitive bootstrap keeps the memory protocol.
MCP servers	Registered by egc init under the mcp key of ~/.config/kilo/kilo.json, in OpenCode's {type: "local", command: [...]} shape, only when Kilo is present; its own kilo.json keeps the servers apart from OpenCode's config.

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

Share memory between Kilo Code CLI and

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