hey folks been using claude code heavily on a massive ts project lately and tbh im hitting that exact same brick wall everyone else is talking about: context rot. after like 30 turns claude just turns into an amnesiac junior dev. it will blindly run a massive git diff or try to read a 3500 line file just to find a single function. it completely destroys whatever context budget is left and triggers compaction way too early. worse part is it keeps making changes that are “locally correct” but silently break downstream modules bc it cant see the full blast radius of its edits. i got so sick of constantly resetting sessions and manually editing CLAUDE.md files that i spent the last few weeks building a local fix. i really just wanted to see wtf happens if you intercept claudes mcp tool calls before they hit the llm and algorithmically prune the noise. dogfooded it today during a brutal refactor on my repos shell-classifier and the telemetry actually blew me away. in a single turn, claude attempted to read local-graph.ts (3,522 lines) just to verify a dependency. the background daemon i built intercepted the read, skeletonized the file into an AST outline, and only served claude the structural lines it actually needed. it also intercepted a raw git diff and compressed it down to a semantic summary. the result on just that single turn: saved 218,427 tokens from entering the context window (bought me roughly 6 extra turns of pure reasoning headroom) caught and blocked a cascading edit that would have nuked 3 downstream callers claude didnt even know existed anyway the tool is called unerr and i just open sourced the cli. how it works structurally: runs as a zero config local background process on your machine. plugs directly behind the mcp channel claude code already uses. when claude tries to read a file or run a shell exec, unerr processes it against an embedded local CozoDB code graph first, strips the noise, anchors the project memory so docs dont rot, and hands claude the surgical context. zero cloud, zero fluff. no accounts, no api keys, your code never leaves your machine. i basically built this out of pure desperation bc i was bleeding api costs and losing my mind watching claude loop on large codebases. its completely free and open source. if you are a heavy claude code power user hitting the scaling wall, would love for u to spin it up on your messiest repo, look at the local dashboard trace, and lmk if the context savings actually hold up for your workflow too. repo here: https://github.com/unerr-ai/unerr-cli submitted by /u/StatisticianFluid747
Originally posted by u/StatisticianFluid747 on r/ClaudeCode