Where the code map pays off: Haiku on a 90k-line repo.
The cheap-model story.
On a small test app, searching text keeps up. On real repos it doesn't, because finding where the bug lives is the expensive part. That is what Empryo's Genome, its live map of how your code connects, is for. On Haiku, Empryo fixed one more bug than pi, spent 19% less, and finished in about half the time.
The hardest bug was a parser regression in zod, deep in a 580-file monorepo. Only Opus fixed it, for both agents. Empryo did it in 33 steps for $2.10. pi's first attempt hung until the 8-minute limit stopped it, and its retry took 69 steps and $2.42.
By each agent's own reports, pi looked about 11% cheaper over the round. The Anthropic console says otherwise, as the next section shows.
Opus 4.8 on zod preprocess-catch, one dot per step
Empryo33 steps$2.10, fixed
pi69 steps$2.42, fixed on the retry