Integrations
EGC for Mistral Vibe
Give Mistral Vibe 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 Mistral Vibe 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 Mistral Vibe alone with egc install --target vibe --profile full.
What Mistral Vibe gets
Memory
Decisions, session context, working memory and lessons captured in Mistral Vibe 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; Mistral Vibe 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 [[hooks]] entries of type pre_tool in hooks.toml: the Guardian strict on the shell tools and edit, answering {decision: "deny", reason} through vibe-guardian-adapter.js; the Crusher on the shell tools, returning the command rewritten through egc run in hook_specific_output.tool_input.
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 | vibe |
|---|---|
| Files | Skills installed flat under ~/.vibe/skills/<name>/SKILL.md, where Vibe discovers them (VIBE_HOME moves the root; vibe-project writes .vibe/skills/ for a trusted folder); agents, commands and rules ship as a library under egc/library/ in the same root, out of the agents/ directory Vibe reads TOML profiles from; the root AGENTS.md installs as ~/.vibe/AGENTS.md, the user-level instructions file Vibe reads for every project, where the cognitive bootstrap keeps the memory protocol. |
| MCP servers | Registered by egc init in config.toml under VIBE_HOME or ~/.vibe as [[mcp_servers]] tables with transport = "stdio", the shape vibe mcp add writes. |
The full map of how each tool integrates lives in the integration tiers spec.
Share memory between Mistral Vibe and
Every tool below reads and writes the same memory as Mistral Vibe. Open two of them side by side and the second already knows what the first decided.
