Blog

Building better coding agents. The decisions, systems and checks behind mux.

Subscribe via RSS

12 posts

  1. How we measure Reviewer before we change it

    A language model does not fail like normal software. It writes a fluent, confident review that may be wrong, and one good review tells you nothing about the next hundred. So every change to Reviewer, the Cowork coworker that reviews pull requests, runs through the same eval before it ships. This is what an eval is, why Reviewer has one, and what the second round found on 7 November 2026, with the code index's own code in place of a simulation and 30 new cases.

  2. Reviewer reads the code your diff breaks, not just the diff

    Most bugs that reach production pass review because the reviewer only saw the change. Reviewer, Cowork's ready-made coworker for pull requests, reads the callers the change reaches before it writes a word. On a 24-case eval it found the broken caller in every cross-file run, against none without it, and left every correct change alone. Here is how it works, why a pull request cannot steer it, and how we know.

  3. No compaction

    When a task fills its context window, pi opens a fresh one with a short handoff instead of a summary; here is where that line sits, what crosses it and what it costs.