Integrations
EGC for Auggie
Give Auggie 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-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 Auggie 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 Auggie alone with egc install --target auggie --profile full.
What Auggie gets
Memory
Decisions, session context, working memory and lessons captured in Auggie 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; Auggie 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. No hooks: Auggie documents no hook or plugin API with an allow/deny decision, so the Guardian is out of scope there; 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 | auggie |
|---|---|
| Files | Skills installed flat under .augment/skills/<name>/SKILL.md, commands flat under .augment/commands/<name>.md and rules flattened under .augment/rules/*.md, the three families Auggie reads natively, in the home (~/.augment) and in each project; agents ship as a library folder under .augment/agents/, since Auggie has no sub-agent catalog. |
| MCP servers | Registered in ~/.augment/settings.json under the standard mcpServers key by egc init and the installers, the same file auggie mcp add writes to. |
The full map of how each tool integrates lives in the integration tiers spec.
Share memory between Auggie and
Every tool below reads and writes the same memory as Auggie. Open two of them side by side and the second already knows what the first decided.
