I built a self-managing memory system for Claude Code (and it changed how I work)

I built a self-managing memory system for Claude Code (and it changed how I work) Every time I started a new Claude Code session, I had the same problem: the agent had no idea what I'd been working on. It didn't know which branches were active, what decisions I'd made yesterday, or which bugs I'd already solved. I was constantly re-explaining context. My "memory" was a single flat file (MEMORY.md) with a 200-line cap. It was a dump of random facts, project notes, and workarounds crammed together with no structure. Claude would load it, skip half of it, and miss critical details buried on line 147. So I built something better. The problem with flat memory Claude Code has a built-in memory system. It reads a MEMORY.md file from a project-specific directory on session start. That's useful, but it has limits: 200-line cap : anything beyond that gets truncated No structure : facts about six different projects, infrastructure details, and content strategy rules all jammed into one file No se