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
build(pages): rebuild the public changelog and feature feeds with the packaging entry
nirholas76af0b4f4b4e
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8e3b7ee54..09887f049 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -72,6 +72,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **three.ws Drive: your agent, in the car**: There is a new page at /drive built for a car screen instead of a desk. Your agent is on it full size, you hold one big button and talk, and it answers out loud in its own voice with its face moving. It shows you one line of what it said rather than a wall of chat, because you are driving. It starts dark, because a bright panel at night is glare, and it will switch to a day palette on one press or one sentence. The keyboard stays out of the way while you are moving: if your browser can tell how fast you are going, text entry locks itself the moment you pull away and comes back when you have properly stopped. A few things you say never leave the car at all, so "repeat that", "stop talking", "louder" and "night mode" happen instantly, while "stop at the next charger" still goes to your agent like any other question. It works today on a head unit browser, on a phone in a cradle, and on Android Automotive. The Apple CarPlay version is built and waiting on Apple's approval for voice assistants in the car. One thing this fixed for everyone: an avatar used to answer in silence if you were not signed in, and now it always has a voice. (`/drive`) `[feature, improvement]`- **Tour Atlas counts its own stops honestly, and says why a stop has no picture**: The atlas advertised 185 stops in its page title, its search prompt, its social cards and its listing everywhere on the site. It has had 263 for a while, and nothing was checking, so the number quietly went stale. It now says 263, and the atlas guard fails the build if that number ever stops matching the manifest again. Eighteen stops carry no screenshot because they are live 3D or live-market pages that never stop painting long enough to be photographed; their cards used to claim the page 'did not respond', which was untrue of all of them, and now they say what actually happened and invite you to open the page live. Opening one of those stops used to show an empty black frame above the write-up, and now shows the same explanation. If the atlas itself cannot load you get a plain sentence about what went wrong and a Try again button, instead of a raw browser error or an instruction to run a developer command. And a /tour/atlas#stop-name link now opens that stop even when you are already on the page or have a filter narrowing the grid. (`/tour/atlas`) `[fix, improvement]`- **Traders can now price the latency of their own calls**: Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts. (`/docs/alpha-drip`) `[feature]`+- **Twenty-one finished packages were built and never shipped; the publisher now finds them by itself**: Twenty-one packages in this repo were written, tested and documented and then sat unpublished, because the publish script read a hand-maintained array that nobody remembered to edit. That array is gone: the publisher now discovers every package on disk, so a package ships by existing rather than by being added to a list. It also runs a preflight first and refuses to publish anything that would land broken (a scoped package that would go out private, a missing README or LICENSE, an entry point that is not actually in the tarball). The standalone-repo mirror had the same blind spot and only ever saw MCP servers; it now covers library packages too. Along the way the licensing was made consistent: 86 packages shipped a LICENSE file saying all rights reserved while their manifest and the repo both said Apache-2.0, and every one of them now says Apache-2.0 in all three places. (`/docs`) `[improvement, sdk, docs]`- **We tried making your agent a Matter device, measured it, and decided against it for now**: Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over. (`/docs/smart-home`) `[docs]`- **Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple**: The widget that has been on Android home screens and the Windows 11 widgets board now runs on Apple platforms too, from one WidgetKit extension shared by both. On a Mac it lives in Notification Centre in small, medium or large, fed by a small menu bar app that shows the same card and carries Open my agent, Refresh now and Unlink this Mac. On iPhone and iPad it is a home screen widget inside the three.ws app. Linking is one press on three.ws/glance: the page hands the device its own token, and if nothing opens (a Mac whose browser is signed in elsewhere) it shows a code to paste instead. The widget refreshes about every half hour without you opening anything, follows light and dark mode because it fetches the card in both, keeps the last card it downloaded when you are offline and says when that was rather than showing a spinner, and opens your agent on a tap. Every linked device is listed on three.ws/glance with a revoke button, and each token can only ever read your glance card. (`/glance`) `[feature]`- **Your Home Assistant voice assistant can have a face now**: If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face. (`/smart-home/satellite`) `[feature]`diff --git a/public/changelog.json b/public/changelog.jsonindex d57a250a5..27db5d493 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-03T08:55:49.851Z",+ "generated_at": "2026-09-03T16:28:57.686Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -705,6 +705,18 @@"feature"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "Twenty-one finished packages were built and never shipped; the publisher now finds them by itself",+ "summary": "Twenty-one packages in this repo were written, tested and documented and then sat unpublished, because the publish script read a hand-maintained array that nobody remembered to edit. That array is gone: the publisher now discovers every package on disk, so a package ships by existing rather than by being added to a list. It also runs a preflight first and refuses to publish anything that would land broken (a scoped package that would go out private, a missing README or LICENSE, an entry point that is not actually in the tarball). The standalone-repo mirror had the same blind spot and only ever saw MCP servers; it now covers library packages too. Along the way the licensing was made consistent: 86 packages shipped a LICENSE file saying all rights reserved while their manifest and the repo both said Apache-2.0, and every one of them now says Apache-2.0 in all three places.",+ "link": "/docs",+ "tags": [+ "improvement",+ "sdk",+ "docs"+ ]+ },{"date": "2026-09-03","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex e69857947..2883f8613 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -534,6 +534,14 @@<category>feature</category><description>Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts.</description></item>+ <item>+ <title>Twenty-one finished packages were built and never shipped; the publisher now finds them by itself</title>+ <link>https://three.ws/docs</link>+ <guid isPermaLink="false">2026-09-03:Twenty-one finished packages were built and never shipped; the publisher now finds them by itself</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Twenty-one packages in this repo were written, tested and documented and then sat unpublished, because the publish script read a hand-maintained array that nobody remembered to edit. That array is gone: the publisher now discovers every package on disk, so a package ships by existing rather than by being added to a list. It also runs a preflight first and refuses to publish anything that would land broken (a scoped package that would go out private, a missing README or LICENSE, an entry point that is not actually in the tarball). The standalone-repo mirror had the same blind spot and only ever saw MCP servers; it now covers library packages too. Along the way the licensing was made consistent: 86 packages shipped a LICENSE file saying all rights reserved while their manifest and the repo both said Apache-2.0, and every one of them now says Apache-2.0 in all three places.</description>+ </item><item><title>We tried making your agent a Matter device, measured it, and decided against it for now</title><link>https://three.ws/docs/smart-home</link>diff --git a/public/features.json b/public/features.jsonindex b0b149ae5..de076dcb1 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-03T08:55:49.823Z",+ "generated_at": "2026-09-03T16:28:57.677Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",