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): record the agent wall connection fix and the viewer drop message
nirholas7cd5f2529a99
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex becdf15a7..45987ddcd 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -43,7 +43,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The $THREE rider pass now recognises the wallets that paid for it**: The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message. `[fix]`- **The Agent Commerce demo is usable on a phone, and says what happened when a trade cannot finish**: The page where two agents pay each other on Solana had three problems. On a narrow screen the language picker in the bottom corner sat directly on top of the Run button, so the demo could not be started on a phone at all, and the agent name plates and speech bubbles were drawn underneath the payment card. The related-page links in the header were rendering at the size and colour of the site brand, which is what pushed the header off the edge of a 320 pixel screen. And when the live stream dropped part way through a trade, the page kept showing the payment step as if it were still running, left the last speech bubble frozen on screen, and explained itself only in a red message that disappeared after eight seconds. The layout now gives every control its own space at 320, 768 and 1440 pixels, the step that was running is marked as failed, and the middle of the screen carries a plain explanation with a button to run it again. Two more states were missing and are now designed: a skeleton card while the wallet balances are being read, and a retry when that check cannot reach the server at all. (`/agent-trade`) `[fix, improvement]`- **The agent showcase pages all the way through, and the strategy board ranks the whole marketplace**: Three fixes to public read surfaces. Paging the ERC-8004 agent showcase past the first page could repeat a row forever or quietly skip one, because the cursor rounded the registration timestamp to the millisecond while the index stores microseconds, and an agent whose registry event carried no timestamp at all fell out of every page after the first. Both are fixed, and asking for a fractional number of results now returns a page instead of a server error. The published strategy board's default 'performance' order was ranking only the most recently published slice, so a proven, high-return strategy could sit invisible behind newer unproven ones; it now ranks the whole published pool before trimming to your page. And /sitemap.xml no longer answers a POST or a DELETE with the sitemap. (`/showcase`) `[fix]`+- **The agent wallet is usable on a phone again, and visitors see a real balance**: On a narrow screen the wallet hub was quietly cut off. The column sized itself to the width of its tab strip rather than to the screen, and because the page cannot scroll sideways everything past the fold was simply unreachable: the Refresh button and the right edge of every card were invisible on a phone. The column now fits the screen and the section tabs scroll on their own, so every control is reachable at any width. Two things were also wrong for anyone looking at an agent wallet they do not own. The balance read as a dash even though an agent's balance is public on-chain data, and it now shows the real live figure. The recent-activity card claimed it had failed to load and offered a Retry that could never work, because the transaction feed is private to the wallet's owner; it now says exactly that and links to the block explorer, where the same transactions are public. Finally, the browser tab title sometimes flipped back to a generic label instead of naming the agent whose wallet you were looking at. (`/agent-wallet`) `[fix, improvement]`- **The agent wallet MCP server now quotes its own address when it asks an agent to pay**: Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz. (`/docs/mcp-agent`) `[fix]`+- **The AGI page no longer goes quiet when its 3D body cannot load**: The AGI page is built around a live 3D body that reacts to the market, and when that model could not be fetched the page said nothing at all. The loading line disappeared on a timer whether or not anything had arrived, so the centrepiece became a silent empty panel with no explanation and no way to try again, while the decision stream and track record beside it carried on as normal. A body that fails to load now falls back to the platform's own avatar, so there is still something on the stage reacting to the agent's mood. If that cannot be fetched either, the stage says so plainly, makes clear that the agent is still trading and that the decisions and track record below are live and unaffected, and offers a button to try embodying again. The loading line now stays up until the body genuinely arrives instead of vanishing early, and the stage no longer re-requests a model it already knows is unreachable every twenty seconds. The page's description shown in search results and link previews was also carrying an older wording than the page itself. (`/agi`) `[fix, improvement]`- **The Animation Gallery keeps its keyboard, its focus, and its promises about what will play**: The gallery of nearly 3,000 motion clips had a set of small breakages that added up. Roughly a third of the mocap catalogue has no picture made for it yet, and the page was asking the picture store for one anyway: every one of those requests came back empty, so a third of the cards spent a request to arrive at the same drawing they now show immediately. Opening a clip's details trapped nobody: pressing Tab walked out of the open window and into the page behind it, and closing the window dropped you back at the very top of the page instead of the card you came from. The playback controls were on show while a preview was still loading and stayed on show when it failed, so there were buttons that did nothing. Arrow keys jumped to the next clip even while you were dragging the speed slider, which moved the slider and changed the clip at the same time. Sharing a filtered view was misleading too: a link carrying the loops or one-shot filter applied it but left the buttons showing All, and a link with a filter the page does not recognise emptied the sort menu. All of it is fixed, along with the keyboard hint the window shows: Space really does play and pause now, from the moment the window opens. (`/animations`) `[fix, improvement]`- **The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again**: Three corrections found by reading the docs pages against the code they describe. The AWS page told you a three.ws subscription would bill usage onto your AWS invoice, draw down AWS credits, and count toward Enterprise Discount Program commitments. None of that is the plan: the Marketplace subscription is free, and usage is paid per call in USDC over x402, exactly as it is for any other caller, so there is nothing to reconcile on your AWS bill at all. The page now says that, and describes the free subscription, the single key that opens every x402 endpoint, and the absence of any trial clock. Separately, the GLB optimization command documented on the 3D asset pipeline page failed on every compressed avatar, which is most of them, because it loaded the glTF extensions without the matching decoders; it now decodes meshopt and Draco and leaves the output as plain glTF the way its own contract promises. The NVIDIA models page also listed the tool-capable fallback model under the wrong vendor prefix. (`/aws`) `[fix, docs]`- **The creations gallery now counts every creation a creator has made, and pages all the way to the end**: The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did. (`/creations`) `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex b374a415a..eb909c304 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$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-16",+ "title": "The agent wallet is usable on a phone again, and visitors see a real balance",+ "summary": "On a narrow screen the wallet hub was quietly cut off. The column sized itself to the width of its tab strip rather than to the screen, and because the page cannot scroll sideways everything past the fold was simply unreachable: the Refresh button and the right edge of every card were invisible on a phone. The column now fits the screen and the section tabs scroll on their own, so every control is reachable at any width. Two things were also wrong for anyone looking at an agent wallet they do not own. The balance read as a dash even though an agent's balance is public on-chain data, and it now shows the real live figure. The recent-activity card claimed it had failed to load and offered a Retry that could never work, because the transaction feed is private to the wallet's owner; it now says exactly that and links to the block explorer, where the same transactions are public. Finally, the browser tab title sometimes flipped back to a generic label instead of naming the agent whose wallet you were looking at.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/agent-wallet"+ },{"date": "2026-08-16","title": "The AGI page no longer goes quiet when its 3D body cannot load",diff --git a/public/changelog.json b/public/changelog.jsonindex d849a9da6..6c960687a 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:51:35.071Z",+ "generated_at": "2026-08-16T18:24:16.397Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -395,6 +395,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "The agent wallet is usable on a phone again, and visitors see a real balance",+ "summary": "On a narrow screen the wallet hub was quietly cut off. The column sized itself to the width of its tab strip rather than to the screen, and because the page cannot scroll sideways everything past the fold was simply unreachable: the Refresh button and the right edge of every card were invisible on a phone. The column now fits the screen and the section tabs scroll on their own, so every control is reachable at any width. Two things were also wrong for anyone looking at an agent wallet they do not own. The balance read as a dash even though an agent's balance is public on-chain data, and it now shows the real live figure. The recent-activity card claimed it had failed to load and offered a Retry that could never work, because the transaction feed is private to the wallet's owner; it now says exactly that and links to the block explorer, where the same transactions are public. Finally, the browser tab title sometimes flipped back to a generic label instead of naming the agent whose wallet you were looking at.",+ "link": "/agent-wallet",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",@@ -405,6 +416,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "The AGI page no longer goes quiet when its 3D body cannot load",+ "summary": "The AGI page is built around a live 3D body that reacts to the market, and when that model could not be fetched the page said nothing at all. The loading line disappeared on a timer whether or not anything had arrived, so the centrepiece became a silent empty panel with no explanation and no way to try again, while the decision stream and track record beside it carried on as normal. A body that fails to load now falls back to the platform's own avatar, so there is still something on the stage reacting to the agent's mood. If that cannot be fetched either, the stage says so plainly, makes clear that the agent is still trading and that the decisions and track record below are live and unaffected, and offers a button to try embodying again. The loading line now stays up until the body genuinely arrives instead of vanishing early, and the stage no longer re-requests a model it already knows is unreachable every twenty seconds. The page's description shown in search results and link previews was also carrying an older wording than the page itself.",+ "link": "/agi",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 5261725b9..db5fe04f8 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -302,6 +302,14 @@<category>fix</category><description>Three fixes to public read surfaces. Paging the ERC-8004 agent showcase past the first page could repeat a row forever or quietly skip one, because the cursor rounded the registration timestamp to the millisecond while the index stores microseconds, and an agent whose registry event carried no timestamp at all fell out of every page after the first. Both are fixed, and asking for a fractional number of results now returns a page instead of a server error. The published strategy board's default 'performance' order was ranking only the most recently published slice, so a proven, high-return strategy could sit invisible behind newer unproven ones; it now ranks the whole published pool before trimming to your page. And /sitemap.xml no longer answers a POST or a DELETE with the sitemap.</description></item>+ <item>+ <title>The agent wallet is usable on a phone again, and visitors see a real balance</title>+ <link>https://three.ws/agent-wallet</link>+ <guid isPermaLink="false">2026-08-16:The agent wallet is usable on a phone again, and visitors see a real balance</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>On a narrow screen the wallet hub was quietly cut off. The column sized itself to the width of its tab strip rather than to the screen, and because the page cannot scroll sideways everything past the fold was simply unreachable: the Refresh button and the right edge of every card were invisible on a phone. The column now fits the screen and the section tabs scroll on their own, so every control is reachable at any width. Two things were also wrong for anyone looking at an agent wallet they do not own. The balance read as a dash even though an agent's balance is public on-chain data, and it now shows the real live figure. The recent-activity card claimed it had failed to load and offered a Retry that could never work, because the transaction feed is private to the wallet's owner; it now says exactly that and links to the block explorer, where the same transactions are public. Finally, the browser tab title sometimes flipped back to a generic label instead of naming the agent whose wallet you were looking at.</description>+ </item><item><title>The agent wallet MCP server now quotes its own address when it asks an agent to pay</title><link>https://three.ws/docs/mcp-agent</link>@@ -310,6 +318,14 @@<category>fix</category><description>Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz.</description></item>+ <item>+ <title>The AGI page no longer goes quiet when its 3D body cannot load</title>+ <link>https://three.ws/agi</link>+ <guid isPermaLink="false">2026-08-16:The AGI page no longer goes quiet when its 3D body cannot load</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The AGI page is built around a live 3D body that reacts to the market, and when that model could not be fetched the page said nothing at all. The loading line disappeared on a timer whether or not anything had arrived, so the centrepiece became a silent empty panel with no explanation and no way to try again, while the decision stream and track record beside it carried on as normal. A body that fails to load now falls back to the platform's own avatar, so there is still something on the stage reacting to the agent's mood. If that cannot be fetched either, the stage says so plainly, makes clear that the agent is still trading and that the decisions and track record below are live and unaffected, and offers a button to try embodying again. The loading line now stays up until the body genuinely arrives instead of vanishing early, and the stage no longer re-requests a model it already knows is unreachable every twenty seconds. The page's description shown in search results and link previews was also carrying an older wording than the page itself.</description>+ </item><item><title>The Animation Gallery keeps its keyboard, its focus, and its promises about what will play</title><link>https://three.ws/animations</link>diff --git a/public/features.json b/public/features.jsonindex d420e3dc8..274df41d2 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:28:16.659Z",+ "generated_at": "2026-08-16T18:24:16.182Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",