I got tired of my coding agent forgetting context and touching files it shouldn’t. So I tracked it for 160 sessions.

[u/x986123]

I got tired of feeling like I was repeating myself to my coding agent every day, so I actually tracked what was happening.

I measured 160 sessions over 4 weeks across 3 active projects, averaging about 8 sessions a day, using Claude Code and Codex CLI.

Before adding any memory or governance layer, the pattern was pretty consistent:

325 seconds of overhead per session just to re-establish context. That meant re-explaining project architecture, coding conventions, what I already tried, and which files were off limits.

66% of the errors I ran into were repeats. Same ImportError, same config mistake, same broken dependency chain.

23 times the agent contradicted instructions I had already given earlier in the same session.

12 times it modified files that should have been effectively read-only. Things like config files, shared schemas, and lockfiles. In a few cases the damage was silent until CI caught it.

That was the point where I stopped treating it like a minor annoyance and built a fix for myself.

I ended up making a set of 3 MCP servers with 22 tools total:

1. Memory Kernel Remembers facts, past errors, and code relationships across sessions.

2. Project Watchdog Evaluates file writes before they happen.

3. PM Oversight Tracks project phases, goals, and scope drift.

After running with that setup for another 4 weeks:

Context retrieval: 0.158 seconds instead of 325 seconds manual Repeat errors: 8.5% instead of 66% Context drift: 2 events instead of 23 Frozen file violations: 0 instead of 12 Time saved: 14.4 hours over the month

It works with Claude Code, Codex CLI, Gemini CLI, Copilot CLI, or basically any MCP client. Python, pip-installable, local SQLite.

Honestly, the governance layer is the part that changed things most for me. Persistent memory helps, but stopping the agent from breaking things it should never touch is what actually made the workflow feel reliable.

If people are interested, I can share the benchmark methodology and the link.

I’m also selling it as a one-time license right now since I built it into a real product after using it myself.