My AI agent kept blind-reading my files. So I built a local CLI to give it "eyes" (Looking for beta testers! 🐛)

Hey DEV community 👋,

As a solo dev, I’ve been relying heavily on AI coding agents lately (Claude Code, Cursor, etc.). They're amazing, but my token bills have been getting ridiculous, and the agent's context window inevitably turns into a clogged mess after a few turns.

Digging into it, I realized the biggest culprit is file reads.

When an agent wants to explore a codebase, it usually reads full files blindly. It doesn't actually "know" the structure or the blast radius of what it's touching until it reads 500 lines of irrelevant code.

I looked at existing context tools like Graphify and RTK, but they either rely on post-hoc compression (compressing the output after the agent has already wasted the read) or they use an external LLM to do the reasoning. I wanted something deterministic, entirely local, and pre-hoc.

So, for the past few weeks, I’ve been building unerr.

npm install -g @unerr-ai/unerr

(No cloud, no accounts, no API keys needed. The intelligence runs entirely locally).

If you hit a bug, get a weird error log, or if the agent just ignores it, please drop it in the comments. I will be glued to my keyboard squashing bugs all weekend!

Thanks for reading!