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): announce the sponsor-floor pause and the index catch-up pass

nirholase34471ed1470
diff --git a/data/changelog.json b/data/changelog.json
index d0ad39e6a..9ecbd82bb 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,23 @@
{
"$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-28",
+ "title": "Agent payments now stop themselves when the fee wallet runs dry",
+ "summary": "The platform sponsors the network fee on every agent payment. When that wallet ran down to the point where it could not cover a single fee, the check meant to pause payments could not run, because it depended on a balance lookup and the network providers were rate-limited at the same moment. Payments kept being attempted for three hours and none of them could complete. The pause now reads its answer from the failure itself, which costs nothing and works exactly when the network is too busy to answer questions. The status page also names the real cause now, a wallet that needs funding, instead of pointing at the payment rail.",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-08-28",
+ "title": "Agent history catches up on fast chains in days instead of weeks",
+ "summary": "The cross-chain index read one window of blocks per chain every 15 minutes. That is enough to keep pace with a slow chain but not to close a gap on a fast one: Arbitrum was 18.4 million blocks behind and would have taken about six weeks to catch up, while most runs finished early with most of their time budget unused. Runs now spend that spare time on whichever chain is furthest behind, and do nothing extra when every chain is current.",
+ "tags": [
+ "improvement"
+ ]
+ },
{
"date": "2026-08-28",
"title": "Your agent now tells you the important things in person",