Is your reviewer agent ever actually called? Counting it from session logs Among people in Korea who run AI coding agents for real work, one habit keeps coming up in conversation. A reviewer agent gets defined with care, given a strict read-only tool list and a verdict format, and then the main agent quietly does the work itself. The definition exists. Whether it is ever invoked is a different question, and nobody I know had measured it. So I wrote a script that reads the session logs my coding agent leaves behind, counts who edited files and whether any review step ran, and pointed it at two machines. All numbers in this post come from my own logs on 2026-11-02, covering roughly the last month on each machine. The question A review step, for me, is one of three things: a sub-agent whose type looks like a reviewer (critic, verifier, judge, anything with "review" in the name), a read-only run of a second model on the same diff, or a review skill. A producing session is any ...
How people in Korea actually use AI at work: real workflows, actually run, with the numbers and the parts that broke.