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.

chore(changelog): regenerate the changelog feeds and features manifest

nirholascc77c1fa569c
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 803dd3207..a47a9acab 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -29,6 +29,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Photo mode in the coin worlds now actually hands you the photo**: Press P in a coin world, or the camera button on the heads-up display, and you get a picture of the world on a share card: the scene itself, the three.ws mark, the coin you are standing in, and, during a live event, that event's name stamped on it. The card was there but the shutter went nowhere. Every single press answered "Couldn't photograph the world just now" and showed nothing, because of a fault in the code that builds the preview, so nobody has ever actually been handed one of these. Pressing it now opens the card, with Download and Copy image next to it. The picture is taken as a separate render rather than grabbed off the screen, so no panel, name tag or chat line is ever in the frame, and it works the same in zen mode, which is when most people will want it. It costs nothing when you are not using it: none of photo mode is loaded until the first press. Two smaller things fixed alongside: taking a second photo while the first card is open now replaces it cleanly instead of briefly stacking two sheets, where a click landing in the wrong moment could dismiss the shot you just took; and the line promising that P takes another one is true now, and visible, having previously rendered as nothing at all. Verified end to end in both Chrome and Safari, on a laptop frame and a phone frame, down to the pixels in the saved file, so the black rectangle that a mishandled 3D screenshot usually produces cannot come back unnoticed. (`/play`) `[fix, feature]`
- **The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves**: The free 3D Studio connector grew to eleven tools when look_at_model landed alongside check_job, but a lot of the writing about it had not caught up: the connector page, the press kit, the partner page, the blog summary, the announcement copy, the press release and the store-submission package still said nine or ten, and the social card enumerated only nine tool names. Every one of those now matches a fresh pull from the live server, the social card lists all eleven, and the module headers inside the connector describe the real catalog including which tools spend generation quota. A test now pins the total, so the next tool to land fails the suite instead of quietly re-opening the same drift. The standalone viewer also stopped crediting the AR launch endpoint with a renderer it no longer loads. Two smaller corrections rode along: the pending-generation example now shows the field that tells a client whether the model coming back is a bare mesh or a finished rig, and the three places the platform pins the 3D viewer library are now explained in one comment, so nobody has to guess why an embed and a standalone page load different builds. (`/docs/mcp-studio`) `[docs, fix]`
- **The treasury's self-heal plan now only promises SOL it can actually move**: When the payment rail runs short of the SOL it needs to settle, the platform first tries to heal itself: it looks across its own agent wallets for idle funds and pulls them back to the wallet that pays fees. The preview of that plan was counting wallets it could never open. Eight custodial wallets were encrypted under a key retired during the 2026-07 move to Google Cloud, so the preview kept advertising their balance as available while every real run failed on them, and the plan looked the same the next time anyone checked. The preview now opens each wallet's key before listing it, exactly as a real run does, and reports the ones it cannot open separately with the reason. A plan that reads as capital on hand when the capital is unreachable is worse than no plan at all, and it cost two separate investigations. The health check's settlement hint was corrected to match: it no longer says owner funds are needed only once every wallet reports being at its floor, because a sealed wallet never reports that. `[fix, infra]`
+- **Your Materialize order now tells you where it is, every step**: Ordering a physical print is only half the promise; the other half is knowing it is actually happening. Every Materialize order now moves through a real fulfillment queue that a person works, and every step it takes is recorded and sent to you: it went to the production lane, it is on the printer, it is in quality check, it shipped, here is the tracking number and the carrier. Nothing skips a step and nothing goes backwards, because the order's status follows one fixed set of rules rather than whatever the last message said. If a print fails quality check it goes back to the printer rather than out the door. If a job goes quiet for longer than the lead time you were quoted, we get told before you have to ask. And when a print bureau's own system reports in, we check it really came from them and ignore repeats, so a retried message can never leave your order in a state it was never in. (`/materialize`) `[feature]`
## 2026-09-01
diff --git a/data/changelog.json b/data/changelog.json
index 2436730da..5635207ba 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -25751,6 +25751,15 @@
"security"
],
"link": "/materialize"
+ },
+ {
+ "date": "2026-09-02",
+ "title": "Your Materialize order now tells you where it is, every step",
+ "summary": "Ordering a physical print is only half the promise; the other half is knowing it is actually happening. Every Materialize order now moves through a real fulfillment queue that a person works, and every step it takes is recorded and sent to you: it went to the production lane, it is on the printer, it is in quality check, it shipped, here is the tracking number and the carrier. Nothing skips a step and nothing goes backwards, because the order's status follows one fixed set of rules rather than whatever the last message said. If a print fails quality check it goes back to the printer rather than out the door. If a job goes quiet for longer than the lead time you were quoted, we get told before you have to ask. And when a print bureau's own system reports in, we check it really came from them and ignore repeats, so a retried message can never leave your order in a state it was never in.",
+ "tags": [
+ "feature"
+ ],
+ "link": "/materialize"
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 8457ad407..2f9c46a50 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-02T19:43:20.615Z",
+ "generated_at": "2026-09-02T19:50:36.665Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -249,6 +249,16 @@
"infra"
]
},
+ {
+ "date": "2026-09-02",
+ "type": "update",
+ "title": "Your Materialize order now tells you where it is, every step",
+ "summary": "Ordering a physical print is only half the promise; the other half is knowing it is actually happening. Every Materialize order now moves through a real fulfillment queue that a person works, and every step it takes is recorded and sent to you: it went to the production lane, it is on the printer, it is in quality check, it shipped, here is the tracking number and the carrier. Nothing skips a step and nothing goes backwards, because the order's status follows one fixed set of rules rather than whatever the last message said. If a print fails quality check it goes back to the printer rather than out the door. If a job goes quiet for longer than the lead time you were quoted, we get told before you have to ask. And when a print bureau's own system reports in, we check it really came from them and ignore repeats, so a retried message can never leave your order in a state it was never in.",
+ "link": "/materialize",
+ "tags": [
+ "feature"
+ ]
+ },
{
"date": "2026-09-01",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index a49272e0c..b63ea1592 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -190,6 +190,14 @@
<category>fix</category>
<description>When the payment rail runs short of the SOL it needs to settle, the platform first tries to heal itself: it looks across its own agent wallets for idle funds and pulls them back to the wallet that pays fees. The preview of that plan was counting wallets it could never open. Eight custodial wallets were encrypted under a key retired during the 2026-07 move to Google Cloud, so the preview kept advertising their balance as available while every real run failed on them, and the plan looked the same the next time anyone checked. The preview now opens each wallet's key before listing it, exactly as a real run does, and reports the ones it cannot open separately with the reason. A plan that reads as capital on hand when the capital is unreachable is worse than no plan at all, and it cost two separate investigations. The health check's settlement hint was corrected to match: it no longer says owner funds are needed only once every wallet reports being at its floor, because a sealed wallet never reports that.</description>
</item>
+ <item>
+ <title>Your Materialize order now tells you where it is, every step</title>
+ <link>https://three.ws/materialize</link>
+ <guid isPermaLink="false">2026-09-02:Your Materialize order now tells you where it is, every step</guid>
+ <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Ordering a physical print is only half the promise; the other half is knowing it is actually happening. Every Materialize order now moves through a real fulfillment queue that a person works, and every step it takes is recorded and sent to you: it went to the production lane, it is on the printer, it is in quality check, it shipped, here is the tracking number and the carrier. Nothing skips a step and nothing goes backwards, because the order's status follows one fixed set of rules rather than whatever the last message said. If a print fails quality check it goes back to the printer rather than out the door. If a job goes quiet for longer than the lead time you were quoted, we get told before you have to ask. And when a print bureau's own system reports in, we check it really came from them and ignore repeats, so a retried message can never leave your order in a state it was never in.</description>
+ </item>
<item>
<title>3D Drops</title>
<link>https://three.ws/drops</link>
diff --git a/public/features.json b/public/features.json
index 8e07c8d0f..79897e140 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-02T19:43:20.555Z",
+ "generated_at": "2026-09-02T19:50:36.395Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",