FAQ

No. All state is stored locally at ~/.egc/. Nothing is sent to external servers. The MCP servers communicate over stdio with your local AI tool only.

28 tools: Claude Code, Cursor, Codex CLI, Antigravity CLI, OpenCode, Devin Desktop, Amp, VS Code Copilot, Zed, Kiro, Trae, CodeBuddy, JetBrains Junie, Goose, OpenHands, Aider, Warp, Cline, Qwen Code, Kimi Code CLI, Crush, Auggie, Mistral Vibe, Grok Build, Kilo Code CLI, MiMo Code, Pi, and Droid. The installer auto-detects which ones are installed. Gemini CLI, Continue.dev, and Roo Code were retired after their vendors discontinued them, and Amazon Q Developer CLI followed on 2026-09-30 (sign-ups closed, support ending on 2027-04-30, the CLI became the Kiro CLI).

No. The cognitive bootstrap injected by the installer (egc install, then egc init in each project) writes the protocol into each tool's global instruction file. The AI is instructed to call get_state at the start of each session automatically. For tools where the AI instruction file isn't read automatically (varies by tool version), you may need to add the project's CLAUDE.md or equivalent to the session context manually.

Yes. State is stored per project and per git branch: the project slug comes from the absolute path of the directory, and each branch gets its own state document. Open different projects in different sessions and each gets its own memory.

Run egc repair to restore managed files. State files are Markdown encrypted at rest; the memory server reads and writes them for you, and its GCM authentication detects corruption on read. Use egc export to read what is stored. You can delete a state file manually to reset a project. The SQLite database is separate from the state files.

No. It's optional and off by default: the installer asks, and from v1.1.22 egc install --prompt-library adds it without the question. The MCP servers (memory and guardian) work independently of the prompt library.

Those files are static and committed to the repo. EGC's state is dynamic and project-local: the AI writes to it every session, accumulating decisions and preferences over time. They complement each other: static rules for repo conventions, EGC state for session continuity.

Yes. The engine is Apache-2.0 and stays free. If EGC ever offers something paid, it will be a team layer on top of the engine, never the memory on your machine. The direction is written down in docs/VISION.md.

Every tool gets the same install path and memory protocol. Core-supported tools (Claude Code, Antigravity, Cursor, Codex CLI, OpenCode) are run daily by the maintainer or a steward, and a regression caused by a vendor change is fixed before the next release. Community-supported tools are installed and tested in CI like the rest, but a vendor change waits for a report or a pull request. The list and the criteria live in docs/governance/support-levels.md, and each tool has its own page under Integrations.

Yes. Read CONTRIBUTING.md on GitHub. PRs are welcome for bug fixes, new tool integrations, and prompt library additions.