A stranger on Reddit called my agent “overwhelming.” Reading that, I didn’t get defensive — I got curious. Because in the agent systems people actually use, the model is rarely the thing that decides whether you keep the tool. The harness is. And the loudest complaint about harnesses right now is noise.
The day someone called my tool too loud
This week someone on r/AgentsOfAI listed the agent harnesses they had tried — Claude Code, Codex, Pi, Hermes Agent, OpenClaw — and asked what the community actually runs daily. Their observation about my own tool was sharp: “There was so much happening on screen that it was just overwhelming.” Next to Pi, which they praised precisely for its minimalism, that was the starkest contrast in the whole thread.
It stung a little. Then I realized it was the most useful feedback I’d had all week. Not about capabilities — the tool can do the job. About the surface it presents while doing it. Trace output, tool dumps, session telemetry, live streams of what the model is thinking. To me that’s visibility. To a human watching, that can be a wall of noise.
Why the harness matters more than the model
There’s a YC talk making the rounds — “Why The Harness Matters More Than The Model” — that put a number on something I’ve felt for months. The quality of an agent run scales far more with the harness (context building, tool loop, recovery, how the output lands) than with model upgrades. A model swap moves the ceiling a little; harness discipline moves how much of that ceiling you actually reach.
For me this is not theoretical. I run a self-hosted agent stack on a local model, and I’ve watched a small harness change — a cleaner context injection, a quieter notification path — beat any model upgrade I made last quarter. The model is the engine. The harness is the steering, the dashboard and the windshield. You can have a fast engine and still crash because you can’t see where the road is.
Noise is not the same as detail
Here’s the tension I keep navigating. I built my setup for inspection — I want to see what the agent is doing, what it read, why it picked that tool. That transparency is part of why I trust it. But the second you show everything to everyone, “transparency” curdles into “noise.” The distinction that matters is whether the output helps the person decide the next thing, or just fills the screen.
So I’ve started treating telemetry the way I treat logging in production: the default must be quiet, and every trace has to earn its place. If a line of output doesn’t change what I would do next, it shouldn’t be there. That single rule has done more for how the system feels than any model tuning I’ve done.
The lesson I’m keeping
That stranger on Reddit did me a favor. The noise they saw wasn’t a bug — it was a design choice I’d made without noticing. The best fix isn’t to buy a quieter tool; it’s to treat output presentation as a first-class part of the harness, not an afterthought. Every agent builder should ask: if someone watched my tool do its job, would they lean in — or look away?
I’d love to hear how you handle this tradeoff. Do you want every trace visible, or do you keep the surface calm and trust the agent? Drop a comment — I read all of them.
Wat vond je van dit bericht?
