Integrations
EGC for Pi
Give Pi 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 Pi 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 Pi alone with egc install --target pi --profile full.
What Pi gets
Memory
Decisions, session context, working memory and lessons captured in Pi 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; Pi 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 the extension ~/.pi/agent/extensions/egc-guardian.js: its tool_call handler blocks a destructive bash command, a protected edit or write, or an edit that would put a denied command into a shell script, with {block: true, reason}, and rewrites the bash command through the 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 | pi |
|---|---|
| Files | Everything goes into Pi's agent directory, ~/.pi/agent (PI_CODING_AGENT_DIR moves it): skills flat under skills/<name>/SKILL.md, the commands as prompt templates under prompts/, invoked as /<name>, and agents and rules as library folders under egc/library/; the root AGENTS.md installs as the global instructions file Pi loads at startup, where the cognitive bootstrap keeps the memory protocol. |
| MCP servers | Pi has MCP built in: egc init registers the servers in ~/.pi/agent/mcp.json, in the standard mcpServers shape, only when Pi is present (its agent directory exists or pi is on PATH). |
The full map of how each tool integrates lives in the integration tiers spec.
Share memory between Pi and
Every tool below reads and writes the same memory as Pi. Open two of them side by side and the second already knows what the first decided.
