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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(roadmap): fold the shipped copy and readiness work into the reuse map and playbook
nirholas89fcb0573ee5
diff --git a/prompts/finish/roadmap-REUSE-MAP.md b/prompts/finish/roadmap-REUSE-MAP.mdindex 2c40114a4..9b3871f15 100644--- a/prompts/finish/roadmap-REUSE-MAP.md+++ b/prompts/finish/roadmap-REUSE-MAP.md@@ -116,8 +116,9 @@ reject a library.| Embed component | model-viewer | ✅ Apache-2.0 | **[wired]** | See §2 on the CDN-not-npm reality. || oEmbed provider | oembed.com spec (no library) | spec | **[wired]** | Hand-rolled exactly as this file predicted: `api/agent-oembed.js` (routed from `/api/oembed`) and `api/play-oembed.js`, plus `/api/widgets/oembed`. Extend those. || GLB→PNG | `puppeteer-core` + `@sparticuz/chromium-min` | ✅ Apache-2.0 | **[wired]** | **Correction to the June survey**, which named `poppygl` primary and `@shopify/screenshot-glb` (plain `@sparticuz/chromium`) the fallback. Neither was adopted. Three renderers share the headless-chromium approach: `api/_lib/render-glb.js` (OG cards), `api/_lib/avatar-render.js` (the public render endpoint and the `render_avatar_image` MCP tool) and `api/_lib/render-clip.js` (`render_avatar_clip`). The `-min` build downloads its chromium pack at first use, pinned in lockstep with the package version. |-| The renderers' three.js supply | `api/_lib/three-cdn.js` | n/a | **[wired]** | All three renderers build a page whose import map points at a pinned three.js release, and they resolve the host through `resolveThreeCdn()` (unpkg, falling back to jsDelivr on a bounded HEAD probe, cached ten minutes). `THREE_VERSION` lives in that one module. Do not hardcode a CDN host in a renderer; `tests/api/three-cdn-wiring.test.js` fails the build if you do. |-| GLB→PNG, pure JS | `poppygl` | ✅ MIT | **[open]** | Software rasterizer, zero native deps. Its original selling point was surviving a Vercel function, which no longer constrains us. Still the cheapest option if a lane ever needs a poster without paying chromium's cold start. |+| The renderers' three.js supply | `api/_lib/three-cdn.js` | n/a | **[wired]** | The chromium pages build an import map pointing at a pinned three.js release, and resolve the host through `resolveThreeCdn()` (unpkg, falling back to jsDelivr on a bounded HEAD probe, cached ten minutes). `THREE_VERSION` lives in that one module, not three copies. This is the one external dependency in the render path, and it only bites on the chromium failover, so it stayed invisible while the CPU lane absorbed the traffic. Do not hardcode a CDN host in a renderer; `tests/api/three-cdn-wiring.test.js` fails the build if you do. |+| GLB→PNG, pure JS | `@three-ws/render` (`packages/render/`) | in-house | **[wired]** | **The role poppygl was proposed for, filled by our own package instead.** `api/_lib/render-cpu.js` is the PRIMARY thumbnail lane: an in-process software rasterizer, same framing and three-light rig as the chromium page, roughly 200-500 ms with no subprocess and no CDN fetch. Chromium is now the failover, taken only for models this lane cannot decode itself (Draco geometry, KTX2/Basis textures), which is most forge output. `RENDER_CPU_LANE=off` pins everything back to chromium without a deploy. See `docs/avatar-thumbnails.md`. |+| GLB→PNG, pure JS (alternative) | `poppygl` | ✅ MIT | **[open]** | Not adopted, and now largely redundant next to `@three-ws/render`. Its original selling point was surviving a Vercel function, which no longer constrains us. |---