aihu — The reactive Web Components framework

What is aihu?

aihu builds durable Web Components your AI agent can read and drive — not disposable UI it has to generate. You write .aihu Single-File Components (block-structured with @state, @template, @style, and @agent), and a Rust compiler emits standards-compliant Web Components plus a machine-readable agent manifest. An agent inspects a real component (llms.txt + MCP) and calls its actions on the live, on-screen instance over a server-mediated capability bridge — the component the user sees is the one the agent drives. The runtime is sub-2 kB and the output is vanilla custom elements. Under the hood it's a full meta-framework — file-based routing, SSR, loaders, auth, and cloud adapters are first-class, not add-ons.

Why durable, not generative

• Read and drive, not generate — the agent drives the live component the user sees, not throwaway HTML/JSON regenerated each turn (the MCP-Apps / generated-iframe model).
• Governed — the server is the policy gate (auth scope + rate limit, auditable); the browser is the sole executor.
• Agent-native by construction — the @agent block emits a matching MCP tool schema + llms.txt entry next to the component. No separate API gateway.
• Vanilla custom elements — no framework lock-in, no global context, no hydration step.
• Sub-2 kB, dependency-free — signals, computeds, effects, and direct DOM diffing; zero non-@aihu/* runtime dependencies.

Try it in one command — npx create-aihu my-app --template agent — or read the introduction, getting started, or API reference.