Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(changelog): announce the tutorial figures and the vitals route, and release three entries stranded in the worktree
nirholas798c0f692fc6
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 37a808218..ba68265ee 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -8,16 +8,23 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **A GPU waking up now says so, instead of looking like a stuck progress bar**: Some of our 3D engines release their graphics card when nobody is using them, so the first request of a quiet spell has to boot one back up before any sculpting starts. That wait is normal and it ends, but several surfaces showed nothing but a spinning step while it happened, which reads as a hang. Now every place you can watch a model being built names it: the homepage forge, the Studio, the in-world item forge on /play, and the tools other apps drive us through all say a GPU is waking, how much of the boot is left, and that your job is already accepted and starts the second the worker answers. Every number comes from the generator itself, so nothing is a guessed timer. Two related fixes came out of it: the elapsed counter on /forge now reports how long your job has really been running rather than how long the tab has been open, so reopening the page mid-build no longer restarts the clock at zero; and the countdown now uses each engine's real boot budget instead of an estimate. The keep-warm schedule that holds those engines open during busy hours was also missing our highest-quality lane, which has the longest boot of the fleet. (`/forge`) `[improvement, fix]`- **Agent Galaxy no longer strands you when the star map cannot be built**: When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link. (`/galaxy`) `[fix, improvement]`+- **Agent Launches: the Tip button on every launch card actually works now**: Each card on the launches feed carries the launching agent's wallet, and the whole-card link to the coin profile was sitting on top of it: every tap on Tip, and every attempt to preview the wallet, opened the coin page instead. The wallet now sits above that link, so tipping and the wallet preview both work, on the feed and everywhere else the wallet badge appears. Keyboard and screen-reader use got the same pass: the Mainnet/Devnet switch responds to the arrow keys and says which feed it controls, the graduation bars announce which coin they belong to and how far along it is, the wallet's trust score and balance no longer read as unlabelled boxes while they load, and a page that found nothing on devnet now offers a button back to mainnet instead of only telling you to switch. (`/launches`) `[fix, improvement]`- **Avatars keep their real skin, eyes and hair, and we can prove it on a phone**: Every avatar the platform loads gets its skin, eyes, hair and teeth re-shaded with real-world material values the moment it appears: skin at the roughness bare skin actually has with a warm scattering layer, a wet cornea that catches a highlight, and hair that reads as strands rather than a helmet. That pass was already running, but the check meant to prove it was pointed at the wrong page and had been quietly reporting nothing at all, so it could not have caught the day it broke. It now runs against the same embed page your visitors see, at phone, tablet and desktop widths, and records exactly which materials it upgraded and to what values. Alongside it, a new check loads a full 4K-textured model on an emulated iPhone and Android phone over a slow mobile connection and measures the real bytes and load time, so a model that would not open on a phone is caught before it ships rather than after. `[improvement, infra]`- **Buttons that looked dead now respond, and the whole site paints from one palette**: A consistency pass across the platform. Fifty controls set the clickable cursor but had no hover styling at all, so the pointer changed shape and the button did not, which made working controls read as broken; the marketplace, Widget Studio, the brain workspace, the pump dashboard, agent detail and the on-chain deploy panel now all answer under the pointer, on the same timing. The retry buttons on an agent page were the worst case, because they only appear after something already failed. Separately, 73 colours were still typed in by hand across 24 stylesheets instead of coming from the shared palette, which is why a handful of panels stayed dark when you switched to the light theme and why some captions drifted a shade off everywhere else; they now all read from one source. Eight standalone pages that had quietly grown their own private palette (the demos, Widget Studio, the dashboard sub-pages, the print insert, agent detail) were folded back onto the shared one, so they also pick up the site-wide keyboard focus ring and the reduced-motion setting for the first time. Two new checks keep both from creeping back. (`/marketplace`) `[improvement, fix]`+- **Every tutorial now shows you the page it is teaching**: Twenty screenshots of the real product had been captured for the tutorials and then never put on the page: the tutorials described the Forge, Avatar Studio, Voice Lab, Scene Studio, Widget Studio and the rest entirely in words, while the pictures sat unused. All twenty are now embedded where they belong, each with a caption and a link straight to the live page, so you can see what you are about to open before you open it. The sign-language reference gained its two figures as well, and the missing Scene Studio capture was taken. (`/tutorials/text-to-3d`) `[docs, improvement]`- **Forge tells you when uploads are down, instead of blaming your connection**: Adding a photo on the Forge could fail with "Network error during upload" when nothing was wrong with your network or your photo. Our asset storage had stopped accepting our credential, but the page had no way to know that: the browser is handed a short-lived upload address and sends the image straight to storage, and when storage refuses, the refusal comes back without the header a browser needs in order to show the page what happened. So a platform outage arrived looking exactly like a bad phone signal, and Retry could never fix it. The page now checks that storage will actually accept an upload before handing one out, and says so plainly when it will not, so you can tell "come back in a few minutes" apart from "try a different photo". The same fix covers the Forge Studio and 3D print upload paths. (`/forge`) `[fix]`- **Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch**: Launch Studio, the catalog of 50 coin-launch recipes, was written entirely in white text and never flipped for the light theme, so on a light background its title, its recipe cards and its preview drawer were white on white with a dark strip painted across the top. The whole surface now draws from the site's colour system and reads in both themes. The bigger fix sits behind the Launch this coin button: every reward recipe promises that a coin's creator fees route to its subject, and that choice was being dropped the moment you left the studio, so the launch form opened with no recipient at all. The routing now travels with the coin, shows on the launch form before you mint, and opens the fee split pre-filled with that recipient the moment the coin is live, ready to review and sign. Two planner options no launch could ever apply were removed rather than left promising a payout. The preview drawer also behaves as a real dialog now: focus moves into it, Tab stays inside it, and closing it returns you to the card you opened. (`/launch-studio`) `[fix, improvement]`- **Robinhood Portfolios can now show you what a basket would have done, and what the rebalancing did to it**: Every generated portfolio now comes with a backtest, and it runs the basket twice: once rebalanced on the schedule it published, and once left alone. The gap between those two lines is the whole reason to pick one schedule over another, and it goes both ways, since rebalancing quietly harvests the swings in a basket whose holdings move against each other and quietly gives up gains in one where a single holding keeps winning. Coverage is stated rather than glossed over: a holding with no price history is named and left out, the window shown is only the stretch where every remaining holding has real observations, and nothing is filled in to close a gap. Getting that history at all took some doing, because this chain keeps no price archive and produces about 864,000 blocks a day, so reading a month of prices back off the chain is not something a page can do while you wait. Tokenized stocks are covered from their price feeds going back weeks, and a nightly snapshot now records the whole market so coverage keeps growing for everything else, memecoins included. Sharing a portfolio also got fixed: a link now carries the portfolio itself rather than the sentence that produced it, so what you send is exactly what the other person opens, where before the wording was re-run and could quietly come back as a different basket. There is a new endpoint for checking that a portfolio document really is the one a portfolio was published under, and a client library for developers who want the market, the generator, the backtest and that check from their own code. Along the way two data bugs were fixed that were quietly under-reporting the market: the tokenized-stock board had been describing only a couple of tokens per batch instead of all thirty, and the price-history reads had been silently returning less history the more of it you asked for. (`/markets/robinhood/portfolios`) `[feature, improvement]`- **Text to 3D no longer stops when our image storage does**: Turning a written prompt into a model takes one step you never see: we paint a reference picture of what you asked for, save it somewhere our sculpting engines can read, and hand them the link. If that save failed, the whole thing was over before a graphics card was ever asked for anything, and the error you got back was our storage provider's own wording about signatures and access keys, which told you nothing you could act on. Making a model from a photo you upload was unaffected, because it brings its own picture, so half the feature could look perfectly healthy while the other half was completely down. Our own engines never needed that saved copy: they accept the picture itself, sent along with the request. So when storage will not take the write, the reference view now travels inside the job and your model still gets built. The engines that genuinely need a link, the outside ones you can pick by name, now say so in plain language and point you at the ones still running, instead of failing with a message about our secret keys. Generations that take this route lose the extra angles we normally paint to fill in a subject's back, so they are built from the single front view. (`/forge`) `[fix, improvement]`- **The Agent Economy page is readable on a phone, and its x402 services finally have names**: On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled "Service", the price sat next to a raw token contract address, and the network read "eip155:8453" instead of "Base". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of "40+". (`/economy`) `[fix, improvement]`+- **The agent vitals endpoint answers again, and eight documented API examples now say what they really return**: GET /api/agents/vitals, the operator view that reports whether each autonomous agent can actually act, had been unreachable: a broader routing rule for agent profiles was catching the request first and answering with an agent lookup instead. It resolves to its own handler again. Separately, every runnable curl sample in the documentation was replayed against the live API, and the ones whose example used a placeholder id or needed a signed-in session now say so above the snippet rather than looking like a call that should have worked. (`/docs/agent-vitals`) `[fix, docs]`- **The ChatGPT and AR docs now describe the AR launcher that actually runs**: Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation. (`/docs/ar`) `[docs, fix]`- **The club now takes $THREE at the door and at the stage, not just USDC**: The club has always advertised two ways to pay: USDC or $THREE, on Solana, for both the cover charge and every dance tip. Only one of them was reachable. The checkout window picked the first token a service offered and gave you no way to choose the other, so $THREE was quoted on every paid page and payable on none of them. Across every club tip ever settled, not one was paid in $THREE, which is what you would expect from a menu with a hidden second item. The checkout now shows a token picker whenever a service quotes more than one, with each token's real price on it, so you can compare 0.001 USDC against its $THREE equivalent before you approve anything, and the price at the top of the window follows what you pick. If you have agent wallets, they still pay in USDC only, and the window now says so instead of quietly hiding them when you switch tokens. Two settlement bugs behind the door were fixed at the same time. The first would have hit the very first person to pay in $THREE: sending a token to a wallet that has never held it requires opening an account for it on-chain, and the check that decides whether we can afford to sponsor a payment was ignoring that cost, so the payment would have been accepted and then failed on-chain for a reason that looked like something else entirely. The second was making the club look open when it was not: a healthy payer covering their own fees could reset a shared 'we can still sponsor payments' flag that belonged to a different wallet, so the door kept quoting prices it could not actually take. Finally, when payments are paused because the wallet that settles them needs topping up, the checkout now says that in a sentence and tells you nothing was charged, instead of showing you the raw error envelope it used to paste in, which read like a broken link. (`/club`) `[fix, improvement]`+- **The guardian console now tells you why someone is asking for an agent back**: If a friend has named you a guardian or a beneficiary of their agent, /guardian is where you decide whether to let them back in. Until now the card told you a process was open and asked you to approve it, without showing you the one thing a decision actually turns on: the reason the person gave when they opened the request. It now shows that reason, names every guardian who has already approved or declined, and says how long the request has before it expires if nobody acts. The status stopped reading like a database field, so a card says "awaiting approvals" or "in the safety window" instead of pending_approvals. Approving takes a couple of seconds to travel; the button now says Approving while it does, rather than going quiet. If the safety window lifts while you have the page open, it refreshes itself so Complete transfer appears without a reload, and it refreshes again whenever you come back to the tab. Signed out, the page has a proper heading, offers to make you an account, and brings you straight back here after you sign in; with nobody yet naming you, it now points you at setting up guardians on your own agents. When the console cannot load at all it explains what went wrong in plain words, telling a dropped connection apart from a rate limit and a fault on our side, instead of printing the browser's own "Failed to fetch". (`/guardian`) `[improvement, fix]`- **The Launch a Coin button now works once you have filled the form**: On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read "Add name, symbol & description to launch" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into "Connect wallet to launch" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges. (`/launch`) `[fix, improvement]`+- **The Revenue view on Protocol Fees stopped calling itself Fees**: Open /fees, switch to Revenue, and the numbers, the chart and the stat cards all changed to revenue while the table heading and the browser tab kept saying "Fees". The page writes those two pieces of copy itself, and the site-wide translation pass, which lands a second or two after the page does, was overwriting them back to the fees wording. Both now hold the metric you actually selected, and hand themselves back to the translator when you switch to Fees, so a reader in another language keeps their own copy. Four more things on that page while we were in there: the footer line now says when a figure is a cached copy served because DeFiLlama is unreachable, rather than presenting it as live; a run where the feed returns nothing no longer paints three empty totals and a "Top 0 protocols" line that read like a claim DeFi earned nothing; toggling Fees and Revenue faster than the network answers can no longer land one metric's numbers under the other's heading; and screen readers are now told every column is sortable, told which metric each region is showing, and given a proper pair of toggle buttons instead of tabs with no panel behind them. The "+3" badge on a protocol's chain list also names the chains it is hiding. (`/fees`) `[fix, improvement]`+- **Watch your model being made, instead of watching a spinner**: Making a model from a written prompt starts with work you never saw: an art director rewrites your words into a proper brief, then an image model paints the reference picture the mesh is actually sculpted from, and on our best lane it paints the extra angles that fill in the subject's back. All of that used to happen inside one long silent request, so Forge could only say "art-directing your prompt" for the whole wait and then reveal the reference picture at the very end, when it had already existed for half a minute. Now the pipeline reports each step the instant it finishes, so the stage list ticks over as the work really happens and the reference image appears on screen while the sculpting is still running. Nothing on that list is a guess: a step only lights up because the server said it finished. On a phone, pressing Generate now brings the panel into view instead of leaving the whole thing playing out below the fold, and the same is true when a model lands or when something goes wrong. If our asset storage is the thing that is down, Forge now says so plainly, tells you nothing was charged, and points you at the models you already made, which keep working throughout. A model on screen also stops spinning by itself for anyone who has asked their device for less motion, and the report-a-bug prompt no longer pops up on top of the recovery buttons on a narrow screen. (`/forge`) `[improvement, fix]`+- **Your avatars show up on the dashboard again, and a failed one says why**: The avatar previews on your dashboard, and every three.ws avatar embedded through the <threews-avatar> tag, were being pointed straight at the storage bucket that holds the 3D file. That address is on a different domain to the page asking for it, and the browser refuses cross-domain reads it has not been given permission for, so the model was blocked before a single byte arrived and the preview sat empty. Stored avatars now load through three.ws itself, which is the same origin as the page, carries your session so a private avatar stays private, and already knows to fall back to the public copy of the file when the signed read is refused. That last part is why this was invisible on our own site and total everywhere else: the bucket permits three.ws by name and nothing else, so a dashboard preview, a developer running the site locally, and a customer embedding an avatar on their own domain all failed for the same reason. When a model genuinely cannot be loaded, the frame no longer paints the raw network error, complete with an internal URL, into the box. It now says whether the avatar is private, gone, or the service is down, and what to do next. My Agents got the same treatment: a failed load explains the cause and gives you a Try again button instead of telling you to refresh the page, its keyboard focus outlines are visible again, and the page respects a reduced-motion preference. (`/dashboard`) `[fix, improvement]`## 2026-09-07diff --git a/data/changelog.json b/data/changelog.jsonindex 966073f19..c4dd44512 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,25 +1,64 @@{"$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-08",+ "title": "Watch your model being made, instead of watching a spinner",+ "summary": "Making a model from a written prompt starts with work you never saw: an art director rewrites your words into a proper brief, then an image model paints the reference picture the mesh is actually sculpted from, and on our best lane it paints the extra angles that fill in the subject's back. All of that used to happen inside one long silent request, so Forge could only say \"art-directing your prompt\" for the whole wait and then reveal the reference picture at the very end, when it had already existed for half a minute. Now the pipeline reports each step the instant it finishes, so the stage list ticks over as the work really happens and the reference image appears on screen while the sculpting is still running. Nothing on that list is a guess: a step only lights up because the server said it finished. On a phone, pressing Generate now brings the panel into view instead of leaving the whole thing playing out below the fold, and the same is true when a model lands or when something goes wrong. If our asset storage is the thing that is down, Forge now says so plainly, tells you nothing was charged, and points you at the models you already made, which keep working throughout. A model on screen also stops spinning by itself for anyone who has asked their device for less motion, and the report-a-bug prompt no longer pops up on top of the recovery buttons on a narrow screen.",+ "tags": [+ "improvement",+ "fix"+ ],+ "link": "/forge"+ },+ {+ "date": "2026-09-08",+ "title": "The guardian console now tells you why someone is asking for an agent back",+ "summary": "If a friend has named you a guardian or a beneficiary of their agent, /guardian is where you decide whether to let them back in. Until now the card told you a process was open and asked you to approve it, without showing you the one thing a decision actually turns on: the reason the person gave when they opened the request. It now shows that reason, names every guardian who has already approved or declined, and says how long the request has before it expires if nobody acts. The status stopped reading like a database field, so a card says \"awaiting approvals\" or \"in the safety window\" instead of pending_approvals. Approving takes a couple of seconds to travel; the button now says Approving while it does, rather than going quiet. If the safety window lifts while you have the page open, it refreshes itself so Complete transfer appears without a reload, and it refreshes again whenever you come back to the tab. Signed out, the page has a proper heading, offers to make you an account, and brings you straight back here after you sign in; with nobody yet naming you, it now points you at setting up guardians on your own agents. When the console cannot load at all it explains what went wrong in plain words, telling a dropped connection apart from a rate limit and a fault on our side, instead of printing the browser's own \"Failed to fetch\".",+ "tags": [+ "improvement",+ "fix"+ ],+ "link": "/guardian"+ },+ {+ "date": "2026-09-08",+ "title": "Your avatars show up on the dashboard again, and a failed one says why",+ "summary": "The avatar previews on your dashboard, and every three.ws avatar embedded through the <threews-avatar> tag, were being pointed straight at the storage bucket that holds the 3D file. That address is on a different domain to the page asking for it, and the browser refuses cross-domain reads it has not been given permission for, so the model was blocked before a single byte arrived and the preview sat empty. Stored avatars now load through three.ws itself, which is the same origin as the page, carries your session so a private avatar stays private, and already knows to fall back to the public copy of the file when the signed read is refused. That last part is why this was invisible on our own site and total everywhere else: the bucket permits three.ws by name and nothing else, so a dashboard preview, a developer running the site locally, and a customer embedding an avatar on their own domain all failed for the same reason. When a model genuinely cannot be loaded, the frame no longer paints the raw network error, complete with an internal URL, into the box. It now says whether the avatar is private, gone, or the service is down, and what to do next. My Agents got the same treatment: a failed load explains the cause and gives you a Try again button instead of telling you to refresh the page, its keyboard focus outlines are visible again, and the page respects a reduced-motion preference.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/dashboard"+ },{"date": "2026-09-08","title": "The Revenue view on Protocol Fees stopped calling itself Fees","summary": "Open /fees, switch to Revenue, and the numbers, the chart and the stat cards all changed to revenue while the table heading and the browser tab kept saying \"Fees\". The page writes those two pieces of copy itself, and the site-wide translation pass, which lands a second or two after the page does, was overwriting them back to the fees wording. Both now hold the metric you actually selected, and hand themselves back to the translator when you switch to Fees, so a reader in another language keeps their own copy. Four more things on that page while we were in there: the footer line now says when a figure is a cached copy served because DeFiLlama is unreachable, rather than presenting it as live; a run where the feed returns nothing no longer paints three empty totals and a \"Top 0 protocols\" line that read like a claim DeFi earned nothing; toggling Fees and Revenue faster than the network answers can no longer land one metric's numbers under the other's heading; and screen readers are now told every column is sortable, told which metric each region is showing, and given a proper pair of toggle buttons instead of tabs with no panel behind them. The \"+3\" badge on a protocol's chain list also names the chains it is hiding.",- "tags": ["fix", "improvement"],+ "tags": [+ "fix",+ "improvement"+ ],"link": "/fees"},{"date": "2026-09-08","title": "The ChatGPT and AR docs now describe the AR launcher that actually runs","summary": "Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.",- "tags": ["docs", "fix"],+ "tags": [+ "docs",+ "fix"+ ],"link": "/docs/ar"},{"date": "2026-09-08","title": "The Launch a Coin button now works once you have filled the form","summary": "On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read \"Add name, symbol & description to launch\" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into \"Connect wallet to launch\" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.",- "tags": ["fix", "improvement"],+ "tags": [+ "fix",+ "improvement"+ ],"link": "/launch"},{@@ -27108,6 +27147,26 @@"improvement"],"link": "/launches"+ },+ {+ "date": "2026-09-08",+ "title": "Every tutorial now shows you the page it is teaching",+ "summary": "Twenty screenshots of the real product had been captured for the tutorials and then never put on the page: the tutorials described the Forge, Avatar Studio, Voice Lab, Scene Studio, Widget Studio and the rest entirely in words, while the pictures sat unused. All twenty are now embedded where they belong, each with a caption and a link straight to the live page, so you can see what you are about to open before you open it. The sign-language reference gained its two figures as well, and the missing Scene Studio capture was taken.",+ "tags": [+ "docs",+ "improvement"+ ],+ "link": "/tutorials/text-to-3d"+ },+ {+ "date": "2026-09-08",+ "title": "The agent vitals endpoint answers again, and eight documented API examples now say what they really return",+ "summary": "GET /api/agents/vitals, the operator view that reports whether each autonomous agent can actually act, had been unreachable: a broader routing rule for agent profiles was catching the request first and answering with an agent lookup instead. It resolves to its own handler again. Separately, every runnable curl sample in the documentation was replayed against the live API, and the ones whose example used a placeholder id or needed a signed-in session now say so above the snippet rather than looking like a call that should have worked.",+ "tags": [+ "fix",+ "docs"+ ],+ "link": "/docs/agent-vitals"}]}diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex dbfbbe3ab..1b8c1d604 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-08T17:37:03.863Z",+ "generated_at": "2026-09-08T18:09:04.268Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3557,+ "total": 3564,"complete": false,"full_feed": "/changelog.json","entries": [@@ -31,6 +31,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Agent Launches: the Tip button on every launch card actually works now",+ "summary": "Each card on the launches feed carries the launching agent's wallet, and the whole-card link to the coin profile was sitting on top of it: every tap on Tip, and every attempt to preview the wallet, opened the coin page instead. The wallet now sits above that link, so tipping and the wallet preview both work, on the feed and everywhere else the wallet badge appears. Keyboard and screen-reader use got the same pass: the Mainnet/Devnet switch responds to the arrow keys and says which feed it controls, the graduation bars announce which coin they belong to and how far along it is, the wallet's trust score and balance no longer read as unlabelled boxes while they load, and a page that found nothing on devnet now offers a button back to mainnet instead of only telling you to switch.",+ "link": "/launches",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -53,6 +64,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Every tutorial now shows you the page it is teaching",+ "summary": "Twenty screenshots of the real product had been captured for the tutorials and then never put on the page: the tutorials described the Forge, Avatar Studio, Voice Lab, Scene Studio, Widget Studio and the rest entirely in words, while the pictures sat unused. All twenty are now embedded where they belong, each with a caption and a link straight to the live page, so you can see what you are about to open before you open it. The sign-language reference gained its two figures as well, and the missing Scene Studio capture was taken.",+ "link": "/tutorials/text-to-3d",+ "tags": [+ "docs",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -107,6 +129,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The agent vitals endpoint answers again, and eight documented API examples now say what they really return",+ "summary": "GET /api/agents/vitals, the operator view that reports whether each autonomous agent can actually act, had been unreachable: a broader routing rule for agent profiles was catching the request first and answering with an agent lookup instead. It resolves to its own handler again. Separately, every runnable curl sample in the documentation was replayed against the live API, and the ones whose example used a placeholder id or needed a signed-in session now say so above the snippet rather than looking like a call that should have worked.",+ "link": "/docs/agent-vitals",+ "tags": [+ "fix",+ "docs"+ ]+ },{"date": "2026-09-08","type": "update",@@ -129,6 +162,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The guardian console now tells you why someone is asking for an agent back",+ "summary": "If a friend has named you a guardian or a beneficiary of their agent, /guardian is where you decide whether to let them back in. Until now the card told you a process was open and asked you to approve it, without showing you the one thing a decision actually turns on: the reason the person gave when they opened the request. It now shows that reason, names every guardian who has already approved or declined, and says how long the request has before it expires if nobody acts. The status stopped reading like a database field, so a card says \"awaiting approvals\" or \"in the safety window\" instead of pending_approvals. Approving takes a couple of seconds to travel; the button now says Approving while it does, rather than going quiet. If the safety window lifts while you have the page open, it refreshes itself so Complete transfer appears without a reload, and it refreshes again whenever you come back to the tab. Signed out, the page has a proper heading, offers to make you an account, and brings you straight back here after you sign in; with nobody yet naming you, it now points you at setting up guardians on your own agents. When the console cannot load at all it explains what went wrong in plain words, telling a dropped connection apart from a rate limit and a fault on our side, instead of printing the browser's own \"Failed to fetch\".",+ "link": "/guardian",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-08","type": "update",@@ -140,6 +184,39 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Revenue view on Protocol Fees stopped calling itself Fees",+ "summary": "Open /fees, switch to Revenue, and the numbers, the chart and the stat cards all changed to revenue while the table heading and the browser tab kept saying \"Fees\". The page writes those two pieces of copy itself, and the site-wide translation pass, which lands a second or two after the page does, was overwriting them back to the fees wording. Both now hold the metric you actually selected, and hand themselves back to the translator when you switch to Fees, so a reader in another language keeps their own copy. Four more things on that page while we were in there: the footer line now says when a figure is a cached copy served because DeFiLlama is unreachable, rather than presenting it as live; a run where the feed returns nothing no longer paints three empty totals and a \"Top 0 protocols\" line that read like a claim DeFi earned nothing; toggling Fees and Revenue faster than the network answers can no longer land one metric's numbers under the other's heading; and screen readers are now told every column is sortable, told which metric each region is showing, and given a proper pair of toggle buttons instead of tabs with no panel behind them. The \"+3\" badge on a protocol's chain list also names the chains it is hiding.",+ "link": "/fees",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Watch your model being made, instead of watching a spinner",+ "summary": "Making a model from a written prompt starts with work you never saw: an art director rewrites your words into a proper brief, then an image model paints the reference picture the mesh is actually sculpted from, and on our best lane it paints the extra angles that fill in the subject's back. All of that used to happen inside one long silent request, so Forge could only say \"art-directing your prompt\" for the whole wait and then reveal the reference picture at the very end, when it had already existed for half a minute. Now the pipeline reports each step the instant it finishes, so the stage list ticks over as the work really happens and the reference image appears on screen while the sculpting is still running. Nothing on that list is a guess: a step only lights up because the server said it finished. On a phone, pressing Generate now brings the panel into view instead of leaving the whole thing playing out below the fold, and the same is true when a model lands or when something goes wrong. If our asset storage is the thing that is down, Forge now says so plainly, tells you nothing was charged, and points you at the models you already made, which keep working throughout. A model on screen also stops spinning by itself for anyone who has asked their device for less motion, and the report-a-bug prompt no longer pops up on top of the recovery buttons on a narrow screen.",+ "link": "/forge",+ "tags": [+ "improvement",+ "fix"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Your avatars show up on the dashboard again, and a failed one says why",+ "summary": "The avatar previews on your dashboard, and every three.ws avatar embedded through the <threews-avatar> tag, were being pointed straight at the storage bucket that holds the 3D file. That address is on a different domain to the page asking for it, and the browser refuses cross-domain reads it has not been given permission for, so the model was blocked before a single byte arrived and the preview sat empty. Stored avatars now load through three.ws itself, which is the same origin as the page, carries your session so a private avatar stays private, and already knows to fall back to the public copy of the file when the signed read is refused. That last part is why this was invisible on our own site and total everywhere else: the bucket permits three.ws by name and nothing else, so a dashboard preview, a developer running the site locally, and a customer embedding an avatar on their own domain all failed for the same reason. When a model genuinely cannot be loaded, the frame no longer paints the raw network error, complete with an internal URL, into the box. It now says whether the avatar is private, gone, or the service is down, and what to do next. My Agents got the same treatment: a failed load explains the cause and gives you a Try again button instead of telling you to refresh the page, its keyboard focus outlines are visible again, and the page respects a reduced-motion preference.",+ "link": "/dashboard",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-07","type": "launch",@@ -1525,83 +1602,6 @@"security","docs"]- },- {- "date": "2026-09-03",- "type": "update",- "title": "Sign Mirror tells you what went wrong, and remembers how close you got",- "summary": "The ASL practice mirror got a pass over every state it can be in. When the camera cannot start it now says which thing failed and what to do about it: permission refused, no camera on the device, the camera busy in another app, or the hand tracker itself failing to download. It used to print the raw internal error, which nobody could act on. While the tracker downloads you see that it is downloading, instead of a panel that still says the camera is off. Turning the camera off puts the panel back to telling you what to do next rather than leaving an empty box. Every letter square now carries the best score you have reached on it, so twenty six identical squares become a map of where your practice actually is, and that score is kept between sessions. Screen readers now hear the finger being named, and the live skeleton and the per finger bars are redrawn in place instead of being rebuilt on every camera frame, which takes real work off the machine doing the grading.",- "link": "/sign-mirror",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "Soft shadows are soft again in Pose Studio, Mirror and Diorama",- "summary": "These three 3D surfaces were asking for a soft-shadow mode that the renderer stopped supporting and silently swapped for hard-edged shadows, complaining in the console every time a scene started. They now use the supported soft-shadow type, so contact shadows under a figure read as shadows rather than hard cutouts.",- "link": "/pose",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "Talk to your house without finding a phone, and a background \"yeah\" can never open your front door",- "summary": "Hands-free is here for connected homes. Turn it on at /voice/home, say the wake word, and ask for what you want: \"turn the kitchen light off\" works while you are carrying groceries. The wake word is matched by a model that runs inside your own browser tab, so that audio never leaves your device; only the sentence you say afterwards is sent, and only to be turned into text. While the microphone is live there is an indicator on the page that cannot be switched off, and Mute genuinely stops the microphone at the device rather than hiding a dot. Talk over the agent and it stops mid-sentence and listens, in about a tenth of a second, and it will not wake itself up when it happens to say its own wake word out loud. The part we spent the most care on is the door. Anything that opens your house is spoken back in full first, the exact device appears on screen while you decide, and only the word \"confirm\" goes through. A \"yeah\" or a \"sure\" overheard from a conversation on the other side of the room does not, and on a device with no screen the agent refuses to take an unlock by voice at all and offers your phone instead. Four wake phrases to choose from, twelve designed states including an honest one for deployments where speech recognition is not available, and every stage of the round trip timed live on screen so you can see where the seconds go.",- "link": "/voice/home",- "tags": [- "feature",- "security"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The free 3D generation lane is back up, and it can no longer fail quietly",- "summary": "The worker behind the default free text-to-3D and image-to-3D lane stopped being able to load its model on the evening of 2 September, and then kept accepting work it could not do. It had cached that one failure and replayed it to every job that followed, while its status page still reported itself healthy, so nothing raised a flag: roughly a third of generations on that lane failed over about twelve hours. The lane is running again, and four things now stop a repeat. The load is retried instead of one bad moment being treated as final. A worker that genuinely cannot run turns work away, so your generation is handed to another backend rather than dying several minutes later. It reports itself as unhealthy, so it gets replaced automatically and shows up as down on the status page instead of green. And the part of the model that had to be fetched from an outside site every time the worker started, which is what failed, now ships inside the worker, so that fetch cannot fail again.",- "link": "/forge",- "tags": [- "fix",- "infra"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The parametric avatar goes from 122 sliders to 306, and a brush for everything they still cannot reach",- "summary": "Avatar Studio's Parametric base now carries 306 shape sliders instead of 122, curated from source data that was already vendored: eyelid heights and eye folds, nose bridge and septum, philtrum and cupid's bow, ear rotation and shape, temples, jaw bones, lats, navel, knee alignment, upper and lower leg length, and per-ethnicity phenotype anchors. Face regions keep separate left and right controls because facial asymmetry is part of a face; limbs get one symmetric slider. With that many controls the panel grew a filter box, collapsed body groups, and an \"N edited\" pill so you can see which closed group you have already touched. Above all of it sits Free Sculpt: turn the brush on and drag on the avatar to push or pull the surface anywhere, with a real-size on-screen ring, adjustable strength, and symmetry you can switch off. Playback pauses while you paint so the mesh holds still, dragging the background still orbits the camera, and Clear sculpt puts the body back exactly. Two things that used to be editor-only now reach everyone: a body edited in the avatar editor's Proportions panel and any free-sculpt stroke are both rendered into the GLB the server serves, so what you shaped is what viewers, embeds and AR downloads actually see.",- "link": "/create/studio",- "tags": [- "feature",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The payments feed now tells you which volume is ours and which is real demand",- "summary": "three.ws runs a closed loop where platform wallets pay platform endpoints on a schedule, to keep the payment rails warm and provably live. That traffic is real money on a real chain, and it is the overwhelming majority of settled volume, so anyone reading the raw total was reading our own money back to us. The x402 volume report on the paid analytics endpoint now carries a revenue split alongside the totals: how many calls and how much USDC came from outside wallets, how much is the internal loop, and how much is test traffic that was never money at all. A new command, npm run readout:revenue, prints the same breakdown for any window and refuses to print an external figure when it cannot tell our wallets apart from anyone else's, rather than quietly reporting a flattering one. One classifier backs both, so the API and the command can never disagree.",- "link": "/docs/autonomous-x402",- "tags": [- "improvement",- "infra"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The rest of the smart home now speaks your language, and the wall display stays awake",- "summary": "The connect page learned all 87 languages last week; the invitation, plan and voice satellite pages had the same gap and now speak them too, along with the live 3D house. Setting a page to Arabic or Hebrew also actually mirrors it now: the reveal button, the coloured bars beside notices, and the room and device columns in the live house used to stay stuck on the left. If you have asked your device to reduce motion, the house stops animating between states while staying completely live, so lights and locks still update the instant they change, they just arrive rather than glide. The live house also keeps the screen awake now, which is what you want on a kitchen tablet on a shelf, and gives that up the moment you switch away, which is what you want on a phone in your pocket. On a phone with a notch the house fills the screen without hiding its own controls behind the cutout.",- "link": "/smart-home",- "tags": [- "improvement",- "fix"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex eafc5ee3f..a980c94e7 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-08T17:37:03.298Z",+ "generated_at": "2026-09-08T18:09:04.051Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -28,6 +28,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Agent Launches: the Tip button on every launch card actually works now",+ "summary": "Each card on the launches feed carries the launching agent's wallet, and the whole-card link to the coin profile was sitting on top of it: every tap on Tip, and every attempt to preview the wallet, opened the coin page instead. The wallet now sits above that link, so tipping and the wallet preview both work, on the feed and everywhere else the wallet badge appears. Keyboard and screen-reader use got the same pass: the Mainnet/Devnet switch responds to the arrow keys and says which feed it controls, the graduation bars announce which coin they belong to and how far along it is, the wallet's trust score and balance no longer read as unlabelled boxes while they load, and a page that found nothing on devnet now offers a button back to mainnet instead of only telling you to switch.",+ "link": "/launches",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -50,6 +61,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Every tutorial now shows you the page it is teaching",+ "summary": "Twenty screenshots of the real product had been captured for the tutorials and then never put on the page: the tutorials described the Forge, Avatar Studio, Voice Lab, Scene Studio, Widget Studio and the rest entirely in words, while the pictures sat unused. All twenty are now embedded where they belong, each with a caption and a link straight to the live page, so you can see what you are about to open before you open it. The sign-language reference gained its two figures as well, and the missing Scene Studio capture was taken.",+ "link": "/tutorials/text-to-3d",+ "tags": [+ "docs",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -104,6 +126,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The agent vitals endpoint answers again, and eight documented API examples now say what they really return",+ "summary": "GET /api/agents/vitals, the operator view that reports whether each autonomous agent can actually act, had been unreachable: a broader routing rule for agent profiles was catching the request first and answering with an agent lookup instead. It resolves to its own handler again. Separately, every runnable curl sample in the documentation was replayed against the live API, and the ones whose example used a placeholder id or needed a signed-in session now say so above the snippet rather than looking like a call that should have worked.",+ "link": "/docs/agent-vitals",+ "tags": [+ "fix",+ "docs"+ ]+ },{"date": "2026-09-08","type": "update",@@ -126,6 +159,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The guardian console now tells you why someone is asking for an agent back",+ "summary": "If a friend has named you a guardian or a beneficiary of their agent, /guardian is where you decide whether to let them back in. Until now the card told you a process was open and asked you to approve it, without showing you the one thing a decision actually turns on: the reason the person gave when they opened the request. It now shows that reason, names every guardian who has already approved or declined, and says how long the request has before it expires if nobody acts. The status stopped reading like a database field, so a card says \"awaiting approvals\" or \"in the safety window\" instead of pending_approvals. Approving takes a couple of seconds to travel; the button now says Approving while it does, rather than going quiet. If the safety window lifts while you have the page open, it refreshes itself so Complete transfer appears without a reload, and it refreshes again whenever you come back to the tab. Signed out, the page has a proper heading, offers to make you an account, and brings you straight back here after you sign in; with nobody yet naming you, it now points you at setting up guardians on your own agents. When the console cannot load at all it explains what went wrong in plain words, telling a dropped connection apart from a rate limit and a fault on our side, instead of printing the browser's own \"Failed to fetch\".",+ "link": "/guardian",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-08","type": "update",@@ -137,6 +181,39 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Revenue view on Protocol Fees stopped calling itself Fees",+ "summary": "Open /fees, switch to Revenue, and the numbers, the chart and the stat cards all changed to revenue while the table heading and the browser tab kept saying \"Fees\". The page writes those two pieces of copy itself, and the site-wide translation pass, which lands a second or two after the page does, was overwriting them back to the fees wording. Both now hold the metric you actually selected, and hand themselves back to the translator when you switch to Fees, so a reader in another language keeps their own copy. Four more things on that page while we were in there: the footer line now says when a figure is a cached copy served because DeFiLlama is unreachable, rather than presenting it as live; a run where the feed returns nothing no longer paints three empty totals and a \"Top 0 protocols\" line that read like a claim DeFi earned nothing; toggling Fees and Revenue faster than the network answers can no longer land one metric's numbers under the other's heading; and screen readers are now told every column is sortable, told which metric each region is showing, and given a proper pair of toggle buttons instead of tabs with no panel behind them. The \"+3\" badge on a protocol's chain list also names the chains it is hiding.",+ "link": "/fees",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Watch your model being made, instead of watching a spinner",+ "summary": "Making a model from a written prompt starts with work you never saw: an art director rewrites your words into a proper brief, then an image model paints the reference picture the mesh is actually sculpted from, and on our best lane it paints the extra angles that fill in the subject's back. All of that used to happen inside one long silent request, so Forge could only say \"art-directing your prompt\" for the whole wait and then reveal the reference picture at the very end, when it had already existed for half a minute. Now the pipeline reports each step the instant it finishes, so the stage list ticks over as the work really happens and the reference image appears on screen while the sculpting is still running. Nothing on that list is a guess: a step only lights up because the server said it finished. On a phone, pressing Generate now brings the panel into view instead of leaving the whole thing playing out below the fold, and the same is true when a model lands or when something goes wrong. If our asset storage is the thing that is down, Forge now says so plainly, tells you nothing was charged, and points you at the models you already made, which keep working throughout. A model on screen also stops spinning by itself for anyone who has asked their device for less motion, and the report-a-bug prompt no longer pops up on top of the recovery buttons on a narrow screen.",+ "link": "/forge",+ "tags": [+ "improvement",+ "fix"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Your avatars show up on the dashboard again, and a failed one says why",+ "summary": "The avatar previews on your dashboard, and every three.ws avatar embedded through the <threews-avatar> tag, were being pointed straight at the storage bucket that holds the 3D file. That address is on a different domain to the page asking for it, and the browser refuses cross-domain reads it has not been given permission for, so the model was blocked before a single byte arrived and the preview sat empty. Stored avatars now load through three.ws itself, which is the same origin as the page, carries your session so a private avatar stays private, and already knows to fall back to the public copy of the file when the signed read is refused. That last part is why this was invisible on our own site and total everywhere else: the bucket permits three.ws by name and nothing else, so a dashboard preview, a developer running the site locally, and a customer embedding an avatar on their own domain all failed for the same reason. When a model genuinely cannot be loaded, the frame no longer paints the raw network error, complete with an internal URL, into the box. It now says whether the avatar is private, gone, or the service is down, and what to do next. My Agents got the same treatment: a failed load explains the cause and gives you a Try again button instead of telling you to refresh the page, its keyboard focus outlines are visible again, and the page respects a reduced-motion preference.",+ "link": "/dashboard",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-07","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex bf83f784a..cfce329cd 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -22,6 +22,14 @@<category>fix</category><description>When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link.</description></item>+ <item>+ <title>Agent Launches: the Tip button on every launch card actually works now</title>+ <link>https://three.ws/launches</link>+ <guid isPermaLink="false">2026-09-08:Agent Launches: the Tip button on every launch card actually works now</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Each card on the launches feed carries the launching agent's wallet, and the whole-card link to the coin profile was sitting on top of it: every tap on Tip, and every attempt to preview the wallet, opened the coin page instead. The wallet now sits above that link, so tipping and the wallet preview both work, on the feed and everywhere else the wallet badge appears. Keyboard and screen-reader use got the same pass: the Mainnet/Devnet switch responds to the arrow keys and says which feed it controls, the graduation bars announce which coin they belong to and how far along it is, the wallet's trust score and balance no longer read as unlabelled boxes while they load, and a page that found nothing on devnet now offers a button back to mainnet instead of only telling you to switch.</description>+ </item><item><title>Avatars keep their real skin, eyes and hair, and we can prove it on a phone</title><link>https://three.ws/changelog</link>@@ -38,6 +46,14 @@<category>improvement</category><description>A consistency pass across the platform. Fifty controls set the clickable cursor but had no hover styling at all, so the pointer changed shape and the button did not, which made working controls read as broken; the marketplace, Widget Studio, the brain workspace, the pump dashboard, agent detail and the on-chain deploy panel now all answer under the pointer, on the same timing. The retry buttons on an agent page were the worst case, because they only appear after something already failed. Separately, 73 colours were still typed in by hand across 24 stylesheets instead of coming from the shared palette, which is why a handful of panels stayed dark when you switched to the light theme and why some captions drifted a shade off everywhere else; they now all read from one source. Eight standalone pages that had quietly grown their own private palette (the demos, Widget Studio, the dashboard sub-pages, the print insert, agent detail) were folded back onto the shared one, so they also pick up the site-wide keyboard focus ring and the reduced-motion setting for the first time. Two new checks keep both from creeping back.</description></item>+ <item>+ <title>Every tutorial now shows you the page it is teaching</title>+ <link>https://three.ws/tutorials/text-to-3d</link>+ <guid isPermaLink="false">2026-09-08:Every tutorial now shows you the page it is teaching</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>docs</category>+ <description>Twenty screenshots of the real product had been captured for the tutorials and then never put on the page: the tutorials described the Forge, Avatar Studio, Voice Lab, Scene Studio, Widget Studio and the rest entirely in words, while the pictures sat unused. All twenty are now embedded where they belong, each with a caption and a link straight to the live page, so you can see what you are about to open before you open it. The sign-language reference gained its two figures as well, and the missing Scene Studio capture was taken.</description>+ </item><item><title>Forge tells you when uploads are down, instead of blaming your connection</title><link>https://three.ws/forge</link>@@ -78,6 +94,14 @@<category>fix</category><description>On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled "Service", the price sat next to a raw token contract address, and the network read "eip155:8453" instead of "Base". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of "40+".</description></item>+ <item>+ <title>The agent vitals endpoint answers again, and eight documented API examples now say what they really return</title>+ <link>https://three.ws/docs/agent-vitals</link>+ <guid isPermaLink="false">2026-09-08:The agent vitals endpoint answers again, and eight documented API examples now say what they really return</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>GET /api/agents/vitals, the operator view that reports whether each autonomous agent can actually act, had been unreachable: a broader routing rule for agent profiles was catching the request first and answering with an agent lookup instead. It resolves to its own handler again. Separately, every runnable curl sample in the documentation was replayed against the live API, and the ones whose example used a placeholder id or needed a signed-in session now say so above the snippet rather than looking like a call that should have worked.</description>+ </item><item><title>The ChatGPT and AR docs now describe the AR launcher that actually runs</title><link>https://three.ws/docs/ar</link>@@ -94,6 +118,14 @@<category>fix</category><description>The club has always advertised two ways to pay: USDC or $THREE, on Solana, for both the cover charge and every dance tip. Only one of them was reachable. The checkout window picked the first token a service offered and gave you no way to choose the other, so $THREE was quoted on every paid page and payable on none of them. Across every club tip ever settled, not one was paid in $THREE, which is what you would expect from a menu with a hidden second item. The checkout now shows a token picker whenever a service quotes more than one, with each token's real price on it, so you can compare 0.001 USDC against its $THREE equivalent before you approve anything, and the price at the top of the window follows what you pick. If you have agent wallets, they still pay in USDC only, and the window now says so instead of quietly hiding them when you switch tokens. Two settlement bugs behind the door were fixed at the same time. The first would have hit the very first person to pay in $THREE: sending a token to a wallet that has never held it requires opening an account for it on-chain, and the check that decides whether we can afford to sponsor a payment was ignoring that cost, so the payment would have been accepted and then failed on-chain for a reason that looked like something else entirely. The second was making the club look open when it was not: a healthy payer covering their own fees could reset a shared 'we can still sponsor payments' flag that belonged to a different wallet, so the door kept quoting prices it could not actually take. Finally, when payments are paused because the wallet that settles them needs topping up, the checkout now says that in a sentence and tells you nothing was charged, instead of showing you the raw error envelope it used to paste in, which read like a broken link.</description></item>+ <item>+ <title>The guardian console now tells you why someone is asking for an agent back</title>+ <link>https://three.ws/guardian</link>+ <guid isPermaLink="false">2026-09-08:The guardian console now tells you why someone is asking for an agent back</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>If a friend has named you a guardian or a beneficiary of their agent, /guardian is where you decide whether to let them back in. Until now the card told you a process was open and asked you to approve it, without showing you the one thing a decision actually turns on: the reason the person gave when they opened the request. It now shows that reason, names every guardian who has already approved or declined, and says how long the request has before it expires if nobody acts. The status stopped reading like a database field, so a card says "awaiting approvals" or "in the safety window" instead of pending_approvals. Approving takes a couple of seconds to travel; the button now says Approving while it does, rather than going quiet. If the safety window lifts while you have the page open, it refreshes itself so Complete transfer appears without a reload, and it refreshes again whenever you come back to the tab. Signed out, the page has a proper heading, offers to make you an account, and brings you straight back here after you sign in; with nobody yet naming you, it now points you at setting up guardians on your own agents. When the console cannot load at all it explains what went wrong in plain words, telling a dropped connection apart from a rate limit and a fault on our side, instead of printing the browser's own "Failed to fetch".</description>+ </item><item><title>The Launch a Coin button now works once you have filled the form</title><link>https://three.ws/launch</link>@@ -102,6 +134,30 @@<category>fix</category><description>On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read "Add name, symbol & description to launch" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into "Connect wallet to launch" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.</description></item>+ <item>+ <title>The Revenue view on Protocol Fees stopped calling itself Fees</title>+ <link>https://three.ws/fees</link>+ <guid isPermaLink="false">2026-09-08:The Revenue view on Protocol Fees stopped calling itself Fees</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Open /fees, switch to Revenue, and the numbers, the chart and the stat cards all changed to revenue while the table heading and the browser tab kept saying "Fees". The page writes those two pieces of copy itself, and the site-wide translation pass, which lands a second or two after the page does, was overwriting them back to the fees wording. Both now hold the metric you actually selected, and hand themselves back to the translator when you switch to Fees, so a reader in another language keeps their own copy. Four more things on that page while we were in there: the footer line now says when a figure is a cached copy served because DeFiLlama is unreachable, rather than presenting it as live; a run where the feed returns nothing no longer paints three empty totals and a "Top 0 protocols" line that read like a claim DeFi earned nothing; toggling Fees and Revenue faster than the network answers can no longer land one metric's numbers under the other's heading; and screen readers are now told every column is sortable, told which metric each region is showing, and given a proper pair of toggle buttons instead of tabs with no panel behind them. The "+3" badge on a protocol's chain list also names the chains it is hiding.</description>+ </item>+ <item>+ <title>Watch your model being made, instead of watching a spinner</title>+ <link>https://three.ws/forge</link>+ <guid isPermaLink="false">2026-09-08:Watch your model being made, instead of watching a spinner</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Making a model from a written prompt starts with work you never saw: an art director rewrites your words into a proper brief, then an image model paints the reference picture the mesh is actually sculpted from, and on our best lane it paints the extra angles that fill in the subject's back. All of that used to happen inside one long silent request, so Forge could only say "art-directing your prompt" for the whole wait and then reveal the reference picture at the very end, when it had already existed for half a minute. Now the pipeline reports each step the instant it finishes, so the stage list ticks over as the work really happens and the reference image appears on screen while the sculpting is still running. Nothing on that list is a guess: a step only lights up because the server said it finished. On a phone, pressing Generate now brings the panel into view instead of leaving the whole thing playing out below the fold, and the same is true when a model lands or when something goes wrong. If our asset storage is the thing that is down, Forge now says so plainly, tells you nothing was charged, and points you at the models you already made, which keep working throughout. A model on screen also stops spinning by itself for anyone who has asked their device for less motion, and the report-a-bug prompt no longer pops up on top of the recovery buttons on a narrow screen.</description>+ </item>+ <item>+ <title>Your avatars show up on the dashboard again, and a failed one says why</title>+ <link>https://three.ws/dashboard</link>+ <guid isPermaLink="false">2026-09-08:Your avatars show up on the dashboard again, and a failed one says why</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The avatar previews on your dashboard, and every three.ws avatar embedded through the <threews-avatar> tag, were being pointed straight at the storage bucket that holds the 3D file. That address is on a different domain to the page asking for it, and the browser refuses cross-domain reads it has not been given permission for, so the model was blocked before a single byte arrived and the preview sat empty. Stored avatars now load through three.ws itself, which is the same origin as the page, carries your session so a private avatar stays private, and already knows to fall back to the public copy of the file when the signed read is refused. That last part is why this was invisible on our own site and total everywhere else: the bucket permits three.ws by name and nothing else, so a dashboard preview, a developer running the site locally, and a customer embedding an avatar on their own domain all failed for the same reason. When a model genuinely cannot be loaded, the frame no longer paints the raw network error, complete with an internal URL, into the box. It now says whether the avatar is private, gone, or the service is down, and what to do next. My Agents got the same treatment: a failed load explains the cause and gives you a Try again button instead of telling you to refresh the page, its keyboard focus outlines are visible again, and the page respects a reduced-motion preference.</description>+ </item><item><title>Awesome 3D Agents</title><link>https://three.ws/awesome</link>diff --git a/public/features.json b/public/features.jsonindex c516c54e2..f2a6ccbae 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-08T17:37:03.008Z",+ "generated_at": "2026-09-08T18:09:03.851Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",