Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(changelog): publish the five pending holder entries and regenerate the feeds

nirholasf784fcca0d43
diff --git a/CHANGELOG.md b/CHANGELOG.md
index bfbd46bb4..0939e7977 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-08-16
- **Docs · Avatar Artifact viewer** (`/docs/avatar-artifact`): The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.
+- **Docs · Skill bundles** (`/docs/skill-bundles`): How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.
- **A coin world link now unfurls as the live world, and only ever points at three.ws**: Pasting a coin community link into WordPress, Ghost, Discord, Notion or any editor built on embed.ly or iframely now turns it into the live 3D world instead of a plain link. The service that answers those editors existed but nothing on the page told them where to find it, so it was never called. Two problems in that service are fixed at the same time. It used to build the embed from the address in the incoming request rather than from the site address, so a crafted request could hand an editor an embed that framed somebody else site under the three.ws name; the embed is now always built from three.ws itself. And it used to answer for any link at all, returning a generic three.ws world card for a link that was never ours; it now says plainly that the link is not one of ours. It also answers in both of the formats the standard defines, and ignores a coin address that is not a real Solana address instead of putting it in the embed. Separately, the share images for pages and coin worlds, the holder leaderboard card, the free model verification check and the Oracle coin page now accept only read requests, and answer anything else with a clear message rather than doing the work anyway. (`/play`) `[fix, security]`
- **A dropped page in the agent directory no longer throws away everything you scrolled past**: The agent index loads in pages of 24, and until now a network hiccup on page five did more damage than the hiccup deserved. The Load more button vanished, and the only recovery on offer restarted the list from the top, discarding the hundred-odd agents already on screen. A failed page now says so on its own terms and offers Resume loading, which picks up exactly where it stopped; Start over is still there if you want it, and the error notice clears itself once the page arrives instead of lingering under the results. Three smaller repairs came with it: loading another page no longer redraws the agents already listed, so the grid stops flickering once a few pages are in; the search box and sort menu now show a proper focus ring for keyboard users instead of a one-pixel border tint; and the source filter chips reach a full-size tap target on tablets, not just on phones. (`/agents`) `[fix, improvement]`
- **A GitHub seed that stores nothing no longer costs you six hours**: Seeding an agent from your GitHub profile, repositories and READMEs is allowed once every six hours per agent. Two failures used to spend that window without storing a single fact. The first is entirely ours: when every model provider is busy at once, nothing is read and nothing is written, and you were still locked out for six hours over an outage you did not cause. The second is the run that comes back with no usable facts, which tells you to add a README or another repository, advice you could not act on until the window expired. Both now hand the window straight back, so you can try again as soon as a provider frees up or as soon as you have widened your selection, and the reply says which of the two happened. Nothing else changes: your existing memories are untouched by a failed run, the seed still reads only the profile, repositories and READMEs you ticked, and disconnecting GitHub still deletes every fact it wrote across all your agents. (`/docs/github-memory-seeding`) `[improvement, fix]`
@@ -14,15 +15,18 @@ 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]`
+- **Agent Wallet's trust panel stops sending you to a page that does not exist**: The Trust tab of an agent wallet lists what the wallet's credibility score is built from, and offers the owner concrete ways to raise it. Two of those pointers led nowhere: "Verify your on-chain identity" and, for an already-registered agent, the "On-chain identity" evidence link both pointed at an address the site has never served, so clicking either one landed on a not-found page. They now go somewhere real. The suggestion opens the ERC-8004 registration wizard with the agent's avatar already filled in, and the evidence link opens that identity's public on-chain page. The wallet page also stopped reading its address twice when you open the Vanity tab, and the screen reader announcement was corrected: being signed out, or not owning an agent yet, is the page's normal answer rather than an emergency, so those two screens are now read in turn instead of interrupting whatever was being spoken. (`/agent-wallet`) `[fix, improvement]`
- **Agora citizens show the craft they actually work, and the square fits a phone**: Every one of the 200 citizens in the Commons was labelled a Fetcher. The nameplate over each avatar, the citizen list that screen readers and keyboard users navigate by, and the passport header all read the citizen's capability list rather than the craft it is known for. Every citizen carries the fetcher capability, because calling a paid service is the one job anyone in the Commons can take, so that list always begins with Fetcher no matter who you were looking at. Mira the Appraiser and Aria the Sculptor both wore a FETCHER chip, sitting under a coloured ring that was already showing their real craft. Citizens now say what they do: the crowd, the list and the passport agree with each other and with the colour, and a passport leads with the primary craft before the rest of what that citizen is able to claim. On a phone the bottom of the square was a pile-up. The job board, the sign-in bar, the language switcher and the Enter the Commons button all pinned themselves to the same strip of screen, so at 320px wide the button that takes you into the world was completely buried under two other controls and the board's last rows were cut off. Those layers now stack above one another at every screen size, and the stack follows the sign-in bar as it changes height. (`/agora`) `[fix, improvement]`
- **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]`
+- **AR Studio: "Share live" rooms actually connect now, and the model tray answers the keyboard**: AR Studio can put several people in one AR scene at once: open a shared room, hand out the six-character code, and everyone places and moves models in the same space. On the live site that never worked. The page was the only realtime surface on three.ws that never named the server it should talk to, so the studio looked for one, found nothing, and told every user "Shared rooms are offline right now" while the server sat there ready to take the connection. It is now pointed at the same realtime service that /irl and /agora use, and two people joining the same code see each other and each other's models immediately. The failure path was hiding a second bug: when a room could not be reached, the studio threw an error partway through cleaning up, which left the room button stuck mid-state. Creating a room also stopped waiting for the connection before it declared success, so the invite link it promises to copy for you never made it to the clipboard. Both are fixed. Separately, the "Add models" tray is now fully keyboard-operable: left and right arrows move between the Recent, Yours, Community, Objects, and GLB link tabs, Home and End jump to the ends, and closing the tray or either dialog hands focus back to the button that opened it instead of dropping you at the top of the page. On a narrow phone the tab strip now fades at whichever edge still has tabs hidden behind it, so Objects and GLB link stop being invisible. A thumbnail that fails to load falls back to the same placeholder mark an image-less model uses, rather than a broken-image icon. (`/ar/studio`) `[fix, improvement]`
- **AR Studio: the language picker no longer sits on top of the dock controls**: On the AR Studio page the site-wide floating language picker landed in the bottom-right corner, directly over the right-hand end of the control dock, so the Clear button (and the buttons beside it on a phone) could not be tapped at all. The picker now lives in the studio's own top bar, where it is always reachable and leaves the dock its full width. It also shrinks instead of pushing its neighbours off screen on narrow phones, which fixes the same crowding anywhere else it appears in a tight header. The page description now also names every place models can come from: your forges, the community feed, the free CC0 object library, and any GLB link. (`/ar/studio`) `[fix, improvement]`
- **Atlas: a long search term no longer knocks the page sideways, and the clear button is tappable**: /atlas is the whole platform as one searchable map, and its search box had three rough edges. Searching for a very long unbroken term (a pasted URL, a run-on word) pushed the text past the edge of its box and gave the entire page a horizontal scrollbar, so the layout slid sideways under you while you typed. Long text now wraps wherever it has to, and the same rule keeps long route paths from stretching the result grid on a narrow phone. The box also drew two clear buttons side by side, the one the browser paints for a search field and the one the page draws, which every other search surface on the site already suppresses and this one had missed. The remaining clear button was a 16 by 18 pixel target, well under the minimum anyone should have to hit on a phone. It is now a 26 pixel square with its own hover and keyboard focus treatment. (`/atlas`) `[fix, improvement]`
- **Autopilot Activity keeps up when you switch agents, and its receipts link to the exact memory**: Autopilot Activity lists every action your agents took on your behalf, and it has an agent picker for narrowing that list to one of them. Picking a second agent while the first was still loading used to do nothing at all: the picker and the address bar moved to the new agent, but the request for it was never sent and the page kept showing the previous agent's actions, with no sign anything had gone wrong. Whichever agent you picked last now wins, however fast you switch. Two more repairs: each receipt cites the memories that motivated the action, and those links now scroll to the cited memory and highlight it instead of dropping you at the top of a long Knowledge list; and when an agent has no actions yet, the page sends you to that agent's own autopilot controls rather than the dashboard, which is where the setting you need actually lives. (`/autopilot-activity`) `[fix, improvement]`
- **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]`
+- **Avatar Wallet: the send button works again, and a failed reply tells you why**: The embeddable avatar that holds a Solana wallet had its send button covered by the floating language picker, so pressing it did nothing at any window size. The picker now lives in the page's own top bar, where it can be reached without sitting on top of the composer, and the same stray picker no longer floats over the avatar inside every embed. On a phone the fund-your-wallet notice was pinned to a fixed spot and landed on top of the wallet bar once that bar wrapped onto a second line; the two now flow one under the other at every width. When a reply fails, the page repeats the reason the chat service actually gave, such as being at capacity, instead of a generic apology, and offers a Try again control that re-sends the message without retyping it. On a desktop window the wallet bar, the conversation and the composer now sit in a readable centred column instead of stretching the full width of the screen, and the page carries a proper top-level heading for screen readers. (`/avatar-wallet-chat`) `[fix, improvement]`
- **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]`
- **Blockchain TVL by Chain is readable on a phone, and every chain in it is now a real link**: The chain leaderboard at /chains ranks 100 blockchains by total value locked and shows each one's dominance share of on-chain DeFi. On a phone the table was pinned to a fixed 540px width, so the only column that fit on screen was the chain name: the TVL and dominance figures, the entire point of the page, sat off the right edge behind a sideways scroll with nothing to hint they were there. The table now sizes itself to the screen, and all three columns read in full at 320px. Opening a chain's detail page was hidden in a similar way. Rows navigated on click but showed no clickable cursor, and the destination was not a link at all, so it could not be opened in a new tab, copied, followed from a screen reader's list of links, or seen by a search engine. Each chain name is now a genuine link, the row still follows it when you click anywhere along it, and the sortable column headers announce their sort state to screen readers. When the data provider fails, the page now offers a Try again button that refetches in place instead of a link that reloads everything, and it keeps its DeFiLlama attribution instead of going blank. If the provider reports nothing at all, the page says so rather than presenting a $0.00 total as though cross-chain DeFi had emptied out. (`/chains`) `[improvement, fix]`
- **CA to x402 now shows the momentum and risk read its own paid endpoint sells**: Paste a contract address at /ca2x402 and the resolver has always returned four timeframes of price change and a 0-to-100 risk score with the reasoning behind it, the same intel an agent gets when it pays the generated endpoint $0.01 USDC. The page quietly threw both away and rendered only the 24h number, so a buyer could not see what they were about to pay for. Both now render: a momentum strip across 5m, 1h, 6h and 24h that shows whether a move is building or fading, and a risk panel with the score, its level, and the depth, age, float and flow checks that produced it, each marked by severity. Both read at 320px. The primary Resolve button was also painting white text on the white accent, so the page's main action looked like an empty slab; its label is now legible in both themes. And the error card no longer says "Could not resolve" for a mistyped address: a typo, a token with no market, and a resolver outage each say which one happened. Over on /capture, the URL and settings fields get a real focus ring for keyboard users, where an outline reset had left only a faint border tint. (`/ca2x402`) `[improvement, fix]`
@@ -46,6 +50,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Seeding an agent from your X account no longer asks for permission to post as you**: Teaching an agent your voice from your public X posts required connecting X first, and that connect asked X for everything the platform can do with an account, including posting and uploading media on your behalf. Reading your posts once and writing as you are two different things to agree to, and only the first one is what seeding needs. The Connect button on the X card in Settings now asks X for read access to your profile and posts and nothing else, and it says so before you click. Posting is its own connect, offered right beside it and labelled as such, and Reconnect keeps whichever of the two you already chose rather than quietly widening it. If a connection cannot read your posts at all, the card now says which permission is missing and offers a reconnect instead of showing you a consent screen for a seed that could not run, and an agent trying to post through a read-only connection is told exactly that instead of failing against X with nothing to act on. Everything else about the lane is unchanged: nothing is read until you consent on a screen that lists what is read and stored, and revoking still deletes every memory the seeding produced. (`/settings`) `[improvement, security]`
- **Shared agent links keep their preview card through a chain hiccup**: The preview card for an on-chain agent is rendered on demand from the chain and the agent's manifest. When either read was slow or briefly unavailable, the card answered as if the agent did not exist, and social sites cached that answer for up to an hour, so a link to a real agent unfurled with no image at all. The card is now served either way and only kept for a minute when a read fell short, so the next crawl picks up the real thing. Alongside it, ten agent endpoints (the preview card and page, the oEmbed provider, memory sync, the action log, ask, delegate and team tasks) now answer a mistyped agent id with a clear, specific error instead of a generic server failure. `[fix, improvement]`
- **Sharing an agent link posts the agent's picture again**: Pasting a link to an agent into a chat app, a social post or a group thread is supposed to unfurl into a card with the agent's name, its description and a picture of it. For every agent that actually has an avatar picture, which is nearly all of them, the page that builds that card was crashing instead, so the link unfurled as a bare URL with nothing attached. The card now renders with the agent's own thumbnail, falls back to a freshly rendered portrait when an agent has no thumbnail yet, and an unknown or malformed agent link sends the visitor to the app instead of erroring. `[fix]`
+- **Skill Bundles: the page stops telling signed-out visitors they have no agents, and a failed request stops posing as an empty account**: /bundles is where you group several of an agent's skills into one purchase and price it from your own sales. It was asking the wrong endpoint for your agents: one that answers with a single agent rather than a list, and answers it even when nobody is signed in. Every visitor, signed in or not, was told "You have no agents yet" and pointed at the create page, and the sign-in prompt the page ships could never appear. It now asks who you are first, then lists what you own, so a signed-out visitor gets the sign-in prompt and an owner gets their agents. Three other things were wrong once you got in. A dropped request while loading your skills or your published bundles was rendered as "this agent has no priced skills" and "no bundles yet", which is a claim about your account rather than about the network; failures now say so plainly and carry a Retry that re-runs just that call, on the price panel too. Every price was labelled $THREE no matter which token the skill was actually priced in, and each price now carries its real token. And the price field was squeezed to 31 pixels wide on a 320 pixel screen, too narrow to read the number you were typing. The builder also explains the zeros when nobody has yet bought two or more of the selected skills, asks the server for a live "buyers better off" count as you move the price instead of showing a dot, and the page finally has documentation behind the link that has always pointed at it. (`/bundles`) `[fix, improvement, docs]`
- **Skill marketplace: installs are locked to your own clicks, and edits keep their star rating**: Three fixes to the skills marketplace. Installing or removing a skill now carries the same one-time security token every other account action does, so a page you happen to have open elsewhere can no longer quietly add skills to your account behind your back. Editing one of your published skills used to answer back with its rating blanked out, which made the detail panel show 'No ratings yet' on a skill people had actually rated until you reloaded; it now reports the real average and count. And when a skill you were paging past gets deleted or made private mid-scroll, 'Load more' stops cleanly instead of looping the first page of results back into the grid over and over. (`/marketplace`) `[fix, security]`
- **Solana agents from the outside registries get a real link preview, and a mistyped discover link stops erroring**: Two fixes to the Discover detail pages. Agents crawled from the outside Solana registries opened fine in the browser but shared as a nameless card: every one of them unfurled in Slack, Discord, X and iMessage with a generic three.ws title and the stock image, while the Ethereum-side agents in the same grid previewed properly. Those pages now carry the agent name, description and artwork, whether the link points at the mint or at its registry entry. Separately, a Discover link with a mistyped or truncated id answered with a server error and the page showed a vague "something went wrong"; it now says plainly that the item was not found and shows the Not found state, and an agent whose on-chain id is larger than the site could previously handle resolves instead of coming back empty. (`/discover`) `[fix]`
- **The $THREE deploy-burn ledger shows the real burns again**: The $THREE page counts 1,000 $THREE burned for every agent deployed on three.ws, and the ledger beneath that number is meant to list the recent deploys behind it. The query that fetched them asked for a column the agent table has never had, so it failed on every request and the code beside it turned that failure into an empty list: the lifetime burn total kept climbing past 3.1 million while the ledger sat blank, and the protocol activity feed was blanked the same way. Both now read the column that exists and list real deploys again, a failed panel query is written to the logs instead of quietly becoming a zero, and the holder count on the revenue-share view no longer disagrees with the one on the same page's stats panel. (`/dashboard/three-token`) `[fix]`
@@ -65,6 +70,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The assistant widget now tells you the truth when its chat lane is busy**: Two things on the assistant widget page reported the wrong thing. The live preview status line always read "Starting the live preview...", even once the avatar was up and running, because the translation pass reset it a moment after the page wrote it. Every state now carries its own translated line, so the preview says what it is actually doing, and it reports a real failure with a Retry button when the widget or its avatar does not come up instead of silently claiming success. Second, when the free chat lane was throttled the widget only said "Chat failed (HTTP 503)", and a signed-out visitor could even be told to sign in for a capacity problem the widget has no sign-in for. The chat endpoint now answers with a proper at-capacity result and how long to wait, and the widget shows that in full and points at the settings panel where a visitor can drop in their own Groq or OpenRouter key. Editing the builder no longer re-downloads the avatar on every keystroke. (`/assistant`) `[fix, improvement]`
- **The Avatar Artifact page now shows real avatars, not just its house portrait**: /avatar-artifact is the standalone viewer you can paste into any site as a bare iframe, but it only ever rendered one built-in procedural figure, so there was no way to point it at an actual avatar. It now takes ?agent=<id> to show any public agent's avatar, resolved live from the platform, or ?model=<glb url> to show a model directly from an allowed asset host. The agent's name becomes the heading and an Open profile link appears, the Copy embed button hands you an iframe of exactly what you are looking at, and avatars with no baked animation play the shared idle clip retargeted onto their own skeleton instead of standing in a T-pose. Every way it can fail now says what happened and what to do next: an id that matches no agent, an agent whose avatar is private or not created yet, a model URL from a host the viewer will not render, a model that would not load, and a browser without WebGL. Loading a large model reports its download progress instead of guessing, and a slow but healthy download is no longer cut off as a failure. With no parameters the page keeps its original portrait. (`/avatar-artifact`) `[feature, improvement, fix]`
- **The Avatar CLI page terminal is readable by a screen reader, and its recovery link is reachable by keyboard**: The /avatar-cli page teaches the four commands of @three-ws/avatar-cli, and the replayed terminal in its hero was marked up as one flat image. A screen reader announced a single caption for it and hid everything inside: the transcript itself, and the Replay button that restarts it. The transcript is now a named region a screen reader can read line by line, Replay is an ordinary button again, and the transcript reports itself as busy while it is still typing rather than being read half-written. Below it, the live viewer proves the embed snippet works, and when the component loader cannot be reached it swaps in a notice with a link to the web component reference. That link is the only way out of the failure, and it neither looked like a link nor showed a focus ring when tabbed to; it now does both. The scrollable code blocks, which the browser makes keyboard focusable, now show the site focus ring instead of a hairline default. And the copy button's clipboard fallback used to tell everyone to press Command C, including on Windows and Linux; it now names the shortcut for the keyboard you are actually on. (`/avatar-cli`) `[fix, improvement]`
+- **The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it**: The "Try it live" panel on /avatar-sdk offers four controls, and two of them only rewrote the code sample. Picking agent-3d (the full runtime) left a three-ws-viewer on screen, and flipping the auto-rotate switch printed an auto-rotate line into the snippet while the preview stood still. Both controls now drive the live preview: choosing the full runtime loads it and swaps it in with a note saying the heavy bundle is downloading, and if that download fails the panel says so and falls back to the lightweight viewer instead of leaving you on a broken control. Auto-rotate is a viewer-only attribute, so it is now disabled with a reason when the full runtime is selected, and the snippet you copy no longer contains an attribute that runtime ignores. Separately, on a 320px phone the page had been pushing its own content past the right edge of a window that cannot be scrolled sideways, cutting off the end of the hero, the install command and several code samples; each code block now scrolls inside its own frame and nothing leaves the page. If the 3D viewer cannot load at all, the page now explains that in place of each preview and links to the source, where it used to render three silent empty boxes. Copy buttons that a browser blocks from reaching the clipboard now select the snippet and say to press Ctrl+C rather than doing nothing visible, the framework example tabs can be moved through with the arrow keys, and the Avatar Studio demo button reports that it is opening the moment you press it. (`/avatar-sdk`) `[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 background agent mint says out loud whether it ran**: Every avatar that finishes a scan or a prompt is given a draft on-chain identity in the background. That step is deliberately best-effort, so it can never cost you your avatar, but it was also completely silent: whether it minted, was skipped because the deployment holds no minting key, or was switched off entirely, the logs looked identical, which is how a run of avatars can go by without anyone noticing the identity was never created. Each finished avatar now records the outcome of both chains, including the reason a leg was skipped. The documentation for the feature also gained a way to prove the whole path on a machine that cannot reach the public test-network faucet, which is routinely exhausted on shared build machines: run your own node with the real Metaplex programs, and the proof reports which node served it rather than handing back an explorer link that leads nowhere. (`/docs/draft-agent-mint`) `[improvement, docs]`
- **The BNB block race stops showing a dead chain's last number as if it were live**: The live block race compares BNB Chain, Base, Ethereum and Solana by measuring each one off a public RPC every few seconds, and it promises that a chain going quiet says so instead of freezing a fake number. The four lane cards kept that promise; the big headline number did not. When the BNB RPC stopped answering, the headline held its last reading at full brightness, kept claiming it was N times faster than Base, and the Updated stamp sat on "just now" no matter how long the outage ran. The headline now dims the moment the reading stops being live, labels it as last measured and prints its real age in seconds, and drops the speed comparison rather than race a stale number against a live one. The Updated stamp ages off the measurement time the server reports, and a poll that measured nothing no longer refreshes it. If every chain goes down at once the page now raises its outage notice and its Retry button, which previously could only ever appear before the first successful reading and so was unreachable during a real outage. Retry now shows it is working, makes a genuinely new request rather than reporting an older in-flight one's failure, and no longer sits underneath the floating helper widgets where the click was being swallowed. A lane that has never returned a sample says so plainly instead of pointing at a reading that is not on screen, each poll goes to the network instead of replaying a cached body up to fifteen seconds old, and screen readers now hear a lane announce a change of state rather than re-reading all four numbers twelve times a minute. (`/bnb-latency`) `[fix, improvement]`
@@ -87,6 +93,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Trending: muted text on the board is readable, and the Tip button that only navigated is gone**: Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states. (`/trending`) `[fix, improvement]`
- **Wallet reputation stops losing coins it never got around to judging**: The rollup that turns launch history into wallet reputation was judging 80 coins every five minutes while the intel firehose was recording about 32,000 new mints a day, so it fell roughly 8,000 coins a day behind. That backlog does not wait its turn: the rollup works oldest-first and only reaches back 14 days, which is exactly when retention prunes the record, so the tail of the queue aged out and those buyers never counted toward anyone’s reputation at all. 309,000 coins were sitting unjudged with the oldest already 8.4 days from the cliff. The per-run budget is now 400, which outruns the firehose several times over, drains the backlog within days and then idles. Scores across the smart-money surfaces get their full evidence base back. The operations health board also tracks the retention and reconstruct sweeps, so a stall in either is visible instead of showing up later as a symptom. `[fix, infra]`
- **Web search answers again, and a stray address can no longer tie up the server**: Three repairs on the public API. Web search had been answering nothing but an error: the question went to Google's grounded search as designed, but the model was given a single budget to both think and reply, spent all of it thinking, and came back empty, which we correctly reported as a failure and wrongly did so on every single query. Thinking now has its own allowance on top of the answer, and when a search does come back empty the log says why instead of leaving the next person to guess. Second, the machine-readable directory at the root of the site, the file other agents read to learn what three.ws sells, would hang forever on a handful of odd names rather than saying no such thing, and a request that never ends holds a server slot until it is cut off. Every unknown name now gets a plain not-found. Third, at checkout, a wallet that hands back a payment the network could never accept is now told so at the moment it happens, instead of the modal saying sending and the error arriving later from the payment processor. `[fix, security]`
+- **x402 Bazaar: the whole catalog is reachable, and the page stops blaming your connection for a provider that blocks browsers**: The Bazaar advertised a number that was really just the size of one page: it said "200 results" while the facilitators were carrying more than a thousand matching services, and there was no way to reach any of the rest. The count now reads "200 of 1465" and a Load more button walks the catalog a page at a time, on the site and through the list and search endpoints, which both take an offset now. Three other things were quietly wrong. A service description containing one very long unbroken word (a raw URL, an id) stretched the result grid wider than the window, which gave the page a horizontal scrollbar on a desktop and pushed the filter sidebar off the edge of a phone. Changing a filter while results were still loading was silently ignored, so the sidebar could end up describing a filter the cards on screen had never been through; the newest change now always wins. And the search box and every filter field had no visible outline when you tabbed to them, so a keyboard user could not tell where they were. Separately, when a provider refuses browser requests outright, which is most of the catalog, the payment modal used to tell you to check your connection and offer a retry that could never work. It now names the provider and the reason and points you at a server, an agent, or the CLI. (`/bazaar`) `[fix, improvement]`
- **You can now teach an agent your GitHub work without waiting on an OAuth app**: Seeding an agent from GitHub, the flow where you tick your profile, repositories and READMEs and the agent learns to talk about what you build, needed a GitHub sign-in button that this site never had switched on. The Connected accounts card said so honestly, and that was the end of it: an Unavailable tag and nothing you could do. There is now a second way in that needs nothing set up on our side. You create a read-only token on GitHub yourself, tick read:user and nothing more, paste it into Settings, and the same consent list, the same seeding and the same one-click deletion all work exactly as before. Consent still happens on GitHub's own screen, where you choose what the token may do, and we check what you chose: a token carrying access the feature cannot use, anything reaching your private repositories or able to delete them, is refused on the spot and never stored, with the offending permission named so you know which box to untick. The token is encrypted before it is saved and destroyed when you disconnect. One honest difference from the sign-in route: disconnecting deletes our copy and every memory it produced, but GitHub gives no way for a token to delete itself, so the confirmation now tells you to remove it on GitHub too and links you straight there. (`/settings`) `[feature, improvement]`
## 2026-08-15
diff --git a/data/changelog.json b/data/changelog.json
index 2c87dd9ce..b36f70bef 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,57 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-16",
+ "title": "The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it",
+ "summary": "The \"Try it live\" panel on /avatar-sdk offers four controls, and two of them only rewrote the code sample. Picking agent-3d (the full runtime) left a three-ws-viewer on screen, and flipping the auto-rotate switch printed an auto-rotate line into the snippet while the preview stood still. Both controls now drive the live preview: choosing the full runtime loads it and swaps it in with a note saying the heavy bundle is downloading, and if that download fails the panel says so and falls back to the lightweight viewer instead of leaving you on a broken control. Auto-rotate is a viewer-only attribute, so it is now disabled with a reason when the full runtime is selected, and the snippet you copy no longer contains an attribute that runtime ignores. Separately, on a 320px phone the page had been pushing its own content past the right edge of a window that cannot be scrolled sideways, cutting off the end of the hero, the install command and several code samples; each code block now scrolls inside its own frame and nothing leaves the page. If the 3D viewer cannot load at all, the page now explains that in place of each preview and links to the source, where it used to render three silent empty boxes. Copy buttons that a browser blocks from reaching the clipboard now select the snippet and say to press Ctrl+C rather than doing nothing visible, the framework example tabs can be moved through with the arrow keys, and the Avatar Studio demo button reports that it is opening the moment you press it.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/avatar-sdk"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Agent Wallet's trust panel stops sending you to a page that does not exist",
+ "summary": "The Trust tab of an agent wallet lists what the wallet's credibility score is built from, and offers the owner concrete ways to raise it. Two of those pointers led nowhere: \"Verify your on-chain identity\" and, for an already-registered agent, the \"On-chain identity\" evidence link both pointed at an address the site has never served, so clicking either one landed on a not-found page. They now go somewhere real. The suggestion opens the ERC-8004 registration wizard with the agent's avatar already filled in, and the evidence link opens that identity's public on-chain page. The wallet page also stopped reading its address twice when you open the Vanity tab, and the screen reader announcement was corrected: being signed out, or not owning an agent yet, is the page's normal answer rather than an emergency, so those two screens are now read in turn instead of interrupting whatever was being spoken.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/agent-wallet"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "AR Studio: \"Share live\" rooms actually connect now, and the model tray answers the keyboard",
+ "summary": "AR Studio can put several people in one AR scene at once: open a shared room, hand out the six-character code, and everyone places and moves models in the same space. On the live site that never worked. The page was the only realtime surface on three.ws that never named the server it should talk to, so the studio looked for one, found nothing, and told every user \"Shared rooms are offline right now\" while the server sat there ready to take the connection. It is now pointed at the same realtime service that /irl and /agora use, and two people joining the same code see each other and each other's models immediately. The failure path was hiding a second bug: when a room could not be reached, the studio threw an error partway through cleaning up, which left the room button stuck mid-state. Creating a room also stopped waiting for the connection before it declared success, so the invite link it promises to copy for you never made it to the clipboard. Both are fixed. Separately, the \"Add models\" tray is now fully keyboard-operable: left and right arrows move between the Recent, Yours, Community, Objects, and GLB link tabs, Home and End jump to the ends, and closing the tray or either dialog hands focus back to the button that opened it instead of dropping you at the top of the page. On a narrow phone the tab strip now fades at whichever edge still has tabs hidden behind it, so Objects and GLB link stop being invisible. A thumbnail that fails to load falls back to the same placeholder mark an image-less model uses, rather than a broken-image icon.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/ar/studio"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Skill Bundles: the page stops telling signed-out visitors they have no agents, and a failed request stops posing as an empty account",
+ "summary": "/bundles is where you group several of an agent's skills into one purchase and price it from your own sales. It was asking the wrong endpoint for your agents: one that answers with a single agent rather than a list, and answers it even when nobody is signed in. Every visitor, signed in or not, was told \"You have no agents yet\" and pointed at the create page, and the sign-in prompt the page ships could never appear. It now asks who you are first, then lists what you own, so a signed-out visitor gets the sign-in prompt and an owner gets their agents. Three other things were wrong once you got in. A dropped request while loading your skills or your published bundles was rendered as \"this agent has no priced skills\" and \"no bundles yet\", which is a claim about your account rather than about the network; failures now say so plainly and carry a Retry that re-runs just that call, on the price panel too. Every price was labelled $THREE no matter which token the skill was actually priced in, and each price now carries its real token. And the price field was squeezed to 31 pixels wide on a 320 pixel screen, too narrow to read the number you were typing. The builder also explains the zeros when nobody has yet bought two or more of the selected skills, asks the server for a live \"buyers better off\" count as you move the price instead of showing a dot, and the page finally has documentation behind the link that has always pointed at it.",
+ "tags": [
+ "fix",
+ "improvement",
+ "docs"
+ ],
+ "link": "/bundles"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "x402 Bazaar: the whole catalog is reachable, and the page stops blaming your connection for a provider that blocks browsers",
+ "summary": "The Bazaar advertised a number that was really just the size of one page: it said \"200 results\" while the facilitators were carrying more than a thousand matching services, and there was no way to reach any of the rest. The count now reads \"200 of 1465\" and a Load more button walks the catalog a page at a time, on the site and through the list and search endpoints, which both take an offset now. Three other things were quietly wrong. A service description containing one very long unbroken word (a raw URL, an id) stretched the result grid wider than the window, which gave the page a horizontal scrollbar on a desktop and pushed the filter sidebar off the edge of a phone. Changing a filter while results were still loading was silently ignored, so the sidebar could end up describing a filter the cards on screen had never been through; the newest change now always wins. And the search box and every filter field had no visible outline when you tabbed to them, so a keyboard user could not tell where they were. Separately, when a provider refuses browser requests outright, which is most of the catalog, the payment modal used to tell you to check your connection and offer a retry that could never work. It now names the provider and the reason and points you at a server, an agent, or the CLI.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/bazaar"
+ },
{
"date": "2026-08-16",
"title": "Atlas: a long search term no longer knocks the page sideways, and the clear button is tappable",
@@ -23942,6 +23993,16 @@
"security"
],
"link": "/play"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Avatar Wallet: the send button works again, and a failed reply tells you why",
+ "summary": "The embeddable avatar that holds a Solana wallet had its send button covered by the floating language picker, so pressing it did nothing at any window size. The picker now lives in the page's own top bar, where it can be reached without sitting on top of the composer, and the same stray picker no longer floats over the avatar inside every embed. On a phone the fund-your-wallet notice was pinned to a fixed spot and landed on top of the wallet bar once that bar wrapped onto a second line; the two now flow one under the other at every width. When a reply fails, the page repeats the reason the chat service actually gave, such as being at capacity, instead of a generic apology, and offers a Try again control that re-sends the message without retyping it. On a desktop window the wallet bar, the conversation and the composer now sit in a readable centred column instead of stretching the full width of the screen, and the page carries a proper top-level heading for screen readers.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/avatar-wallet-chat"
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index c9405d8fb..c3f0e9a7e 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T21:10:19.865Z",
+ "generated_at": "2026-08-16T22:10:38.249Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -16,6 +16,16 @@
"launch"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "launch",
+ "title": "Docs · Skill bundles",
+ "summary": "How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.",
+ "link": "/docs/skill-bundles",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -91,6 +101,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Agent Wallet's trust panel stops sending you to a page that does not exist",
+ "summary": "The Trust tab of an agent wallet lists what the wallet's credibility score is built from, and offers the owner concrete ways to raise it. Two of those pointers led nowhere: \"Verify your on-chain identity\" and, for an already-registered agent, the \"On-chain identity\" evidence link both pointed at an address the site has never served, so clicking either one landed on a not-found page. They now go somewhere real. The suggestion opens the ERC-8004 registration wizard with the agent's avatar already filled in, and the evidence link opens that identity's public on-chain page. The wallet page also stopped reading its address twice when you open the Vanity tab, and the screen reader announcement was corrected: being signed out, or not owning an agent yet, is the page's normal answer rather than an emergency, so those two screens are now read in turn instead of interrupting whatever was being spoken.",
+ "link": "/agent-wallet",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -132,6 +153,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "AR Studio: \"Share live\" rooms actually connect now, and the model tray answers the keyboard",
+ "summary": "AR Studio can put several people in one AR scene at once: open a shared room, hand out the six-character code, and everyone places and moves models in the same space. On the live site that never worked. The page was the only realtime surface on three.ws that never named the server it should talk to, so the studio looked for one, found nothing, and told every user \"Shared rooms are offline right now\" while the server sat there ready to take the connection. It is now pointed at the same realtime service that /irl and /agora use, and two people joining the same code see each other and each other's models immediately. The failure path was hiding a second bug: when a room could not be reached, the studio threw an error partway through cleaning up, which left the room button stuck mid-state. Creating a room also stopped waiting for the connection before it declared success, so the invite link it promises to copy for you never made it to the clipboard. Both are fixed. Separately, the \"Add models\" tray is now fully keyboard-operable: left and right arrows move between the Recent, Yours, Community, Objects, and GLB link tabs, Home and End jump to the ends, and closing the tray or either dialog hands focus back to the button that opened it instead of dropping you at the top of the page. On a narrow phone the tab strip now fades at whichever edge still has tabs hidden behind it, so Objects and GLB link stop being invisible. A thumbnail that fails to load falls back to the same placeholder mark an image-less model uses, rather than a broken-image icon.",
+ "link": "/ar/studio",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -186,6 +218,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Avatar Wallet: the send button works again, and a failed reply tells you why",
+ "summary": "The embeddable avatar that holds a Solana wallet had its send button covered by the floating language picker, so pressing it did nothing at any window size. The picker now lives in the page's own top bar, where it can be reached without sitting on top of the composer, and the same stray picker no longer floats over the avatar inside every embed. On a phone the fund-your-wallet notice was pinned to a fixed spot and landed on top of the wallet bar once that bar wrapped onto a second line; the two now flow one under the other at every width. When a reply fails, the page repeats the reason the chat service actually gave, such as being at capacity, instead of a generic apology, and offers a Try again control that re-sends the message without retyping it. On a desktop window the wallet bar, the conversation and the composer now sit in a readable centred column instead of stretching the full width of the screen, and the page carries a proper top-level heading for screen readers.",
+ "link": "/avatar-wallet-chat",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -432,6 +475,18 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Skill Bundles: the page stops telling signed-out visitors they have no agents, and a failed request stops posing as an empty account",
+ "summary": "/bundles is where you group several of an agent's skills into one purchase and price it from your own sales. It was asking the wrong endpoint for your agents: one that answers with a single agent rather than a list, and answers it even when nobody is signed in. Every visitor, signed in or not, was told \"You have no agents yet\" and pointed at the create page, and the sign-in prompt the page ships could never appear. It now asks who you are first, then lists what you own, so a signed-out visitor gets the sign-in prompt and an owner gets their agents. Three other things were wrong once you got in. A dropped request while loading your skills or your published bundles was rendered as \"this agent has no priced skills\" and \"no bundles yet\", which is a claim about your account rather than about the network; failures now say so plainly and carry a Retry that re-runs just that call, on the price panel too. Every price was labelled $THREE no matter which token the skill was actually priced in, and each price now carries its real token. And the price field was squeezed to 31 pixels wide on a 320 pixel screen, too narrow to read the number you were typing. The builder also explains the zeros when nobody has yet bought two or more of the selected skills, asks the server for a live \"buyers better off\" count as you move the price instead of showing a dot, and the page finally has documentation behind the link that has always pointed at it.",
+ "link": "/bundles",
+ "tags": [
+ "fix",
+ "improvement",
+ "docs"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -636,6 +691,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it",
+ "summary": "The \"Try it live\" panel on /avatar-sdk offers four controls, and two of them only rewrote the code sample. Picking agent-3d (the full runtime) left a three-ws-viewer on screen, and flipping the auto-rotate switch printed an auto-rotate line into the snippet while the preview stood still. Both controls now drive the live preview: choosing the full runtime loads it and swaps it in with a note saying the heavy bundle is downloading, and if that download fails the panel says so and falls back to the lightweight viewer instead of leaving you on a broken control. Auto-rotate is a viewer-only attribute, so it is now disabled with a reason when the full runtime is selected, and the snippet you copy no longer contains an attribute that runtime ignores. Separately, on a 320px phone the page had been pushing its own content past the right edge of a window that cannot be scrolled sideways, cutting off the end of the hero, the install command and several code samples; each code block now scrolls inside its own frame and nothing leaves the page. If the 3D viewer cannot load at all, the page now explains that in place of each preview and links to the source, where it used to render three silent empty boxes. Copy buttons that a browser blocks from reaching the clipboard now select the snippet and say to press Ctrl+C rather than doing nothing visible, the framework example tabs can be moved through with the arrow keys, and the Avatar Studio demo button reports that it is opening the moment you press it.",
+ "link": "/avatar-sdk",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -875,6 +941,17 @@
"security"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "x402 Bazaar: the whole catalog is reachable, and the page stops blaming your connection for a provider that blocks browsers",
+ "summary": "The Bazaar advertised a number that was really just the size of one page: it said \"200 results\" while the facilitators were carrying more than a thousand matching services, and there was no way to reach any of the rest. The count now reads \"200 of 1465\" and a Load more button walks the catalog a page at a time, on the site and through the list and search endpoints, which both take an offset now. Three other things were quietly wrong. A service description containing one very long unbroken word (a raw URL, an id) stretched the result grid wider than the window, which gave the page a horizontal scrollbar on a desktop and pushed the filter sidebar off the edge of a phone. Changing a filter while results were still loading was silently ignored, so the sidebar could end up describing a filter the cards on screen had never been through; the newest change now always wins. And the search box and every filter field had no visible outline when you tabbed to them, so a keyboard user could not tell where they were. Separately, when a provider refuses browser requests outright, which is most of the catalog, the payment modal used to tell you to check your connection and offer a retry that could never work. It now names the provider and the reason and points you at a server, an agent, or the CLI.",
+ "link": "/bazaar",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index bde3a817e..866cccf93 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -14,6 +14,14 @@
<category>launch</category>
<description>The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.</description>
</item>
+ <item>
+ <title>Docs · Skill bundles</title>
+ <link>https://three.ws/docs/skill-bundles</link>
+ <guid isPermaLink="false">2026-08-16:Docs · Skill bundles</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.</description>
+ </item>
<item>
<title>A coin world link now unfurls as the live world, and only ever points at three.ws</title>
<link>https://three.ws/play</link>
@@ -70,6 +78,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>Agent Wallet's trust panel stops sending you to a page that does not exist</title>
+ <link>https://three.ws/agent-wallet</link>
+ <guid isPermaLink="false">2026-08-16:Agent Wallet's trust panel stops sending you to a page that does not exist</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Trust tab of an agent wallet lists what the wallet's credibility score is built from, and offers the owner concrete ways to raise it. Two of those pointers led nowhere: &quot;Verify your on-chain identity&quot; and, for an already-registered agent, the &quot;On-chain identity&quot; evidence link both pointed at an address the site has never served, so clicking either one landed on a not-found page. They now go somewhere real. The suggestion opens the ERC-8004 registration wizard with the agent's avatar already filled in, and the evidence link opens that identity's public on-chain page. The wallet page also stopped reading its address twice when you open the Vanity tab, and the screen reader announcement was corrected: being signed out, or not owning an agent yet, is the page's normal answer rather than an emergency, so those two screens are now read in turn instead of interrupting whatever was being spoken.</description>
+ </item>
<item>
<title>Agora citizens show the craft they actually work, and the square fits a phone</title>
<link>https://three.ws/agora</link>
@@ -102,6 +118,14 @@
<category>fix</category>
<description>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.</description>
</item>
+ <item>
+ <title>AR Studio: &quot;Share live&quot; rooms actually connect now, and the model tray answers the keyboard</title>
+ <link>https://three.ws/ar/studio</link>
+ <guid isPermaLink="false">2026-08-16:AR Studio: &quot;Share live&quot; rooms actually connect now, and the model tray answers the keyboard</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>AR Studio can put several people in one AR scene at once: open a shared room, hand out the six-character code, and everyone places and moves models in the same space. On the live site that never worked. The page was the only realtime surface on three.ws that never named the server it should talk to, so the studio looked for one, found nothing, and told every user &quot;Shared rooms are offline right now&quot; while the server sat there ready to take the connection. It is now pointed at the same realtime service that /irl and /agora use, and two people joining the same code see each other and each other's models immediately. The failure path was hiding a second bug: when a room could not be reached, the studio threw an error partway through cleaning up, which left the room button stuck mid-state. Creating a room also stopped waiting for the connection before it declared success, so the invite link it promises to copy for you never made it to the clipboard. Both are fixed. Separately, the &quot;Add models&quot; tray is now fully keyboard-operable: left and right arrows move between the Recent, Yours, Community, Objects, and GLB link tabs, Home and End jump to the ends, and closing the tray or either dialog hands focus back to the button that opened it instead of dropping you at the top of the page. On a narrow phone the tab strip now fades at whichever edge still has tabs hidden behind it, so Objects and GLB link stop being invisible. A thumbnail that fails to load falls back to the same placeholder mark an image-less model uses, rather than a broken-image icon.</description>
+ </item>
<item>
<title>AR Studio: the language picker no longer sits on top of the dock controls</title>
<link>https://three.ws/ar/studio</link>
@@ -142,6 +166,14 @@
<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>Avatar Wallet: the send button works again, and a failed reply tells you why</title>
+ <link>https://three.ws/avatar-wallet-chat</link>
+ <guid isPermaLink="false">2026-08-16:Avatar Wallet: the send button works again, and a failed reply tells you why</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The embeddable avatar that holds a Solana wallet had its send button covered by the floating language picker, so pressing it did nothing at any window size. The picker now lives in the page's own top bar, where it can be reached without sitting on top of the composer, and the same stray picker no longer floats over the avatar inside every embed. On a phone the fund-your-wallet notice was pinned to a fixed spot and landed on top of the wallet bar once that bar wrapped onto a second line; the two now flow one under the other at every width. When a reply fails, the page repeats the reason the chat service actually gave, such as being at capacity, instead of a generic apology, and offers a Try again control that re-sends the message without retyping it. On a desktop window the wallet bar, the conversation and the composer now sit in a readable centred column instead of stretching the full width of the screen, and the page carries a proper top-level heading for screen readers.</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>
@@ -326,6 +358,14 @@
<category>fix</category>
<description>Pasting a link to an agent into a chat app, a social post or a group thread is supposed to unfurl into a card with the agent's name, its description and a picture of it. For every agent that actually has an avatar picture, which is nearly all of them, the page that builds that card was crashing instead, so the link unfurled as a bare URL with nothing attached. The card now renders with the agent's own thumbnail, falls back to a freshly rendered portrait when an agent has no thumbnail yet, and an unknown or malformed agent link sends the visitor to the app instead of erroring.</description>
</item>
+ <item>
+ <title>Skill Bundles: the page stops telling signed-out visitors they have no agents, and a failed request stops posing as an empty account</title>
+ <link>https://three.ws/bundles</link>
+ <guid isPermaLink="false">2026-08-16:Skill Bundles: the page stops telling signed-out visitors they have no agents, and a failed request stops posing as an empty account</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>/bundles is where you group several of an agent's skills into one purchase and price it from your own sales. It was asking the wrong endpoint for your agents: one that answers with a single agent rather than a list, and answers it even when nobody is signed in. Every visitor, signed in or not, was told &quot;You have no agents yet&quot; and pointed at the create page, and the sign-in prompt the page ships could never appear. It now asks who you are first, then lists what you own, so a signed-out visitor gets the sign-in prompt and an owner gets their agents. Three other things were wrong once you got in. A dropped request while loading your skills or your published bundles was rendered as &quot;this agent has no priced skills&quot; and &quot;no bundles yet&quot;, which is a claim about your account rather than about the network; failures now say so plainly and carry a Retry that re-runs just that call, on the price panel too. Every price was labelled $THREE no matter which token the skill was actually priced in, and each price now carries its real token. And the price field was squeezed to 31 pixels wide on a 320 pixel screen, too narrow to read the number you were typing. The builder also explains the zeros when nobody has yet bought two or more of the selected skills, asks the server for a live &quot;buyers better off&quot; count as you move the price instead of showing a dot, and the page finally has documentation behind the link that has always pointed at it.</description>
+ </item>
<item>
<title>Skill marketplace: installs are locked to your own clicks, and edits keep their star rating</title>
<link>https://three.ws/marketplace</link>
@@ -478,6 +518,14 @@
<category>fix</category>
<description>The /avatar-cli page teaches the four commands of @three-ws/avatar-cli, and the replayed terminal in its hero was marked up as one flat image. A screen reader announced a single caption for it and hid everything inside: the transcript itself, and the Replay button that restarts it. The transcript is now a named region a screen reader can read line by line, Replay is an ordinary button again, and the transcript reports itself as busy while it is still typing rather than being read half-written. Below it, the live viewer proves the embed snippet works, and when the component loader cannot be reached it swaps in a notice with a link to the web component reference. That link is the only way out of the failure, and it neither looked like a link nor showed a focus ring when tabbed to; it now does both. The scrollable code blocks, which the browser makes keyboard focusable, now show the site focus ring instead of a hairline default. And the copy button's clipboard fallback used to tell everyone to press Command C, including on Windows and Linux; it now names the shortcut for the keyboard you are actually on.</description>
</item>
+ <item>
+ <title>The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it</title>
+ <link>https://three.ws/avatar-sdk</link>
+ <guid isPermaLink="false">2026-08-16:The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The &quot;Try it live&quot; panel on /avatar-sdk offers four controls, and two of them only rewrote the code sample. Picking agent-3d (the full runtime) left a three-ws-viewer on screen, and flipping the auto-rotate switch printed an auto-rotate line into the snippet while the preview stood still. Both controls now drive the live preview: choosing the full runtime loads it and swaps it in with a note saying the heavy bundle is downloading, and if that download fails the panel says so and falls back to the lightweight viewer instead of leaving you on a broken control. Auto-rotate is a viewer-only attribute, so it is now disabled with a reason when the full runtime is selected, and the snippet you copy no longer contains an attribute that runtime ignores. Separately, on a 320px phone the page had been pushing its own content past the right edge of a window that cannot be scrolled sideways, cutting off the end of the hero, the install command and several code samples; each code block now scrolls inside its own frame and nothing leaves the page. If the 3D viewer cannot load at all, the page now explains that in place of each preview and links to the source, where it used to render three silent empty boxes. Copy buttons that a browser blocks from reaching the clipboard now select the snippet and say to press Ctrl+C rather than doing nothing visible, the framework example tabs can be moved through with the arrow keys, and the Avatar Studio demo button reports that it is opening the moment you press it.</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>
@@ -654,6 +702,14 @@
<category>fix</category>
<description>Three repairs on the public API. Web search had been answering nothing but an error: the question went to Google's grounded search as designed, but the model was given a single budget to both think and reply, spent all of it thinking, and came back empty, which we correctly reported as a failure and wrongly did so on every single query. Thinking now has its own allowance on top of the answer, and when a search does come back empty the log says why instead of leaving the next person to guess. Second, the machine-readable directory at the root of the site, the file other agents read to learn what three.ws sells, would hang forever on a handful of odd names rather than saying no such thing, and a request that never ends holds a server slot until it is cut off. Every unknown name now gets a plain not-found. Third, at checkout, a wallet that hands back a payment the network could never accept is now told so at the moment it happens, instead of the modal saying sending and the error arriving later from the payment processor.</description>
</item>
+ <item>
+ <title>x402 Bazaar: the whole catalog is reachable, and the page stops blaming your connection for a provider that blocks browsers</title>
+ <link>https://three.ws/bazaar</link>
+ <guid isPermaLink="false">2026-08-16:x402 Bazaar: the whole catalog is reachable, and the page stops blaming your connection for a provider that blocks browsers</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Bazaar advertised a number that was really just the size of one page: it said &quot;200 results&quot; while the facilitators were carrying more than a thousand matching services, and there was no way to reach any of the rest. The count now reads &quot;200 of 1465&quot; and a Load more button walks the catalog a page at a time, on the site and through the list and search endpoints, which both take an offset now. Three other things were quietly wrong. A service description containing one very long unbroken word (a raw URL, an id) stretched the result grid wider than the window, which gave the page a horizontal scrollbar on a desktop and pushed the filter sidebar off the edge of a phone. Changing a filter while results were still loading was silently ignored, so the sidebar could end up describing a filter the cards on screen had never been through; the newest change now always wins. And the search box and every filter field had no visible outline when you tabbed to them, so a keyboard user could not tell where they were. Separately, when a provider refuses browser requests outright, which is most of the catalog, the payment modal used to tell you to check your connection and offer a retry that could never work. It now names the provider and the reason and points you at a server, an agent, or the CLI.</description>
+ </item>
<item>
<title>You can now teach an agent your GitHub work without waiting on an OAuth app</title>
<link>https://three.ws/settings</link>
diff --git a/public/features.json b/public/features.json
index b9736e0a2..009130f17 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T21:10:19.687Z",
+ "generated_at": "2026-08-16T22:10:38.040Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -2947,6 +2947,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/skill-bundles",
+ "title": "Docs · Skill bundles",
+ "description": "How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.",
+ "added": "2026-08-16",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/avatar-artifact",
"title": "Docs · Avatar Artifact viewer",