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.

fix(token): read the $THREE buyback and micro-buy balances from the Token-2022 ATA

nirholas483b90ae5c37
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1db2ad6ec..becdf15a7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -24,10 +24,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly**: Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them. `[fix, improvement]`
- **External Solana agents get their names and artwork back in the directory**: Every agent the platform indexes from the Metaplex Agent Registry had been sitting in the directory as a bare address since August 6: no name, no picture, no 3D model. The crawler asks a Solana node for each agent's artwork through a method only some nodes support, and it was asking the same node every time, one that does not support it. Worse, the node that does support it answers a refusal in the same shape when it is simply busy, so the crawler could not tell 'I cannot do this' from 'not right now'. It now tries each node in turn, keeps the one that answers, waits and retries a busy one instead of writing it off, and refreshes the agents that are missing artwork rather than the same handful at the top of the list every half hour. If no node will serve the artwork at all, the crawl now says so out loud instead of quietly marking every agent as failed. (`/agents`) `[fix, infra]`
- **Forge tools refuse a made-up style or file type, and a worker hiccup no longer reads as a broken job**: Three repairs to the Forge model tools. The stylize filter (voxel, brick, voronoi, lowpoly) checked the requested style against its list in a way that quietly accepted a handful of reserved words, so a request naming one of them was sent to the worker with an unknown filter and no density setting instead of being turned down. The same flaw let the reference-image uploader accept a made-up file type and hand back an upload slot with a nonsense filename. Both now check their list properly, and an unrecognised value falls back to the default or is refused. Separately, while the background remover, mesh optimiser, part splitter and stylizer were checking on a running job, a momentary fault at the worker was reported as a crash on our side, once for every check, which buried the real signal in the alerts. A fault now answers plainly and the page keeps waiting, which is what a passing hiccup deserves. (`/forge`) `[fix, improvement]`
+- **Live Agents: every card on the wall now shows what its agent is actually doing**: The Live Agents wall opened a separate live connection for every card on screen, and a browser will not give a page that many. The first handful connected, and the rest, more than forty of the forty-eight on the first page, sat on Connecting and an empty screen for as long as you left the tab open. Scrolling did not help them, because the connections that had been handed out were never given back. The wall now loads the real recent activity for the whole page in a single request, so every card has a genuine terminal of that agent's on-chain and skill actions the moment it appears, however far down the list it sits. Live connections are kept for what actually needs pushing: an agent with a real browser feed running, the one holding the spotlight, and the card you hover or tab to, which goes live under your cursor. A card that never manages to connect now falls back to its real activity instead of claiming to be connecting forever, the standby screen tells you how many actions an agent has recorded rather than flatly saying it has none, and the reaction buttons on a card no longer run off the edge of a phone screen. (`/agents-live`) `[fix, improvement]`
- **Live stage hosts stop swallowing hyphens, and only confirmed tippers get greeted by name**: Two repairs to the Living Stages host. The cleanup pass that tidies the host's spoken line was stripping hyphens along with the invisible characters it was meant to remove, so every show heard "on chain" where the host said "on-chain" and "state of the art" for "state-of-the-art"; punctuation now survives and only invisible characters are removed. Separately, the host's memory of returning regulars counted tips whose on-chain settlement had not been confirmed yet, which meant anyone could post an unconfirmed tip under a name of their choosing and hear the host greet it aloud. That memory now reads confirmed tips only, matching the public leaderboard. Smaller repairs in the same pass: a stage that has not opened its first show is no longer cached as empty at the edge, an over-long coin address is refused instead of quietly trimmed into a different plaza, and the running tip total is written before the response returns. (`/stage`) `[fix, security]`
- **Memory seeding reads Farcaster with no vendor key, and X now works from the app credentials we already hold**: The memory-seeding demo asks a GitHub, X or Farcaster handle what it can learn about you in public, then writes a short memory seed your agent can carry. Two of those three connectors were showing a "connector not configured" card to everyone, because each insisted on a vendor key nobody had set. Farcaster now reads through the same failover the rest of the platform uses: an indexer when a key exists, and a public Farcaster hub with no key at all otherwise, so it returns real profiles and casts on any deployment. Anything the keyless lane genuinely cannot know, such as follower counts, is now shown as unknown instead of zero. The X connector accepts the app key and secret the platform already stores, exchanging them for a read-only token itself, so it no longer needs a separate token provisioned by hand. A mistyped Farcaster name now comes back as not found rather than as an upstream outage, and all four endpoints are documented in the API reference for the first time. (`/demos/memory-seed`) `[fix, improvement, docs]`
- **Mistyped filters on the revenue, checkout and ring endpoints answer plainly instead of failing**: The public revenue feed, the checkout SKU API and the ring report all took values straight from the URL into the database. A timestamp that was not a timestamp, a checkout id that was not an id, and the query fell over: the caller got an opaque "something went wrong" with a support reference, and our own alerting logged a fault that was only ever a typo. All three now say what was wrong, in words, with the right status code. The ring report also stops treating an unrecognised period as "show me everything", which quietly answered the wrong question and ran the most expensive query it has. The revenue feed now echoes back the endpoint filter it actually applied rather than the raw text it was sent, and the paid-call lookup only accepts something shaped like a real transaction signature. (`/x402-revenue`) `[fix]`
-- **Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed**: Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. (`/credits`) `[fix]`
+- **Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed**: Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. The same mix-up was quietly hobbling the treasury side: the buyback and micro-buy lanes read their own $THREE balance from the wrong place, always saw zero, and so never moved what they had bought into the treasury. They now read and move it correctly. (`/credits`) `[fix]`
- **Prompt polish keeps its quotes out of your model, and a busy Forge says so plainly**: Three fixes across the Forge endpoints. The Enhance button, which rewrites your rough idea into the prompt the generator actually draws from, stopped removing the quotation marks the writing model wraps around its answer: those quotes were being handed straight to the image step as if you had asked for them to be drawn. Both plain and curly quotes are stripped again. Second, when you ask the studio to change a model you already made and the generator is saturated, you now get an honest "busy, try again in a moment" with a wait time instead of a vague failure that blamed the wording of your request. Third, the self-hosted generator panel now tells a caller which input was missing rather than reporting the whole feature as unconfigured, and its status light no longer claims nothing is set up when the only problem was the address you typed. (`/forge`) `[fix, improvement]`
- **Robinhood Chain worlds survive a hiccup in the live feed instead of going dark**: The in-world trading terminal inside a Robinhood Chain world polls the chain feed every five seconds, and the Worlds lobby lists those coins from the same feed. A single event that arrived without its payload, or with a timestamp the chain wrote in an unexpected format, took both requests down with a server error: the terminal showed a dead tape, and the lobby's Robinhood Chain tab quietly emptied with nothing on screen to say why. Bad events are now skipped and the rest of the tape still renders, a price that is genuinely missing stays blank rather than printing as a real $0 trade, and a launch with no readable contract address no longer produces a card that leads nowhere. Asking for trades with an address that is not a contract address now gets a clear error back instead of an empty list that read as "this coin has never traded". (`/worlds`) `[fix]`
- **Scrolling the activity feed past a bad cursor no longer breaks the whole feed**: An audit of the account endpoints found one real break and two smaller ones. The activity feed on /community and your personal feed ask for the next page of results by passing the last item’s timestamp back; if that value arrived malformed, from a hand-edited link or a stale bookmark, the database rejected it and the entire feed came back as a server error with nothing to act on. It now answers with a plain "that is not a timestamp" so the page can recover and reload from the top. The referral code editor stated its length rule with a typographic dash that read as a minus sign on some devices, and now spells it out. The purchase history endpoint also documented the wrong default view: it always merges your purchases and your sales, which is what the dashboard shows. (`/community`) `[fix]`
@@ -61,6 +62,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Trending: muted text on the board is readable, and the Tip button that only navigated is gone**: Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states. (`/trending`) `[fix, improvement]`
- **Wallet reputation stops losing coins it never got around to judging**: The rollup that turns launch history into wallet reputation was judging 80 coins every five minutes while the intel firehose was recording about 32,000 new mints a day, so it fell roughly 8,000 coins a day behind. That backlog does not wait its turn: the rollup works oldest-first and only reaches back 14 days, which is exactly when retention prunes the record, so the tail of the queue aged out and those buyers never counted toward anyone’s reputation at all. 309,000 coins were sitting unjudged with the oldest already 8.4 days from the cliff. The per-run budget is now 400, which outruns the firehose several times over, drains the backlog within days and then idles. Scores across the smart-money surfaces get their full evidence base back. The operations health board also tracks the retention and reconstruct sweeps, so a stall in either is visible instead of showing up later as a symptom. `[fix, infra]`
- **Web search answers again, and a stray address can no longer tie up the server**: Three repairs on the public API. Web search had been answering nothing but an error: the question went to Google's grounded search as designed, but the model was given a single budget to both think and reply, spent all of it thinking, and came back empty, which we correctly reported as a failure and wrongly did so on every single query. Thinking now has its own allowance on top of the answer, and when a search does come back empty the log says why instead of leaving the next person to guess. Second, the machine-readable directory at the root of the site, the file other agents read to learn what three.ws sells, would hang forever on a handful of odd names rather than saying no such thing, and a request that never ends holds a server slot until it is cut off. Every unknown name now gets a plain not-found. Third, at checkout, a wallet that hands back a payment the network could never accept is now told so at the moment it happens, instead of the modal saying sending and the error arriving later from the payment processor. `[fix, security]`
+- **You can now teach an agent your GitHub work without waiting on an OAuth app**: Seeding an agent from GitHub, the flow where you tick your profile, repositories and READMEs and the agent learns to talk about what you build, needed a GitHub sign-in button that this site never had switched on. The Connected accounts card said so honestly, and that was the end of it: an Unavailable tag and nothing you could do. There is now a second way in that needs nothing set up on our side. You create a read-only token on GitHub yourself, tick read:user and nothing more, paste it into Settings, and the same consent list, the same seeding and the same one-click deletion all work exactly as before. Consent still happens on GitHub's own screen, where you choose what the token may do, and we check what you chose: a token carrying access the feature cannot use, anything reaching your private repositories or able to delete them, is refused on the spot and never stored, with the offending permission named so you know which box to untick. The token is encrypted before it is saved and destroyed when you disconnect. One honest difference from the sign-in route: disconnecting deletes our copy and every memory it produced, but GitHub gives no way for a token to delete itself, so the confirmation now tells you to remove it on GitHub too and links you straight there. (`/settings`) `[feature, improvement]`
## 2026-08-15
diff --git a/api/_lib/token/buyback.js b/api/_lib/token/buyback.js
index 83f315db2..226841b95 100644
--- a/api/_lib/token/buyback.js
+++ b/api/_lib/token/buyback.js
@@ -30,6 +30,7 @@ import { submitProtected } from '../execution-engine.js';
import { SOLANA_USDC_MINT } from '../../payments/_config.js';
import { TOKEN_MINT, TOKEN_DECIMALS } from './config.js';
import { treasuryWallet, treasuryWalletOrNull } from './config.js';
+import { tokenProgramIdForMint } from './token-program.js';
import { jupiterQuote as jupQuote, jupiterSwapTx as jupSwapTx } from './jupiter.js';
import {
computeSpend,
@@ -102,8 +103,11 @@ const threeTokens = (atomics) => atomicsToTokens(atomics, TOKEN_DECIMALS);
/** SPL balance of `owner` for `mint`, in atomics. Missing ATA → 0n (never throws). */
async function splBalanceAtomics(connection, ownerPk, mintPk) {
- const ata = getAssociatedTokenAddressSync(mintPk, ownerPk, true);
try {
+ // $THREE is Token-2022, so the spl-token default program would derive an ATA
+ // that does not exist and report a zero balance for a wallet holding tokens.
+ const programId = await tokenProgramIdForMint(connection, mintPk);
+ const ata = getAssociatedTokenAddressSync(mintPk, ownerPk, true, programId);
const bal = await connection.getTokenAccountBalance(ata);
return BigInt(bal.value.amount);
} catch {
@@ -210,12 +214,13 @@ export async function executeBuyback(signer, plan) {
let sweepSig = null;
if (treasury !== payer.toBase58() && boughtAtomics > 0n) {
const treasuryPk = new PublicKey(treasury);
- const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true);
- const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true);
+ const programId = await tokenProgramIdForMint(connection, mintPk);
+ const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true, programId);
+ const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true, programId);
const tag = `three.ws buyback → treasury $${usd(plan.spendUsdcAtomics).toFixed(2)}`.slice(0, 180);
const sweepIxs = [
- createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk),
- createTransferInstruction(fromAta, toAta, payer, boughtAtomics),
+ createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk, programId),
+ createTransferInstruction(fromAta, toAta, payer, boughtAtomics, [], programId),
new TransactionInstruction({ keys: [], programId: new PublicKey(MEMO_PROGRAM_ID), data: Buffer.from(tag, 'utf8') }),
];
try {
@@ -257,11 +262,12 @@ export async function sweepStrandedThree(signer) {
if (stranded <= 0n) return null;
const treasuryPk = new PublicKey(treasury);
- const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true);
- const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true);
+ const programId = await tokenProgramIdForMint(connection, mintPk);
+ const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true, programId);
+ const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true, programId);
const strandedIxs = [
- createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk),
- createTransferInstruction(fromAta, toAta, payer, stranded),
+ createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk, programId),
+ createTransferInstruction(fromAta, toAta, payer, stranded, [], programId),
new TransactionInstruction({ keys: [], programId: new PublicKey(MEMO_PROGRAM_ID), data: Buffer.from('three.ws buyback → treasury (recover)', 'utf8') }),
];
// Protected send: priority fee + CU estimate, rebroadcast with blockhash
diff --git a/api/_lib/token/microbuy.js b/api/_lib/token/microbuy.js
index 98368dc40..9e5034229 100644
--- a/api/_lib/token/microbuy.js
+++ b/api/_lib/token/microbuy.js
@@ -39,6 +39,7 @@ import { getRedis } from '../redis.js';
import { sql } from '../db.js';
import { SOLANA_USDC_MINT } from '../../payments/_config.js';
import { TOKEN_MINT, TOKEN_DECIMALS, treasuryWallet, treasuryWalletOrNull } from './config.js';
+import { tokenProgramIdForMint } from './token-program.js';
import { jupiterQuote, jupiterSwapTx } from './jupiter.js';
import {
envUsd,
@@ -276,8 +277,11 @@ const threeTokens = (a) => atomicsToTokens(a, TOKEN_DECIMALS);
/** SPL balance of `owner` for `mint`, in atomics. Missing ATA → 0n (never throws). */
async function splBalanceAtomics(connection, ownerPk, mintPk) {
- const ata = getAssociatedTokenAddressSync(mintPk, ownerPk, true);
try {
+ // $THREE is Token-2022; the spl-token default program derives an ATA that does
+ // not exist, which reads back as a zero balance on a wallet that holds tokens.
+ const programId = await tokenProgramIdForMint(connection, mintPk);
+ const ata = getAssociatedTokenAddressSync(mintPk, ownerPk, true, programId);
const bal = await connection.getTokenAccountBalance(ata);
return BigInt(bal.value.amount);
} catch {
@@ -468,11 +472,12 @@ export async function sweepMicrobuyThree(signer) {
if (held <= 0n) return null;
const treasuryPk = new PublicKey(treasury);
- const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true);
- const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true);
+ const programId = await tokenProgramIdForMint(connection, mintPk);
+ const fromAta = getAssociatedTokenAddressSync(mintPk, payer, true, programId);
+ const toAta = getAssociatedTokenAddressSync(mintPk, treasuryPk, true, programId);
const ixs = [
- createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk),
- createTransferInstruction(fromAta, toAta, payer, held),
+ createAssociatedTokenAccountIdempotentInstruction(payer, toAta, treasuryPk, mintPk, programId),
+ createTransferInstruction(fromAta, toAta, payer, held, [], programId),
new TransactionInstruction({
keys: [],
programId: new PublicKey(MEMO_PROGRAM_ID),
diff --git a/api/_lib/token/token-program.js b/api/_lib/token/token-program.js
new file mode 100644
index 000000000..4b860dd07
--- /dev/null
+++ b/api/_lib/token/token-program.js
@@ -0,0 +1,43 @@
+// Which SPL token program owns the $THREE mint, read from the chain.
+//
+// $THREE is a Token-2022 mint (as is every pump.fun coin minted since the
+// Token-2022 switch), while @solana/spl-token defaults every helper to the legacy
+// TOKEN_PROGRAM_ID. Code that takes the default derives an associated-token
+// address that does not exist: a balance read comes back as zero for a wallet that
+// actually holds tokens, and a transfer built against it is rejected on-chain with
+// "incorrect program id for instruction". Both failures are silent-looking, which
+// is exactly why this is centralized rather than repeated per call site.
+//
+// The mint account's owner is canonical and fixed for the life of the mint, so the
+// lookup is memoized per process. resolveTokenProgramForMintOwner does the
+// classification (and throws a typed 422 for a non-SPL owner).
+
+import { PublicKey } from '@solana/web3.js';
+import { resolveTokenProgramForMintOwner } from '../pump-trade-args.js';
+
+const cache = new Map();
+
+/**
+ * @param {import('@solana/web3.js').Connection} connection
+ * @param {import('@solana/web3.js').PublicKey|string} mint
+ * @returns {Promise<PublicKey>} the token program that owns `mint`
+ * @throws if the mint account is missing, or is owned by neither SPL token program
+ */
+export async function tokenProgramIdForMint(connection, mint) {
+ const mintPk = mint instanceof PublicKey ? mint : new PublicKey(mint);
+ const key = mintPk.toBase58();
+ const cached = cache.get(key);
+ if (cached) return cached;
+
+ const info = await connection.getAccountInfo(mintPk);
+ if (!info) {
+ const e = new Error(`mint account not found: ${key}`);
+ e.status = 422;
+ e.code = 'mint_not_found';
+ throw e;
+ }
+
+ const programId = resolveTokenProgramForMintOwner(info.owner);
+ cache.set(key, programId);
+ return programId;
+}
diff --git a/data/changelog.json b/data/changelog.json
index ac6b588c3..e4dd12785 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,10 +1,30 @@
{
"$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-16",
+ "title": "Live Agents: every card on the wall now shows what its agent is actually doing",
+ "summary": "The Live Agents wall opened a separate live connection for every card on screen, and a browser will not give a page that many. The first handful connected, and the rest, more than forty of the forty-eight on the first page, sat on Connecting and an empty screen for as long as you left the tab open. Scrolling did not help them, because the connections that had been handed out were never given back. The wall now loads the real recent activity for the whole page in a single request, so every card has a genuine terminal of that agent's on-chain and skill actions the moment it appears, however far down the list it sits. Live connections are kept for what actually needs pushing: an agent with a real browser feed running, the one holding the spotlight, and the card you hover or tab to, which goes live under your cursor. A card that never manages to connect now falls back to its real activity instead of claiming to be connecting forever, the standby screen tells you how many actions an agent has recorded rather than flatly saying it has none, and the reaction buttons on a card no longer run off the edge of a phone screen.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/agents-live"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "You can now teach an agent your GitHub work without waiting on an OAuth app",
+ "summary": "Seeding an agent from GitHub, the flow where you tick your profile, repositories and READMEs and the agent learns to talk about what you build, needed a GitHub sign-in button that this site never had switched on. The Connected accounts card said so honestly, and that was the end of it: an Unavailable tag and nothing you could do. There is now a second way in that needs nothing set up on our side. You create a read-only token on GitHub yourself, tick read:user and nothing more, paste it into Settings, and the same consent list, the same seeding and the same one-click deletion all work exactly as before. Consent still happens on GitHub's own screen, where you choose what the token may do, and we check what you chose: a token carrying access the feature cannot use, anything reaching your private repositories or able to delete them, is refused on the spot and never stored, with the offending permission named so you know which box to untick. The token is encrypted before it is saved and destroyed when you disconnect. One honest difference from the sign-in route: disconnecting deletes our copy and every memory it produced, but GitHub gives no way for a token to delete itself, so the confirmation now tells you to remove it on GitHub too and links you straight there.",
+ "tags": [
+ "feature",
+ "improvement"
+ ],
+ "link": "/settings"
+ },
{
"date": "2026-08-16",
"title": "Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed",
- "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.",
+ "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. The same mix-up was quietly hobbling the treasury side: the buyback and micro-buy lanes read their own $THREE balance from the wrong place, always saw zero, and so never moved what they had bought into the treasury. They now read and move it correctly.",
"tags": [
"fix"
],
diff --git a/public/changelog.json b/public/changelog.json
index a748cf8b7..d849a9da6 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T17:28:16.748Z",
+ "generated_at": "2026-08-16T17:51:35.071Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -195,6 +195,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Live Agents: every card on the wall now shows what its agent is actually doing",
+ "summary": "The Live Agents wall opened a separate live connection for every card on screen, and a browser will not give a page that many. The first handful connected, and the rest, more than forty of the forty-eight on the first page, sat on Connecting and an empty screen for as long as you left the tab open. Scrolling did not help them, because the connections that had been handed out were never given back. The wall now loads the real recent activity for the whole page in a single request, so every card has a genuine terminal of that agent's on-chain and skill actions the moment it appears, however far down the list it sits. Live connections are kept for what actually needs pushing: an agent with a real browser feed running, the one holding the spotlight, and the card you hover or tab to, which goes live under your cursor. A card that never manages to connect now falls back to its real activity instead of claiming to be connecting forever, the standby screen tells you how many actions an agent has recorded rather than flatly saying it has none, and the reaction buttons on a card no longer run off the edge of a phone screen.",
+ "link": "/agents-live",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
@@ -232,7 +243,7 @@
"date": "2026-08-16",
"type": "update",
"title": "Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed",
- "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.",
+ "summary": "Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. The same mix-up was quietly hobbling the treasury side: the buyback and micro-buy lanes read their own $THREE balance from the wrong place, always saw zero, and so never moved what they had bought into the treasury. They now read and move it correctly.",
"link": "/credits",
"tags": [
"fix"
@@ -591,6 +602,17 @@
"security"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "You can now teach an agent your GitHub work without waiting on an OAuth app",
+ "summary": "Seeding an agent from GitHub, the flow where you tick your profile, repositories and READMEs and the agent learns to talk about what you build, needed a GitHub sign-in button that this site never had switched on. The Connected accounts card said so honestly, and that was the end of it: an Unavailable tag and nothing you could do. There is now a second way in that needs nothing set up on our side. You create a read-only token on GitHub yourself, tick read:user and nothing more, paste it into Settings, and the same consent list, the same seeding and the same one-click deletion all work exactly as before. Consent still happens on GitHub's own screen, where you choose what the token may do, and we check what you chose: a token carrying access the feature cannot use, anything reaching your private repositories or able to delete them, is refused on the spot and never stored, with the offending permission named so you know which box to untick. The token is encrypted before it is saved and destroyed when you disconnect. One honest difference from the sign-in route: disconnecting deletes our copy and every memory it produced, but GitHub gives no way for a token to delete itself, so the confirmation now tells you to remove it on GitHub too and links you straight there.",
+ "link": "/settings",
+ "tags": [
+ "feature",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 8a82fc035..5261725b9 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -150,6 +150,14 @@
<category>fix</category>
<description>Three repairs to the Forge model tools. The stylize filter (voxel, brick, voronoi, lowpoly) checked the requested style against its list in a way that quietly accepted a handful of reserved words, so a request naming one of them was sent to the worker with an unknown filter and no density setting instead of being turned down. The same flaw let the reference-image uploader accept a made-up file type and hand back an upload slot with a nonsense filename. Both now check their list properly, and an unrecognised value falls back to the default or is refused. Separately, while the background remover, mesh optimiser, part splitter and stylizer were checking on a running job, a momentary fault at the worker was reported as a crash on our side, once for every check, which buried the real signal in the alerts. A fault now answers plainly and the page keeps waiting, which is what a passing hiccup deserves.</description>
</item>
+ <item>
+ <title>Live Agents: every card on the wall now shows what its agent is actually doing</title>
+ <link>https://three.ws/agents-live</link>
+ <guid isPermaLink="false">2026-08-16:Live Agents: every card on the wall now shows what its agent is actually doing</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Live Agents wall opened a separate live connection for every card on screen, and a browser will not give a page that many. The first handful connected, and the rest, more than forty of the forty-eight on the first page, sat on Connecting and an empty screen for as long as you left the tab open. Scrolling did not help them, because the connections that had been handed out were never given back. The wall now loads the real recent activity for the whole page in a single request, so every card has a genuine terminal of that agent's on-chain and skill actions the moment it appears, however far down the list it sits. Live connections are kept for what actually needs pushing: an agent with a real browser feed running, the one holding the spotlight, and the card you hover or tab to, which goes live under your cursor. A card that never manages to connect now falls back to its real activity instead of claiming to be connecting forever, the standby screen tells you how many actions an agent has recorded rather than flatly saying it has none, and the reaction buttons on a card no longer run off the edge of a phone screen.</description>
+ </item>
<item>
<title>Live stage hosts stop swallowing hyphens, and only confirmed tippers get greeted by name</title>
<link>https://three.ws/stage</link>
@@ -180,7 +188,7 @@
<guid isPermaLink="false">2026-08-16:Paying with $THREE works again: credits top-ups, tips and purchases stopped failing before they were signed</guid>
<pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
<category>fix</category>
- <description>Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic.</description>
+ <description>Every attempt to top up credits with $THREE died in your wallet with a message about an incorrect program id, before you could approve anything and before any money moved. $THREE is issued under Solana's newer token standard, Token-2022, but the pages building the transfer were addressing the older one. That points the transfer at an account that does not exist, so the network rejected it during the safety check your wallet runs first. The credits page, agent tipping and the in-page purchase flow now read the standard directly from the coin itself and build against whichever one it actually uses, so $THREE and ordinary SPL tokens both go through. Two related touches on the credits page: it now tells you up front if the connected wallet holds no $THREE, or not enough for the amount you typed, instead of letting the wallet fail with something cryptic. The same mix-up was quietly hobbling the treasury side: the buyback and micro-buy lanes read their own $THREE balance from the wrong place, always saw zero, and so never moved what they had bought into the treasury. They now read and move it correctly.</description>
</item>
<item>
<title>Prompt polish keeps its quotes out of your model, and a busy Forge says so plainly</title>
@@ -446,6 +454,14 @@
<category>fix</category>
<description>Three repairs on the public API. Web search had been answering nothing but an error: the question went to Google's grounded search as designed, but the model was given a single budget to both think and reply, spent all of it thinking, and came back empty, which we correctly reported as a failure and wrongly did so on every single query. Thinking now has its own allowance on top of the answer, and when a search does come back empty the log says why instead of leaving the next person to guess. Second, the machine-readable directory at the root of the site, the file other agents read to learn what three.ws sells, would hang forever on a handful of odd names rather than saying no such thing, and a request that never ends holds a server slot until it is cut off. Every unknown name now gets a plain not-found. Third, at checkout, a wallet that hands back a payment the network could never accept is now told so at the moment it happens, instead of the modal saying sending and the error arriving later from the payment processor.</description>
</item>
+ <item>
+ <title>You can now teach an agent your GitHub work without waiting on an OAuth app</title>
+ <link>https://three.ws/settings</link>
+ <guid isPermaLink="false">2026-08-16:You can now teach an agent your GitHub work without waiting on an OAuth app</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Seeding an agent from GitHub, the flow where you tick your profile, repositories and READMEs and the agent learns to talk about what you build, needed a GitHub sign-in button that this site never had switched on. The Connected accounts card said so honestly, and that was the end of it: an Unavailable tag and nothing you could do. There is now a second way in that needs nothing set up on our side. You create a read-only token on GitHub yourself, tick read:user and nothing more, paste it into Settings, and the same consent list, the same seeding and the same one-click deletion all work exactly as before. Consent still happens on GitHub's own screen, where you choose what the token may do, and we check what you chose: a token carrying access the feature cannot use, anything reaching your private repositories or able to delete them, is refused on the spot and never stored, with the offending permission named so you know which box to untick. The token is encrypted before it is saved and destroyed when you disconnect. One honest difference from the sign-in route: disconnecting deletes our copy and every memory it produced, but GitHub gives no way for a token to delete itself, so the confirmation now tells you to remove it on GitHub too and links you straight there.</description>
+ </item>
<item>
<title>3D viewer: shared model links keep their name, and every button on the page does something</title>
<link>https://three.ws/viewer</link>