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): point the embed crash entry at a page that exists, and publish it

nirholas37375a182248
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 94305fac1..6ef149cec 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,6 +12,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Fade Radar: the wallets that are never right** (`/fade`): The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.
- **A link that opens your house in 3D now really opens it in 3D**: The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself. (`/docs/home-scene`) `[fix]`
- **An app key can no longer say yes to unlocking your door**: A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the "the owner already approved this" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with "a person has to approve this", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens. (`/smart-home`) `[security, fix]`
+- **An embedded avatar no longer crashes the page it was removed from**: Sites embed three.ws avatars with the <agent-3d> tag, and a single-page app can swap the whole page out while an avatar is still loading. When that happened the avatar was left holding a piece of the page that no longer existed, and its own tidy-up threw an error into the host site console instead of quietly reporting that loading had stopped. The avatar had already handled the failure correctly; the report of it was what broke. Embedders now get the agent:error event they listen for, and nothing else, whether or not the page moved on while the avatar was still loading. (`/docs/web-component`) `[fix, sdk]`
- **Arm your agent stops telling signed-out visitors to create an agent, and shows them the live conviction stream instead**: A full audit of /oracle/arm found that anyone not signed in was shown “Create a 3D agent to arm it”, a dead end for a visitor with no account, and the rest of the page was hidden behind it. Signing in now gets its own state with sign-in and register buttons, and the live “clearing your bar” preview plus the 30-day win-rate readout stay on screen for everyone, because both run on public data. If the agents list itself fails to load, the page now says so with the status it got back and a Try again button, instead of pretending the account is empty. Four more fixes went with it: the arm switch and the two rule toggles can now be operated from the keyboard (they were focusable but did nothing on Enter or Space), coin artwork routes through the site image proxy so icons stop failing on IPFS gateways, the status line no longer flips back to “Disarmed” when the translation catalog lands after the page has rendered, and every form field now has a real label attached to it. (`/oracle/arm`) `[fix, improvement]`
- **Avatars and token art load again on sites that embed three.ws**: Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists. `[fix]`
- **Connecting a home: the page now says which state it is in, out loud**: Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted. (`/smart-home`) `[improvement, fix]`
diff --git a/data/changelog.json b/data/changelog.json
index 597e4b38b..9e8c4f23e 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -27966,7 +27966,7 @@
"fix",
"sdk"
],
- "link": "/docs/embed"
+ "link": "/docs/web-component"
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 5f0bba700..84deae722 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-09T19:55:21.363Z",
+ "generated_at": "2026-09-09T19:56:43.235Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -67,6 +67,17 @@
"fix"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "An embedded avatar no longer crashes the page it was removed from",
+ "summary": "Sites embed three.ws avatars with the <agent-3d> tag, and a single-page app can swap the whole page out while an avatar is still loading. When that happened the avatar was left holding a piece of the page that no longer existed, and its own tidy-up threw an error into the host site console instead of quietly reporting that loading had stopped. The avatar had already handled the failure correctly; the report of it was what broke. Embedders now get the agent:error event they listen for, and nothing else, whether or not the page moved on while the avatar was still loading.",
+ "link": "/docs/web-component",
+ "tags": [
+ "fix",
+ "sdk"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 1ec7ee0a4..704c7ce08 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -54,6 +54,14 @@
<category>security</category>
<description>A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the &quot;the owner already approved this&quot; flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with &quot;a person has to approve this&quot;, exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens.</description>
</item>
+ <item>
+ <title>An embedded avatar no longer crashes the page it was removed from</title>
+ <link>https://three.ws/docs/web-component</link>
+ <guid isPermaLink="false">2026-09-09:An embedded avatar no longer crashes the page it was removed from</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Sites embed three.ws avatars with the &lt;agent-3d&gt; tag, and a single-page app can swap the whole page out while an avatar is still loading. When that happened the avatar was left holding a piece of the page that no longer existed, and its own tidy-up threw an error into the host site console instead of quietly reporting that loading had stopped. The avatar had already handled the failure correctly; the report of it was what broke. Embedders now get the agent:error event they listen for, and nothing else, whether or not the page moved on while the avatar was still loading.</description>
+ </item>
<item>
<title>Arm your agent stops telling signed-out visitors to create an agent, and shows them the live conviction stream instead</title>
<link>https://three.ws/oracle/arm</link>