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 create-agent keyboard fix and rebuild the feeds

nirholas52562033aebc
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 57a5e2851..e3aeeb96a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -14,7 +14,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Blockchain TVL by Chain is readable again, and its numbers can be copied**: The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it. (`/chains`) `[fix, improvement]`
- **Chat stops hiding two nav links, and says something useful when a reply fails**: The chat at /chat was audited end to end in a real browser: loading it cold, sending a message on the free built-in lane and getting a reply back, following every link in the header and footer, and the empty, loading, error and populated states at phone, tablet and desktop widths. The header was covering itself: the centred site links sat on top of the wallet controls, so Features and Docs were partly hidden and could not be clicked at any desktop width, and between tablet and laptop widths there was no way to reach those links at all. The links now sit in the row with everything else, and below the width where they fit they move into the menu. The footer had been shipping a mangled copyright line (a leftover encoding accident that printed stray characters where the copyright symbol belongs). When a reply could not be sent, the thread printed the browser's own words, Failed to fetch; it now says what happened, that nothing was sent, and how to retry, in a message styled as an error rather than as a quieter reply. A rate-limited reply used to say Try again in 79445s; it now says the wait in hours or minutes and, when the free daily allowance is the thing that ran out, points at adding your own provider key. Icon-only buttons across the header and each message (share, model settings, copy, edit, regenerate, delete) now carry names for screen readers, and the page title and description finally describe the page. (`/chat`) `[fix, improvement]`
- **Choreographer share links are readable again, and the studio fits a phone**: The gesture composer at /choreograph was audited end to end in a real browser: loading a starter routine, adding and reordering beats, retiming and repointing a step, previewing the whole performance on a live avatar, scrubbing the timeline, sharing a link, and saving to a real agent, at phone, tablet and desktop widths. Copy share link used to hand you a link with the routine name escaped twice, so a routine called The pitch travelled as The%2520pitch: it worked, but it looked broken, and it invited people to tidy it up and break it for real. Links now carry the routine as you can read it, and every link shared before today still opens. A routine whose name ended in the loop marker came back from a link under the wrong name and looping when it should not. On a 320 pixel phone, opening either of the two code panels pushed the whole page sideways; the code block now scrolls on its own instead. Pressing the transport a second time while the first play was still loading its clips said Pause but started a second load; it now stops the one in progress, and deleting the last beat mid-load can no longer bring an avatar back onto a stage the routine has left. Signed-out visitors also no longer see a failed request in the browser console on first paint. (`/choreograph`) `[fix, improvement]`
+- **Coin Clash stops claiming it is connecting when it has gone offline**: The live indicator at the top of Coin Clash sat on a pulsing amber "connecting" forever, even once the page had established that the battle service was offline and had stopped trying to reach it. The cause was the page's own translation pass: the line of copy holding the indicator is translatable, and applying it rewrote that whole line back to the wording it shipped with, wiping out the status the page had just worked out. The indicator now survives a translation pass, so it reads offline when the arena is offline and live when battles are running. The same fault was quietly affecting the leaderboard, labor market and signals pages, and is fixed for all four. Two more repairs on Coin Clash: when the arena cannot be reached at all, the error card now explains that in words you can act on and offers Try again, instead of showing the browser's raw "Failed to fetch"; and on a narrow phone the Arena, War Records and Communities tabs wrap onto a second row rather than running off the right edge, where the Communities tab was cut in half and unreachable. (`/clash`) `[fix, improvement]`
- **Crypto Categories reads correctly in all 84 languages**: The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one. (`/categories`) `[fix]`
+- **My Collection loads visibly, keeps its counts, and never mangles an agent's name**: The collection page had a loading state nobody could see: the shimmer placeholders were drawn inside a container the page kept hidden until the data had already arrived, so a slow connection got a blank stretch of nothing instead. The tabs, the placeholders and the counts now appear from the first frame. The counts next to Skills and Subscriptions used to vanish at random, because the page's own translation pass could overwrite the tab label a split second after the number was written into it; the count now lives in its own slot and survives. A skill published by an agent whose name contains a quotation mark or an angle bracket rendered as broken markup rather than as the name, and a publisher who earned a vanity wallet address had it shown as an ordinary one, because the card was reading a field the collection endpoint does not return. Both are fixed, so tipping a creator from your collection now shows the wallet they actually have. Empty states are centred under the tabs instead of squeezed into the first column, both of them now point you at the marketplace, the Retry button on a failed load is a real button rather than a raw grey box, and the whole page is keyboard-navigable: arrow keys move between tabs, Home and End jump to the ends, and every link and button shows a clear focus ring. (`/collection`) `[fix, improvement]`
- **Pausing a skill bundle is no longer permanent, and every tooltip fits on a phone**: The bundle builder at /bundles was audited end to end in a real browser: signing in, picking priced skills, the price panel and its backtest, publishing, the published list, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that Deactivate was a one-way door. It hid the bundle from buyers, which is correct, but it also removed it from the only page that could put it back, so a misclick permanently retired a bundle you had just priced. The button is now called Pause, a paused bundle stays on the page dimmed and clearly marked, and a Reactivate button puts it back on sale. Buyers still never see a paused bundle: the public list is unchanged, and paused ones are returned only to a signed-in owner of that agent. The small question-mark tooltips that explain every number on the page were also cut off at the edge of a phone screen, so four of the seven explanations were partly unreadable at 320 pixels wide; they now shift to stay on screen at any width. The sum of the parts and the suggested price were cramped into a broken-looking two-line squeeze on a narrow screen and now stack cleanly. Finally, a pricing error raised by one agent no longer sits on screen after you switch to another agent, where it read as a verdict on an agent it had never looked at. (`/bundles`) `[fix, improvement]`
- **The avatar SDK bundle we ship is now built from the code we deploy**: The <agent-3d> runtime that sites load from three.ws is a single bundled file, and the production build never rebuilt it. It was copied from whatever the build machine happened to have on disk, which could be days older than the code being deployed, so a fix to the avatar element could ship everywhere else on the site and quietly not reach the SDK. The deploy now rebuilds that bundle from the same commit as the rest of the release, every time. Nothing to change on your side: existing embeds keep working and simply pick up the current runtime. (`/avatar-sdk`) `[fix, sdk, infra]`
- **The Characters gallery pages past the first screen, and stops fighting dark mode**: The character gallery at /characters was audited end to end in a real browser: loading the feed, both sort orders, search, Load more, following a card through to its character page, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that the Top sort was quietly broken. Sorting by most-chatted read the right first screen, but pressing Load more asked the server to continue from the wrong place, so the feed ended after eight characters out of more than two thousand. It now pages all the way through, in order. The page also ignored the site theme: it painted a fixed light-blue background under the dark header no matter what you had chosen, which is now fixed in both directions, and wallet addresses on the cards were nearly invisible on a light background everywhere they appear on the site. The gallery filled only a narrow strip down the middle of a desktop screen and now uses the full width, up to four cards across. If the feed failed to load you got one line of grey text and no way to retry; there is now a proper message with a Try again button, a failed Load more keeps the characters you already had, and searching for something with no matches offers to clear the search rather than leaving you at a dead end. Pressing Top while the first screen was still loading used to light up the button and change nothing, so you were left reading New results under a Top heading. The search box had no label for screen readers, the sort buttons never showed which was selected, and neither they nor Load more showed a focus outline for anyone navigating by keyboard. Keyboard users can also now skip the header and land in the gallery. Finally, the feed itself is several times faster to answer on a cold request, because it no longer counts every conversation of every published character just to show you twenty-four of them. (`/characters`) `[fix, improvement]`
diff --git a/pages/character-library.html b/pages/character-library.html
index b76b72571..0df6e1208 100644
--- a/pages/character-library.html
+++ b/pages/character-library.html
@@ -106,7 +106,11 @@
background: radial-gradient(120% 120% at 50% 20%, rgba(255,255,255,.05), rgba(0,0,0,.25));
}
.ch-card-mv { width: 100%; height: 100%; --poster-color: transparent; background: transparent; }
- .ch-card-poster { width: 100%; height: 100%; object-fit: contain; display: block; }
+ .ch-card-poster {
+ width: 100%; height: 100%; object-fit: contain; display: block;
+ pointer-events: none; transition: opacity .35s ease;
+ }
+ model-viewer[data-loaded="1"] .ch-card-poster { opacity: 0; }
.ch-card-pill {
position: absolute; top: 10px; left: 10px; z-index: 2;
font-family: var(--font-mono); font-size: 10px; letter-spacing: .05em; text-transform: uppercase;
diff --git a/pages/create-agent.html b/pages/create-agent.html
index 8cc0223b2..b4482bb32 100644
--- a/pages/create-agent.html
+++ b/pages/create-agent.html
@@ -215,12 +215,35 @@
}
.step-pip {
display: flex;
+ }
+ /* The pip's interactive core is a real button so completed steps are
+ reachable by keyboard, not just by mouse. Reset it to look exactly
+ like the inline text row it replaced. */
+ .step-pip-btn {
+ display: flex;
align-items: center;
gap: 9px;
color: var(--muted);
font-size: 12.5px;
font-weight: 500;
white-space: nowrap;
+ appearance: none;
+ background: none;
+ border: 0;
+ margin: 0;
+ padding: 0;
+ font-family: inherit;
+ cursor: default;
+ }
+ .step-pip-btn:disabled {
+ /* Not-yet-reached steps are inert, but must not read as greyed-out
+ chrome: the pip is the progress indicator either way. */
+ opacity: 1;
+ }
+ .step-pip-btn:focus-visible {
+ outline: 2px solid var(--accent);
+ outline-offset: 3px;
+ border-radius: 999px;
}
.step-pip .num {
width: 26px;
@@ -240,7 +263,7 @@
transform 0.2s;
flex: 0 0 auto;
}
- .step-pip[data-state='active'] {
+ .step-pip[data-state='active'] .step-pip-btn {
color: var(--text);
}
.step-pip[data-state='active'] .num {
@@ -249,7 +272,7 @@
color: var(--accent-ink);
transform: scale(1.06);
}
- .step-pip[data-state='done'] {
+ .step-pip[data-state='done'] .step-pip-btn {
color: var(--text);
}
.step-pip[data-state='done'] .num {
@@ -257,12 +280,16 @@
border-color: rgba(74, 222, 128, 0.5);
color: var(--ok);
}
- .step-pip[data-clickable='true'] {
+ .step-pip[data-clickable='true'] .step-pip-btn {
cursor: pointer;
}
- .step-pip[data-clickable='true']:hover .num {
+ .step-pip[data-clickable='true'] .step-pip-btn:hover .num,
+ .step-pip[data-clickable='true'] .step-pip-btn:focus-visible .num {
border-color: var(--accent);
}
+ .step-pip[data-clickable='true'] .step-pip-btn:active .num {
+ transform: scale(0.94);
+ }
.step-pip .label {
display: none;
}
@@ -1608,12 +1635,14 @@
you can always swap it later.
</p>
- <div class="model-tabs" role="tablist">
+ <div class="model-tabs" role="tablist" aria-label="Choose where the 3D body comes from">
<button
type="button"
class="model-tab is-active"
data-pane="starter"
role="tab"
+ id="model-tab-starter"
+ aria-controls="model-pane-starter"
aria-selected="true"
data-i18n="create_agent.starter_library">
Starter library
@@ -1623,7 +1652,10 @@
class="model-tab"
data-pane="library"
role="tab"
+ id="model-tab-library"
+ aria-controls="model-pane-library"
aria-selected="false"
+ tabindex="-1"
data-i18n="create_agent.my_avatars">
My avatars
</button>
@@ -1632,7 +1664,10 @@
class="model-tab"
data-pane="upload"
role="tab"
+ id="model-tab-upload"
+ aria-controls="model-pane-upload"
aria-selected="false"
+ tabindex="-1"
data-i18n="create_agent.upload_your_own">
Upload your own
</button>
@@ -1641,17 +1676,34 @@
class="model-tab"
data-pane="skip"
role="tab"
+ id="model-tab-skip"
+ aria-controls="model-pane-skip"
aria-selected="false"
+ tabindex="-1"
data-i18n="create_agent.add_later">
Add later
</button>
</div>
- <div class="model-pane is-active" data-pane="starter">
+ <div
+ class="model-pane is-active"
+ data-pane="starter"
+ id="model-pane-starter"
+ role="tabpanel"
+ aria-labelledby="model-tab-starter"
+ tabindex="0"
+ >
<div class="starter-grid" id="starter-grid"></div>
</div>
- <div class="model-pane" data-pane="library">
+ <div
+ class="model-pane"
+ data-pane="library"
+ id="model-pane-library"
+ role="tabpanel"
+ aria-labelledby="model-tab-library"
+ tabindex="0"
+ >
<div
class="starter-grid"
id="library-grid"
@@ -1659,7 +1711,14 @@
></div>
</div>
- <div class="model-pane" data-pane="upload">
+ <div
+ class="model-pane"
+ data-pane="upload"
+ id="model-pane-upload"
+ role="tabpanel"
+ aria-labelledby="model-tab-upload"
+ tabindex="0"
+ >
<div
class="dropzone"
id="dropzone"
@@ -1696,7 +1755,14 @@
/>
</div>
- <div class="model-pane" data-pane="skip">
+ <div
+ class="model-pane"
+ data-pane="skip"
+ id="model-pane-skip"
+ role="tabpanel"
+ aria-labelledby="model-tab-skip"
+ tabindex="0"
+ >
<p class="panel-help" style="margin: 6px 0 0" data-i18n="create_agent.a_3d_avatar_is_how_people_recognize">
A 3D avatar is how people recognize and connect with your agent
across three.ws — we strongly recommend giving it one now from
diff --git a/public/changelog.json b/public/changelog.json
index 0bb677913..b285b74f9 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T02:55:03.975Z",
+ "generated_at": "2026-08-17T02:59:54.492Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -92,6 +92,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "Coin Clash stops claiming it is connecting when it has gone offline",
+ "summary": "The live indicator at the top of Coin Clash sat on a pulsing amber \"connecting\" forever, even once the page had established that the battle service was offline and had stopped trying to reach it. The cause was the page's own translation pass: the line of copy holding the indicator is translatable, and applying it rewrote that whole line back to the wording it shipped with, wiping out the status the page had just worked out. The indicator now survives a translation pass, so it reads offline when the arena is offline and live when battles are running. The same fault was quietly affecting the leaderboard, labor market and signals pages, and is fixed for all four. Two more repairs on Coin Clash: when the arena cannot be reached at all, the error card now explains that in words you can act on and offers Try again, instead of showing the browser's raw \"Failed to fetch\"; and on a narrow phone the Arena, War Records and Communities tabs wrap onto a second row rather than running off the right edge, where the Communities tab was cut in half and unreachable.",
+ "link": "/clash",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-17",
"type": "update",
@@ -102,6 +113,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "My Collection loads visibly, keeps its counts, and never mangles an agent's name",
+ "summary": "The collection page had a loading state nobody could see: the shimmer placeholders were drawn inside a container the page kept hidden until the data had already arrived, so a slow connection got a blank stretch of nothing instead. The tabs, the placeholders and the counts now appear from the first frame. The counts next to Skills and Subscriptions used to vanish at random, because the page's own translation pass could overwrite the tab label a split second after the number was written into it; the count now lives in its own slot and survives. A skill published by an agent whose name contains a quotation mark or an angle bracket rendered as broken markup rather than as the name, and a publisher who earned a vanity wallet address had it shown as an ordinary one, because the card was reading a field the collection endpoint does not return. Both are fixed, so tipping a creator from your collection now shows the wallet they actually have. Empty states are centred under the tabs instead of squeezed into the first column, both of them now point you at the marketplace, the Retry button on a failed load is a real button rather than a raw grey box, and the whole page is keyboard-navigable: arrow keys move between tabs, Home and End jump to the ends, and every link and button shows a clear focus ring.",
+ "link": "/collection",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-17",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index abbfb9e76..932718c04 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -70,6 +70,14 @@
<category>fix</category>
<description>The gesture composer at /choreograph was audited end to end in a real browser: loading a starter routine, adding and reordering beats, retiming and repointing a step, previewing the whole performance on a live avatar, scrubbing the timeline, sharing a link, and saving to a real agent, at phone, tablet and desktop widths. Copy share link used to hand you a link with the routine name escaped twice, so a routine called The pitch travelled as The%2520pitch: it worked, but it looked broken, and it invited people to tidy it up and break it for real. Links now carry the routine as you can read it, and every link shared before today still opens. A routine whose name ended in the loop marker came back from a link under the wrong name and looping when it should not. On a 320 pixel phone, opening either of the two code panels pushed the whole page sideways; the code block now scrolls on its own instead. Pressing the transport a second time while the first play was still loading its clips said Pause but started a second load; it now stops the one in progress, and deleting the last beat mid-load can no longer bring an avatar back onto a stage the routine has left. Signed-out visitors also no longer see a failed request in the browser console on first paint.</description>
</item>
+ <item>
+ <title>Coin Clash stops claiming it is connecting when it has gone offline</title>
+ <link>https://three.ws/clash</link>
+ <guid isPermaLink="false">2026-08-17:Coin Clash stops claiming it is connecting when it has gone offline</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The live indicator at the top of Coin Clash sat on a pulsing amber &quot;connecting&quot; forever, even once the page had established that the battle service was offline and had stopped trying to reach it. The cause was the page's own translation pass: the line of copy holding the indicator is translatable, and applying it rewrote that whole line back to the wording it shipped with, wiping out the status the page had just worked out. The indicator now survives a translation pass, so it reads offline when the arena is offline and live when battles are running. The same fault was quietly affecting the leaderboard, labor market and signals pages, and is fixed for all four. Two more repairs on Coin Clash: when the arena cannot be reached at all, the error card now explains that in words you can act on and offers Try again, instead of showing the browser's raw &quot;Failed to fetch&quot;; and on a narrow phone the Arena, War Records and Communities tabs wrap onto a second row rather than running off the right edge, where the Communities tab was cut in half and unreachable.</description>
+ </item>
<item>
<title>Crypto Categories reads correctly in all 84 languages</title>
<link>https://three.ws/categories</link>
@@ -78,6 +86,14 @@
<category>fix</category>
<description>The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one.</description>
</item>
+ <item>
+ <title>My Collection loads visibly, keeps its counts, and never mangles an agent's name</title>
+ <link>https://three.ws/collection</link>
+ <guid isPermaLink="false">2026-08-17:My Collection loads visibly, keeps its counts, and never mangles an agent's name</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The collection page had a loading state nobody could see: the shimmer placeholders were drawn inside a container the page kept hidden until the data had already arrived, so a slow connection got a blank stretch of nothing instead. The tabs, the placeholders and the counts now appear from the first frame. The counts next to Skills and Subscriptions used to vanish at random, because the page's own translation pass could overwrite the tab label a split second after the number was written into it; the count now lives in its own slot and survives. A skill published by an agent whose name contains a quotation mark or an angle bracket rendered as broken markup rather than as the name, and a publisher who earned a vanity wallet address had it shown as an ordinary one, because the card was reading a field the collection endpoint does not return. Both are fixed, so tipping a creator from your collection now shows the wallet they actually have. Empty states are centred under the tabs instead of squeezed into the first column, both of them now point you at the marketplace, the Retry button on a failed load is a real button rather than a raw grey box, and the whole page is keyboard-navigable: arrow keys move between tabs, Home and End jump to the ends, and every link and button shows a clear focus ring.</description>
+ </item>
<item>
<title>Pausing a skill bundle is no longer permanent, and every tooltip fits on a phone</title>
<link>https://three.ws/bundles</link>
diff --git a/public/features.json b/public/features.json
index 1ed8bcc16..780cb6ae3 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T02:55:03.763Z",
+ "generated_at": "2026-08-17T02:59:54.342Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",