{"slug": "empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10", "title": "Empryo vs pi on Opus 5: four bugs fixed, $2.27 vs $3.10", "summary": "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.", "body_md": "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.\n\nI'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.\n\nThe bugs came from hono and opencode. Hidden regression tests from the merged fixes graded the changes.\n\n| Opus 5 task | Empryo | pi | \n|---|---|---|\n| Cookie mangling, hono | $0.468 | $0.269 | \n| TrieRouter regexp, hono | $0.570 | $0.634 | \n| Symlinked grep root, opencode | $0.762 | $1.19 | \n| Revert by ID, opencode | $0.472 | $1.01 | \n| Round total, rounded | $2.27 | $3.10 | \n\npi was cheaper on the cookie bug. Most of Empryo's net savings came from the two opencode tasks.\n\nThe 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.\n\nThe 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.", "url": "https://wpnews.pro/news/empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10", "canonical_source": "https://dev.to/proxyosul/empryo-vs-pi-on-opus-5-four-bugs-fixed-227-vs-310-3eml", "published_at": "2026-09-27 16:55:13+00:00", "updated_at": "2026-09-27 17:31:20.006473+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "large-language-models"], "entities": ["Empryo", "pi", "Opus 5", "hono", "opencode", "Genome"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10", "markdown": "https://wpnews.pro/news/empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10.md", "text": "https://wpnews.pro/news/empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10.txt", "jsonld": "https://wpnews.pro/news/empryo-vs-pi-on-opus-5-four-bugs-fixed-2-27-vs-3-10.jsonld"}}