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 Alpha Co-pilot launch counter, stale stage and avatar fixes
nirholascbbcb4dd255b
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 11dc88c09..e8f2dec24 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -13,10 +13,13 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Agent attestations that stopped indexing now recover on their own**: An agent's on-chain attestation history is indexed by walking Solana signatures newer than the last one we recorded. If that recorded signature aged out of the RPC node's history, the walk failed outright and kept failing: the same dead signature was replayed on every run, so that agent's attestations silently stopped appearing on its profile while the scheduled job still reported success. The crawler now recognises that case, re-scans from the most recent signatures instead, and clears the stale marker, so an agent that fell behind catches up by itself on the next pass. `[fix, infra]`- **Agent share cards survive an unconfigured bucket, and a mistyped payment mint is refused instead of listed**: An audit of the agent endpoints turned up four things worth fixing. A skill price set through /api/agents/:id/skills/set-price accepted any text as its payment mint and saved it, so a typo produced a listing nobody could actually pay; it now has to be a real base58 address, matching the other door onto the same table. The agent share page and its OG image used to answer a social crawler with a hard error whenever object storage was not configured, instead of falling back to the plain card they already knew how to draw. A mistyped agent id in the diary, skill-price and screen-push endpoints came back as a server error rather than the plain "that is not an agent id" it is. And an agent screen with no live frame store now tells you the agent is offline right away instead of leaving you on "Connecting" for five minutes. `[fix, improvement]`- **Agent Studio shows your real avatar again, and a shared studio link stops opening the wrong agent**: Four repairs to the Agent Studio. The live stage on the left is meant to be your agent's actual body, but the 3D renderer was leaking its internal debug controls into that panel, including a stray rainbow colour strip painted over the avatar. Those controls are hidden now, everywhere the live agent appears. Second, opening a studio link that names someone else's agent used to quietly load your own agent instead and put it in a full editor under the other agent's address, so any edit went to the wrong record; it now loads the agent the link names and, when it is not yours, says so and offers its public profile. Third, on a phone the five section tabs ran off the edge of the screen, leaving Money and Skills unreachable behind a hidden scrollbar; all five now fit. Finally the status pill on the stage moved to the top so it stops sitting on top of your agent's name, and the walking companion no longer doubles up in the corner on a page that already shows your agent life-size. (`/agent-studio`) `[fix]`+- **Alpha Co-pilot counts its live launches again, and a mistyped agent ID no longer leaves the last one on stage**: Four things were wrong on the page where your agent reads a launch out loud. The badge next to Live launches, which tells you how many launches are waiting, was always blank: the counter was written inside the heading text, and translating the heading replaced the very element the page updates, so the number was thrown away every time. It now sits beside the heading and survives a switch into any of the 85 languages. Loading an agent that does not exist used to leave the previous agent standing on stage with its launch cards still on screen, and every Ask for a read button on those cards did nothing at all when clicked; the stage is now cleared back to its starting state with a prompt to pick another co-pilot. The buy button in the confirm drawer showed the amount with its unit twice over. And on a local or preview copy of the site the avatar's 3D body failed to load at all, because this page was the only one that did not route model files through the same asset path every other page uses. (`/alpha-copilot`) `[fix]`- **An expired X connection now offers to reconnect instead of sending you to the login page**: Posting a Walk screenshot or clip to X goes through your connected X account. When that connection could no longer be renewed, the share endpoint answered with the same code it uses for a signed-out visitor, so the capture panel told an already signed-in user to sign in to three.ws and linked them to the login page, which fixed nothing. That case now comes back as its own answer with the X connect link attached, and the panel offers a Reconnect X button that takes you straight to the flow that repairs it. The share caption also lost a stray dash. (`/walk`) `[fix]`- **An unsubscribe now sticks, even if you click an old confirm link**: Every three.ws newsletter email carries a confirm link and an unsubscribe link that share one token, so a reader who unsubscribed and later opened an older email and clicked confirm was quietly put back on the list. That link no longer signs anyone up: it says you are unsubscribed and leaves it that way, and opting back in starts from the site. Three other fixes ship alongside it. The allocation planner at /meta-allocator no longer serves an empty basket when the model declines to answer, it falls back to the allocator that always produces a real spread across verified leaders. The motion capture uploader told you an upload link lasted ten minutes when it really lasted five, so a large video queued on that promise could fail with nothing explaining why. And an agent whose stablecoin payment is rejected by the x402 Bazaar now gets the Bazaar's own details back instead of a different server's, so its retry is aimed at the right place. (`/changelog`) `[fix]`- **Avatar link previews stop rebuilding themselves, and two feeds answer a bad page link plainly**: An audit of the chat, media and board endpoints found three real breaks. When you share an avatar link, the preview image is drawn once and then kept, so every later share is instant. A mix-up between the stored image and its address meant every freshly drawn preview was mistaken for an old broken one: the saved copy was thrown away and the picture was redrawn from scratch on every single share. The preview is now kept, as it always should have been, and genuinely broken old records are repaired the next time they are drawn. Separately, the character directory answered a hand-edited or stale "next page" link with a server error instead of saying the value was not a timestamp, and the bounty board did the same when the page size in the address was not a number. Both now answer plainly, and the board simply falls back to its normal page size. (`/characters`) `[fix]`- **Avatar Studio trait library: the mirror can no longer be pointed at someone else's server**: Avatar Studio loads its hair, clothing and accessory traits through a three.ws address that mirrors the open-source trait library, so your browser never talks to an outside CDN. The list of where those traits live was being written using the address in the incoming request, and that address can be set by whoever sends the request. Because the mirror is cached at the edge for a day, one crafted request could have left every Avatar Studio visitor loading trait files from a stranger's server for the next 24 hours. That list is now written the same way for everybody, with no part of it taken from the request, so there is nothing left to steer. Three smaller repairs went in alongside it: asking the mirror how big a file is no longer answers with the compressed size (a trait manifest claimed 2 KB and delivered 20 KB), the mirror will not hand back a web page or script even if the upstream library ever served one, and a failure at the library now answers plainly as either not found or mirror is down instead of passing its raw status through as ours. (`/avatar-studio`) `[security, fix]`+- **Avatars no longer lose their preview picture forever because a server had a bad minute**: Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue. (`/gallery`) `[fix]`+- **Community-voted models reach our Sketchfab showcase with a real name**: Models made from a picture rather than a written description carry no prompt to name them by, so they were labelled with the internal route name instead. Models the community voted for skip the usual title checks on purpose, since a winning model should never be dropped over its title, which meant a winner made from a picture was one run away from being published to the official three.ws Sketchfab account under the name Image-To-3d. It was, in fact, the second model queued to go out. Those models are now named from their category, or given a plain generic name when the category says nothing useful. (`/forge`) `[fix]`- **Corrected stale numbers across the avatar and animation docs**: An audit of eight documentation pages against the code they describe turned up four claims that had drifted. The Animations page said the motion-capture library held about 2,000 clips when it actually serves 2,874, so both the intro and the gallery section now quote the real size and point at the count the API itself returns. The selfie-to-avatar page listed the wrong default for the face-morph displacement clamp and credited a single tuning sweep instead of the two that chose it. The avatar-creation walkthrough still told people to pick a body type on the selfie flow, a control that was deliberately removed because it changed nothing, and named the wrong fields on the event the page dispatches. The architecture page now says plainly that the whitelist trust mode is reserved rather than enforced. (`/docs/animations`) `[docs]`- **Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly**: Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them. `[fix, improvement]`- **External Solana agents get their names and artwork back in the directory**: Every agent the platform indexes from the Metaplex Agent Registry had been sitting in the directory as a bare address since August 6: no name, no picture, no 3D model. The crawler asks a Solana node for each agent's artwork through a method only some nodes support, and it was asking the same node every time, one that does not support it. Worse, the node that does support it answers a refusal in the same shape when it is simply busy, so the crawler could not tell 'I cannot do this' from 'not right now'. It now tries each node in turn, keeps the one that answers, waits and retries a busy one instead of writing it off, and refreshes the agents that are missing artwork rather than the same handful at the top of the list every half hour. If no node will serve the artwork at all, the crawl now says so out loud instead of quietly marking every agent as failed. (`/agents`) `[fix, infra]`@@ -36,8 +39,10 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The $THREE economy dashboard no longer errors out on an odd date range**: Asking the public $THREE economy stats endpoint for a window it could not read (a non-numeric range, or one longer than ten years) returned a server error instead of an answer. It now replies with a clear message for a range it cannot parse, caps an oversized one at ten years of history, and treats a blank range as all-time again. The creator earnings ledger does the same for a bad page cursor. `[fix]`- **The $THREE price quote survives an out-of-range dollar amount, and the payment audit log is admin-only for real**: The public $THREE price endpoint converts a dollar amount into a token amount. Because $THREE trades well under a cent, a dollar figure large enough to overflow what a number can hold turned that conversion into a server error, and every such request also filed a false internal alert. It now answers plainly that the amount is out of range. The token amount it quotes is also computed from the exact price printed beside it, so the two can no longer disagree when the live price refreshes partway through a request. Separately, the settled-payment audit log checked admin wallets with its own copy of the rule, comparing Solana addresses without regard to capitalisation. Solana addresses are case-sensitive, so a lookalike address that differed only in capitalisation would have been accepted; the log now uses the platform-wide admin check, which compares Solana addresses exactly and also recognises an admin who signed in with a linked wallet. `[fix, security]`- **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 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 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]`- **The Forge community board remembers what you liked**: The community showcase on /forge, and the same feed on the daily page and the model explorer, kept showing your own likes as un-liked. The board is held at the edge for a minute so it loads instantly for everyone, but the copy being held was the one built for a visitor who is not you, and it was handed to you as well. Your like button then started from the wrong state, and pressing it again fought with what the server already knew. The board now keeps a separate copy for a signed browser, so the hearts you filled in stay filled. Alongside it, a security fix on the Game-Ready export: when the export was paid for with $THREE rather than covered by holding, a badly formed payment reference made the server answer with the raw internals of its own database instead of a plain "that payment could not be verified". It now says only what a caller needs, and a database problem is no longer reported as a bad payment, so nobody is told to pay twice for an outage on our side. (`/forge`) `[fix, security]`diff --git a/data/changelog.json b/data/changelog.jsonindex 0be8d4619..ac6b588c3 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,62 @@{"$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": "Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed",+ "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.",+ "tags": [+ "fix"+ ],+ "link": "/credits"+ },+ {+ "date": "2026-08-16",+ "title": "Alpha Co-pilot counts its live launches again, and a mistyped agent ID no longer leaves the last one on stage",+ "summary": "Four things were wrong on the page where your agent reads a launch out loud. The badge next to Live launches, which tells you how many launches are waiting, was always blank: the counter was written inside the heading text, and translating the heading replaced the very element the page updates, so the number was thrown away every time. It now sits beside the heading and survives a switch into any of the 85 languages. Loading an agent that does not exist used to leave the previous agent standing on stage with its launch cards still on screen, and every Ask for a read button on those cards did nothing at all when clicked; the stage is now cleared back to its starting state with a prompt to pick another co-pilot. The buy button in the confirm drawer showed the amount with its unit twice over. And on a local or preview copy of the site the avatar's 3D body failed to load at all, because this page was the only one that did not route model files through the same asset path every other page uses.",+ "tags": [+ "fix"+ ],+ "link": "/alpha-copilot"+ },+ {+ "date": "2026-08-16",+ "title": "The Animation Gallery keeps its keyboard, its focus, and its promises about what will play",+ "summary": "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.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/animations"+ },+ {+ "date": "2026-08-16",+ "title": "The Agent Commerce demo is usable on a phone, and says what happened when a trade cannot finish",+ "summary": "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.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/agent-trade"+ },+ {+ "date": "2026-08-16",+ "title": "Avatars no longer lose their preview picture forever because a server had a bad minute",+ "summary": "Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue.",+ "tags": [+ "fix"+ ],+ "link": "/gallery"+ },+ {+ "date": "2026-08-16",+ "title": "Community-voted models reach our Sketchfab showcase with a real name",+ "summary": "Models made from a picture rather than a written description carry no prompt to name them by, so they were labelled with the internal route name instead. Models the community voted for skip the usual title checks on purpose, since a winning model should never be dropped over its title, which meant a winner made from a picture was one run away from being published to the official three.ws Sketchfab account under the name Image-To-3d. It was, in fact, the second model queued to go out. Those models are now named from their category, or given a plain generic name when the category says nothing useful.",+ "tags": [+ "fix"+ ],+ "link": "/forge"+ },{"date": "2026-08-16","title": "Agent Studio shows your real avatar again, and a shared studio link stops opening the wrong agent",diff --git a/public/changelog.json b/public/changelog.jsonindex 263654ca1..d5f11ee69 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:20:56.851Z",+ "generated_at": "2026-08-16T17:27:32.868Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -81,6 +81,16 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "Alpha Co-pilot counts its live launches again, and a mistyped agent ID no longer leaves the last one on stage",+ "summary": "Four things were wrong on the page where your agent reads a launch out loud. The badge next to Live launches, which tells you how many launches are waiting, was always blank: the counter was written inside the heading text, and translating the heading replaced the very element the page updates, so the number was thrown away every time. It now sits beside the heading and survives a switch into any of the 85 languages. Loading an agent that does not exist used to leave the previous agent standing on stage with its launch cards still on screen, and every Ask for a read button on those cards did nothing at all when clicked; the stage is now cleared back to its starting state with a prompt to pick another co-pilot. The buy button in the confirm drawer showed the amount with its unit twice over. And on a local or preview copy of the site the avatar's 3D body failed to load at all, because this page was the only one that did not route model files through the same asset path every other page uses.",+ "link": "/alpha-copilot",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-16","type": "update",@@ -122,6 +132,26 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "Avatars no longer lose their preview picture forever because a server had a bad minute",+ "summary": "Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue.",+ "link": "/gallery",+ "tags": [+ "fix"+ ]+ },+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "Community-voted models reach our Sketchfab showcase with a real name",+ "summary": "Models made from a picture rather than a written description carry no prompt to name them by, so they were labelled with the internal route name instead. Models the community voted for skip the usual title checks on purpose, since a winning model should never be dropped over its title, which meant a winner made from a picture was one run away from being published to the official three.ws Sketchfab account under the name Image-To-3d. It was, in fact, the second model queued to go out. Those models are now named from their category, or given a plain generic name when the category says nothing useful.",+ "link": "/forge",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-16","type": "update",@@ -323,6 +353,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "The Agent Commerce demo is usable on a phone, and says what happened when a trade cannot finish",+ "summary": "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.",+ "link": "/agent-trade",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",@@ -343,6 +384,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "The Animation Gallery keeps its keyboard, its focus, and its promises about what will play",+ "summary": "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.",+ "link": "/animations",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex a8e0ecd3b..9192a685a 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -62,6 +62,14 @@<category>fix</category><description>Four repairs to the Agent Studio. The live stage on the left is meant to be your agent's actual body, but the 3D renderer was leaking its internal debug controls into that panel, including a stray rainbow colour strip painted over the avatar. Those controls are hidden now, everywhere the live agent appears. Second, opening a studio link that names someone else's agent used to quietly load your own agent instead and put it in a full editor under the other agent's address, so any edit went to the wrong record; it now loads the agent the link names and, when it is not yours, says so and offers its public profile. Third, on a phone the five section tabs ran off the edge of the screen, leaving Money and Skills unreachable behind a hidden scrollbar; all five now fit. Finally the status pill on the stage moved to the top so it stops sitting on top of your agent's name, and the walking companion no longer doubles up in the corner on a page that already shows your agent life-size.</description></item>+ <item>+ <title>Alpha Co-pilot counts its live launches again, and a mistyped agent ID no longer leaves the last one on stage</title>+ <link>https://three.ws/alpha-copilot</link>+ <guid isPermaLink="false">2026-08-16:Alpha Co-pilot counts its live launches again, and a mistyped agent ID no longer leaves the last one on stage</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Four things were wrong on the page where your agent reads a launch out loud. The badge next to Live launches, which tells you how many launches are waiting, was always blank: the counter was written inside the heading text, and translating the heading replaced the very element the page updates, so the number was thrown away every time. It now sits beside the heading and survives a switch into any of the 85 languages. Loading an agent that does not exist used to leave the previous agent standing on stage with its launch cards still on screen, and every Ask for a read button on those cards did nothing at all when clicked; the stage is now cleared back to its starting state with a prompt to pick another co-pilot. The buy button in the confirm drawer showed the amount with its unit twice over. And on a local or preview copy of the site the avatar's 3D body failed to load at all, because this page was the only one that did not route model files through the same asset path every other page uses.</description>+ </item><item><title>An expired X connection now offers to reconnect instead of sending you to the login page</title><link>https://three.ws/walk</link>@@ -94,6 +102,22 @@<category>security</category><description>Avatar Studio loads its hair, clothing and accessory traits through a three.ws address that mirrors the open-source trait library, so your browser never talks to an outside CDN. The list of where those traits live was being written using the address in the incoming request, and that address can be set by whoever sends the request. Because the mirror is cached at the edge for a day, one crafted request could have left every Avatar Studio visitor loading trait files from a stranger's server for the next 24 hours. That list is now written the same way for everybody, with no part of it taken from the request, so there is nothing left to steer. Three smaller repairs went in alongside it: asking the mirror how big a file is no longer answers with the compressed size (a trait manifest claimed 2 KB and delivered 20 KB), the mirror will not hand back a web page or script even if the upstream library ever served one, and a failure at the library now answers plainly as either not found or mirror is down instead of passing its raw status through as ours.</description></item>+ <item>+ <title>Avatars no longer lose their preview picture forever because a server had a bad minute</title>+ <link>https://three.ws/gallery</link>+ <guid isPermaLink="false">2026-08-16:Avatars no longer lose their preview picture forever because a server had a bad minute</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue.</description>+ </item>+ <item>+ <title>Community-voted models reach our Sketchfab showcase with a real name</title>+ <link>https://three.ws/forge</link>+ <guid isPermaLink="false">2026-08-16:Community-voted models reach our Sketchfab showcase with a real name</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Models made from a picture rather than a written description carry no prompt to name them by, so they were labelled with the internal route name instead. Models the community voted for skip the usual title checks on purpose, since a winning model should never be dropped over its title, which meant a winner made from a picture was one run away from being published to the official three.ws Sketchfab account under the name Image-To-3d. It was, in fact, the second model queued to go out. Those models are now named from their category, or given a plain generic name when the category says nothing useful.</description>+ </item><item><title>Corrected stale numbers across the avatar and animation docs</title><link>https://three.ws/docs/animations</link>@@ -246,6 +270,14 @@<category>fix</category><description>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.</description></item>+ <item>+ <title>The Agent Commerce demo is usable on a phone, and says what happened when a trade cannot finish</title>+ <link>https://three.ws/agent-trade</link>+ <guid isPermaLink="false">2026-08-16:The Agent Commerce demo is usable on a phone, and says what happened when a trade cannot finish</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item><item><title>The agent showcase pages all the way through, and the strategy board ranks the whole marketplace</title><link>https://three.ws/showcase</link>@@ -262,6 +294,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 Animation Gallery keeps its keyboard, its focus, and its promises about what will play</title>+ <link>https://three.ws/animations</link>+ <guid isPermaLink="false">2026-08-16:The Animation Gallery keeps its keyboard, its focus, and its promises about what will play</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item><item><title>The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again</title><link>https://three.ws/aws</link>diff --git a/public/features.json b/public/features.jsonindex 9de6c83af..4b3d3c1b4 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T17:20:56.730Z",+ "generated_at": "2026-08-16T17:27:32.742Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",