A framework-neutral foundation for devtools. One definition becomes a Web Standard handler you can mount into any host, ship as a CLI or static report, and expose to coding agents.
`defineDevframe()` describes a tool once; `initDevframe()` turns it into a `Request → Response` handler you mount into Hono, Nitro, Next.js, SvelteKit, Vite, Rsbuild, Deno, or Bun.
The same definition also becomes a standalone CLI, a dev server, a static report, an MCP server, or a Vite DevTools dock — pick the entry points your package ships.
Bidirectional calls built on birpc, validated against any Standard Schema validator, plus observable patch-synced state that survives reconnects and bridges server and browser.
Expose the same internal state and capabilities to a web UI and to coding agents over MCP — one source of truth, two interfaces, each playing to its strengths.
`@devframes/hub` composes many devframes behind one handler with docks, commands, terminals, and messages — the composition layer flagship hosts like Vite DevTools build on.
Official plugins span Vue, Svelte, Solid, and React — living proof that devframe owns the protocol and leaves the UI framework choice entirely to the author.