Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

1.9 KB
Raw Blame

public/

Vite's static asset root. Everything here is copied verbatim into dist/ at build time (npm run build) and served by production exactly as-is: no bundling, no hashing, no transformation. That is the difference from ../pages/, whose HTML files are Vite build inputs that get processed, and from ../src/, which holds the bundled application modules.

What belongs here

  • Static pages that must ship byte-for-byte. Some standalone pages live here instead of pages/ because they need to bypass the bundler (for example watch.html, 404.html, 500.html, agent-passport.html, and the cookbook/ notebook page). They still need a vercel.json rewrite to get a clean URL; see the routing walkthrough in ../pages/README.md.
  • Brand and platform assets: brand/ (logo marks, press assets), icons, Open Graph images.
  • Prebuilt vendor bundles and loose page scripts that pages reference with plain <script src> tags rather than module imports.
  • Data-like static directories consumed at runtime: animations/, avatars/, accessories/, badges/, plus the generated changelog outputs (changelog.json, changelog.xml, and the rendered pages under changelog/).
  • Per-surface asset folders (admin/, assistant/, concierge/, dashboard-next/, ...) holding CSS and media for their matching pages.

Rules

  • Nothing here is processed, so nothing here can use bare module imports, TypeScript, or anything a browser cannot run directly.
  • A file placed here is public the moment it deploys. No secrets, no drafts, no scratch output.
  • Generated artifacts (for example the changelog feeds under changelog/ written by npm run build:pages) are regenerated by their build steps; edit the source, not the output.
  • Adding a new user-facing page? Prefer pages/ unless it genuinely must skip the bundler, and register it in data/pages.json either way.