Tech
Repository Harness, Part 2: 30 Runs Later, It Wasn’t Cheaper. It Was More Predictable.
This is the follow-up to Coding Agents Evolved. Our Repositories Didn’t. .
My first Repository Harness benchmark produced an uncomfortable result.
The Harness completed the task faster than a monolithic AGENTS.md , but it used more fresh input tokens.
That could have meant the idea was wrong.
It could also have meant that my first implementation of progressive disclosure was not strict enough.
So I changed the routing model, rebuilt the benchmark baseline, and ran the experime...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to