Integrations
EGC for Cline
Give Cline 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-supportedInstalled, 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 Cline 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 initThe 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 Cline alone with egc install --target cline --profile full.
What Cline gets
Memory
Decisions, session context, working memory and lessons captured in Cline 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; Cline 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 the PreToolUse hook in .clinerules/hooks, which the VS Code extension and the Cline CLI both run (their shell tools, execute_command and run_commands, are both judged); Token Crusher through the PATH-level shim.
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 | cline |
|---|---|
| Files | Rules flattened into .clinerules/ in each project with collision-safe namespaced filenames. |
| MCP servers | Not registered: egc init and the installers write the servers into seven tools, and Cline 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.
Share memory between Cline and
Every tool below reads and writes the same memory as Cline. Open two of them side by side and the second already knows what the first decided.
