Using Cloudflare Agents SDK (Durable Objects) alongside Nitro - current workaround & suggested improvement

[lukalafayedemicheaux]

Hi team 👋

We're building on Nuxt + Cloudflare Workers and wanted to integrate the Cloudflare Agents SDK (agents package) alongside our Nitro server.

Nitro's exports.cloudflare.ts support already covers the Durable Object export requirement nicely. Since Cloudflare requires Durable Object classes referenced in the Worker config to be exported by name from the Worker entrypoint, we can expose our Agent class like this:

export { GuichetAgent } from './server/agents/guichet'

This avoids the usual Wrangler error:

Your Worker depends on the following Durable Objects which are not exported in your entrypoint file: GuichetAgent

The remaining issue is request routing. Cloudflare Agents expects requests to go through routeAgentRequest(request, env) before falling back to the app handler:

return (
  (await routeAgentRequest(request, env))
  ?? app.fetch(request, env, ctx)
)

As far as I can tell, Nitro's generated Cloudflare Worker entrypoint owns the default fetch handler, and there doesn't seem to be a first-class way to wrap it or prepend this Agents routing logic.

Our current workaround is a committed worker.ts that Wrangler bundles directly:

import { WorkerEntrypoint } from 'cloudflare:workers'
import { routeAgentRequest } from 'agents'
import nitroServer from './.output/server/index.mjs'

export { GuichetAgent } from './server/agents/guichet'

export default class Worker extends WorkerEntrypoint<Env> {
  override async fetch(request: Request) {
    return (
      (await routeAgentRequest(request, this.env))
      ?? nitroServer.fetch(request, this.env, this.ctx)
    )
  }
}

This works well, but only if we set deployConfig: false. Otherwise Nitro generates .wrangler/deploy/config.json, which redirects Wrangler to .output/server/wrangler.json, where main points to index.mjs and bypasses our custom worker.ts.

Would Nitro consider adding a way to compose custom Cloudflare fetch logic before the generated Nitro handler? For example, a request hook that can return a Response or fall through to Nitro.

That would make Cloudflare Agents integration possible without replacing the Worker entrypoint or disabling Nitro's generated deploy config.

Thanks for the great work on Cloudflare Workers support and exports.cloudflare.ts 🙌

[RihanArfan]

Perhaps we could introduce a new Nitro hook for this. Perhaps like cloudflare:fetch to be similar to the others?