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(agenc-embed): resolve the meshopt decoder without a usable script address

nirholasbbab195fe99c
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 09719125c..f9edb511d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,6 +13,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **My Creations: one button that takes you back to everything you made**: A creator told us the making part was intuitive and the finding part was not: they built an agent, closed the tab, and had no obvious way back to it. There is now a My creations button in the header, and it opens a single page holding everything you have made, newest first: your agents, the 3D avatars saved to your account, and every model you forged, with Open, Edit and Copy link on each one. Signed out it still finds the models forged in this browser, so work made before you had an account is not lost. Filter by type, search by name or prompt, and hover any card to spin it in 3D. The create wizard and the Forge now point here too, so you are told where your work lives at the moment you make it. (`/mine`) `[feature, improvement]`
- **Point an AI agent at the Blender on your own machine**: A new MCP server drives the Blender you already have installed, with no GUI open and no add-on to install first. An assistant can now read a 3D file and tell you what is actually in it (objects, triangle counts, materials, bones, animations, real-world size), convert between GLB, glTF, FBX, OBJ, STL, PLY, Collada, Alembic, USD and .blend in either direction, render a preview image of a bare asset file that arrives with no camera or lighting of its own, and run a Blender Python script to do the things no single tool covers, like halving a mesh's triangle count and exporting the result in one step. It also reaches back into three.ws: describe something in a sentence and the free text-to-3D lane generates it and opens it in Blender. Blender runs in the background, one process per request, so it works the same on a laptop, a server, or in CI. `[feature, sdk]`
- **Shared avatar and agent links now show a real page to Google, not a loading spinner**: Search engines were shown a different version of every /avatars/... and /agents/... page than people were, and that version had nothing on it: the name and description were hidden in a fallback block that a crawler removes before reading, the rest was a spinner, and the last line of the page sent the crawler straight back to the URL it was already on. Tens of thousands of avatar and agent pages therefore looked identical to Google and were filed as duplicates instead of being listed. Crawlers now get the same content a visitor sees: the name, the description, the rendered card, the creator, the tags, the skills, the on-chain identity, and links onward into the gallery and the directory. A link to an avatar or agent that no longer exists now says so honestly instead of quietly bouncing to a listing page, an id that belongs to the other side of the platform redirects to where it actually lives, and a private agent is no longer readable by anything sending a crawler's name. Signed-in surfaces were also unblocked in robots.txt so their existing no-index instruction can finally be read and obeyed. `[fix, infra]`
+- **The AgenC task embed now loads even when it is inlined or served from a blob**: The <three-ws-agent> element that shows a 3D avatar reacting to an on-chain AgenC task resolves its mesh decoder relative to its own script address. A copy that had been pasted inline, bundled, or loaded from a blob: or data: URL has no address to resolve against, and the element failed to register before it drew anything. It now falls back to the decoder on three.ws in that case and keeps the same-origin path everywhere else, so the embed works wherever the snippet ends up. (`/agenc/embodied`) `[fix]`
- **The Blender tools now show you the render instead of describing it**: Asking an assistant to render a 3D model used to hand back a file path, which is useless if the assistant cannot open files on your disk. The rendered image now comes back with the answer, scaled to fit, while the full-resolution PNG still lands on disk. That turns a look at this model into one step, so an assistant can render, spot the problem, fix it and render again. Reading a file also reports its texture budget now: every image with its resolution and byte size, plus the total, which is usually what actually decides whether a model is small enough to ship, and it was previously reported as nothing more than a count. Two reliability fixes came out of real use: several requests at once now queue instead of all starting Blender at the same moment and exhausting the machine, and when Blender is installed but momentarily will not start you get a message saying exactly that, with the details, rather than being told to install software you already have. `[improvement, feature]`
## 2026-09-05
diff --git a/data/changelog.json b/data/changelog.json
index da6c72427..d1040e141 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-07",
+ "title": "The AgenC task embed now loads even when it is inlined or served from a blob",
+ "summary": "The <three-ws-agent> element that shows a 3D avatar reacting to an on-chain AgenC task resolves its mesh decoder relative to its own script address. A copy that had been pasted inline, bundled, or loaded from a blob: or data: URL has no address to resolve against, and the element failed to register before it drew anything. It now falls back to the decoder on three.ws in that case and keeps the same-origin path everywhere else, so the embed works wherever the snippet ends up.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/agenc/embodied"
+ },
{
"date": "2026-09-07",
"title": "Shared avatar and agent links now show a real page to Google, not a loading spinner",
diff --git a/public/agenc/embed.js b/public/agenc/embed.js
index 8f024b7f5..f8ac940ae 100644
--- a/public/agenc/embed.js
+++ b/public/agenc/embed.js
@@ -40,7 +40,23 @@ const MODEL_VIEWER_CDN = 'https://cdn.jsdelivr.net/npm/@google/[email protected].
// Served from three.ws rather than a public CDN: the decoder is a hard
// dependency of every compressed avatar, so it must have the same availability
// as the embed script itself.
-const MESHOPT_DECODER_CDN = new URL('/vendor/meshopt_decoder.js', import.meta.url).href;
+function meshoptDecoderUrl() {
+ // On a normal site import.meta.url is this script's own http(s) address, so
+ // the decoder resolves same-origin. A copy that was inlined or loaded from a
+ // blob: or data: URL has no origin to resolve against (new URL throws
+ // "Invalid URL", and at module level that killed the whole embed before the
+ // element could register), so that copy reads the decoder from three.ws.
+ try {
+ const base = new URL(import.meta.url);
+ if (base.protocol === 'http:' || base.protocol === 'https:') {
+ return new URL('/vendor/meshopt_decoder.js', base).href;
+ }
+ } catch {
+ // no usable base URL; use the canonical origin below
+ }
+ return 'https://three.ws/vendor/meshopt_decoder.js';
+}
+const MESHOPT_DECODER_CDN = meshoptDecoderUrl();
// Register the EXT_meshopt_compression decoder with <model-viewer> before it
// begins loading. Server-baked avatars (the /api/avatars/<id>/glb lane and Forge
diff --git a/public/changelog.json b/public/changelog.json
index 64970f091..1e78fb517 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-07T05:42:31.482Z",
+ "generated_at": "2026-09-07T06:05:18.015Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -82,6 +82,16 @@
"infra"
]
},
+ {
+ "date": "2026-09-07",
+ "type": "update",
+ "title": "The AgenC task embed now loads even when it is inlined or served from a blob",
+ "summary": "The <three-ws-agent> element that shows a 3D avatar reacting to an on-chain AgenC task resolves its mesh decoder relative to its own script address. A copy that had been pasted inline, bundled, or loaded from a blob: or data: URL has no address to resolve against, and the element failed to register before it drew anything. It now falls back to the decoder on three.ws in that case and keeps the same-origin path everywhere else, so the embed works wherever the snippet ends up.",
+ "link": "/agenc/embodied",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-09-07",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 7d0f25934..832301451 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -62,6 +62,14 @@
<category>fix</category>
<description>Search engines were shown a different version of every /avatars/... and /agents/... page than people were, and that version had nothing on it: the name and description were hidden in a fallback block that a crawler removes before reading, the rest was a spinner, and the last line of the page sent the crawler straight back to the URL it was already on. Tens of thousands of avatar and agent pages therefore looked identical to Google and were filed as duplicates instead of being listed. Crawlers now get the same content a visitor sees: the name, the description, the rendered card, the creator, the tags, the skills, the on-chain identity, and links onward into the gallery and the directory. A link to an avatar or agent that no longer exists now says so honestly instead of quietly bouncing to a listing page, an id that belongs to the other side of the platform redirects to where it actually lives, and a private agent is no longer readable by anything sending a crawler's name. Signed-in surfaces were also unblocked in robots.txt so their existing no-index instruction can finally be read and obeyed.</description>
</item>
+ <item>
+ <title>The AgenC task embed now loads even when it is inlined or served from a blob</title>
+ <link>https://three.ws/agenc/embodied</link>
+ <guid isPermaLink="false">2026-09-07:The AgenC task embed now loads even when it is inlined or served from a blob</guid>
+ <pubDate>Mon, 07 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The &lt;three-ws-agent&gt; element that shows a 3D avatar reacting to an on-chain AgenC task resolves its mesh decoder relative to its own script address. A copy that had been pasted inline, bundled, or loaded from a blob: or data: URL has no address to resolve against, and the element failed to register before it drew anything. It now falls back to the decoder on three.ws in that case and keeps the same-origin path everywhere else, so the embed works wherever the snippet ends up.</description>
+ </item>
<item>
<title>The Blender tools now show you the render instead of describing it</title>
<link>https://three.ws/changelog</link>
diff --git a/public/features.json b/public/features.json
index 1228305d3..6957bdf1d 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-07T05:42:31.471Z",
+ "generated_at": "2026-09-07T06:05:18.005Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",