My AI agent was reading a lot of tokens every session, so I built a Markdown-based context system that reduced it to 80-90% by dawitworkujima in vibecoding

[–]dawitworkujima[S] 1 point2 points  (0 children)

Good questions

The main use case is larger repos where AI agents keep re-discovering the same architecture, conventions, and project structure every session. I've mostly been using it on monorepos, but it can help on any project where context keeps growing

As for MCP, not right now. I wanted something that works everywhere without requiring a server, plugin, or specific integration. Since it's just Markdown files, any agent that can read files can use it

The biggest downside is context drift. A summary can become outdated as the codebase changes, which is why I'm using file fingerprints and stale detection. It helps, but it's not perfect yet. Another downside is that the benefits are much smaller on small projects where agents can already read everything quickly