hono

Hono Skill

Build Hono web applications. This skill provides inline API knowledge for AI. Use Hono CLI to inspect and test the app.

Latest Documentation

For details beyond this inline reference, fetch the latest documentation from https://hono.dev. Get the index of doc pages from https://hono.dev/llms.txt, then fetch a page with the Accept: text/markdown header to receive it as Markdown:

curl -H "Accept: text/markdown" https://hono.dev/docs/helpers/cookie

Hono CLI

Verify with Hono CLI, not with throwaway scripts or a dev server. It is a dev dependency (projects from create-hono already have it), loads the app in-process with app.request(), and prints JSON. Install it if missing, then read its help:

npm install -D @hono/cli@next
npx hono --help

Follow the note at the top. It explains the JSON output contract and the workflow. npx hono <command> --help has examples and notes for each command (routes, request, batch, snapshot, benchmark, ssg, init).

Notes:

• npx hono routes lists the routes; npx hono request /path sends one request — no server needed. If the app is not at the default path (src/index.ts), pass the file to every command: npx hono request / src/app.ts. Do not pass credentials directly in CLI arguments; use environment variables for sensitive values.
• Cloudflare bindings (KV, D1, R2, vars) reach c.env automatically — no server, no flag. In a project with cloudflare.config.ts (the cf CLI) and a Vite config, request, batch, and snapshot run through the Vite dev server by default, and c.env has the local bindings; request and batch default to Vite as well in a Vite project with no src/index.* (an app built by a Vite plugin; snapshot still needs the file), and --runtime vite selects it explicitly. In a project with a wrangler config, the app runs on Node.js with the real local bindings loaded; for the full Workers runtime there, add --runtime workerd (pass no file argument; the entry is main in the wrangler config). --trace, --watch, and a file argument run the app on Node.js, where c.env is empty in a cf project.
• routes and snapshot also load apps that import cloudflare:workers (Durable Objects); the import is stubbed while the routes are read.
• To add a Hono app to an existing directory, run npx hono init --template cloudflare-workers (or nodejs, bun, deno, ...; without --template it is detected from the files in the directory), then install the dependencies. It copies the create-hono template and never overwrites an existing file. For an empty directory, npm create hono@next does the same with prompts.
• For several requests, or a flow that keeps state (POST, then use the returned id), run them in one hono batch - call. One JSON object per line; save a value and use it as {{id}} in later steps. The steps share one app instance. Declare the expected status/body per step with expect (body is a deep partial match) and iterate until the summary shows "failed": 0: