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(changelog): announce the Create page keyboard fix
nirholas2f26d19f3dbc
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 1aea5fd6a..c269085f7 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -25,6 +25,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Fact checks stop saying "not enough evidence" when the evidence was there**: A fact check reads five sources and asks a language model where each one stands on the claim. When that model answered in a shape the reader could not parse, every source was quietly recorded as saying nothing, the check reported "not enough evidence", and nothing anywhere said the reading had failed. A live check on whether a tomato is a vegetable came back that way while holding the Supreme Court case that settles the question. The reader now copes with the formats models actually use, including the thinking-out-loud preamble and code fences it used to choke on, and it no longer stops at the first square bracket it sees. When a reply genuinely cannot be read, the check now says it was degraded instead of presenting a verdict it did not earn, which also keeps that answer out of the week-long cache and out of the published accuracy score. The same fault had been collapsing the three search angles behind each check down to one. (`/fact-checker`) `[fix, improvement]`- **Fixed a footer link that led to a dead page**: The terminal page's footer offered an Avatars link that pointed at an address the site does not serve, so clicking it returned a 404 instead of the avatar gallery. It now opens the gallery, the same place every other page sends you. On the knock page, a placeholder link that sat empty until the profile finished loading was removed, so people navigating by keyboard or screen reader no longer land on a link with no name and nowhere to go. (`/tty`) `[fix]`- **Groundwork for agents that can run your house**: A three.ws agent already has a body, a voice and a memory, all of it stuck inside a browser tab. This is the first piece of letting it reach past the screen: a new developer package, @three-ws/home-bridge, that connects an agent to a real Home Assistant, the open-source home platform that already runs in millions of houses and already speaks to Zigbee, Z-Wave, Matter, Thread and about fifteen hundred other things. We wrote no device code at all, on purpose. What the package adds is the part nobody had built: live state from the house shaped into rooms, so a 3D scene can dim when your real lights dim; "good night" and "I'm leaving" resolved to the scenes you already made yourself, in Home Assistant, rather than to something we invented for you; and a safety gate that reads the way our on-chain one does. Turning a light off is free. Unlocking a door stops and asks you, every time, until you say otherwise for that one door. Locking up never asks, because moving your house toward safety should not need permission. That last part turned out to matter more than expected: Home Assistant's own "turn it off" command performs an unlock when you point it at a lock, so an assistant told to turn something off can open your front door with nothing in the command's name to warn anyone. Our gate catches it. All of it was built and checked against a real Home Assistant running here, not against stand-ins, and the write-up of what else is out there and where this goes next (voice in every room, the agent standing in a live model of your home) is published alongside it. (`/docs/smart-home`) `[sdk, docs, security]`+- **Keyboard users can move past the Create page hero card**: The recommended card on /create wrapped its rotating 3D preview inside the button itself, so the preview took a tab stop of its own and screen readers announced a control inside a control. The preview is now decorative, as it was always meant to be: the whole card is one target, and the model still wakes up and rotates when you hover or tab to it. (`/create`) `[fix]`- **License terms for three.ws containers on NVIDIA NGC**: three.ws is preparing to publish its image-to-3D inference server in NVIDIA's NGC catalog, so the licence that will cover those container images is now public. It states plainly what you get: Apache-2.0 source, no model weights inside the image (you bring your own, under the upstream licence), and a container that carries no analytics or telemetry and sends nothing back to us. It sits alongside the other policies on the legal page. (`/legal/nvidia-ngc-eula`) `[docs]`- **Limited editions: cap how many copies of your model can ever exist**: Any model you forged now has a Physical editions panel on its page where you set one number: how many physical copies of it may ever be printed. Leave it empty and it stays an open edition, which is what every model is by default. Set it and the number starts meaning something everywhere: the price panel tells a buyer which number they would be and how many are left, a sold-out edition is refused where the price is quoted rather than after someone has paid, and every certificate that ships reads "3 of 25" for good. It counts copies that actually shipped rather than orders people started, so an abandoned checkout never strands the last one, and it cannot be lowered below what has already left the building, because a certificate reading "edition 7 of 5" would be a lie already in somebody's hands. There is also now a page at /cert for looking a certificate up by the number printed on its card, and a certificate whose on-chain proof was delayed retries on its own until it lands. (`/materialize`) `[feature, improvement]`- **Materialize checkout: buy a real print, or let an agent buy one**: You can now order a physical print of a model and pay for it. Quote the job, pick a material and a size, and checkout hands you a payment in USDC on Solana with the itemised price you were shown, never a recomputed one. Once the payment lands the order moves into safety screening on its own, and every step writes to a timeline you can read at any time. The same checkout is open to AI agents at /api/x402/print-order: an agent quotes the job, pays, and a real object is manufactured and shipped to a street address, with no account anywhere in the loop. Prices come from one catalog file and nothing else, a quote is signed so it cannot be altered on the way to checkout, and an order that was never going to be accepted is refused before anyone is charged. (`/materialize`) `[feature, sdk]`diff --git a/data/changelog.json b/data/changelog.jsonindex 16174b62e..bb140c861 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,15 @@{"$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-09-02",+ "title": "Keyboard users can move past the Create page hero card",+ "summary": "The recommended card on /create wrapped its rotating 3D preview inside the button itself, so the preview took a tab stop of its own and screen readers announced a control inside a control. The preview is now decorative, as it was always meant to be: the whole card is one target, and the model still wakes up and rotates when you hover or tab to it.",+ "tags": [+ "fix"+ ],+ "link": "/create"+ },{"date": "2026-09-02","title": "Groundwork for agents that can run your house",diff --git a/public/changelog.json b/public/changelog.jsonindex 5ad141426..0b09f6645 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-02T21:35:59.568Z",+ "generated_at": "2026-09-02T21:37:37.970Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -207,6 +207,16 @@"security"]},+ {+ "date": "2026-09-02",+ "type": "update",+ "title": "Keyboard users can move past the Create page hero card",+ "summary": "The recommended card on /create wrapped its rotating 3D preview inside the button itself, so the preview took a tab stop of its own and screen readers announced a control inside a control. The preview is now decorative, as it was always meant to be: the whole card is one target, and the model still wakes up and rotates when you hover or tab to it.",+ "link": "/create",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-02","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 28e08eaad..026cbcffe 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -158,6 +158,14 @@<category>sdk</category><description>A three.ws agent already has a body, a voice and a memory, all of it stuck inside a browser tab. This is the first piece of letting it reach past the screen: a new developer package, @three-ws/home-bridge, that connects an agent to a real Home Assistant, the open-source home platform that already runs in millions of houses and already speaks to Zigbee, Z-Wave, Matter, Thread and about fifteen hundred other things. We wrote no device code at all, on purpose. What the package adds is the part nobody had built: live state from the house shaped into rooms, so a 3D scene can dim when your real lights dim; "good night" and "I'm leaving" resolved to the scenes you already made yourself, in Home Assistant, rather than to something we invented for you; and a safety gate that reads the way our on-chain one does. Turning a light off is free. Unlocking a door stops and asks you, every time, until you say otherwise for that one door. Locking up never asks, because moving your house toward safety should not need permission. That last part turned out to matter more than expected: Home Assistant's own "turn it off" command performs an unlock when you point it at a lock, so an assistant told to turn something off can open your front door with nothing in the command's name to warn anyone. Our gate catches it. All of it was built and checked against a real Home Assistant running here, not against stand-ins, and the write-up of what else is out there and where this goes next (voice in every room, the agent standing in a live model of your home) is published alongside it.</description></item>+ <item>+ <title>Keyboard users can move past the Create page hero card</title>+ <link>https://three.ws/create</link>+ <guid isPermaLink="false">2026-09-02:Keyboard users can move past the Create page hero card</guid>+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The recommended card on /create wrapped its rotating 3D preview inside the button itself, so the preview took a tab stop of its own and screen readers announced a control inside a control. The preview is now decorative, as it was always meant to be: the whole card is one target, and the model still wakes up and rotates when you hover or tab to it.</description>+ </item><item><title>License terms for three.ws containers on NVIDIA NGC</title><link>https://three.ws/legal/nvidia-ngc-eula</link>