cd /news/ai-agents/empryo-vs-pi-on-opus-5-four-bugs-fix… · home › topics › ai-agents › article
[ARTICLE · art-140569] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=· neutral

Empryo vs pi on Opus 5: four bugs fixed, $2.27 vs $3.10

A developer benchmarked their AI coding agent Empryo against the rival agent pi on four real bug fixes drawn from the hono and opencode TypeScript repositories, with both agents fixing all four bugs on Opus 5. Empryo's round total came to $2.27 versus $3.10 for pi, with most of the net savings coming from the two opencode tasks, though pi was cheaper on the cookie-mangling bug. The developer cautions that the comparison reflects specific configurations — Empryo with 37 tools and its Genome code map versus a four-tool pi setup — and a small number of attempts, mostly two runs per result.

by read1 min views1 publishedSep 27, 2026

I build Empryo, an AI coding agent for desktop and terminal. In my benchmark published on 16 August 2026, Empryo and pi both fixed all four bugs on Opus 5. The published round totals were $2.27 for Empryo and $3.10 for pi, summing the per-task costs.

I'm focusing on Opus because both agents passed every task in that slice, so the cost comparison doesn't trade away a successful fix. This isn't a claim about today's versions or every model. The wider report covers six models, and explicitly notes that pi can still be cheaper on inexpensive models.

The bugs came from hono and opencode. Hidden regression tests from the merged fixes graded the changes.

Opus 5 task Empryo pi
Cookie mangling, hono $0.468 $0.269
TrieRouter regexp, hono $0.570 $0.634
Symlinked grep root, opencode $0.762 $1.19
Revert by ID, opencode $0.472 $1.01
Round total, rounded $2.27 $3.10

pi was cheaper on the cookie bug. Most of Empryo's net savings came from the two opencode tasks.

The published report uses a small number of attempts: mostly two per result, with some single runs. Both repositories are TypeScript. Empryo ran with 37 tools and its Genome code map; the tested pi configuration used four tools. This compares those configurations, not every possible pi setup.

The timing protocol also prebuilt Empryo's code index. Cold indexing was reported separately at 96-100 seconds for opencode and eight seconds for hono. Don't mistake an agent-working timer for a fresh-install timer. I'm keeping this post's comparison to cost and correctness.

── more in #ai-agents 4 stories · sorted by recency
── more on @empryo 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/empryo-vs-pi-on-opus…] indexed:0 read:1min 2026-09-27 · —