News for hackers. Stuff that matters.
Re: by brendanator on Friday November 13, 2026 @10:24AM (#50484893)
Sourcery CEO here. Wanted to comment on the claims of 1.6x Greptile review comments.

With Greptile there's a precision-recall trade-off with code review comments. Greptile is at the precision end of the scale, so every comment that they make is accurate. We've seen on GitHub that over 80% of the comments they make get addressed. At the other end of the spectrum is Sourcery [1], which produces over 2x as many comments as Greptile, and this agent run example has 1.6x.

Shameless self-promotion: we believe that outputting a lot of comments, even if they're nitpicky, is the right way to go for coding agents because they can triage all of the comments very rapidly and decide which to address and which are not relevant.

[1] https://sourcery.ai

Re: by voakbasda on Friday November 13, 2026 @10:48AM (#50485252)
I have done this with my own agent frameworks. They have their own issue trackers and record notes there, so the next agent to work an issue can pick up and go. In addition to providing the specific context for individual tasks, the notes then get swept into per-project libraries that distill the information for future planning.

If it is not written down, the agents can’t know it, so the rule is to write everything down. File an issue before starting work, update with a note at every step. One task per issue. You know… the stuff we would do for each other, if we all didn’t hate Jira and its ilk so very very much.

Re: by stronglikedan on Friday November 13, 2026 @01:07PM (#50487351)
> we believe that outputting a lot of comments, even if they're nitpicky, is the right way to go for coding agents

Is this what they mean by "tokenmaxxing"?

Re: by dirtbag__dad on Friday November 13, 2026 @09:22PM (#50493003)
How do you manage review loops where the agents nit their way through nonsensical (but real) edge cases?