Integrations

EGC for Codex CLI

Give Codex CLI 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.

Core-supported

The maintainer or an area steward runs it daily; a regression caused by a vendor change is fixed before the next release. How support levels work.

Install

One command sets up the engine for Codex CLI 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 init

The 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 Codex CLI alone with egc install --target codex --profile full.

What Codex CLI gets

Memory

Decisions, session context, working memory and lessons captured in Codex CLI 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. The same hook file injects the mesh notice as additional context.

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. Hooks at ~/.codex/hooks.json.

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	codex
Files	Skills installed flat under ~/.agents/skills/<name>/SKILL.md; persistent instructions appended.
MCP servers	~/.codex/config.toml, written by egc init and the installers.

The full map of how each tool integrates lives in the integration tiers spec.