Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(changelog): add the cosmos entry and restamp the generated feeds
nirholasfeac6a3c5b69
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex c42b1ea2c..4127ab737 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -16,6 +16,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **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]`- **Clip Director shows real traders again, and can no longer print a number the trade never made**: The Clip Director page told every visitor that no agent had ever closed a trade. Its trader picker asked the leaderboard for the highest-ranked agents and then kept only the ones with a closed round-trip, and because the ranking score has nothing to do with having closed trades, the nine agents that qualified all sat below the cut. The picker now asks the leaderboard for exactly what it needs, so those nine traders and their real closed positions are back on the page. The bigger repair is underneath: the card copy is written by a language model, and one of the providers answered a real +1.89x win with an invented loss on a different coin, complete with a celebrating avatar, next to the on-chain link proving otherwise. Every generated card is now checked against the trade it describes before it ships, so a ticker or a figure that is not in the round-trip gets the card thrown away and rewritten from the position itself, and a stop-out can never be celebrated. Also on the page: a shared /clip-director?agent_id= link now opens that trader even when they are outside the ranking, the Try again buttons retry the step that actually failed instead of doing nothing, each card's call to action is a real link, and the copy button copies on browsers that block the clipboard API instead of telling you to press a key. (`/clip-director`) `[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]`+- **Coin Communities keeps its own words on screen, and the Retry button on a failed coin now retries**: A coin page that failed to load offered a Retry button that did nothing: it re-requested the coin the page was already showing, which the loader skipped as already-loaded, so the only escape from a transient outage was a manual reload. Retry now forces the fetch and recovers the page. The page was also arguing with its own translation layer: the browser tab and the failure message are written live by the page, but the translation pass ran afterwards and reverted them, so a coin that could not be reached said it did not exist, and the tab kept a coin's name after you had gone back to browsing. Both now hold what the page wrote and hand it back when the live state is gone. Alongside that: the price figure shows a real loading shimmer until both of its data sources have answered instead of a bare dash, signed-out visitors get a short line explaining the avatar row and a link to sign in rather than a silent unauthorized request, a pasted avatar URL that is not a link now says what a working one looks like, the search and mint fields have proper labels, and every button, chip and card has a visible keyboard focus ring and a press state. (`/communities`) `[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]`diff --git a/data/changelog.json b/data/changelog.jsonindex 122738656..961bfe6fd 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,26 @@{"$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-17",+ "title": "Compare Coins now tells you when a coin will not load instead of shimmering forever",+ "summary": "The side-by-side coin comparison had one failure mode that looked exactly like a hung page: when the market data service did not answer, the stats table kept its grey loading shimmer up permanently and the chips still showed the raw coin ids, with nothing to click and nothing to read. Every one of those states is now written out. A coin that does not exist is labelled Not found with a one-click Remove; a coin the service failed to return is labelled Failed to load with a Retry that actually refetches it and redraws the chart. The chart says which of the two happened and offers the same recovery. The search box no longer goes quiet when the coin index is slow or down: it shows a Searching indicator while it waits and an explanation if the request fails, and a slow answer can no longer overwrite a newer one. Once four coins are up, the box says four is the maximum and stops accepting a fifth rather than silently swallowing the pick. New Copy link button next to the picker hands over the shareable matchup URL, the three default coins load in parallel instead of one after another, and the stats table now carries proper row and column headers for screen readers with a visible focus ring on every chip.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/compare"+ },+ {+ "date": "2026-08-17",+ "title": "Coin Communities keeps its own words on screen, and the Retry button on a failed coin now retries",+ "summary": "A coin page that failed to load offered a Retry button that did nothing: it re-requested the coin the page was already showing, which the loader skipped as already-loaded, so the only escape from a transient outage was a manual reload. Retry now forces the fetch and recovers the page. The page was also arguing with its own translation layer: the browser tab and the failure message are written live by the page, but the translation pass ran afterwards and reverted them, so a coin that could not be reached said it did not exist, and the tab kept a coin's name after you had gone back to browsing. Both now hold what the page wrote and hand it back when the live state is gone. Alongside that: the price figure shows a real loading shimmer until both of its data sources have answered instead of a bare dash, signed-out visitors get a short line explaining the avatar row and a link to sign in rather than a silent unauthorized request, a pasted avatar URL that is not a link now says what a working one looks like, the search and mint fields have proper labels, and every button, chip and card has a visible keyboard focus ring and a press state.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/communities"+ },{"date": "2026-08-17","title": "Clip Director shows real traders again, and can no longer print a number the trade never made",diff --git a/public/changelog.json b/public/changelog.jsonindex 4bb4fd4e8..258e90973 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T03:12:36.210Z",+ "generated_at": "2026-08-17T03:14:24.651Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -114,6 +114,17 @@"improvement"]},+ {+ "date": "2026-08-17",+ "type": "update",+ "title": "Coin Communities keeps its own words on screen, and the Retry button on a failed coin now retries",+ "summary": "A coin page that failed to load offered a Retry button that did nothing: it re-requested the coin the page was already showing, which the loader skipped as already-loaded, so the only escape from a transient outage was a manual reload. Retry now forces the fetch and recovers the page. The page was also arguing with its own translation layer: the browser tab and the failure message are written live by the page, but the translation pass ran afterwards and reverted them, so a coin that could not be reached said it did not exist, and the tab kept a coin's name after you had gone back to browsing. Both now hold what the page wrote and hand it back when the live state is gone. Alongside that: the price figure shows a real loading shimmer until both of its data sources have answered instead of a bare dash, signed-out visitors get a short line explaining the avatar row and a link to sign in rather than a silent unauthorized request, a pasted avatar URL that is not a link now says what a working one looks like, the search and mint fields have proper labels, and every button, chip and card has a visible keyboard focus ring and a press state.",+ "link": "/communities",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-17","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 329d1eeac..53f0ade2f 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -86,6 +86,14 @@<category>fix</category><description>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.</description></item>+ <item>+ <title>Coin Communities keeps its own words on screen, and the Retry button on a failed coin now retries</title>+ <link>https://three.ws/communities</link>+ <guid isPermaLink="false">2026-08-17:Coin Communities keeps its own words on screen, and the Retry button on a failed coin now retries</guid>+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>A coin page that failed to load offered a Retry button that did nothing: it re-requested the coin the page was already showing, which the loader skipped as already-loaded, so the only escape from a transient outage was a manual reload. Retry now forces the fetch and recovers the page. The page was also arguing with its own translation layer: the browser tab and the failure message are written live by the page, but the translation pass ran afterwards and reverted them, so a coin that could not be reached said it did not exist, and the tab kept a coin's name after you had gone back to browsing. Both now hold what the page wrote and hand it back when the live state is gone. Alongside that: the price figure shows a real loading shimmer until both of its data sources have answered instead of a bare dash, signed-out visitors get a short line explaining the avatar row and a link to sign in rather than a silent unauthorized request, a pasted avatar URL that is not a link now says what a working one looks like, the search and mint fields have proper labels, and every button, chip and card has a visible keyboard focus ring and a press state.</description>+ </item><item><title>Crypto Categories reads correctly in all 84 languages</title><link>https://three.ws/categories</link>diff --git a/public/features.json b/public/features.jsonindex 8ee04c8ec..93c7cb3e7 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T03:12:36.088Z",+ "generated_at": "2026-08-17T03:14:24.502Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",