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(feeds): regenerate the changelog and features outputs for this batch

nirholas06a423183998
diff --git a/public/changelog.json b/public/changelog.json
index 30acd8ade..093632782 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T01:33:22.537Z",
+ "generated_at": "2026-08-17T01:41:05.174Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -81,6 +81,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "The Characters gallery pages past the first screen, and stops fighting dark mode",
+ "summary": "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.",
+ "link": "/characters",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-17",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 5b4d2f3e7..9b42701bb 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -62,6 +62,14 @@
<category>fix</category>
<description>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.</description>
</item>
+ <item>
+ <title>The Characters gallery pages past the first screen, and stops fighting dark mode</title>
+ <link>https://three.ws/characters</link>
+ <guid isPermaLink="false">2026-08-17:The Characters gallery pages past the first screen, and stops fighting dark mode</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>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.</description>
+ </item>
<item>
<title>The viewer's backdrop picker stops vanishing while you read it, and sharing no longer posts &quot;Meet Agent&quot;</title>
<link>https://three.ws/app</link>
diff --git a/public/features.json b/public/features.json
index b9fb8bde4..4c8266986 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T01:33:22.503Z",
+ "generated_at": "2026-08-17T01:41:04.937Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",