This has become very powerful to us at Tessl. We have build a maintenance agent that periodically reads historic pull requests, findings and logs, then proposes changes like as pull requests that our team reviews.
Simon MapleHead of Developer Relations · Leader, 
Tessl
Post: Anatomy of an Agentic Code Review, Tessl blog, October 9, 2026, at 6. A memory.
Simon Maple, Head of Developer Relations. Writes on Tessl's own blog about how Tessl reviews code; a vendor employee, so framing may favor Tessl's product.
Tessl sells AI or agent tools or services, so it has a reason to publish flattering numbers about AI. The passage stays in the archive; read it with that in mind.
Checked against the source by a first reader, then confirmed independently by a second reader who fetched the source without seeing the first reader's notes (Independent review agent (Claude Sonnet), blind second pass from passage text and citation only, no repository access, 2026-11-04).
Exact match, including the source's typos ('We have build', 'like as pull requests'). I did not separately confirm the byline names Simon Maple, so the speaker attribution rests on the packet.
Simon Maple (Tessl), “Anatomy of an Agentic Code Review”, Tessl blog, 2026-10-09, at 6. A memory. https://tessl.io/blog/anatomy-of-an-agentic-code-review Archived at https://the-ai-record.com/passages/tessl-maintenance-agent-periodically-reads-historic-pull-requests-2026
Coding agents abruptly changed that reality. They can turn a ticket into a pull request in minutes, so teams end up getting greater numbers of PRs, much faster. Review didn't speed up with them and, as we well know, it became the bottleneck.
Simon MapleHead of Developer Relations · Leader, Tessl
Post: Anatomy of an Agentic Code Review, Tessl blog, October 9, 2026, at Introduction.
A verifier runs in seconds, costs almost nothing and gives the same answer every time. Anything a verifier can catch, review shouldn't have to, which leaves the lenses free to spend their attention on problems that genuinely need reasoning about.
Simon MapleHead of Developer Relations · Leader, Tessl
Post: Anatomy of an Agentic Code Review, Tessl blog, October 9, 2026, at Beyond the code review: Tessl verifiers and security findings.
Something wrong? Report a correction. JSON: /api/v1/passages/tessl-maintenance-agent-periodically-reads-historic-pull-requests-2026.json