Integrations
EGC for Letta Code
Give Letta Code the same persistent memory, guardrails and context as 28 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 Letta Code 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 Letta Code alone with egc install --target letta --profile full.
What Letta Code gets
Memory
Decisions, session context, working memory and lessons captured in Letta Code 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; Letta Code 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. None: Letta Code documents no hook or lifecycle surface, so neither Guardian nor the Token Crusher is wired.
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 | letta |
|---|---|
| Files | Skills installed flat under ~/.letta/skills/<name>/SKILL.md, the computer-scoped root Letta Code shares across every agent on the machine; agents, commands, rules and the root AGENTS.md ship as reference copies under ~/.letta/egc/library/, since Letta Code documents no file that reads them. Its agent-scoped skills, inside its own git-backed memory, and the project-scoped .agents/skills/ are never written. |
| MCP servers | Not registered: Letta Code documents no MCP config file for the CLI, and its own docs steer users to skills instead of MCP, so egc init writes nothing here. |
The full map of how each tool integrates lives in the integration tiers spec.
Share memory between Letta Code and
Every tool below reads and writes the same memory as Letta Code. Open two of them side by side and the second already knows what the first decided.

