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.

docs(changelog): announce the Describe it to 3D recovery and light-theme fixes

nirholasaeb2d5f6ec5b
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9de0edd08..e832621c6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -14,6 +14,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Creator Gallery cards stay put while you scroll, and the leaderboards show they are loading**: On /creations, the 3D preview on every gallery card and leaderboard row was accidentally accepting drag input, so a card could be flung out of frame and a swipe over one scrolled nothing on a phone instead of moving the feed. The previews now spin on their own and hand the drag back to the page. The trending and top-creator columns also render shimmer rows while they load instead of sitting blank, the browse tally no longer shows a stale number over a loading grid, and keyboard focus on the search field is now clearly outlined. (`/creations`) `[fix, improvement]`
- **Credits shows your $THREE discount tier, and no longer goes blank when it cannot load**: The Credits page had a hole where its error state should be: if the balance request failed, every panel disappeared and the page ended below the heading with nothing on it. There is now a designed card that says what happened, links to platform status, and retries in one click, and a dropped connection reads as a real sentence instead of the browser's "Failed to fetch". The page also finally states the thing it promises: a pill showing the $THREE tier you are actually charged at, with the discount you are getting or how much more $THREE reaches the next tier. On a 320px phone the whole layout used to be a hundred pixels wider than the screen with the right edge silently cut off, so nothing over there was reachable; the page now fits, and the history table scrolls inside its own box. Smaller fixes throughout: every button and field has a visible keyboard focus ring, the deposit address has a copy button, the $THREE unit price shows real decimals instead of rounding to $0.00, the amount field and the history controls stay translated when you switch asset or load another page, and the price list dropped the dashes from its labels. (`/credits`) `[fix, improvement]`
- **Crew HQ keeps its 3D room standing, and crew links now open where they point**: Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's "Failed to fetch". (`/crews`) `[fix, improvement]`
+- **Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme**: Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more. (`/create/prompt`) `[fix, improvement]`
- **Text-to-3D no longer hangs when the concept painter stalls**: Every text-to-3D generation starts by painting a concept image, and that step tried its image providers one after another with no overall time limit. When the first provider stalled, a request could sit for two and a half minutes before answering, and anything with a shorter patience (ChatGPT, agent clients) simply saw nothing. The painter now works to one shared budget: a slow provider hands off with real time left for the next one, and if the whole chain runs out you get a quick, honest retry-in-a-moment answer instead of a hang. Image-to-3D was never affected. (`/forge`) `[fix]`
- **The first-contribution guide now hands you real open work, and the docs sidebar can find it**: The 15-minute contributor guide walked through adding MikuMikuDance rig support as its example, but that support had already shipped, so anyone following it literally would have re-done merged work and been told a bone was unmapped when it was not. It now shows the MMD change as the finished reference, exactly as it landed with its tests, and points you at two rig conventions that are genuinely still open, each with the bones that fail today. The community, triage, and first-contribution pages also appear in the docs sidebar under Guides instead of being reachable only from the README, and the triage page now explains every label the repo actually uses. (`/docs/first-contribution`) `[docs, fix]`
- **The full $THREE thesis is now a single document**: A long-form research thesis on $THREE now lives in the docs: what three.ws is, every way the token is used (hold-to-access tiers, plan and pass discounts, marketplace and labor escrow, game cosmetics, gated embeds, deploy-fee waivers), how platform revenue is routed into buybacks, where the token trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself, each claim sourced to the code. (`/three-token`) `[docs]`
diff --git a/data/changelog.json b/data/changelog.json
index 18d6ad3f9..ae8637768 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,26 @@
{
"$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-25",
+ "title": "Dashboard Analytics fits a phone screen and its failure page can actually reload",
+ "summary": "On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare shell-level failure page showed a Reload button that did nothing when tapped, so it now reloads. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/dashboard/analytics"
+ },
+ {
+ "date": "2026-08-25",
+ "title": "Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme",
+ "summary": "Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/create/prompt"
+ },
{
"date": "2026-08-25",
"title": "Credits shows your $THREE discount tier, and no longer goes blank when it cannot load",
diff --git a/prompts/swarm-100/route-create-prompt.md b/prompts/swarm-100/route-create-prompt.md
deleted file mode 100644
index 76be16679..000000000
--- a/prompts/swarm-100/route-create-prompt.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Route audit: /create/prompt (Describe it to 3D)
-
-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/prompt')console.log(JSON.stringify(g,null,2))"
-
-2. Find the serving implementation: grep "/create/prompt" 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/prompt
-
-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/prompt ("Describe it to 3D", section "build").
-Declared purpose: Type a description. About a minute later: a rigged 3D avatar you can animate and download.
-
-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/prompt. 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/prompt: 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-prompt.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 1201e50c0..ce665a4a5 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-25T16:50:49.964Z",
+ "generated_at": "2026-08-25T17:06:41.379Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -90,6 +90,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-25",
+ "type": "update",
+ "title": "Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme",
+ "summary": "Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more.",
+ "link": "/create/prompt",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-25",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 4bfcb0b3b..9e951061d 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -70,6 +70,14 @@
<category>fix</category>
<description>Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's &quot;Failed to fetch&quot;.</description>
</item>
+ <item>
+ <title>Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme</title>
+ <link>https://three.ws/create/prompt</link>
+ <guid isPermaLink="false">2026-08-25:Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme</guid>
+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more.</description>
+ </item>
<item>
<title>Text-to-3D no longer hangs when the concept painter stalls</title>
<link>https://three.ws/forge</link>
diff --git a/public/features.json b/public/features.json
index 2d57769e2..5cfa734a1 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-25T16:50:06.533Z",
+ "generated_at": "2026-08-25T17:06:41.173Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",