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.

Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity CLI, OpenCode, Kiro, Trae, and CodeBuddy. The installer auto-detects which ones are installed.

No. The cognitive bootstrap injected by install.sh 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, derived from the absolute path of the project directory. Open different projects in different sessions and each gets its own memory.

Run egc repair to restore managed files. State files are plain Markdown — you can also edit or delete them manually. The SQLite database is separate from the Markdown files.

No. It's optional and asked during installation. 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. Read CONTRIBUTING.md on GitHub. PRs are welcome for bug fixes, new tool integrations, and prompt library additions.