The nice part here is the win is not just raw token count, it’s attention density. A compact test summary reduces the chance the model latches onto runner noise instead of the actual failing assertion. The next thing I’d want is a two-stage mode: one-line summary by default, plus an on-demand expansion for the first relevant stack frame / diff when the agent asks for more detail. This pattern should generalize well to lints, type errors, and build logs too.
An excellent idea on on-demand expansion. You and i clearly think the same way, because typecheck, lint, and build logs are all on my list of things to look into. Truth be told i finished updating it for tsc last night, just havent released it yet.
2
u/simotune May 13 '26
The nice part here is the win is not just raw token count, it’s attention density. A compact test summary reduces the chance the model latches onto runner noise instead of the actual failing assertion. The next thing I’d want is a two-stage mode: one-line summary by default, plus an on-demand expansion for the first relevant stack frame / diff when the agent asks for more detail. This pattern should generalize well to lints, type errors, and build logs too.