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 remesh reading FBX and stylize refusing it with a clear message

nirholas6998c767679d
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1162fefa8..3dd4b169c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,9 +9,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **A paid call that fails after payment now tells you to retry, not to pay again**: If a paid x402 call fails after your payment has already settled, the response now says so: paid, retry safe, the settlement transaction, and how many retries are left. Repeat the exact same request with the same payment and the server re-runs the work without charging you again, instead of answering that the payment was already used. Paid POST routes also now tell apart two different request bodies sent under one payment identifier. The MCP docs gained a Use cases section that spells out every guided prompt as the ordered tool calls it makes, with the steps that spend money marked, and a test keeps it in step with the real tools. (`/docs/x402`) `[improvement, docs]`
- **Agent MCP: price an x402 payment with pay_quote before pay_and_call spends it**: The Agent MCP server now has a pay_quote tool. It asks a paid x402 endpoint what it charges without paying, and shows who gets paid, how much, in which token and on which chain, which wallet pays, the per-call limit, and anything that would stop the payment. pay_and_call needs the quote_id it returns plus an explicit confirm_payment, so an assistant always shows you the price before your agent wallet pays. One approval pays one call. Before this, turning pay_and_call on still left it refusing every call, because the quote step it requires did not exist. `[feature, fix]`
- **Cloud agents get their own free 3D budget with a connector link**: Grok Bot and other hosted AI agents all call the free 3D studio from the same network address, so one busy user could use up the allowance for everyone. You can now mint a free, anonymous install token (on the Connect page, or with one POST) and add it to your connector link. Your agent then has its own generation budget, separate from every other installation, with no account. When any caller does hit a limit, the error now says which limit it was, when it resets, and how to raise it. (`/connect`) `[feature, improvement]`
+- **Connected apps: clearer sign-in screen and instant revoke**: When an app such as Grok Bot asks to connect to your three.ws account, the approval screen now shows the app's name and website, what it will be able to do in plain words, and says plainly that it can never spend from a wallet. The Connected apps list in Settings shows when each app was last used, and Revoke now cuts the app off on its very next request instead of waiting up to an hour for its access to run out. (`/dashboard/settings`) `[feature, security]`
- **Creator rewards include fees pump.fun now holds on the curve and pool**: pump.fun's October program update changed where creator rewards land: newer trades leave the creator fee on the coin's bonding curve or pool until someone sweeps it into the creator's vault. Without handling that, those rewards were invisible to a claim and read as already claimed on coin pages. Every claim on three.ws now sweeps your coins first and collects everything in the same transaction, from your wallet, an agent wallet or the automatic claimer. Reward balances, coin pages and earnings history count the held fees as unclaimed, fee-sharing changes and distributions no longer fail on unswept fees, and the biggest buy a coin ever sees (the one that completes its curve) is now reported at its full size in trade feeds and whale alerts. The automatic claimer for agent sniper wallets also had a bug that stopped every claim; that is fixed. (`/launch`) `[improvement, fix]`
- **Funding an agent's inference from its wallet now needs the signed real-funds agreements**: Topping up an agent's inference credits, switching on its automatic top-up, and provisioning an inference API key all send real USDC out of the agent's wallet. They now ask for the same signed Terms of Service, Risk Disclosure and Agent Wallet Agreement as every other real-funds action, on the page and on the API alike. Previews and switching the automatic top-up off stay open, since nothing moves. `[security]`
- **Paired coins: launch a coin on Robinhood Chain that trades against up to five assets at once**: A paired coin trades in up to five markets at the same time, each its own bonding curve: tokenized stocks, WETH, stablecoins or chain coins, in whatever split you choose. Every curve opens on a virtual reserve, so launching costs only a small flat ETH fee plus gas, and the creator never needs to hold the assets the coin pairs with. Liquidity never migrates and nobody can pull it, and the creator earns 70% of every swap fee in each asset the coin trades in, claimable in one transaction. Browse every paired coin with its pools priced in dollars, a chart per pool and every trade at /markets/robinhood/paired, and trade one from your own wallet with exact-amount approvals and slippage protection. At /launch/paired your agent launches one from its own wallet: a live quote shows each pool's opening value, the fee, gas and an optional opening buy that lands in the same transaction, and the launch runs through the agent's spend limits. Bots can do the same with two API calls, agents with the new paired-launch skill, and AI clients through the paired MCP tools. The developer guide is at /docs/paired-coins. (`/markets/robinhood/paired`) `[feature]`
+- **Remesh reads FBX files, and stylize says plainly when it cannot**: The remesh tool now accepts a binary FBX for every operation, not only FBX-to-FBX conversion: convert it to GLB, OBJ or any other format, simplify it, repair it or retopologize it, even from a download link with no file extension. Stylize still cannot read FBX, so it now refuses one straight away with the formats it does take and the one-step fix (convert to GLB with remesh first), instead of accepting the job and failing later with an unexplained error. Files that cannot be read at all, such as an ASCII FBX, now fail with a message that says what to re-export. Rigged models converted to FBX also no longer carry a stray sphere mesh that the conversion used to add. (`/forge`) `[improvement, fix]`
- **The desktop companion, CLI and MCP server now work with just the bridge token**: The companion bridge token is the one credential the desktop app, the companion command line and its MCP server are given, but the feed, marking a message as spoken, replying, reading contacts and checking sources all refused it, so pasting the token into the desktop app said it was wrong and an agent asking what you had heard got turned away. Those calls now accept the bridge token and only ever show the messages and contacts of the person it belongs to. It still cannot connect sources, edit contacts, change settings or rotate itself; those stay behind your signed-in account, and they now say so plainly instead of answering as if the token were wrong. (`/companion`) `[fix]`
- **The leaderboard now ranks agents by what they earned**: A new Earned tab on the leaderboard ranks every public agent by what it earned over the last 24 hours, 7 days, 30 days or all time: creator fees from its coin plus what people and other agents paid for its skills, shown separately and added up in SOL with dollars beside it, with how far each agent moved since the previous period. Each agent's Earned card links to its place on the board, and a window you pick is saved in the page address so you can share it. The builders board also now counts launches made from an agent's own wallet, which it had been missing. (`/leaderboard`) `[feature, fix]`
diff --git a/data/changelog.json b/data/changelog.json
index fe2829541..506563f43 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,13 @@
{
"$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, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-10-09",
+ "title": "Remesh reads FBX files, and stylize says plainly when it cannot",
+ "summary": "The remesh tool now accepts a binary FBX for every operation, not only FBX-to-FBX conversion: convert it to GLB, OBJ or any other format, simplify it, repair it or retopologize it, even from a download link with no file extension. Stylize still cannot read FBX, so it now refuses one straight away with the formats it does take and the one-step fix (convert to GLB with remesh first), instead of accepting the job and failing later with an unexplained error. Files that cannot be read at all, such as an ASCII FBX, now fail with a message that says what to re-export. Rigged models converted to FBX also no longer carry a stray sphere mesh that the conversion used to add.",
+ "tags": ["improvement", "fix"],
+ "link": "/forge"
+ },
{
"date": "2026-10-09",
"title": "The leaderboard now ranks agents by what they earned",
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 7f51dce08..f885e90f9 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-10-09T03:34:09.045Z",
+ "generated_at": "2026-10-09T03:49:07.130Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3844,
+ "total": 3846,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -42,6 +42,17 @@
"improvement"
]
},
+ {
+ "date": "2026-10-09",
+ "type": "update",
+ "title": "Connected apps: clearer sign-in screen and instant revoke",
+ "summary": "When an app such as Grok Bot asks to connect to your three.ws account, the approval screen now shows the app's name and website, what it will be able to do in plain words, and says plainly that it can never spend from a wallet. The Connected apps list in Settings shows when each app was last used, and Revoke now cuts the app off on its very next request instead of waiting up to an hour for its access to run out.",
+ "link": "/dashboard/settings",
+ "tags": [
+ "feature",
+ "security"
+ ]
+ },
{
"date": "2026-10-09",
"type": "update",
@@ -73,6 +84,17 @@
"feature"
]
},
+ {
+ "date": "2026-10-09",
+ "type": "update",
+ "title": "Remesh reads FBX files, and stylize says plainly when it cannot",
+ "summary": "The remesh tool now accepts a binary FBX for every operation, not only FBX-to-FBX conversion: convert it to GLB, OBJ or any other format, simplify it, repair it or retopologize it, even from a download link with no file extension. Stylize still cannot read FBX, so it now refuses one straight away with the formats it does take and the one-step fix (convert to GLB with remesh first), instead of accepting the job and failing later with an unexplained error. Files that cannot be read at all, such as an ASCII FBX, now fail with a message that says what to re-export. Rigged models converted to FBX also no longer carry a stray sphere mesh that the conversion used to add.",
+ "link": "/forge",
+ "tags": [
+ "improvement",
+ "fix"
+ ]
+ },
{
"date": "2026-10-09",
"type": "update",
@@ -1537,29 +1559,6 @@
"tags": [
"launch"
]
- },
- {
- "date": "2026-09-17",
- "type": "update",
- "title": "A payment that is still confirming no longer reads as a failed payment",
- "summary": "Settling an x402 payment on Solana means broadcasting a transaction and then waiting for the network to confirm it, and in between the answer is genuinely unknown. Until now an unfinished wait was reported as a failure, so a payment the chain was in the middle of accepting could tell the buyer it had failed and withhold what they paid for. Our facilitator now answers with the protocol's pending state and the settlement signature instead, a retry re-checks that same transaction rather than sending a second one, the endpoint still returns the work with the signature to watch, and a reconciler closes the books every two minutes once the chain answers. The confirmation wait also dropped from 30 seconds to 12, so paid calls come back faster.",
- "link": "/docs/x402-settlement-pending",
- "tags": [
- "fix",
- "improvement",
- "infra"
- ]
- },
- {
- "date": "2026-09-17",
- "type": "update",
- "title": "A plan for meeting agents through smart glasses",
- "summary": "three.ws already lets you pin a 3D agent at a real place and walk up to it, and /irl can already mirror the nearest-agent cue to Brilliant Labs Frame and Even Realities G1 lenses over Bluetooth. New documentation maps the whole glasses lane: how the work splits between the lens (who is near, which way, how far) and the phone (the 3D body in AR), a full build plan for Meta Ray-Ban Display glasses and the Neural Band, and an honest survey of every platform, repository and package involved, including which ones have shut down and should not be built on.",
- "link": "/docs/glasses",
- "tags": [
- "docs",
- "feature"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 1ff999d13..4b2b79522 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-09T03:34:08.975Z",
+ "generated_at": "2026-10-09T03:49:07.107Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -39,6 +39,17 @@
"improvement"
]
},
+ {
+ "date": "2026-10-09",
+ "type": "update",
+ "title": "Connected apps: clearer sign-in screen and instant revoke",
+ "summary": "When an app such as Grok Bot asks to connect to your three.ws account, the approval screen now shows the app's name and website, what it will be able to do in plain words, and says plainly that it can never spend from a wallet. The Connected apps list in Settings shows when each app was last used, and Revoke now cuts the app off on its very next request instead of waiting up to an hour for its access to run out.",
+ "link": "/dashboard/settings",
+ "tags": [
+ "feature",
+ "security"
+ ]
+ },
{
"date": "2026-10-09",
"type": "update",
@@ -70,6 +81,17 @@
"feature"
]
},
+ {
+ "date": "2026-10-09",
+ "type": "update",
+ "title": "Remesh reads FBX files, and stylize says plainly when it cannot",
+ "summary": "The remesh tool now accepts a binary FBX for every operation, not only FBX-to-FBX conversion: convert it to GLB, OBJ or any other format, simplify it, repair it or retopologize it, even from a download link with no file extension. Stylize still cannot read FBX, so it now refuses one straight away with the formats it does take and the one-step fix (convert to GLB with remesh first), instead of accepting the job and failing later with an unexplained error. Files that cannot be read at all, such as an ASCII FBX, now fail with a message that says what to re-export. Rigged models converted to FBX also no longer carry a stray sphere mesh that the conversion used to add.",
+ "link": "/forge",
+ "tags": [
+ "improvement",
+ "fix"
+ ]
+ },
{
"date": "2026-10-09",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 64bbd38a0..59429e148 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -30,6 +30,14 @@
<category>feature</category>
<description>Grok Bot and other hosted AI agents all call the free 3D studio from the same network address, so one busy user could use up the allowance for everyone. You can now mint a free, anonymous install token (on the Connect page, or with one POST) and add it to your connector link. Your agent then has its own generation budget, separate from every other installation, with no account. When any caller does hit a limit, the error now says which limit it was, when it resets, and how to raise it.</description>
</item>
+ <item>
+ <title>Connected apps: clearer sign-in screen and instant revoke</title>
+ <link>https://three.ws/dashboard/settings</link>
+ <guid isPermaLink="false">2026-10-09:Connected apps: clearer sign-in screen and instant revoke</guid>
+ <pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>When an app such as Grok Bot asks to connect to your three.ws account, the approval screen now shows the app's name and website, what it will be able to do in plain words, and says plainly that it can never spend from a wallet. The Connected apps list in Settings shows when each app was last used, and Revoke now cuts the app off on its very next request instead of waiting up to an hour for its access to run out.</description>
+ </item>
<item>
<title>Creator rewards include fees pump.fun now holds on the curve and pool</title>
<link>https://three.ws/launch</link>
@@ -54,6 +62,14 @@
<category>feature</category>
<description>A paired coin trades in up to five markets at the same time, each its own bonding curve: tokenized stocks, WETH, stablecoins or chain coins, in whatever split you choose. Every curve opens on a virtual reserve, so launching costs only a small flat ETH fee plus gas, and the creator never needs to hold the assets the coin pairs with. Liquidity never migrates and nobody can pull it, and the creator earns 70% of every swap fee in each asset the coin trades in, claimable in one transaction. Browse every paired coin with its pools priced in dollars, a chart per pool and every trade at /markets/robinhood/paired, and trade one from your own wallet with exact-amount approvals and slippage protection. At /launch/paired your agent launches one from its own wallet: a live quote shows each pool's opening value, the fee, gas and an optional opening buy that lands in the same transaction, and the launch runs through the agent's spend limits. Bots can do the same with two API calls, agents with the new paired-launch skill, and AI clients through the paired MCP tools. The developer guide is at /docs/paired-coins.</description>
</item>
+ <item>
+ <title>Remesh reads FBX files, and stylize says plainly when it cannot</title>
+ <link>https://three.ws/forge</link>
+ <guid isPermaLink="false">2026-10-09:Remesh reads FBX files, and stylize says plainly when it cannot</guid>
+ <pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate>
+ <category>improvement</category>
+ <description>The remesh tool now accepts a binary FBX for every operation, not only FBX-to-FBX conversion: convert it to GLB, OBJ or any other format, simplify it, repair it or retopologize it, even from a download link with no file extension. Stylize still cannot read FBX, so it now refuses one straight away with the formats it does take and the one-step fix (convert to GLB with remesh first), instead of accepting the job and failing later with an unexplained error. Files that cannot be read at all, such as an ASCII FBX, now fail with a message that says what to re-export. Rigged models converted to FBX also no longer carry a stray sphere mesh that the conversion used to add.</description>
+ </item>
<item>
<title>The desktop companion, CLI and MCP server now work with just the bridge token</title>
<link>https://three.ws/companion</link>
diff --git a/public/features.json b/public/features.json
index d379e34c8..76db73450 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-09T03:34:08.947Z",
+ "generated_at": "2026-10-09T03:49:07.094Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",