I built persistent memory for AI coding tools one install, every tool, no more re-explaining context

A developer built EGC (Extended Global Context), an open-source tool that gives AI coding assistants persistent memory across sessions and tools. The tool installs two MCP servers into 13 supported AI coding tools, automatically saving and loading project context so developers no longer need to re-explain their codebase, decisions, or next steps. EGC reduces context rebuilding from roughly 1,500 tokens per session to about 200 tokens, and is available on GitHub under the MIT license.

Every AI coding session starts from zero. Close Claude Code and open it tomorrow. The AI doesn't know your project. You spend the first 10 minutes re-explaining the stack, the architectural decisions from last week, the approach that failed after three attempts. It gets worse when you switch tools. Move from Cursor to Codex and you start over again. I got tired of this. So I built EGC — Extended Global Context. One install. Every tool. Permanent memory. sh install.sh detects which AI tools you have Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Windsurf, Kiro, Trae, CodeBuddy and registers two local MCP servers in all of them. It also writes the memory protocol into each tool's global instruction file, so the AI calls get state {} at session start and update state {} at session end — automatically. The state file lives at ~/.egc/state/ on your machine. It follows the project, not the IDE. You open Claude Code on a project you haven't touched in two weeks. Without typing anything: State loaded from egc-memory Context acknowledged. Ready to pick up: • Fix the auth middleware regression • Add rate limiting before deploy • Decision: use Redis, not in-memory discussed 2 sessions ago The AI already knows. You just start working. Rebuilding context from scratch costs ~1,500 tokens per session. EGC delivers the same in ~200 tokens. 20 sessions/month = ~$0.08 saved. The money is small. The interrupted flow is not. Requires Node.js 20+. bash npm install -g @egchq/egc egc install That's it. Run egc doctor to verify. The two MCP servers egc-memory — the one you use every session - get state — reads project memory at session start - update state — saves decisions, preferences, next steps - store decision — persists a decision to SQLite - query history — returns past decisions by timestamp egc-guardian — runs in the background - validate command — blocks shell injection - validate write — blocks writes to sensitive paths - reduce context — deduplicates Markdown payloads It's open source GitHub: https://github.com/Fmarzochi/EGC MIT license. Built by one developer. 13 supported tools. If it saves you time, a star helps other developers find it. --- If you've been re-explaining context every session, try it and let me know what breaks. https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7y8tf9v3gtaqdwln2wye.png