Next.js file routing, except the endpoints think

What it does Dawn wraps LangGraph in a Next.js-style meta-framework so you author agents as filesystem routes instead of hand-rolling node graphs. Export an agent() descriptor from a file under src/app/, colocate tools and state schemas beside it, and Dawn discovers the route, wires everything together, and emits a langgraph.json package for LangSmith. A default SQLite checkpointer and thread store ship with every app, so durable threads and human-in-the-loop pauses work without extra setup.

The interesting bit It treats agent development like full-stack web development: route-local scope, middleware for access control, an HMR dev server, and even a dawn verify pre-deploy gate. The dawn dev server speaks the Agent Protocol, letting you create threads and invoke routes via HTTP exactly as you would call a local API endpoint.

Key highlights

• Routes export agent, workflow, graph, or chain descriptors from the same filesystem convention.
• dawn dev provides local Agent Protocol endpoints for blocking JSON or streaming SSE runs.
• Built-in SQLite checkpointer; threads survive dawn dev restarts and human-input pauses.
• @dawn-ai/testing and dawn eval support fixture replay for offline CI and live-model local checks.
• Optional sandbox mode routes filesystem and shell calls through an isolated provider.

Verdict Grab it if you want Next.js ergonomics for LangGraph and live entirely in TypeScript. Look elsewhere if you need a polyglot framework or want to keep fine-grained control over every graph edge.