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(viewer): stop a second Embed click from sticking the card on its own confirmation

nirholas0bff347952a1
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 34ab8b058..4f69c0d8f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -35,6 +35,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Eight build tutorials now match what the platform actually does**: An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations. (`/tutorials/connect-ai-brain`) `[docs, fix]`
- **Grind-Bounty Market: shared bounty links now open the bounty, and "Grind this" grinds that one**: Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers. (`/vanity/bounties`) `[fix, improvement]`
- **Grind-Bounty Market: shared bounty links now open the bounty, and "Grind this" grinds that one**: Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers. (`/vanity/bounties`) `[fix, improvement]`
+- **KOL Tracker: the whole board is readable on a phone, and dead columns are gone**: On any screen narrower than the board, five of the tracker's seven columns were unreachable: the page could not shrink, and the overflow was clipped rather than scrollable, so P&L, win rate and trade count simply were not there on a phone. The board now fits any viewport and scrolls sideways on its own. Columns with nothing to show are dropped instead of rendering a full column of dashes, so followers and volume appear only once there is data behind them. Each wallet is printed once (it used to appear twice on every row) and links to its Solscan account, so any number on the board can be audited on-chain. Where the P&L for a window comes from is now stated once under the board instead of repeating on all fifty rows, the board refreshes every minute with the time of the last update on screen, and a refresh that fails keeps the rows you are reading rather than blanking them. A failed load now offers a Try again button, an empty window points at the trader leaderboard, and the whole board is navigable and announced properly with a keyboard and a screen reader. (`/tracker`) `[fix, improvement]`
- **Looking up an on-chain agent by its CAIP reference works again**: The public resolver that turns an ERC-8004 agent reference into its owner, token URI and verified agent card could not be reached at all. An agent reference ends in a slash before its token id, and the documentation told callers to percent-encode the whole reference, which turns that slash into %2F. The API refuses any address segment holding an encoded separator, because that is the same trick used to escape a path and reach files that were never meant to be served, so every correctly-formed lookup was turned away as an unknown address before it ever reached the resolver. The verification badge you can embed on your own site built its request in exactly that shape, so it never showed a result either. The resolver now accepts the reference with its slash as a normal part of the address, the badge asks for it that way, and the documentation shows the form that works. The protection against encoded separators is untouched. New tests resolve the address through the same routing the live site uses, so this cannot quietly break again. (`/docs/api-reference`) `[fix]`
- **Oracle stops answering "nothing is happening" when the database is the thing that is down**: Several Oracle reads shared a habit: if the database was unreachable for a few seconds, they answered normally with an empty result. The movers panel said nothing was moving, the stats hero said no coin had ever been scored and no agent was armed, a coin's conviction sparkline came back flat, and the machine-readable signal endpoint told autonomous agents there were no plays, which is exactly the cue for an agent to stand down. Every one of those answers was then cached at the edge for a minute or two, so a blip lasting seconds kept showing a dead market long after the database was back. Those endpoints now tell the difference between a connectivity failure and an ordinary query fault: the first is reported honestly as a temporary outage with a retry hint and is never cached, the second still degrades to the empty answer it always did. The social ingest got the sharper end of the same bug: it used to reply that a batch had been accepted while reporting zero mints written, a receipt for a write that never landed. It now fails loudly so the sender retries. Shared conviction cards behave too: one built during an outage is no longer pinned to a coin's link preview for 15 minutes. (`/oracle`) `[fix, improvement]`
- **Pages stop loading a 3D robot you have not scrolled to yet**: The small animated robot in the site footer was starting up the moment a page opened, at the bottom of a page nobody had scrolled to. On plain pages that meant downloading a whole second 3D engine (253 KB) before anything else, and on the Forge it was the single busiest thing on the page: nearly 20 seconds of browser work, more than the Forge itself. It now waits until you are about a screen away from the footer, so it still greets you on the way down but no longer competes with the page you actually opened. It also stops taking a 3D slot away from the avatars on the page, which on a busy grid could leave a real avatar unable to render. Separately, the Forge's example prompt chips no longer shove the page down as they shuffle to a fresh set on load. (`/forge`) `[improvement, fix]`
@@ -101,9 +102,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Viability now shows skeletons while it reads and says what broke when a read fails**: The Viability page (/viability) reports the two real money loops behind three.ws: $THREE marketplace GMV and take-rate, and guarded agent coin trades with realized P&L. Until now, a slow read left the page as a bare headline with nothing underneath, and a failed read quietly deleted both panels while the page still claimed it had just updated. Both panels now hold their shape with skeletons while the live read is in flight, so the numbers land without the page jumping. If a read fails, that panel says so in plain language, names the reason (offline, rate limited, the status the API returned, or a deploy still rolling out), and offers a Retry that re-runs only that panel, leaving a healthy one untouched. The freshness stamp is honest too: it reports a read in flight, a failed read, or how long ago the figures on screen were actually good. Section titles are now real headings, and the network toggle announces itself correctly to screen readers. (`/viability`) `[improvement, fix]`
- **Voice and vision SDKs ship runnable examples, and the x402 seller SDK reads its Solana sponsor from the environment**: @three-ws/voice and @three-ws/vision-mcp now include example scripts you can run as-is against the live free lanes: the voice one speaks a sentence, animates a face from those exact bytes, and transcribes it back; the vision one probes the lane, writes alt text for an image, and reads the text off it. @three-ws/x402-server used to demand the Solana sponsor account as a code option even though its own error message told you to set X402_FEE_PAYER_SOLANA, so a correctly configured deployment still got missing_fee_payer; it now reads that environment variable when the option is omitted. The VS Code x402 extension's endpoint scaffolder was generating Base-only endpoints and now generates Solana-first ones, matching every paid route on the platform, and it ships with a test suite covering which payment requirement it selects. `[sdk, fix]`
- **Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click**: Google Gemini has been refusing every request on the platform's account, and Voice Lab had no way to know: it listed all 30 Gemini voices, put them first, and the first Preview a visitor pressed came back with a wall of raw error JSON quoting internal project numbers. Now the first refusal is the last one anybody sees. A provider that turns down the platform's credentials is withheld from the voice list for a few minutes with the reason written on its filter chip, its voices disappear from the grid the moment a preview hits it, and the free Microsoft Edge and NVIDIA lanes are named as the alternative. It restores itself the moment the provider works again, with nothing to switch back on by hand. Failure messages across the page are now single readable sentences rather than vendor dumps. The rest is the same page, checked end to end: the catalog error state offers a working Try again, a search that matches nothing offers Clear filters, a deployment with no provider at all says so instead of claiming no voices match, the Remove button next to your own ElevenLabs key is styled like a button again, every control shows a focus ring when you tab to it, and the text box in the playground has a label. The space bar no longer hijacks the button you are pressing: it starts a recording only when nothing on the page is focused. (`/voice`) `[fix, improvement]`
+- **Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it**: Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to "updates live": it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation. (`/walk-leaderboard`) `[fix, improvement]`
- **Watchlist: the portfolio summary stops reporting numbers it does not have**: The watchlist summary bar claimed $0 of 24h volume across every coin you watch. The pump.fun feed simply stops reporting 24h volume once a coin graduates, and the bar was treating each missing figure as a zero and adding them up, so a confident "$0" stood where the honest answer is "not reported". Every aggregate now counts only the coins that actually report it, shows a dash when none do, and says on hover how many of your watched coins it covers. The Oracle tier bar does the same: coins the Oracle has not scored get their own marked-off slice instead of quietly vanishing from the distribution, and each unscored card now carries an "unrated" badge that links to its coin page rather than leaving a blank corner. If the Oracle itself is unreachable, the page says so instead of labelling every coin unrated. Also fixed: at 320px wide the "Clear all" button was pushed off the edge of the screen with no way to reach it, the add-a-coin field had no visible keyboard focus ring, and the page description advertised a verdict the page does not show. (`/watchlist`) `[fix, improvement]`
- **Widget analytics can tell you where your visitors are again, and a shared widget link previews correctly everywhere**: The country column in your widget stats has been empty since the platform moved to its current host in July. A visitor's country was read from a header only the old host set, so once it was gone every view was recorded with no country at all and the top-countries panel stayed blank no matter how much traffic a widget got. Country is now read from the headers our current edge provides, and it is checked against the shape of a real two-letter country code before it is stored, so nobody can push junk into your analytics by editing a request. Chat sessions on talking-agent widgets get the same fix. Separately, the oEmbed endpoint that Slack, Discord, WordPress, Ghost and Notion call to unfurl a shared widget link now says plainly when a consumer asks for a format we do not publish, instead of returning JSON labelled as the format that was asked for and leaving the embed broken with nothing to explain why. (`/widgets`) `[fix, improvement]`
- **World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard**: The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a "Meet the agent in AR" option next to "Begin the encounter", and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970. (`/world-lines`) `[fix, improvement]`
+- **Your master wallet: creating one no longer reports a failure, and your balances are real numbers again**: Two faults on the master wallet page are fixed. First, every account that pressed Create my master wallet was told the creation had failed. The wallet was in fact created every time; the page then showed an error, and the same fault sat on the send and fund-an-agent paths, where a transfer that had already settled on Solana was reported as "The transfer did not go through", inviting people to send the same money twice. Nothing about the money was ever wrong, only what the page said about it. Second, the SOL and Solana USDC figures, and the total value, read "unavailable" for everyone regardless of what the wallet held, because the balance reader and the page were describing balances in two different shapes. They now show live amounts, priced against the SOL rate, and an empty wallet reads a plain 0 instead of "unavailable". A balance the network genuinely could not answer for still says "unavailable" and is left out of the total rather than counted as zero. Alongside that: failures now explain themselves in plain words with a support reference instead of printing raw operator text, the explainer bubbles fit inside a phone screen, and each one names what it explains for screen-reader users. (`/wallet`) `[fix, improvement]`
- **Your walk keeps syncing across devices, and a remotely driven avatar reports where it really is**: Four fixes across the walking avatar. Signed-in walkers sync their walk (avatar, environment, camera, position) between devices, and the page saves that snapshot on a half-minute heartbeat, but the endpoint only allowed thirty writes an hour and counted every read against the same budget: about a quarter hour into a walk, syncing quietly stopped, and everyone sharing an office or cafe connection shared one allowance. Writes are now measured per account, sized to how often the page actually saves, and reading your snapshot back costs nothing. When an outside program drives a live walk page through the control API, the page reports its position, heading, motion and scene on every poll; one unexpected value in that report used to discard the whole thing, so the controller's status read could show a stale avatar with nothing to explain it. Each field is now taken on its own merits. A command sent with an invalid control token is refused before its contents are inspected. And the leaderboard now shows an unranked walker with the same handle, profile link and picture as everyone else on the board, always drawn from a single avatar rather than pairing one avatar's name with another's picture. (`/walk`) `[fix]`
## 2026-08-14
diff --git a/prompts/swarm-100/route-viewer.md b/prompts/swarm-100/route-viewer.md
deleted file mode 100644
index 9de09566b..000000000
--- a/prompts/swarm-100/route-viewer.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Route audit: /viewer (glTF / GLB Viewer)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. This route's declared entry (path, description, added date):
-
- node -e "const p=require('./data/pages.json');for(const s of p.sections)for(const g of s.pages)if(g.path==='/viewer')console.log(JSON.stringify(g,null,2))"
-
-2. Find the serving implementation: grep "/viewer" in vercel.json (the live
- route table server/index.mjs boots from), then list matching files in
- pages/ and src/. STRUCTURE.md maps every surface to its directory if the
- grep is ambiguous.
-3. Production right now:
-
- curl -so /dev/null -w '%{http_code}\n' https://three.ws/viewer
-
-4. Start (or reuse) the local dev server: npm run dev (vite, port 3000).
-
-## Task: audit this one route end to end, then fix everything found
-
-Route: /viewer ("glTF / GLB Viewer", section "labs").
-Declared purpose: Preview any public glTF/GLB inline, then take it further: pose and animate it, restyle the material, build a scene, place it in AR, embed it on your site, or launch it as a pump.fun coin.
-
-Drive the page in a real headless browser. Playwright is already a dev
-dependency; keep your probe script in the session scratchpad, never in the
-repo.
-
-1. Load http://localhost:3000/viewer. Record the HTTP status, every console
- error and warning, and every failed network request.
-2. Exercise it like a first-time user: click the primary actions, run the
- primary flow if one exists, follow the page's internal links. Every button
- must do something real; every link must resolve. If the page renders data,
- prove in the network log that it came from a live endpoint, not a baked-in
- fallback array.
-3. States: verify populated, empty, loading, and error states are designed and
- reachable. Block the page's primary fetch in Playwright and confirm an
- actionable error state appears, not a blank void or a raw exception.
-4. Responsive: render at 320, 768, and 1440 px. No horizontal page scroll, no
- overlapping or clipped controls.
-5. Accessibility basics: one h1; interactive elements are real buttons or
- links with visible focus states; images carry alt text; form fields have
- labels.
-6. Head: a specific title tag and meta description that match the declared
- purpose above.
-7. Fix every defect at its root in the page's real source files and re-run the
- probe until clean. Defects in shared modules are in scope when this route
- exercises them.
-
-## Definition of done
-
-- [ ] Local load of /viewer: HTTP 200, zero console errors, zero unhandled
- failed requests (a third-party outage must land in a designed fallback,
- not a broken page).
-- [ ] No dead interactive element on the page: no stub href="#", no button
- without a handler, no link to a missing path.
-- [ ] Empty, loading, error, and populated states verified.
-- [ ] 320 / 768 / 1440 px renders verified clean.
-- [ ] Title and meta description present and specific.
-- [ ] npm test passes; npm run check:rules -- --paths <touched files> exits 0.
-- [ ] Production status from step 0 recorded in the report; if production
- needs a deploy to pick up a fix, the report says so (deploys stay
- owner-gated).
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/route-viewer.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index e451967e4..296de7331 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T21:13:40.596Z",
+ "generated_at": "2026-08-15T21:35:55.185Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -319,6 +319,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "KOL Tracker: the whole board is readable on a phone, and dead columns are gone",
+ "summary": "On any screen narrower than the board, five of the tracker's seven columns were unreachable: the page could not shrink, and the overflow was clipped rather than scrollable, so P&L, win rate and trade count simply were not there on a phone. The board now fits any viewport and scrolls sideways on its own. Columns with nothing to show are dropped instead of rendering a full column of dashes, so followers and volume appear only once there is data behind them. Each wallet is printed once (it used to appear twice on every row) and links to its Solscan account, so any number on the board can be audited on-chain. Where the P&L for a window comes from is now stated once under the board instead of repeating on all fifty rows, the board refreshes every minute with the time of the last update on screen, and a refresh that fails keeps the rows you are reading rather than blanking them. A failed load now offers a Try again button, an empty window points at the trader leaderboard, and the whole board is navigable and announced properly with a keyboard and a screen reader.",
+ "link": "/tracker",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -1038,6 +1049,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it",
+ "summary": "Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to \"updates live\": it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation.",
+ "link": "/walk-leaderboard",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -1071,6 +1093,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Your master wallet: creating one no longer reports a failure, and your balances are real numbers again",
+ "summary": "Two faults on the master wallet page are fixed. First, every account that pressed Create my master wallet was told the creation had failed. The wallet was in fact created every time; the page then showed an error, and the same fault sat on the send and fund-an-agent paths, where a transfer that had already settled on Solana was reported as \"The transfer did not go through\", inviting people to send the same money twice. Nothing about the money was ever wrong, only what the page said about it. Second, the SOL and Solana USDC figures, and the total value, read \"unavailable\" for everyone regardless of what the wallet held, because the balance reader and the page were describing balances in two different shapes. They now show live amounts, priced against the SOL rate, and an empty wallet reads a plain 0 instead of \"unavailable\". A balance the network genuinely could not answer for still says \"unavailable\" and is left out of the total rather than counted as zero. Alongside that: failures now explain themselves in plain words with a support reference instead of printing raw operator text, the explainer bubbles fit inside a phone screen, and each one names what it explains for screen-reader users.",
+ "link": "/wallet",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index de49e9d9e..adfc74413 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -238,6 +238,14 @@
<category>fix</category>
<description>Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#&lt;id&gt;), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers.</description>
</item>
+ <item>
+ <title>KOL Tracker: the whole board is readable on a phone, and dead columns are gone</title>
+ <link>https://three.ws/tracker</link>
+ <guid isPermaLink="false">2026-08-15:KOL Tracker: the whole board is readable on a phone, and dead columns are gone</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>On any screen narrower than the board, five of the tracker's seven columns were unreachable: the page could not shrink, and the overflow was clipped rather than scrollable, so P&amp;L, win rate and trade count simply were not there on a phone. The board now fits any viewport and scrolls sideways on its own. Columns with nothing to show are dropped instead of rendering a full column of dashes, so followers and volume appear only once there is data behind them. Each wallet is printed once (it used to appear twice on every row) and links to its Solscan account, so any number on the board can be audited on-chain. Where the P&amp;L for a window comes from is now stated once under the board instead of repeating on all fifty rows, the board refreshes every minute with the time of the last update on screen, and a refresh that fails keeps the rows you are reading rather than blanking them. A failed load now offers a Try again button, an empty window points at the trader leaderboard, and the whole board is navigable and announced properly with a keyboard and a screen reader.</description>
+ </item>
<item>
<title>Looking up an on-chain agent by its CAIP reference works again</title>
<link>https://three.ws/docs/api-reference</link>
@@ -766,6 +774,14 @@
<category>fix</category>
<description>Google Gemini has been refusing every request on the platform's account, and Voice Lab had no way to know: it listed all 30 Gemini voices, put them first, and the first Preview a visitor pressed came back with a wall of raw error JSON quoting internal project numbers. Now the first refusal is the last one anybody sees. A provider that turns down the platform's credentials is withheld from the voice list for a few minutes with the reason written on its filter chip, its voices disappear from the grid the moment a preview hits it, and the free Microsoft Edge and NVIDIA lanes are named as the alternative. It restores itself the moment the provider works again, with nothing to switch back on by hand. Failure messages across the page are now single readable sentences rather than vendor dumps. The rest is the same page, checked end to end: the catalog error state offers a working Try again, a search that matches nothing offers Clear filters, a deployment with no provider at all says so instead of claiming no voices match, the Remove button next to your own ElevenLabs key is styled like a button again, every control shows a focus ring when you tab to it, and the text box in the playground has a label. The space bar no longer hijacks the button you are pressing: it starts a recording only when nothing on the page is focused.</description>
</item>
+ <item>
+ <title>Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it</title>
+ <link>https://three.ws/walk-leaderboard</link>
+ <guid isPermaLink="false">2026-08-15:Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to &quot;updates live&quot;: it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation.</description>
+ </item>
<item>
<title>Watchlist: the portfolio summary stops reporting numbers it does not have</title>
<link>https://three.ws/watchlist</link>
@@ -790,6 +806,14 @@
<category>fix</category>
<description>The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a &quot;Meet the agent in AR&quot; option next to &quot;Begin the encounter&quot;, and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970.</description>
</item>
+ <item>
+ <title>Your master wallet: creating one no longer reports a failure, and your balances are real numbers again</title>
+ <link>https://three.ws/wallet</link>
+ <guid isPermaLink="false">2026-08-15:Your master wallet: creating one no longer reports a failure, and your balances are real numbers again</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Two faults on the master wallet page are fixed. First, every account that pressed Create my master wallet was told the creation had failed. The wallet was in fact created every time; the page then showed an error, and the same fault sat on the send and fund-an-agent paths, where a transfer that had already settled on Solana was reported as &quot;The transfer did not go through&quot;, inviting people to send the same money twice. Nothing about the money was ever wrong, only what the page said about it. Second, the SOL and Solana USDC figures, and the total value, read &quot;unavailable&quot; for everyone regardless of what the wallet held, because the balance reader and the page were describing balances in two different shapes. They now show live amounts, priced against the SOL rate, and an empty wallet reads a plain 0 instead of &quot;unavailable&quot;. A balance the network genuinely could not answer for still says &quot;unavailable&quot; and is left out of the total rather than counted as zero. Alongside that: failures now explain themselves in plain words with a support reference instead of printing raw operator text, the explainer bubbles fit inside a phone screen, and each one names what it explains for screen-reader users.</description>
+ </item>
<item>
<title>Your walk keeps syncing across devices, and a remotely driven avatar reports where it really is</title>
<link>https://three.ws/walk</link>
diff --git a/public/features.json b/public/features.json
index 175a3a4ee..ba9b6d0ca 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T21:13:40.484Z",
+ "generated_at": "2026-08-15T21:35:54.904Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/public/viewer.html b/public/viewer.html
index 4100af82b..5f203018f 100644
--- a/public/viewer.html
+++ b/public/viewer.html
@@ -510,8 +510,13 @@
// Embed: copy a paste-anywhere iframe of this exact viewer.
var embedCard = document.getElementById('act-embed');
+ var embedBusy = false;
function escAttr(s) { return s.replace(/&/g, '&amp;').replace(/"/g, '&quot;').replace(/</g, '&lt;'); }
embedCard.addEventListener('click', function () {
+ // While the result line is showing, the snippet is already on the clipboard.
+ // Ignoring the click keeps that line from being read back as the default.
+ if (embedBusy) return;
+ embedBusy = true;
var embedDefault = cardDesc('embed-d').textContent;
var pageUrl = location.origin + '/viewer?src=' + enc(src) + tOpt;
var snippet = '<iframe src="' + escAttr(pageUrl) + '" width="640" height="480" '
@@ -519,7 +524,7 @@
+ 'allow="xr-spatial-tracking; fullscreen" title="' + escAttr(title || '3D model') + ' · three.ws 3D viewer"></iframe>';
function done(ok) {
setCardDesc('embed-d', ok ? 'Copied. Paste it into any HTML page.' : 'Copy failed: select and copy the address bar URL instead.');
- setTimeout(function () { setCardDesc('embed-d', embedDefault); }, 2600);
+ setTimeout(function () { setCardDesc('embed-d', embedDefault); embedBusy = false; }, 2600);
}
if (navigator.clipboard && navigator.clipboard.writeText) {
navigator.clipboard.writeText(snippet).then(function () { done(true); }, function () { done(false); });