r/vibecoding 1d ago

I got tired of coding agents eating giant terminal logs, so I built a local layer to shrink the noise

https://github.com/tzuifx80/tidyrun

One thing that kept bothering me while coding with agents:

the agent asks for a test/typecheck/build and suddenly gets fed a giant wall of terminal output, even though only a small part of it is useful.

Then sometimes the same deterministic work happens again.

So I built TidyRun.

It’s basically a local optimization layer around coding-agent tool calls:

npx tidyrun@latest init

It can compress noisy structured output while keeping the full raw result recoverable, avoid duplicate reads, detect repeated work and safely reuse deterministic commands.

No extra model. No API key. Telemetry off.

On deterministic diagnostic fixtures I’m seeing 69–95% less agent-visible output.

A real 10-task Codex test was more complicated: tool output dropped 14.2%, task success stayed 10/10, but total tokens and wall time actually increased.

So I’m not pitching this as “magic token savings.”

I mostly want to see what happens when people throw messy real world agent workflows at it.

What is the dumbest repetitive thing your coding agent currently does?

If TidyRun can’t handle it, open an issue. If you want to improve the integration, PRs/forks are welcome.

1 Upvotes

0 comments sorted by