Integrations
EGC for Droid
Give Droid 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 Droid 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 Droid alone with egc install --target droid --profile full.
What Droid gets
Memory
Decisions, session context, working memory and lessons captured in Droid 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; Droid 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 as PreToolUse hooks on Execute, Droid's shell tool, and the write validator on Edit, Create and ApplyPatch, in the Claude Code shape Droid reads, merged under the hooks key of ~/.factory/settings.json next to your own settings and hooks.
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 | droid |
|---|---|
| Files | Droid, from Factory, reads its personal files from ~/.factory: skills installed flat under ~/.factory/skills/<name>/SKILL.md, commands under ~/.factory/commands/, invoked as /<name>, and agents and rules as library folders under ~/.factory/egc/library/, since custom droids carry their own model and tool ids; the root AGENTS.md installs as ~/.factory/AGENTS.md, the personal instructions file Droid reads, where the cognitive bootstrap keeps the memory protocol. |
| MCP servers | Registered by egc init under mcpServers in ~/.factory/mcp.json, only when Droid is present. |
The full map of how each tool integrates lives in the integration tiers spec.
Share memory between Droid and
Every tool below reads and writes the same memory as Droid. Open two of them side by side and the second already knows what the first decided.
