Pass the Hono request object into agent handlers

[FredKSchott]

Today, agent handlers do not receive the underlying request object, which makes it harder to implement route-level auth or inspect request metadata such as headers. A useful improvement would be to pass the Hono request object into handlers so authors can consistently inspect things like Authorization headers, cookies, and other request details.

This assumes Flue uses Hono consistently across targets, including Node and Cloudflare, so the request object shape stays portable instead of becoming target-specific.

[stainlu]

+1 on passing request context, but i would be careful about making the Hono request object the public contract too early.

maybe the portable layer should expose a standard request shape instead:

• method / url / headers on FlueContext
• maybe request: Request if body parsing can use request.clone() safely
• parsed payload stays as-is

that gives auth enough surface area (Authorization, cookies, etc.) without coupling agent handlers to Hono. if #56 grows into a user-owned app entrypoint, that can be the Hono escape hatch, while handlers stay runtime-agnostic.

[FredKSchott]

Shipped in @flue/sdk@0.4.0: handlers now receive ctx.req: Request | undefined, a standard Fetch Request for the current invocation. You can read headers (ctx.req.headers.get(...)), method, URL, and the raw body (req.text() / req.json() / req.arrayBuffer() / req.formData()). The body is preserved for handlers (Flue clones internally), so things like HMAC signature verification work directly.

This deliberately exposes the standard Request shape rather than the Hono request object — keeps handlers portable across Node and Cloudflare, and matches @stainlu's suggestion in the thread. If you do need full Hono primitives, app.ts (shipped from #56) is the escape hatch.

Closing as resolved.