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): regenerate the public feeds with the motion-clip fix entry

nirholasfc68f9d3854e
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4ec43b015..2c673f075 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -45,6 +45,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The Coin Wars arena reconnects to its battle server, and a link with no battle now shows you where the wars are**: A full audit of /play/war, the arena where two coin communities fight to the kill cap. The page had lost the address of the multiplayer server it joins, so every player walking through a war portal landed on 'The arena server is unreachable' instead of a battlefield; the arena is wired back up. Beyond that, a link with no pairing (a shared URL, an expired ticket, a battle that already finished) used to be one sentence and a button back to the lobby, which told you nothing about where a war actually is. It is now the war room: the battles running right now with their live score and clock, the communities queued for an opponent, and the top of the Elo ladder, each one a link into that coin's world where its war portal stands. The same panel sits under every other dead end, so 'there is no battle here' always comes with 'here is where one is'. Also fixed: a failed holder check used to show an internal service error instead of telling you what to do, the Fire button announced itself as 'Firespace' to screen readers, pressing Space on the result card did nothing because the arena was eating the key, and the HUD's hover and focus animations were dead because the page never loaded the site's motion tokens. The arena now says it is playable with WASD, moves focus onto the way out when a card appears, and reads cleanly from 320px up. (`/play/war`) `[fix, improvement]`
- **The economy solver says which level its numbers belong to, and shares a link that lands on them**: The solver at /play/solver reprices the whole /play world when you move the skill level, and it fetches the new level as you move. If that fetch failed, the page dimmed its tables slightly and said nothing else: the chart marker sat at level 60 while every table below it still held level 1 figures, with no visible explanation, no way to tell which level you were reading, and no retry. The explanation existed but was written only into a region screen readers can reach, so anyone looking at the page saw a silent mismatch. A failed level now raises a banner in the open that names the level that failed, says plainly that the figures below are still the old level, and offers both a retry and a way back. A level still loading shows the same banner as a busy state with the level it is solving, so a slow connection reads as slow rather than as broken. The page also writes the level into its own address bar now: it has always read a level from a shared link, but never wrote one, so sending someone the URL after dragging to level 60 sent them level 1. And a link asking for a level past the cap settles on the cap instead of leaving the page waiting on a level that will never arrive. Alongside it, a conclusion in the model that shouted one word in capitals now reads as a normal sentence. (`/play/solver`) `[fix, improvement]`
- **The floorplan editor can make rooms, so a home with no areas is no longer a dead end**: Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list. (`/smart-home`) `[feature, improvement]`
+- **The generated motion clips were playing upside down, and we can now tell**: Every one of the 133 motion clips three.ws generates from a text prompt was being written down in the wrong reference frame. The bone names all matched the rest of the library, so nothing looked wrong in the data, but a clip's rotations are measured against a rig's resting pose and the generator was measuring against a different one. The result was a half turn missing from the legs: play one of these clips on an avatar and the feet fold up over the body. Forward kinematics put the feet at 1.71 m and the head at 1.45 m, where a hand-authored clip puts them at 0.15 m and 1.68 m. Clips can now be converted into the library's own frame, which puts all 133 back on their feet, and the quality check has learned to spot the fault: it was invisible before because every other rule measures a clip against itself, and a clip in the wrong frame is perfectly consistent with itself. A second fault went with it. Every generated clip was drifting forward at about a quarter of a metre a second whatever it was asked for, so a clip of someone applauding walked a metre across the room while it clapped, and standing-still idles drifted faster than the walks did. That turned out to be an artifact of how the motion model's output is scaled back into real units, and it is now measured and removed while the real motion, a pirouette's sway or a walk's per-step surge, is kept. Removing it also repaired the foot-sliding check, which had been dividing by a stride that was never real, so the library's quality bar finally means something: 39 of the 133 clips meet it, and the rest are being held back rather than served. (`/animations`) `[fix, improvement]`
- **The homepage stops calling its Community strip live when no new models are arriving**: The Community strip on the homepage is headed "Made with Forge. Right now." and carries a pulsing live chip. That chip was switched on by the Fresh tab alone, so it asserted liveness no matter how old the newest model on the strip actually was. When our object storage started rejecting the platform's credential on 2026-09-07, finished generations could no longer be recorded, the strip froze on the last model stored before that, and the chip went on pulsing live over two-day-old work with nothing on the page to say otherwise. The chip is now earned by the data: it appears only when the newest model on the strip is from the last six hours, and it reads the newest timestamp in the list rather than trusting the order it arrives in. Older models still show exactly as before, because a quiet stretch is worth showing; it just is not live. (`/`) `[fix]`
- **The in-game economy page reads correctly on a phone, and the boutique shows what you are buying**: A full audit of /play/economy, the published reference for every price, prize and gate in the /play world. On a 320px screen the general store and currency panels were wider than the viewport, and because the page suppresses sideways scrolling their right edge was simply cut off: the store's price column was unreachable on the narrowest phones. Those panels now shrink to fit, and the wide tables scroll inside their own labelled box instead. The bar showing how a paid $THREE sale splits used to print its labels inside the coloured segments, where "50% holder rewards" was truncated to "50% holder re..."; the split now reads from a legend beneath the bar, which stays legible at any ratio. In the boutique, the Stetson and the Shades rendered as blank grey circles while the five colour items showed their colour, because the page ignored the thumbnail the server was already sending; both now show the item, with the colour swatch as the fallback if an image ever goes missing. The wheel's top prize is relabelled "JACKPOT: 100 Cash", and a failed load now reads as a proper sentence before the retry hint. (`/play/economy`) `[fix, improvement]`
- **The Money Pulse now tells you when its stats are down, and retries on the spot**: When the money-intelligence call behind /pulse failed, the three side panels (Top earners, Busiest wallets, Fresh launches) sat on "Loading..." forever and the 7-day activity strip went blank, which reads as "the platform is quiet" rather than "we could not fetch this". Each surface now says what went wrong, notes that the live feed itself is unaffected and that it retries every minute, and offers a Retry button that refetches immediately. First paint uses skeletons shaped like the real counters, bars and rows instead of dashes and a loading label, so nothing shifts when the numbers land. The empty states point somewhere useful now: no tips yet links to the agent directory, no wallet activity links to the agents that are online. Switching between mainnet and devnet shows the skeletons again rather than leaving the previous network's numbers under the new label. The stat cards report their filter state to screen readers, the rail cards are real headings, and the per-row explorer link is a full-size tap target that says where it goes. (`/pulse`) `[fix, improvement]`
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index cfa849522..6af629017 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-09-09T15:28:55.673Z",
+ "generated_at": "2026-09-09T15:29:36.953Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3644,
+ "total": 3645,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -429,6 +429,17 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The generated motion clips were playing upside down, and we can now tell",
+ "summary": "Every one of the 133 motion clips three.ws generates from a text prompt was being written down in the wrong reference frame. The bone names all matched the rest of the library, so nothing looked wrong in the data, but a clip's rotations are measured against a rig's resting pose and the generator was measuring against a different one. The result was a half turn missing from the legs: play one of these clips on an avatar and the feet fold up over the body. Forward kinematics put the feet at 1.71 m and the head at 1.45 m, where a hand-authored clip puts them at 0.15 m and 1.68 m. Clips can now be converted into the library's own frame, which puts all 133 back on their feet, and the quality check has learned to spot the fault: it was invisible before because every other rule measures a clip against itself, and a clip in the wrong frame is perfectly consistent with itself. A second fault went with it. Every generated clip was drifting forward at about a quarter of a metre a second whatever it was asked for, so a clip of someone applauding walked a metre across the room while it clapped, and standing-still idles drifted faster than the walks did. That turned out to be an artifact of how the motion model's output is scaled back into real units, and it is now measured and removed while the real motion, a pirouette's sway or a walk's per-step surge, is kept. Removing it also repaired the foot-sliding check, which had been dividing by a stride that was never real, so the library's quality bar finally means something: 39 of the 133 clips meet it, and the rest are being held back rather than served.",
+ "link": "/animations",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
@@ -1601,16 +1612,6 @@
"tags": [
"launch"
]
- },
- {
- "date": "2026-09-04",
- "type": "launch",
- "title": "Trader Wrapped: your season on pump.fun",
- "summary": "The season recap for any verified pump.fun trading agent on three.ws: realized profit and loss, the trade that carried the season, the trade that hurt, the rhythm behind both, and where they finished against the field. Cut from closed on-chain round-trips with buy and sell signatures attached, so a losing season reads as a losing season. Swipeable, shareable, no account and no wallet.",
- "link": "/wrapped",
- "tags": [
- "launch"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 334539d29..c5cdf426e 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-09T15:28:55.541Z",
+ "generated_at": "2026-09-09T15:29:36.906Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -426,6 +426,17 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The generated motion clips were playing upside down, and we can now tell",
+ "summary": "Every one of the 133 motion clips three.ws generates from a text prompt was being written down in the wrong reference frame. The bone names all matched the rest of the library, so nothing looked wrong in the data, but a clip's rotations are measured against a rig's resting pose and the generator was measuring against a different one. The result was a half turn missing from the legs: play one of these clips on an avatar and the feet fold up over the body. Forward kinematics put the feet at 1.71 m and the head at 1.45 m, where a hand-authored clip puts them at 0.15 m and 1.68 m. Clips can now be converted into the library's own frame, which puts all 133 back on their feet, and the quality check has learned to spot the fault: it was invisible before because every other rule measures a clip against itself, and a clip in the wrong frame is perfectly consistent with itself. A second fault went with it. Every generated clip was drifting forward at about a quarter of a metre a second whatever it was asked for, so a clip of someone applauding walked a metre across the room while it clapped, and standing-still idles drifted faster than the walks did. That turned out to be an artifact of how the motion model's output is scaled back into real units, and it is now measured and removed while the real motion, a pirouette's sway or a walk's per-step surge, is kept. Removing it also repaired the foot-sliding check, which had been dividing by a stride that was never real, so the library's quality bar finally means something: 39 of the 133 clips meet it, and the rest are being held back rather than served.",
+ "link": "/animations",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 73f065602..14c453004 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -318,6 +318,14 @@
<category>feature</category>
<description>Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list.</description>
</item>
+ <item>
+ <title>The generated motion clips were playing upside down, and we can now tell</title>
+ <link>https://three.ws/animations</link>
+ <guid isPermaLink="false">2026-09-09:The generated motion clips were playing upside down, and we can now tell</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Every one of the 133 motion clips three.ws generates from a text prompt was being written down in the wrong reference frame. The bone names all matched the rest of the library, so nothing looked wrong in the data, but a clip's rotations are measured against a rig's resting pose and the generator was measuring against a different one. The result was a half turn missing from the legs: play one of these clips on an avatar and the feet fold up over the body. Forward kinematics put the feet at 1.71 m and the head at 1.45 m, where a hand-authored clip puts them at 0.15 m and 1.68 m. Clips can now be converted into the library's own frame, which puts all 133 back on their feet, and the quality check has learned to spot the fault: it was invisible before because every other rule measures a clip against itself, and a clip in the wrong frame is perfectly consistent with itself. A second fault went with it. Every generated clip was drifting forward at about a quarter of a metre a second whatever it was asked for, so a clip of someone applauding walked a metre across the room while it clapped, and standing-still idles drifted faster than the walks did. That turned out to be an artifact of how the motion model's output is scaled back into real units, and it is now measured and removed while the real motion, a pirouette's sway or a walk's per-step surge, is kept. Removing it also repaired the foot-sliding check, which had been dividing by a stride that was never real, so the library's quality bar finally means something: 39 of the 133 clips meet it, and the rest are being held back rather than served.</description>
+ </item>
<item>
<title>The homepage stops calling its Community strip live when no new models are arriving</title>
<link>https://three.ws/</link>