Measure and improve the developer experience of coding agents using Hono.
Given a neutral prompt — no framework named — does a coding agent choose Hono? Hono adoption rate and the most-chosen option, per runtime × scenario. Click a cell for history and details.
| Runtime | minimal | routes | api | framework |
|---|---|---|---|---|
| cloudflare-workers | 0%Raw handler 100% | 0%Raw handler 80% | 20%Raw handler 50% | 100%Hono 100% |
| bun | 0%Raw handler 80% | 0%Raw handler 90% | 0%Raw handler 60% | 10%Elysia 90% |
| node-js | 0%Raw handler 60% | 0%Express 80% | 0%Express 80% | 0%Express 100% |
| deno | 0%Raw handler 100% | 0%Raw handler 100% | 0%Raw handler 70% | 0%Oak 100% |
| Runtime | minimal | routes | api | framework |
|---|---|---|---|---|
| cloudflare-workers | 0%Raw handler 100% | 0%Raw handler 100% | 0%Raw handler 80% | 100%Hono 100% |
| bun | 0%Raw handler 100% | 0%Raw handler 100% | 0%Raw handler 100% | 100%Hono 100% |
| node-js | 0%Raw handler 60% | 0%Raw handler 100% | 0%Failed 60% | 0%Express 100% |
| deno | 0%Other 100% | 0%Other 80% | 0%Other 100% | 60%Hono 60% |
Is Hono worth using when an agent writes the code? Same task, same acceptance spec, same model: a project with no framework (the agent writes a raw fetch handler) against a project with Hono in package.json.
| Task | plain | Hono |
|---|---|---|
| shop API (products, cart, checkout) | 2/10103k tok · 85s · 254 lines | 4/1087k tok · 72s · 156 lines |
| notes API with auth (login, bearer, CORS, JSON errors) | 10/10134k tok · 103s · 195 lines | 10/1093k tok · 82s · 129 lines |
Experiment of 2026-09-06 · 10 runs per cell · claude-haiku-4-5 · success, median tokens, median duration, median lines of code written. Not yet part of the weekly schedule.
Hand the agent a real Hono project and a change request, grade the result with hidden deterministic checks. Success rate, median tokens, and CLI usage per task — with and without the Hono CLI and skill.
| Task | baseline | cli + skill |
|---|---|---|
| add-user-route | 100%14k tok · CLI 0% | 100%21k tok · CLI 0% |
| build-endpoints | 80%39k tok · CLI 0% | 100%60k tok · CLI 100% |
| fix-404 | 100%25k tok · CLI 0% | 100%40k tok · CLI 20% |
| fix-404-shadow | 100%38k tok · CLI 0% | 100%40k tok · CLI 20% |
| refactor-routes | 100%172k tok · CLI 0% | 100%153k tok · CLI 40% |