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.

fix(create-video): send the avatar, not its .glb, so a talking-head job stops failing inside the worker

nirholas0e354dd31dbd
diff --git a/data/changelog.json b/data/changelog.json
index 233db7335..52c1c12ff 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,35 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-17",
+ "title": "Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down",
+ "summary": "The /create/video page turns one of your avatars plus an audio clip into a lip-synced video, and it was driven end to end in a real browser: every state, every button, every width. The worst finding was invisible from the page. The reference frame the GPU worker renders from was being taken from whatever the browser had handy, which for an avatar with no thumbnail meant its 3D model file. The worker saved that as the reference photo and then failed on it minutes later, after the wait had already been spent. The page now sends only the avatar, and the server resolves a real image for it: the stored thumbnail, or a fresh portrait render when there is none. Second, the GPU renderer is a separate service, and when it is not running the only signal was a failure after you had already picked a file and uploaded it. The page now asks first and, if the lane is down, says so at the top, keeps Generate switched off, and points at the Avatar Studio and prompt-to-avatar in the meantime. The rest is the ordinary polish an audit turns up: a failed avatar list used to look identical to owning no avatars, so it sent people off to create one they already had, and now it says what broke and offers a retry; having no avatars yet gets a real empty state with a link to make one; the Generate button always explains what it is still waiting for and, once audio is in, how many clips of video that audio is worth; the clip you picked can be played back with its length and size before you spend a generation on it; a render job that goes unreachable now says so after thirty seconds instead of spinning for twenty minutes; and after a spent free trial the button under the error no longer stayed stuck on Upgrade plan for every later error. Avatar thumbnails are real buttons with visible focus rings, the two form fields have proper labels, and the second animated avatar that the site companion used to drop onto this page no longer loads over the one you are working on.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/create/video"
+ },
+ {
+ "date": "2026-08-17",
+ "title": "The Pole Club audio controls no longer fall off the edge of a small phone",
+ "summary": "On a narrow phone the club's top bar ran out of room and simply cut off whatever did not fit, and the page cannot scroll sideways, so the mute button and the 8D audio toggle were gone with no way to reach them. The bar now gives up the parts that are only there to read (the tagline and the price and rail labels, all of which the panel's How it works section repeats) and keeps both controls at full size at every width, down to a 320px screen.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/club"
+ },
+ {
+ "date": "2026-08-17",
+ "title": "Scene Composer works on a phone, starts you off with real models, and answers the keyboard",
+ "summary": "Scene Composer was unusable on anything narrower than a laptop. Below 900px the scene panel was switched off, which pushed the 3D canvas into a zero-width column, so a tablet visitor got no viewport at all and no way back to the hierarchy, inspector or bone-attach controls; at phone widths the toolbar forced the whole editor wider than the screen and shoved the right-hand panel out of view. The panel is now a drawer behind a toolbar button, the toolbar scrolls instead of stretching the layout, and the canvas keeps real dimensions at 320, 768 and 1440 pixels. The Recent Creations strip also no longer greets a first-time visitor with an empty box: until you have forged something it shows the live community showcase, so there are real models to drop into the scene straight away. The avatar picker was asking the directory a question it does not answer and got back a feed of on-chain agents with no 3D model attached, so most slots were silently dropped and the rest never showed their thumbnails; it now asks for public 3D avatars and renders them. The start panel finally honours what it always promised: paste an avatar ID, not just a URL, and a model that cannot be loaded leaves a written explanation instead of a toast that vanishes before you can read it. Both the creations strip and the avatar picker now offer a Try again that works when a request fails. On the keyboard side: the page has a real heading, the camera-view menu and every creation and avatar tile are proper buttons, the scene rows expose their hide and remove actions on focus, the prompt and avatar fields have labels, dialogs trap focus and hand it back on Escape, and there is a visible focus ring throughout. Removing an object now frees its GPU memory once the step drops out of undo range, undo puts a bone-attached item back on its bone, and saving an outfit refuses a locally dropped file rather than storing a link that breaks on reload.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/compose"
+ },
{
"date": "2026-08-17",
"title": "Building an agent no longer throws you out to the login page, and the wizard answers the keyboard",
@@ -24354,16 +24383,6 @@
"improvement"
],
"link": "/coin3d"
- },
- {
- "date": "2026-08-17",
- "title": "Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down",
- "summary": "The /create/video page turns one of your avatars plus an audio clip into a lip-synced video, and it was driven end to end in a real browser: every state, every button, every width. The worst finding was invisible from the page. The reference frame the GPU worker renders from was being taken from whatever the browser had handy, which for an avatar with no thumbnail meant its 3D model file. The worker saved that as the reference photo and then failed on it minutes later, after the wait had already been spent. The page now sends only the avatar, and the server resolves a real image for it: the stored thumbnail, or a fresh portrait render when there is none. Second, the GPU renderer is a separate service, and when it is not running the only signal was a failure after you had already picked a file and uploaded it. The page now asks first and, if the lane is down, says so at the top, keeps Generate switched off, and points at the Avatar Studio and prompt-to-avatar in the meantime. The rest is the ordinary polish an audit turns up: a failed avatar list used to look identical to owning no avatars, so it sent people off to create one they already had, and now it says what broke and offers a retry; having no avatars yet gets a real empty state with a link to make one; the Generate button always explains what it is still waiting for and, once audio is in, how many clips of video that audio is worth; the clip you picked can be played back with its length and size before you spend a generation on it; a render job that goes unreachable now says so after thirty seconds instead of spinning for twenty minutes; and after a spent free trial the button under the error no longer stayed stuck on Upgrade plan for every later error. Avatar thumbnails are real buttons with visible focus rings, the two form fields have proper labels, and the second animated avatar that the site companion used to drop onto this page no longer loads over the one you are working on.",
- "tags": [
- "fix",
- "improvement"
- ],
- "link": "/create/video"
}
]
}
diff --git a/prompts/swarm-100/route-create-video.md b/prompts/swarm-100/route-create-video.md
deleted file mode 100644
index cb97f2b42..000000000
--- a/prompts/swarm-100/route-create-video.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Route audit: /create/video (Talking Avatar Video)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. This route's declared entry (path, description, added date):
-
- node -e "const p=require('./data/pages.json');for(const s of p.sections)for(const g of s.pages)if(g.path==='/create/video')console.log(JSON.stringify(g,null,2))"
-
-2. Find the serving implementation: grep "/create/video" in vercel.json (the live
- route table server/index.mjs boots from), then list matching files in
- pages/ and src/. STRUCTURE.md maps every surface to its directory if the
- grep is ambiguous.
-3. Production right now:
-
- curl -so /dev/null -w '%{http_code}\n' https://three.ws/create/video
-
-4. Start (or reuse) the local dev server: npm run dev (vite, port 3000).
-
-## Task: audit this one route end to end, then fix everything found
-
-Route: /create/video ("Talking Avatar Video", section "main").
-Declared purpose: Turn a three.ws avatar into a talking-head video: upload your audio and export a lip-synced clip.
-
-Drive the page in a real headless browser. Playwright is already a dev
-dependency; keep your probe script in the session scratchpad, never in the
-repo.
-
-1. Load http://localhost:3000/create/video. Record the HTTP status, every console
- error and warning, and every failed network request.
-2. Exercise it like a first-time user: click the primary actions, run the
- primary flow if one exists, follow the page's internal links. Every button
- must do something real; every link must resolve. If the page renders data,
- prove in the network log that it came from a live endpoint, not a baked-in
- fallback array.
-3. States: verify populated, empty, loading, and error states are designed and
- reachable. Block the page's primary fetch in Playwright and confirm an
- actionable error state appears, not a blank void or a raw exception.
-4. Responsive: render at 320, 768, and 1440 px. No horizontal page scroll, no
- overlapping or clipped controls.
-5. Accessibility basics: one h1; interactive elements are real buttons or
- links with visible focus states; images carry alt text; form fields have
- labels.
-6. Head: a specific title tag and meta description that match the declared
- purpose above.
-7. Fix every defect at its root in the page's real source files and re-run the
- probe until clean. Defects in shared modules are in scope when this route
- exercises them.
-
-## Definition of done
-
-- [ ] Local load of /create/video: HTTP 200, zero console errors, zero unhandled
- failed requests (a third-party outage must land in a designed fallback,
- not a broken page).
-- [ ] No dead interactive element on the page: no stub href="#", no button
- without a handler, no link to a missing path.
-- [ ] Empty, loading, error, and populated states verified.
-- [ ] 320 / 768 / 1440 px renders verified clean.
-- [ ] Title and meta description present and specific.
-- [ ] npm test passes; npm run check:rules -- --paths <touched files> exits 0.
-- [ ] Production status from step 0 recorded in the report; if production
- needs a deploy to pick up a fix, the report says so (deploys stay
- owner-gated).
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/route-create-video.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index a0d0d0987..d92b5e496 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T04:58:51.889Z",
+ "generated_at": "2026-08-17T05:04:17.067Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -238,8 +238,8 @@
{
"date": "2026-08-17",
"type": "update",
- "title": "Scene Composer works on a phone, starts you off with real models, and every control is reachable by keyboard",
- "summary": "Scene Composer was unusable on anything narrower than a laptop. Below 900px the scene panel was switched off, which pushed the 3D canvas into a zero-width column, so a tablet visitor got no viewport at all and no way back to the hierarchy, inspector or bone-attach controls; at phone widths the toolbar forced the whole editor wider than the screen and pushed the right-hand panel out of view. The panel is now a drawer behind a toolbar button, the toolbar scrolls instead of shoving the layout off screen, and the canvas keeps real dimensions at 320, 768 and 1440 pixels. The Recent Creations strip also no longer greets a first-time visitor with an empty box: until you have forged something it shows the live community showcase, so there are real models to drop into the scene straight away. The avatar picker was asking the directory a question it does not answer and got a feed of on-chain agents with no 3D model attached, so most slots were silently dropped and the rest never showed their thumbnails; it now asks for public 3D avatars and renders them. The start panel finally honours what it always promised: paste an avatar ID, not just a URL, and a model that cannot be loaded leaves a written explanation instead of a toast that vanishes before you can read it. Both the creations strip and the avatar picker now offer a working Try again when a request fails. On the keyboard side: the page has a real heading, the camera-view menu and every creation and avatar tile are proper buttons, the scene rows expose their hide and remove actions on focus, the prompt and avatar fields have labels, dialogs trap focus and hand it back on Escape, and there is a visible focus ring throughout. Removing an object now frees its GPU memory once the step drops out of undo range, undo puts a bone-attached item back on its bone, and saving an outfit refuses a locally dropped file rather than storing a link that breaks on reload.",
+ "title": "Scene Composer works on a phone, starts you off with real models, and answers the keyboard",
+ "summary": "Scene Composer was unusable on anything narrower than a laptop. Below 900px the scene panel was switched off, which pushed the 3D canvas into a zero-width column, so a tablet visitor got no viewport at all and no way back to the hierarchy, inspector or bone-attach controls; at phone widths the toolbar forced the whole editor wider than the screen and shoved the right-hand panel out of view. The panel is now a drawer behind a toolbar button, the toolbar scrolls instead of stretching the layout, and the canvas keeps real dimensions at 320, 768 and 1440 pixels. The Recent Creations strip also no longer greets a first-time visitor with an empty box: until you have forged something it shows the live community showcase, so there are real models to drop into the scene straight away. The avatar picker was asking the directory a question it does not answer and got back a feed of on-chain agents with no 3D model attached, so most slots were silently dropped and the rest never showed their thumbnails; it now asks for public 3D avatars and renders them. The start panel finally honours what it always promised: paste an avatar ID, not just a URL, and a model that cannot be loaded leaves a written explanation instead of a toast that vanishes before you can read it. Both the creations strip and the avatar picker now offer a Try again that works when a request fails. On the keyboard side: the page has a real heading, the camera-view menu and every creation and avatar tile are proper buttons, the scene rows expose their hide and remove actions on focus, the prompt and avatar fields have labels, dialogs trap focus and hand it back on Escape, and there is a visible focus ring throughout. Removing an object now frees its GPU memory once the step drops out of undo range, undo puts a bone-attached item back on its bone, and saving an outfit refuses a locally dropped file rather than storing a link that breaks on reload.",
"link": "/compose",
"tags": [
"fix",
@@ -339,7 +339,7 @@
"date": "2026-08-17",
"type": "update",
"title": "The Pole Club audio controls no longer fall off the edge of a small phone",
- "summary": "On a narrow phone the club's top bar ran out of room and simply cut off whatever did not fit, and the page cannot scroll sideways, so the mute button and the 8D audio toggle were gone with no way to reach them. The bar now gives up the parts that are only there to read (the tagline and the price and rail labels, all repeated in the panel's How it works section) and keeps both controls at full size at every width, down to a 320px screen.",
+ "summary": "On a narrow phone the club's top bar ran out of room and simply cut off whatever did not fit, and the page cannot scroll sideways, so the mute button and the 8D audio toggle were gone with no way to reach them. The bar now gives up the parts that are only there to read (the tagline and the price and rail labels, all of which the panel's How it works section repeats) and keeps both controls at full size at every width, down to a 320px screen.",
"link": "/club",
"tags": [
"fix"
diff --git a/public/features.json b/public/features.json
index 66e57b9de..a8a22e668 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T04:58:51.601Z",
+ "generated_at": "2026-08-17T05:04:16.973Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",