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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(changelog): publish the vaults deposit fix and six other agents' pending entries
nirholas973afdc85084
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex d367a9bf8..34ab8b058 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -6,6 +6,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-08-15+- **3D viewer: shared model links keep their name, and every button on the page does something**: Open a shared model link and the browser tab now keeps the model's name instead of resetting to a generic one a moment after the page loads, so a bookmarked or shared viewer link is identifiable again. The model's name is also the page's heading now, which is what screen readers and search engines read first. A link whose address does not point at a real https model file used to show a Download button that did nothing; the page now explains what is wrong with the link and offers the only action that helps. Copying the embed snippet from 'Embed it anywhere' confirms it copied, and launching a coin from the model shows that the token image is rendering, both of which were being written to a part of the page the visitor could not see. The page's own title and description now describe what the viewer actually does: preview any public glTF or GLB model, then pose, restyle, scene, AR, embed or download it. (`/viewer`) `[fix, improvement]`- **A broken paid endpoint is no longer reported as a free one**: Payment sessions let you hand an agent a budget instead of a key, and two parts of that path judged an endpoint by one rule: if it did not ask for payment, the call was free. That is only true when the endpoint actually succeeded. A paid API answering 404, 400, or 500 was being scored as a free call, and the consequences ran in the wrong direction in both places. The dry run at /pay/simulator, whose whole job is to tell you in advance whether a budget and an allowlist will carry a workload, reported a plan as feasible at a cost of nothing when in fact every endpoint in it was erroring: free calls are never priced, never allowlist-checked, and never counted, so a wall of failures looked like a clean run. And an agent spending through a session got back a success envelope saying no payment was needed for an endpoint that had just failed on it. Both now separate the two cases: a real success with no payment challenge is still free and still costs nothing, while an error status is reported as an endpoint failure carrying the status the endpoint actually returned. No session is charged either way. The simulator lists each failing endpoint by name in its problems list and no longer calls the plan feasible. (`/pay/simulator`) `[fix]`- **A market intelligence outage no longer tells you your own API key was rejected**: The two market intelligence reads in the unified API, recent narrative intel and momentum-ranked projects, pass a key we hold to the upstream provider; a caller needs no key at all. When that provider stopped accepting our key, both reads answered "unauthorized" with the provider's own wording, so an agent reading the response concluded its own credentials were bad and retried with different ones forever, when nothing on the caller's side was wrong. Both reads now say plainly that the service is temporarily unavailable because this deployment's upstream key was rejected, which is a status clients already know to retry rather than re-authenticate against. The older market intelligence endpoints always classified this correctly; the classification now lives in one place, so the two doors cannot drift apart again, and the error tables in the API reference list every code either one can return. (`/docs/api-reference`) `[fix, docs]`- **A Premium Data API pass you bought straight from your wallet now shows up on your billing page**: You can buy a pass without an account, paying from a Solana wallet on the Data API page. Do that, then sign in with the same wallet later, and billing showed you nothing: the pass was live, the API key worked, but the page insisted you had never bought anything. It was reading a single legacy address field on the account, and signing in with a Solana wallet never fills that field, so the lookup could not match a purchase it was standing right next to. Billing now resolves every Solana wallet you have signed into the account and shows every pass any of them bought, including purchases made before the account existed, with each pass's key, rate limit, and usage. Only wallets you have actually signed in with count, so nobody can claim someone else's purchases by typing an address. Two smaller repairs alongside it: the pricing endpoint now reports each asset's decimal precision from the same source that computes the amount you owe, rather than a fixed number that could one day render a price wrong by a factor of a hundred; and key rotation is now metered per account, because every rotation mints a real key. (`/dashboard/billing`) `[fix, improvement]`@@ -22,10 +23,14 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **An embedded agent keeps talking when the browser refuses to play its voice**: The living agent body that renders inside ChatGPT, Claude, and any site that embeds it speaks each reply with a lip-synced mouth. When a voice track is attached, the body plays the audio and drives the mouth from it. Browsers block that playback routinely: a chat panel the visitor has not clicked in is not allowed to start audio. The body was falling back to an empty line in that case, so it stood there with its mouth shut through the whole reply. It now falls back to the text of the reply it was actually given, so the mouth speaks the line whether or not the audio was allowed to start, and the engine is now covered by tests for the load, speak, emotion, chain-state, and teardown paths. `[fix]`- **Arming an Oracle agent for live trading no longer rounds your trade size up**: The arm page clamps the risk knobs on the server so a bad number can never reach the trading loop, and those clamps have a floor: the smallest trade the loop will place is 0.001 SOL. That floor was being applied in the wrong direction. Ask to arm a live agent with a per-trade size of zero, and instead of being told no, you were armed for real spending at 0.001 SOL a trade with a half-SOL daily ceiling you never asked for. The check meant to catch this looked at the number after the clamp had already raised it, so it could never fire. Arming live now refuses any per-trade size below the floor, and any daily cap smaller than a single trade, and tells you which number to fix; nothing is armed until you do. Clamping a too-large number back down to the ceiling is unchanged, and simulate runs keep the same forgiving behaviour as before. The arm page also shows the reason a save was rejected instead of one generic line, so an ownership problem no longer reads the same as a bad trade size, and a failed Telegram test now prints what Telegram actually said. (`/oracle/arm`) `[fix, security]`- **Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one**: The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed. (`/docs/api-reference`) `[fix, improvement]`+- **Avatar SDK: the React entry finally loads, and the viewer answers to properties as well as attributes**: The React bindings in @three-ws/avatar shipped as a .jsx file even though they contain no JSX, which meant Node refused to import them and browsers refused to run them as a module script: the live React SDK demo had been failing with a MIME type error. That entry is now plain JavaScript, so 'import ... from "@three-ws/avatar/react"' works in Node, in Next.js, and straight from a browser import map, and the demo page renders all four bindings again. The lightweight <three-ws-viewer> element now also accepts src, alt, background, ar and autoRotate as properties, not only as attributes, so frameworks that assign properties (React 19, Vue, or any Object.assign helper) drive it correctly, including values set before the element upgrades. The package's documentation was corrected in the same pass: the element method list now matches the methods that actually exist, the Avatar Studio default URL is the real one, the license is stated correctly, and the two dependency-free runtime entry points are documented. (`/demos/react-sdk`) `[sdk, fix, docs]`+- **Avatar Studio: the trait builder loads again, with its manifest, icons and frames intact**: The trait-based Avatar Studio, the point-and-click builder behind the “three.ws Studio” option in the avatar creator, was shipping a blank page: two copies of React at different versions landed in the bundle, and React refuses to start when its renderer does not match. Both are pinned to the same version now. Behind that, the builder asked for its character manifest at a path containing the literal word “undefined”, so even a booting studio had no character classes to offer; it now reads the manifest from its own base path. The texture-compression library it loads at startup was requested at a doubled URL in local development and never arrived, and the trait card frames, rarity boxes and back/next arrows were pointed one directory too deep, so they silently 404ed. Every one of those assets resolves now, and if the compressor genuinely cannot start, an export that needs it says so instead of failing with an internal error. The in-app creator, the avatar SDK and the Avatar OS demo now open the builder at its exact entry point, so they can no longer land on the wrong studio page. (`/docs/character-studio`) `[fix]`- **Avatars can move their lips again: the Audio2Face lane is back**: Every call that turns speech into facial animation had been failing with an upstream not-found error, so a talking avatar spoke with a frozen face and the one-shot say() path returned nothing usable. The hosted model id the lane pointed at had stopped resolving for our NVIDIA account. It now points at the hosted Audio2Face NIM that is actually live, verified end to end: a synthesized clip drives a 30 fps ARKit blendshape track whose jaw genuinely opens and closes with the words. The discovery helper that finds these model ids was missing the name NVIDIA publishes them under, which is why the outage looked like a configuration mystery; it now finds them. `[fix]`+- **Back-an-Agent Vaults: a successful deposit no longer reports itself as a failure**: Depositing an amount with cents in it (anything that is not a whole dollar) settled on-chain and then showed the backer an error, because the confirmation line converted the amount through floating point and threw on the result. That is fixed, and the confirmation now names the shares you received. Opening a vault and pressing the browser's back button used to trap you on the page: every back press rebuilt the same entry instead of leaving. The open positions table said nothing at all when a vault's holdings had all been sold down to zero; it now says the capital is in USDC. A vault that failed to load offers a retry and a way back to the list instead of a dead end, and a display fault is no longer reported as a network problem. Anonymous visitors no longer trigger a failed sign-in check on load, the feed and the sign-in check now run at the same time rather than one after the other, the open-a-vault form no longer offers a submit button when you have no agents to open one behind, and the dialogs take keyboard focus, keep Tab inside them, and hand focus back when they close. (`/vaults`) `[fix, improvement]`- **Claim Your Wallet stopped telling real traders they had no track record**: Pasting a wallet into Claim Your Wallet could answer "not indexed yet" to a wallet with thousands of indexed pump.fun trades. The page only accepted a wallet the reputation scorer had already graded, and that scorer runs on a rollup that lags the trade indexer by design, so a wallet the platform had watched trade for days was still turned away. Any wallet with a real on-chain record now renders its full ledger and window aggregates immediately, with the reputation panel honestly reading unproven until the grade lands. Three more fixes shipped with it. Win and loss counts now cover closed positions only, so a trader still holding sixty fresh bags no longer reads as sixty losses, and a new realized profit-and-loss figure sits beside the existing net figure that charges an open bag's entry as if it were written off. Asking for devnet returned the wallet's mainnet trades; both halves of the read are now scoped to the network you asked for. And if the database is unreachable, the page now says the record is temporarily unavailable and offers a retry, instead of publishing an empty scorecard that the CDN would then serve to everyone for the next few minutes. (`/claim-wallet`) `[fix]`- **Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page**: The Coin Intelligence radar lets you narrow the live launch feed by verdict (Strong, Watch, Caution, Avoid) and search it by name, symbol, or mint. Both filters were applied only to the page of coins already fetched, so asking for 60 Strong coins returned whichever handful of the newest 60 launches happened to be Strong: one, on a busy day. That reads as "the engine found nothing" when the engine had plenty. Search had the same blind spot, and could not see a coin that matched but sat a page or two back. Search is now run by the database across the observed feed, and the verdict filter looks through a much deeper recent window before handing back the page you asked for, so a filtered view returns a full page whenever a full page of matches exists. Searching for a literal percent sign or underscore now matches that character instead of behaving as a wildcard. The live trade tape at /api/pump/dex-trades also became readable from any origin, matching every other public pump.fun read endpoint, so an agent running on its own domain can consume it directly. (`/coin-intel`) `[fix, improvement]`- **Daily usage caps stopped resetting themselves partway through the day**: When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over. `[fix, infra]`+- **DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending**: The Yields explorer was shipped with its filter row pointing at a stylesheet the page never loaded, so the chain, project and minimum-TVL controls rendered as raw browser dropdowns crammed into one line with their labels colliding. They are proper labelled fields again at every screen size. On a 320 pixel phone the Total TVL card used to be pushed off the right edge with no way to scroll to it, and opening a pool parked its chart outside the visible area inside a table you had to drag sideways; the three headline stats now stack, and the chart stays pinned in view and is drawn at the drawer's real width, so its axis labels are legible instead of shrunk to a third of their size. Fourteen DeFiLlama protocols carry a bracket, a plus or an exclamation mark in their name, and every yield row for one of them linked to a page that answered 404: those links now resolve. When the upstream feed is down, the three stat cards say so rather than sitting as loading placeholders forever, and the result count says the data is unavailable instead of going blank. (`/yields`) `[fix, improvement]`- **Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands**: Nine documentation pages are written as article drafts, so each one starts with a small block of publishing metadata: the title, where it is meant to run, its tags. That block is meant for the tooling, not for you, but the docs reader had no idea what it was and rendered it as an enormous heading at the very top of the article, above the actual writing. It is now recognised and hidden, on the page and in the Copy page text, so those articles begin where they should. Reading the same pages closely turned up claims that had drifted: several said three.ws was already live on AWS Marketplace and billing usage to your AWS invoice. The integration is built and deployed, but the listing itself has not been published yet and the pricing decision is a free subscription with no AWS metering, so the AWS pages now say exactly that and point at the page that tracks the status. The MCP article's vanity-address tool was also listed at a metered price of up to fifty cents; it is a flat five cents per grind, which is what the code has always charged. (`/docs/aws-marketplace`) `[docs, fix]`- **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]`@@ -40,6 +45,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Posed avatar renders finally come out posed**: Asking the public avatar renderer for a pose returned a T-pose on most models: it matched bone names against a short hand-written list, and any rig that did not use those exact names (including every Mixamo export) was silently left in its bind pose while the response still claimed the pose had been applied. The renderer now uses the same posing engine the pose studio uses, so a preset now lands whatever naming convention the model's skeleton uses, and the camera frames the posed figure rather than the unposed one. The background colour on both public renderers is now checked before it is used, and the per-render budget is counted across the whole fleet instead of per server. (`/docs/api-reference`) `[fix, security]`- **Premium Vanity Inventory shows the whole shelf, and is readable in light mode**: The premium vanity shelf listed only the first hundred pre-ground addresses out of the hundreds actually in stock, with nothing on the page saying so: every address past that point was unbuyable because no one could see it. The page now loads sixty at a time, states plainly how many of the total you are looking at, and pages through the rest on demand. In light mode the page was close to unusable, because the addresses themselves, the buy dialog, and the custody notice were all painted in colours meant for the black background; the whole page now switches palette properly. Four smaller fixes shipped with it: the retry button on a failed load rendered as raw browser chrome and threw away your filter, so it is now a real button that simply re-runs the search you had; filtering down to no matches now offers a one-click way to clear the filter instead of just suggesting it; the word x402 in the intro linked to the vanity gallery rather than the x402 page; and keyboard users get a visible focus ring on the search and sort controls, which previously had theirs suppressed. (`/vanity/premium`) `[fix, improvement]`- **Private avatars no longer show their picture in registry lookups**: The registry lookup that turns an agent id, avatar id, slug, or Solana mint into one record already refused to hand out the 3D model of a private avatar, but it still returned the rendered preview image of that same avatar, so anyone holding the id could see what a private creation looked like. The preview is now gated on exactly the same visibility as the model: a private avatar returns its name and identity and no imagery at all. The embeddable widget read did the same thing with its avatar thumbnail and got the same gate. Separately, every read path that turns a stored thumbnail into a URL now goes through the one resolver that drops the old broken image keys, so agent manifests, token metadata, and launch feeds stop publishing image links that answer 404. `[security, fix]`+- **Proof-of-Grind Gallery: filters stop stranding the board, and a shared card proves it is on it**: Switching tier or sort while the gallery was still loading could leave you staring at an empty board until you reloaded: the page refused the new request because the old one had not finished, and then never drew anything. The newest request now always wins, so filters respond immediately no matter how fast you click them. When the board itself could not be reached, the summary strip announced "Gallery: Live", which was simply false; it now says the stats are unavailable and offers a Retry, as do the gallery and the leaderboard, and each retry re-runs just that request instead of reloading the whole page (the gallery's old retry button also rendered as raw browser chrome). Publishing a wallet refreshed the gallery but not the leaderboard, so your new entry was missing from the ranking until you reloaded. Sharing a card is now worth something: opening a shared link shows whether that address really is on the board, with its verified badge, tier and label, instead of only a local estimate. Alongside those: filtering down to nothing offers a one-click way to clear the filters, a failed "Load more" says so instead of silently doing nothing, the tabs work with the browser back button and with arrow keys, a rate-limited publish explains how long to wait rather than printing "too many requests", and a gateway failure during publish no longer surfaces a raw parser error. (`/vanity/gallery`) `[fix, improvement]`- **Push notification sign-up now only accepts a real push service address**: Turning on browser notifications hands the platform the address your browser wants alerts delivered to, and that address is one the platform later calls from its own servers. It was stored exactly as given, so a crafted sign-up could point it at an internal address instead of a push service and use the delivery job as a way to knock on doors inside our own network. Sign-up now checks the address before storing it: it has to be an ordinary secure web address on a genuinely public host, or it is refused with a clear reason. If the check cannot finish because name lookup is briefly down, the browser is told to try again rather than being turned away for good. Delivery re-checks every stored address at send time too, so anything registered before this landed can never be dialed, and an address that could never be legal is dropped from the list the way an expired one already was. `[security]`- **Rotating or revoking an x402 API key now requires a proof the request came from you**: The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all. (`/billing/keys`) `[security, fix]`- **Saving a big build no longer re-downloads the whole world first**: Every time you saved a world, the service fetched and re-parsed the entire previous version of that world just to check who owns it. On a large build that meant a full extra download and parse on each autosave, for a single ownership field. The check now reads only the small index record, so saves on big worlds are noticeably quicker and the storage layer does half the work. Two error replies also got honest labels: a build that exceeds the size cap now answers "payload too large" and a request sent with the wrong content type answers "unsupported media type", instead of both arriving as a generic validation error that gave a client nothing to act on. `[improvement, fix]`@@ -80,6 +86,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The trading control room now tells you when the agents cannot afford to trade**: The /trading page showed a green "Trading live" badge whenever the worker was up and the launch feed was connected. Both of those can be true while the agents' wallets are too empty to place a single buy, which is exactly what was happening: four of twelve armed wallets were below the minimum entry size and the page said everything was fine. It now reads the fleet verdict the trading worker already publishes, so an underfunded fleet says "Live, wallets underfunded" and one that cannot trade at all says "Out of SOL", each naming the real cause instead of blaming the feed. A new Wallets funded vital shows how many armed wallets can actually place their configured size, how much SOL would refill the rest, and whether the funding wallet can do it automatically or a person has to step in. An agent with no return to report now reads "ROI unavailable" rather than a stray dot. (`/trading`) `[fix, improvement]`- **The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them**: The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage. (`/trending`) `[fix]`- **The Tutor’s running tab and end-of-session invoice now show what you actually paid**: The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading "no questions" and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for. (`/tutor`) `[fix]`+- **The Unstoppable Agent dashboard shows its numbers again, and the agent itself is unstuck**: The /unstoppable page promised a live view of an agent that funds itself, but every number on it was a dash unless you paid $0.01 first, so nobody could actually watch anything. It now reads a free public snapshot of the agent's treasury, runway, 24-hour earnings and costs, activity log and daily reflection, refreshed every five minutes, and paying still buys the real-time reading and still funds the agent. Two bugs behind the page were worse: the agent had halted itself months ago and could never restart, because the check that clears a halt only ran on ticks a halted agent skipped, and it was sitting on $8.93 against a ten-cent floor with nothing running. It is live again. Its daily reflection was also optional in practice, left to whatever the planner felt like doing, so none had ever been written; it is now guaranteed. The page also gained a real heading, a designed failure state with a retry instead of a permanent loading shimmer, and a layout fix that stopped the activity log stretching the page off a phone screen. (`/unstoppable`) `[fix, improvement, feature]`- **The vanity receipt verifier says what went wrong instead of going quiet**: Verifying a provably-fair vanity receipt runs entirely in your browser, so when the cryptography modules could not load (a blocking extension, a captive network, an offline laptop) the Verify button silently did nothing at all. The page now loads that code on demand and, when it cannot, says so plainly and hands you the offline command line check instead. Receipts delivered without a sealed envelope now get the custody check too, proving the key you hold is the one the receipt describes, with no extra key to paste. A share link whose receipt payload arrived damaged now explains that rather than leaving you with an empty form, opening a sealed envelope with the wrong key now tells you which key it wanted, and every control has a visible keyboard focus ring. (`/vanity/verify`) `[fix, improvement]`- **The vanity receipt verifier stops calling honest receipts fraudulent, and the avatar CLI takes a Solana address**: Two documented commands did not do what their page said. The command-line verifier for a provably-fair vanity address receipt scored the difficulty claim with the retired flat model, the one that treats every Base58 character as equally likely. Every receipt issued since the leading-character correction landed therefore failed its difficulty check and was reported as untrustworthy, even though the in-browser verifier at /vanity/verify passed the same receipt. The verifier now reads the model each receipt names in its own signed difficulty block, exactly as the page and the SDK do, so current receipts verify and older ones keep verifying under the model they were issued under. Separately, the Rig Doctor page showed an avatar-manifest command taking a Solana address as the owner, which the CLI rejected outright: it understood Ethereum addresses and full CAIP-10 identifiers and nothing else. Since Solana is the home chain, a bare Solana address is now accepted and recorded as solana:mainnet-beta. Alongside those, eight tutorial and reference pages were audited against the code they describe: the Vercel self-hosting guide had a stale copy of the config file and pointed at a migrations folder that has moved, the MCP guide listed three placeholder OAuth scopes where the live server publishes twelve real per-capability ones, and the Avatar CLI page pinned a version number that npm has never had. (`/docs/rig-doctor`) `[fix, docs, sdk]`- **The vanity SDK now uses the payment wallet you hand it, and the in-chat 3D avatar keeps its tuned lighting**: Three fixes in the developer packages. The @three-ws/vanity SDK documented a fetch option on its paid address-grinding lane but silently ignored it, so a developer who passed a payment-enabled fetch got a payment-required error back instead of the keypair they paid for; that option now works, as do a custom API host and key. The avatar MCP server's in-chat 3D viewer had been hand-tuned with softer shadows, brighter exposure and a neutral environment light, but the script that rebuilds it before every release still produced the old flat version, so the next release would have quietly undone the tuning; the script now produces the tuned viewer, and the same settings apply to the fallback view for chat apps that cannot run the interactive one. The tool SDK's quick-start example pointed at an API that does not exist and skipped the wrapper an MCP server needs to return anything at all, so following it produced a tool that answered with nothing; it now runs end to end against a real free three.ws endpoint. `[fix, sdk, docs]`@@ -88,9 +95,13 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The Wardrobe's garment forge no longer locks itself after a job expires**: Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting "no such job" answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with "Reconnecting" as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it. (`/wardrobe`) `[fix, improvement]`- **The widgets gallery stopped clipping its controls on phones and now recovers from a failed load**: The widgets gallery (/widgets) is where you pick a pre-built chat, voice, or 3D-avatar embed and copy the one line of HTML that drops it into your own page. On a narrow phone screen, each card's preview frame and its Customize panel were wider than the card itself, so the right edge got cut off: the mint field ran past the panel and the Reset button was pushed off-screen entirely, out of reach. Card layout now shrinks to the screen it is on, and the whole page is clean from 320px up. If the showcase list fails to load, the page now says so in plain language and offers a Try again button that reloads it in place, plus a link to the widget docs, instead of leaving a one-line error with no way forward. If the list comes back empty, the gallery explains what it would normally show and points at the Studio rather than showing a blank space. The widget count in the header now reflects the widgets actually loaded in every language, the page has a real top-level heading, the type filters announce which one is active to screen readers, the Preview and Code tabs are wired up as real tabs, and Escape closes the embed-format menu. (`/widgets`) `[fix, improvement]`- **Three docs pages stop pointing readers at a dead page, a missing section, and a snippet that does nothing**: The Vanity page told you to grind a long address yourself in the browser at /vanity, but that path has never existed and answers 404; the in-browser grinder lives at /vanity-wallet, and both links on the page now go there. In Troubleshooting, the fix for a Quick Look model that opens and instantly closes linked to a model-optimization section that is not on the AR page, so the link dropped you at the top with nothing to read; it now opens the section that actually covers it. The same page told you to add a responsive attribute to size an inline embed, with a snippet that set the width in CSS. Neither half worked: responsive sizing is already on by default, and the element reads the width attribute rather than the computed style, so the documented snippet never produced the 3:4 ratio it promised. The instructions now show the form that does work, and name the two things that switch it off. (`/docs/troubleshooting`) `[fix, docs]`+- **Trade Terminal: an agent exit now opens the trade, not just the coin**: The trade terminal advertises a feed of notable agent exits with realized PnL, hold time, exit multiple and a one-click path to copy the trader, but clicking an exit only ever opened the coin: the trade behind it was nowhere on the page and the copy-trader link did not exist. Selecting an exit now opens an Agent exit card carrying the whole position (realized PnL and SOL, exit multiple, hold time, entry and exit size, why it closed, how many people are copying) with links to the entry and exit transactions on-chain and a Copy trader button that goes to that agent's passport. Several honest-failure fixes came with it. A section that could not be reached used to say the data does not exist for this coin, blaming the coin for an outage; each one now says the request failed and offers a Retry that re-runs only that request. Coins with no intel snapshot, no funder graph or no indexed wallets no longer dead-end on a bare sentence, and point instead at the Oracle, Bubblemaps and Solscan. The price chart could get stuck behind a permanent "Loading chart" panel that hid the chart underneath it whenever a switched interval had little history. A migrated coin whose price is quoted off Jupiter is now labelled Graduated in the header strip rather than being reported as still on the bonding curve, and the strip names its price source. The failing feed also told the truth about which feed failed, an empty network says it is empty instead of showing one lonely pinned row, the SOL price in the header pulse finally carries a label, and the feed tabs and the coin search box are now navigable and readable with a keyboard and a screen reader. (`/trades`) `[feature, fix, improvement]`+- **Trending: the time window now filters the coin board, and every row links inside the site**: The 24h / 7d / all-time control on Trending only ever changed the agent ranking; the conviction coin list ignored it and always answered with a fixed 36 hour slice. It is a real filter on both boards now, the coin column names the window it is showing, and coins that tie on a perfect score are separated by momentum, smart wallets and freshness instead of coming back in a different order on every reload. Agent and trusted rows used to point at absolute three.ws addresses, which bounced anyone browsing a preview or a mirror off the site, and the fallback link pointed at a path that does not exist; every row is now an in-site link that resolves. The three boards are a proper tab set for keyboard and screen reader users (arrow keys, Home and End move between them, each tab names the panel it opens), the selected tab is kept in the address bar so a view can be shared and the back button walks it, and the time buttons announce which one is pressed. Empty boards now say what to do next instead of stopping at 'nothing here'. On a 320 pixel screen an agent's wallet chip used to push the whole page sideways; it wraps now, with the tip action still reachable. Anonymous visitors also stop seeing two failed requests in the console on any page that loads wallet chips or reputation badges. (`/trending`) `[fix, improvement]`- **Two tutorials stop shipping code samples that quietly do nothing**: An audit of eight developer tutorials found two whose main code sample looked right and silently failed. The custom-skill weather handler split the weather API's reply on a plus sign, but the temperature field arrives with a leading plus of its own, so every field after the condition landed one slot off and the temperature always came back empty; it also mapped the fahrenheit option to a format code that means feels-like rather than Fahrenheit, so the celsius and fahrenheit paths returned the same units. Both are fixed and the sample was run against the live API in both unit modes. The gesture tutorial's AI lane read an emotion-breakdown field the Granite analysis tool has never returned, so the strength check never passed and the agent never played a single animation; it now reads the score and risk flags the tool actually returns, and grades the gesture across four bands instead of a binary. Separately, twelve tutorial hero buttons pointed at anchors on the docs hub that stopped existing when the hub split into per-topic pages, and now open the real pages; a placeholder URL in the Pump.fun tutorial was being parsed as HTML, which broke a link and injected stray elements into the page; and the self-host guide was corrected throughout, including storage variable names that no longer matched the code, a database step that left most tables uncreated, an audit-logging example importing a function that does not exist, a Cloudflare worker setup for a proxy the platform does not run, and a license claim that described the repository as open source when it is not. (`/tutorials/custom-skill`) `[docs, fix]`- **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]`+- **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 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]`diff --git a/data/changelog.json b/data/changelog.jsonindex 56c232a75..18c08afa9 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,87 @@{"$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-15",+ "title": "Trade Terminal: an agent exit now opens the trade, not just the coin",+ "summary": "The trade terminal advertises a feed of notable agent exits with realized PnL, hold time, exit multiple and a one-click path to copy the trader, but clicking an exit only ever opened the coin: the trade behind it was nowhere on the page and the copy-trader link did not exist. Selecting an exit now opens an Agent exit card carrying the whole position (realized PnL and SOL, exit multiple, hold time, entry and exit size, why it closed, how many people are copying) with links to the entry and exit transactions on-chain and a Copy trader button that goes to that agent's passport. Several honest-failure fixes came with it. A section that could not be reached used to say the data does not exist for this coin, blaming the coin for an outage; each one now says the request failed and offers a Retry that re-runs only that request. Coins with no intel snapshot, no funder graph or no indexed wallets no longer dead-end on a bare sentence, and point instead at the Oracle, Bubblemaps and Solscan. The price chart could get stuck behind a permanent \"Loading chart\" panel that hid the chart underneath it whenever a switched interval had little history. A migrated coin whose price is quoted off Jupiter is now labelled Graduated in the header strip rather than being reported as still on the bonding curve, and the strip names its price source. The failing feed also told the truth about which feed failed, an empty network says it is empty instead of showing one lonely pinned row, the SOL price in the header pulse finally carries a label, and the feed tabs and the coin search box are now navigable and readable with a keyboard and a screen reader.",+ "tags": [+ "feature",+ "fix",+ "improvement"+ ],+ "link": "/trades"+ },+ {+ "date": "2026-08-15",+ "title": "The Unstoppable Agent dashboard shows its numbers again, and the agent itself is unstuck",+ "summary": "The /unstoppable page promised a live view of an agent that funds itself, but every number on it was a dash unless you paid $0.01 first, so nobody could actually watch anything. It now reads a free public snapshot of the agent's treasury, runway, 24-hour earnings and costs, activity log and daily reflection, refreshed every five minutes, and paying still buys the real-time reading and still funds the agent. Two bugs behind the page were worse: the agent had halted itself months ago and could never restart, because the check that clears a halt only ran on ticks a halted agent skipped, and it was sitting on $8.93 against a ten-cent floor with nothing running. It is live again. Its daily reflection was also optional in practice, left to whatever the planner felt like doing, so none had ever been written; it is now guaranteed. The page also gained a real heading, a designed failure state with a retry instead of a permanent loading shimmer, and a layout fix that stopped the activity log stretching the page off a phone screen.",+ "tags": [+ "fix",+ "improvement",+ "feature"+ ],+ "link": "/unstoppable"+ },+ {+ "date": "2026-08-15",+ "title": "Watchlist: the portfolio summary stops reporting numbers it does not have",+ "summary": "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.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/watchlist"+ },+ {+ "date": "2026-08-15",+ "title": "Proof-of-Grind Gallery: filters stop stranding the board, and a shared card proves it is on it",+ "summary": "Switching tier or sort while the gallery was still loading could leave you staring at an empty board until you reloaded: the page refused the new request because the old one had not finished, and then never drew anything. The newest request now always wins, so filters respond immediately no matter how fast you click them. When the board itself could not be reached, the summary strip announced \"Gallery: Live\", which was simply false; it now says the stats are unavailable and offers a Retry, as do the gallery and the leaderboard, and each retry re-runs just that request instead of reloading the whole page (the gallery's old retry button also rendered as raw browser chrome). Publishing a wallet refreshed the gallery but not the leaderboard, so your new entry was missing from the ranking until you reloaded. Sharing a card is now worth something: opening a shared link shows whether that address really is on the board, with its verified badge, tier and label, instead of only a local estimate. Alongside those: filtering down to nothing offers a one-click way to clear the filters, a failed \"Load more\" says so instead of silently doing nothing, the tabs work with the browser back button and with arrow keys, a rate-limited publish explains how long to wait rather than printing \"too many requests\", and a gateway failure during publish no longer surfaces a raw parser error.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/vanity/gallery"+ },+ {+ "date": "2026-08-15",+ "title": "Avatar Studio: the trait builder loads again, with its manifest, icons and frames intact",+ "summary": "The trait-based Avatar Studio, the point-and-click builder behind the “three.ws Studio” option in the avatar creator, was shipping a blank page: two copies of React at different versions landed in the bundle, and React refuses to start when its renderer does not match. Both are pinned to the same version now. Behind that, the builder asked for its character manifest at a path containing the literal word “undefined”, so even a booting studio had no character classes to offer; it now reads the manifest from its own base path. The texture-compression library it loads at startup was requested at a doubled URL in local development and never arrived, and the trait card frames, rarity boxes and back/next arrows were pointed one directory too deep, so they silently 404ed. Every one of those assets resolves now, and if the compressor genuinely cannot start, an export that needs it says so instead of failing with an internal error. The in-app creator, the avatar SDK and the Avatar OS demo now open the builder at its exact entry point, so they can no longer land on the wrong studio page.",+ "tags": [+ "fix"+ ],+ "link": "/docs/character-studio"+ },+ {+ "date": "2026-08-15",+ "title": "DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending",+ "summary": "The Yields explorer was shipped with its filter row pointing at a stylesheet the page never loaded, so the chain, project and minimum-TVL controls rendered as raw browser dropdowns crammed into one line with their labels colliding. They are proper labelled fields again at every screen size. On a 320 pixel phone the Total TVL card used to be pushed off the right edge with no way to scroll to it, and opening a pool parked its chart outside the visible area inside a table you had to drag sideways; the three headline stats now stack, and the chart stays pinned in view and is drawn at the drawer's real width, so its axis labels are legible instead of shrunk to a third of their size. Fourteen DeFiLlama protocols carry a bracket, a plus or an exclamation mark in their name, and every yield row for one of them linked to a page that answered 404: those links now resolve. When the upstream feed is down, the three stat cards say so rather than sitting as loading placeholders forever, and the result count says the data is unavailable instead of going blank.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/yields"+ },+ {+ "date": "2026-08-15",+ "title": "Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click",+ "summary": "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.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/voice"+ },+ {+ "date": "2026-08-15",+ "title": "Trending: the time window now filters the coin board, and every row links inside the site",+ "summary": "The 24h / 7d / all-time control on Trending only ever changed the agent ranking; the conviction coin list ignored it and always answered with a fixed 36 hour slice. It is a real filter on both boards now, the coin column names the window it is showing, and coins that tie on a perfect score are separated by momentum, smart wallets and freshness instead of coming back in a different order on every reload. Agent and trusted rows used to point at absolute three.ws addresses, which bounced anyone browsing a preview or a mirror off the site, and the fallback link pointed at a path that does not exist; every row is now an in-site link that resolves. The three boards are a proper tab set for keyboard and screen reader users (arrow keys, Home and End move between them, each tab names the panel it opens), the selected tab is kept in the address bar so a view can be shared and the back button walks it, and the time buttons announce which one is pressed. Empty boards now say what to do next instead of stopping at 'nothing here'. On a 320 pixel screen an agent's wallet chip used to push the whole page sideways; it wraps now, with the tip action still reachable. Anonymous visitors also stop seeing two failed requests in the console on any page that loads wallet chips or reputation badges.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/trending"+ },{"date": "2026-08-15","title": "Avatar SDK: the React entry finally loads, and the viewer answers to properties as well as attributes",@@ -12,6 +93,26 @@],"link": "/demos/react-sdk"},+ {+ "date": "2026-08-15",+ "title": "3D viewer: shared model links keep their name, and every button on the page does something",+ "summary": "Open a shared model link and the browser tab now keeps the model's name instead of resetting to a generic one a moment after the page loads, so a bookmarked or shared viewer link is identifiable again. The model's name is also the page's heading now, which is what screen readers and search engines read first. A link whose address does not point at a real https model file used to show a Download button that did nothing; the page now explains what is wrong with the link and offers the only action that helps. Copying the embed snippet from 'Embed it anywhere' confirms it copied, and launching a coin from the model shows that the token image is rendering, both of which were being written to a part of the page the visitor could not see. The page's own title and description now describe what the viewer actually does: preview any public glTF or GLB model, then pose, restyle, scene, AR, embed or download it.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/viewer"+ },+ {+ "date": "2026-08-15",+ "title": "Back-an-Agent Vaults: a successful deposit no longer reports itself as a failure",+ "summary": "Depositing an amount with cents in it (anything that is not a whole dollar) settled on-chain and then showed the backer an error, because the confirmation line converted the amount through floating point and threw on the result. That is fixed, and the confirmation now names the shares you received. Opening a vault and pressing the browser's back button used to trap you on the page: every back press rebuilt the same entry instead of leaving. The open positions table said nothing at all when a vault's holdings had all been sold down to zero; it now says the capital is in USDC. A vault that failed to load offers a retry and a way back to the list instead of a dead end, and a display fault is no longer reported as a network problem. Anonymous visitors no longer trigger a failed sign-in check on load, the feed and the sign-in check now run at the same time rather than one after the other, the open-a-vault form no longer offers a submit button when you have no agents to open one behind, and the dialogs take keyboard focus, keep Tab inside them, and hand focus back when they close.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/vaults"+ },{"date": "2026-08-15","title": "Grind-Bounty Market: shared bounty links now open the bounty, and \"Grind this\" grinds that one",diff --git a/public/changelog.json b/public/changelog.jsonindex 97e74161a..e451967e4 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,22 @@{- "generated_at": "2026-08-15T19:55:19.478Z",+ "generated_at": "2026-08-15T21:13:40.596Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "3D viewer: shared model links keep their name, and every button on the page does something",+ "summary": "Open a shared model link and the browser tab now keeps the model's name instead of resetting to a generic one a moment after the page loads, so a bookmarked or shared viewer link is identifiable again. The model's name is also the page's heading now, which is what screen readers and search engines read first. A link whose address does not point at a real https model file used to show a Download button that did nothing; the page now explains what is wrong with the link and offers the only action that helps. Copying the embed snippet from 'Embed it anywhere' confirms it copied, and launching a coin from the model shows that the token image is rendering, both of which were being written to a part of the page the visitor could not see. The page's own title and description now describe what the viewer actually does: preview any public glTF or GLB model, then pose, restyle, scene, AR, embed or download it.",+ "link": "/viewer",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -178,6 +189,28 @@"improvement"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Avatar SDK: the React entry finally loads, and the viewer answers to properties as well as attributes",+ "summary": "The React bindings in @three-ws/avatar shipped as a .jsx file even though they contain no JSX, which meant Node refused to import them and browsers refused to run them as a module script: the live React SDK demo had been failing with a MIME type error. That entry is now plain JavaScript, so 'import ... from \"@three-ws/avatar/react\"' works in Node, in Next.js, and straight from a browser import map, and the demo page renders all four bindings again. The lightweight <three-ws-viewer> element now also accepts src, alt, background, ar and autoRotate as properties, not only as attributes, so frameworks that assign properties (React 19, Vue, or any Object.assign helper) drive it correctly, including values set before the element upgrades. The package's documentation was corrected in the same pass: the element method list now matches the methods that actually exist, the Avatar Studio default URL is the real one, the license is stated correctly, and the two dependency-free runtime entry points are documented.",+ "link": "/demos/react-sdk",+ "tags": [+ "sdk",+ "fix",+ "docs"+ ]+ },+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Avatar Studio: the trait builder loads again, with its manifest, icons and frames intact",+ "summary": "The trait-based Avatar Studio, the point-and-click builder behind the “three.ws Studio” option in the avatar creator, was shipping a blank page: two copies of React at different versions landed in the bundle, and React refuses to start when its renderer does not match. Both are pinned to the same version now. Behind that, the builder asked for its character manifest at a path containing the literal word “undefined”, so even a booting studio had no character classes to offer; it now reads the manifest from its own base path. The texture-compression library it loads at startup was requested at a doubled URL in local development and never arrived, and the trait card frames, rarity boxes and back/next arrows were pointed one directory too deep, so they silently 404ed. Every one of those assets resolves now, and if the compressor genuinely cannot start, an export that needs it says so instead of failing with an internal error. The in-app creator, the avatar SDK and the Avatar OS demo now open the builder at its exact entry point, so they can no longer land on the wrong studio page.",+ "link": "/docs/character-studio",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-15","type": "update",@@ -188,6 +221,17 @@"fix"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Back-an-Agent Vaults: a successful deposit no longer reports itself as a failure",+ "summary": "Depositing an amount with cents in it (anything that is not a whole dollar) settled on-chain and then showed the backer an error, because the confirmation line converted the amount through floating point and threw on the result. That is fixed, and the confirmation now names the shares you received. Opening a vault and pressing the browser's back button used to trap you on the page: every back press rebuilt the same entry instead of leaving. The open positions table said nothing at all when a vault's holdings had all been sold down to zero; it now says the capital is in USDC. A vault that failed to load offers a retry and a way back to the list instead of a dead end, and a display fault is no longer reported as a network problem. Anonymous visitors no longer trigger a failed sign-in check on load, the feed and the sign-in check now run at the same time rather than one after the other, the open-a-vault form no longer offers a submit button when you have no agents to open one behind, and the dialogs take keyboard focus, keep Tab inside them, and hand focus back when they close.",+ "link": "/vaults",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -220,6 +264,17 @@"infra"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending",+ "summary": "The Yields explorer was shipped with its filter row pointing at a stylesheet the page never loaded, so the chain, project and minimum-TVL controls rendered as raw browser dropdowns crammed into one line with their labels colliding. They are proper labelled fields again at every screen size. On a 320 pixel phone the Total TVL card used to be pushed off the right edge with no way to scroll to it, and opening a pool parked its chart outside the visible area inside a table you had to drag sideways; the three headline stats now stack, and the chart stays pinned in view and is drawn at the drawer's real width, so its axis labels are legible instead of shrunk to a third of their size. Fourteen DeFiLlama protocols carry a bracket, a plus or an exclamation mark in their name, and every yield row for one of them linked to a page that answered 404: those links now resolve. When the upstream feed is down, the three stat cards say so rather than sitting as loading placeholders forever, and the result count says the data is unavailable instead of going blank.",+ "link": "/yields",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -371,6 +426,17 @@"fix"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Proof-of-Grind Gallery: filters stop stranding the board, and a shared card proves it is on it",+ "summary": "Switching tier or sort while the gallery was still loading could leave you staring at an empty board until you reloaded: the page refused the new request because the old one had not finished, and then never drew anything. The newest request now always wins, so filters respond immediately no matter how fast you click them. When the board itself could not be reached, the summary strip announced \"Gallery: Live\", which was simply false; it now says the stats are unavailable and offers a Retry, as do the gallery and the leaderboard, and each retry re-runs just that request instead of reloading the whole page (the gallery's old retry button also rendered as raw browser chrome). Publishing a wallet refreshed the gallery but not the leaderboard, so your new entry was missing from the ranking until you reloaded. Sharing a card is now worth something: opening a shared link shows whether that address really is on the board, with its verified badge, tier and label, instead of only a local estimate. Alongside those: filtering down to nothing offers a one-click way to clear the filters, a failed \"Load more\" says so instead of silently doing nothing, the tabs work with the browser back button and with arrow keys, a rate-limited publish explains how long to wait rather than printing \"too many requests\", and a gateway failure during publish no longer surfaces a raw parser error.",+ "link": "/vanity/gallery",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -804,6 +870,18 @@"fix"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "The Unstoppable Agent dashboard shows its numbers again, and the agent itself is unstuck",+ "summary": "The /unstoppable page promised a live view of an agent that funds itself, but every number on it was a dash unless you paid $0.01 first, so nobody could actually watch anything. It now reads a free public snapshot of the agent's treasury, runway, 24-hour earnings and costs, activity log and daily reflection, refreshed every five minutes, and paying still buys the real-time reading and still funds the agent. Two bugs behind the page were worse: the agent had halted itself months ago and could never restart, because the check that clears a halt only ran on ticks a halted agent skipped, and it was sitting on $8.93 against a ten-cent floor with nothing running. It is live again. Its daily reflection was also optional in practice, left to whatever the planner felt like doing, so none had ever been written; it is now guaranteed. The page also gained a real heading, a designed failure state with a retry instead of a permanent loading shimmer, and a layout fix that stopped the activity log stretching the page off a phone screen.",+ "link": "/unstoppable",+ "tags": [+ "fix",+ "improvement",+ "feature"+ ]+ },{"date": "2026-08-15","type": "update",@@ -893,6 +971,29 @@"docs"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Trade Terminal: an agent exit now opens the trade, not just the coin",+ "summary": "The trade terminal advertises a feed of notable agent exits with realized PnL, hold time, exit multiple and a one-click path to copy the trader, but clicking an exit only ever opened the coin: the trade behind it was nowhere on the page and the copy-trader link did not exist. Selecting an exit now opens an Agent exit card carrying the whole position (realized PnL and SOL, exit multiple, hold time, entry and exit size, why it closed, how many people are copying) with links to the entry and exit transactions on-chain and a Copy trader button that goes to that agent's passport. Several honest-failure fixes came with it. A section that could not be reached used to say the data does not exist for this coin, blaming the coin for an outage; each one now says the request failed and offers a Retry that re-runs only that request. Coins with no intel snapshot, no funder graph or no indexed wallets no longer dead-end on a bare sentence, and point instead at the Oracle, Bubblemaps and Solscan. The price chart could get stuck behind a permanent \"Loading chart\" panel that hid the chart underneath it whenever a switched interval had little history. A migrated coin whose price is quoted off Jupiter is now labelled Graduated in the header strip rather than being reported as still on the bonding curve, and the strip names its price source. The failing feed also told the truth about which feed failed, an empty network says it is empty instead of showing one lonely pinned row, the SOL price in the header pulse finally carries a label, and the feed tabs and the coin search box are now navigable and readable with a keyboard and a screen reader.",+ "link": "/trades",+ "tags": [+ "feature",+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Trending: the time window now filters the coin board, and every row links inside the site",+ "summary": "The 24h / 7d / all-time control on Trending only ever changed the agent ranking; the conviction coin list ignored it and always answered with a fixed 36 hour slice. It is a real filter on both boards now, the coin column names the window it is showing, and coins that tie on a perfect score are separated by momentum, smart wallets and freshness instead of coming back in a different order on every reload. Agent and trusted rows used to point at absolute three.ws addresses, which bounced anyone browsing a preview or a mirror off the site, and the fallback link pointed at a path that does not exist; every row is now an in-site link that resolves. The three boards are a proper tab set for keyboard and screen reader users (arrow keys, Home and End move between them, each tab names the panel it opens), the selected tab is kept in the address bar so a view can be shared and the back button walks it, and the time buttons announce which one is pressed. Empty boards now say what to do next instead of stopping at 'nothing here'. On a 320 pixel screen an agent's wallet chip used to push the whole page sideways; it wraps now, with the tip action still reachable. Anonymous visitors also stop seeing two failed requests in the console on any page that loads wallet chips or reputation badges.",+ "link": "/trending",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -926,6 +1027,28 @@"fix"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click",+ "summary": "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.",+ "link": "/voice",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Watchlist: the portfolio summary stops reporting numbers it does not have",+ "summary": "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.",+ "link": "/watchlist",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 9a01bcdf7..de49e9d9e 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <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>+ <guid isPermaLink="false">2026-08-15:3D viewer: shared model links keep their name, and every button on the page does something</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Open a shared model link and the browser tab now keeps the model's name instead of resetting to a generic one a moment after the page loads, so a bookmarked or shared viewer link is identifiable again. The model's name is also the page's heading now, which is what screen readers and search engines read first. A link whose address does not point at a real https model file used to show a Download button that did nothing; the page now explains what is wrong with the link and offers the only action that helps. Copying the embed snippet from 'Embed it anywhere' confirms it copied, and launching a coin from the model shows that the token image is rendering, both of which were being written to a part of the page the visitor could not see. The page's own title and description now describe what the viewer actually does: preview any public glTF or GLB model, then pose, restyle, scene, AR, embed or download it.</description>+ </item><item><title>A broken paid endpoint is no longer reported as a free one</title><link>https://three.ws/pay/simulator</link>@@ -134,6 +142,22 @@<category>fix</category><description>The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed.</description></item>+ <item>+ <title>Avatar SDK: the React entry finally loads, and the viewer answers to properties as well as attributes</title>+ <link>https://three.ws/demos/react-sdk</link>+ <guid isPermaLink="false">2026-08-15:Avatar SDK: the React entry finally loads, and the viewer answers to properties as well as attributes</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>sdk</category>+ <description>The React bindings in @three-ws/avatar shipped as a .jsx file even though they contain no JSX, which meant Node refused to import them and browsers refused to run them as a module script: the live React SDK demo had been failing with a MIME type error. That entry is now plain JavaScript, so 'import ... from "@three-ws/avatar/react"' works in Node, in Next.js, and straight from a browser import map, and the demo page renders all four bindings again. The lightweight <three-ws-viewer> element now also accepts src, alt, background, ar and autoRotate as properties, not only as attributes, so frameworks that assign properties (React 19, Vue, or any Object.assign helper) drive it correctly, including values set before the element upgrades. The package's documentation was corrected in the same pass: the element method list now matches the methods that actually exist, the Avatar Studio default URL is the real one, the license is stated correctly, and the two dependency-free runtime entry points are documented.</description>+ </item>+ <item>+ <title>Avatar Studio: the trait builder loads again, with its manifest, icons and frames intact</title>+ <link>https://three.ws/docs/character-studio</link>+ <guid isPermaLink="false">2026-08-15:Avatar Studio: the trait builder loads again, with its manifest, icons and frames intact</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The trait-based Avatar Studio, the point-and-click builder behind the “three.ws Studio” option in the avatar creator, was shipping a blank page: two copies of React at different versions landed in the bundle, and React refuses to start when its renderer does not match. Both are pinned to the same version now. Behind that, the builder asked for its character manifest at a path containing the literal word “undefined”, so even a booting studio had no character classes to offer; it now reads the manifest from its own base path. The texture-compression library it loads at startup was requested at a doubled URL in local development and never arrived, and the trait card frames, rarity boxes and back/next arrows were pointed one directory too deep, so they silently 404ed. Every one of those assets resolves now, and if the compressor genuinely cannot start, an export that needs it says so instead of failing with an internal error. The in-app creator, the avatar SDK and the Avatar OS demo now open the builder at its exact entry point, so they can no longer land on the wrong studio page.</description>+ </item><item><title>Avatars can move their lips again: the Audio2Face lane is back</title><link>https://three.ws/changelog</link>@@ -142,6 +166,14 @@<category>fix</category><description>Every call that turns speech into facial animation had been failing with an upstream not-found error, so a talking avatar spoke with a frozen face and the one-shot say() path returned nothing usable. The hosted model id the lane pointed at had stopped resolving for our NVIDIA account. It now points at the hosted Audio2Face NIM that is actually live, verified end to end: a synthesized clip drives a 30 fps ARKit blendshape track whose jaw genuinely opens and closes with the words. The discovery helper that finds these model ids was missing the name NVIDIA publishes them under, which is why the outage looked like a configuration mystery; it now finds them.</description></item>+ <item>+ <title>Back-an-Agent Vaults: a successful deposit no longer reports itself as a failure</title>+ <link>https://three.ws/vaults</link>+ <guid isPermaLink="false">2026-08-15:Back-an-Agent Vaults: a successful deposit no longer reports itself as a failure</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Depositing an amount with cents in it (anything that is not a whole dollar) settled on-chain and then showed the backer an error, because the confirmation line converted the amount through floating point and threw on the result. That is fixed, and the confirmation now names the shares you received. Opening a vault and pressing the browser's back button used to trap you on the page: every back press rebuilt the same entry instead of leaving. The open positions table said nothing at all when a vault's holdings had all been sold down to zero; it now says the capital is in USDC. A vault that failed to load offers a retry and a way back to the list instead of a dead end, and a display fault is no longer reported as a network problem. Anonymous visitors no longer trigger a failed sign-in check on load, the feed and the sign-in check now run at the same time rather than one after the other, the open-a-vault form no longer offers a submit button when you have no agents to open one behind, and the dialogs take keyboard focus, keep Tab inside them, and hand focus back when they close.</description>+ </item><item><title>Claim Your Wallet stopped telling real traders they had no track record</title><link>https://three.ws/claim-wallet</link>@@ -166,6 +198,14 @@<category>fix</category><description>When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over.</description></item>+ <item>+ <title>DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending</title>+ <link>https://three.ws/yields</link>+ <guid isPermaLink="false">2026-08-15:DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The Yields explorer was shipped with its filter row pointing at a stylesheet the page never loaded, so the chain, project and minimum-TVL controls rendered as raw browser dropdowns crammed into one line with their labels colliding. They are proper labelled fields again at every screen size. On a 320 pixel phone the Total TVL card used to be pushed off the right edge with no way to scroll to it, and opening a pool parked its chart outside the visible area inside a table you had to drag sideways; the three headline stats now stack, and the chart stays pinned in view and is drawn at the drawer's real width, so its axis labels are legible instead of shrunk to a third of their size. Fourteen DeFiLlama protocols carry a bracket, a plus or an exclamation mark in their name, and every yield row for one of them linked to a page that answered 404: those links now resolve. When the upstream feed is down, the three stat cards say so rather than sitting as loading placeholders forever, and the result count says the data is unavailable instead of going blank.</description>+ </item><item><title>Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands</title><link>https://three.ws/docs/aws-marketplace</link>@@ -278,6 +318,14 @@<category>security</category><description>The registry lookup that turns an agent id, avatar id, slug, or Solana mint into one record already refused to hand out the 3D model of a private avatar, but it still returned the rendered preview image of that same avatar, so anyone holding the id could see what a private creation looked like. The preview is now gated on exactly the same visibility as the model: a private avatar returns its name and identity and no imagery at all. The embeddable widget read did the same thing with its avatar thumbnail and got the same gate. Separately, every read path that turns a stored thumbnail into a URL now goes through the one resolver that drops the old broken image keys, so agent manifests, token metadata, and launch feeds stop publishing image links that answer 404.</description></item>+ <item>+ <title>Proof-of-Grind Gallery: filters stop stranding the board, and a shared card proves it is on it</title>+ <link>https://three.ws/vanity/gallery</link>+ <guid isPermaLink="false">2026-08-15:Proof-of-Grind Gallery: filters stop stranding the board, and a shared card proves it is on it</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Switching tier or sort while the gallery was still loading could leave you staring at an empty board until you reloaded: the page refused the new request because the old one had not finished, and then never drew anything. The newest request now always wins, so filters respond immediately no matter how fast you click them. When the board itself could not be reached, the summary strip announced "Gallery: Live", which was simply false; it now says the stats are unavailable and offers a Retry, as do the gallery and the leaderboard, and each retry re-runs just that request instead of reloading the whole page (the gallery's old retry button also rendered as raw browser chrome). Publishing a wallet refreshed the gallery but not the leaderboard, so your new entry was missing from the ranking until you reloaded. Sharing a card is now worth something: opening a shared link shows whether that address really is on the board, with its verified badge, tier and label, instead of only a local estimate. Alongside those: filtering down to nothing offers a one-click way to clear the filters, a failed "Load more" says so instead of silently doing nothing, the tabs work with the browser back button and with arrow keys, a rate-limited publish explains how long to wait rather than printing "too many requests", and a gateway failure during publish no longer surfaces a raw parser error.</description>+ </item><item><title>Push notification sign-up now only accepts a real push service address</title><link>https://three.ws/changelog</link>@@ -598,6 +646,14 @@<category>fix</category><description>The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading "no questions" and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for.</description></item>+ <item>+ <title>The Unstoppable Agent dashboard shows its numbers again, and the agent itself is unstuck</title>+ <link>https://three.ws/unstoppable</link>+ <guid isPermaLink="false">2026-08-15:The Unstoppable Agent dashboard shows its numbers again, and the agent itself is unstuck</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The /unstoppable page promised a live view of an agent that funds itself, but every number on it was a dash unless you paid $0.01 first, so nobody could actually watch anything. It now reads a free public snapshot of the agent's treasury, runway, 24-hour earnings and costs, activity log and daily reflection, refreshed every five minutes, and paying still buys the real-time reading and still funds the agent. Two bugs behind the page were worse: the agent had halted itself months ago and could never restart, because the check that clears a halt only ran on ticks a halted agent skipped, and it was sitting on $8.93 against a ten-cent floor with nothing running. It is live again. Its daily reflection was also optional in practice, left to whatever the planner felt like doing, so none had ever been written; it is now guaranteed. The page also gained a real heading, a designed failure state with a retry instead of a permanent loading shimmer, and a layout fix that stopped the activity log stretching the page off a phone screen.</description>+ </item><item><title>The vanity receipt verifier says what went wrong instead of going quiet</title><link>https://three.ws/vanity/verify</link>@@ -662,6 +718,22 @@<category>fix</category><description>The Vanity page told you to grind a long address yourself in the browser at /vanity, but that path has never existed and answers 404; the in-browser grinder lives at /vanity-wallet, and both links on the page now go there. In Troubleshooting, the fix for a Quick Look model that opens and instantly closes linked to a model-optimization section that is not on the AR page, so the link dropped you at the top with nothing to read; it now opens the section that actually covers it. The same page told you to add a responsive attribute to size an inline embed, with a snippet that set the width in CSS. Neither half worked: responsive sizing is already on by default, and the element reads the width attribute rather than the computed style, so the documented snippet never produced the 3:4 ratio it promised. The instructions now show the form that does work, and name the two things that switch it off.</description></item>+ <item>+ <title>Trade Terminal: an agent exit now opens the trade, not just the coin</title>+ <link>https://three.ws/trades</link>+ <guid isPermaLink="false">2026-08-15:Trade Terminal: an agent exit now opens the trade, not just the coin</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The trade terminal advertises a feed of notable agent exits with realized PnL, hold time, exit multiple and a one-click path to copy the trader, but clicking an exit only ever opened the coin: the trade behind it was nowhere on the page and the copy-trader link did not exist. Selecting an exit now opens an Agent exit card carrying the whole position (realized PnL and SOL, exit multiple, hold time, entry and exit size, why it closed, how many people are copying) with links to the entry and exit transactions on-chain and a Copy trader button that goes to that agent's passport. Several honest-failure fixes came with it. A section that could not be reached used to say the data does not exist for this coin, blaming the coin for an outage; each one now says the request failed and offers a Retry that re-runs only that request. Coins with no intel snapshot, no funder graph or no indexed wallets no longer dead-end on a bare sentence, and point instead at the Oracle, Bubblemaps and Solscan. The price chart could get stuck behind a permanent "Loading chart" panel that hid the chart underneath it whenever a switched interval had little history. A migrated coin whose price is quoted off Jupiter is now labelled Graduated in the header strip rather than being reported as still on the bonding curve, and the strip names its price source. The failing feed also told the truth about which feed failed, an empty network says it is empty instead of showing one lonely pinned row, the SOL price in the header pulse finally carries a label, and the feed tabs and the coin search box are now navigable and readable with a keyboard and a screen reader.</description>+ </item>+ <item>+ <title>Trending: the time window now filters the coin board, and every row links inside the site</title>+ <link>https://three.ws/trending</link>+ <guid isPermaLink="false">2026-08-15:Trending: the time window now filters the coin board, and every row links inside the site</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The 24h / 7d / all-time control on Trending only ever changed the agent ranking; the conviction coin list ignored it and always answered with a fixed 36 hour slice. It is a real filter on both boards now, the coin column names the window it is showing, and coins that tie on a perfect score are separated by momentum, smart wallets and freshness instead of coming back in a different order on every reload. Agent and trusted rows used to point at absolute three.ws addresses, which bounced anyone browsing a preview or a mirror off the site, and the fallback link pointed at a path that does not exist; every row is now an in-site link that resolves. The three boards are a proper tab set for keyboard and screen reader users (arrow keys, Home and End move between them, each tab names the panel it opens), the selected tab is kept in the address bar so a view can be shared and the back button walks it, and the time buttons announce which one is pressed. Empty boards now say what to do next instead of stopping at 'nothing here'. On a 320 pixel screen an agent's wallet chip used to push the whole page sideways; it wraps now, with the tip action still reachable. Anonymous visitors also stop seeing two failed requests in the console on any page that loads wallet chips or reputation badges.</description>+ </item><item><title>Two tutorials stop shipping code samples that quietly do nothing</title><link>https://three.ws/tutorials/custom-skill</link>@@ -686,6 +758,22 @@<category>sdk</category><description>@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.</description></item>+ <item>+ <title>Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click</title>+ <link>https://three.ws/voice</link>+ <guid isPermaLink="false">2026-08-15:Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <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>Watchlist: the portfolio summary stops reporting numbers it does not have</title>+ <link>https://three.ws/watchlist</link>+ <guid isPermaLink="false">2026-08-15:Watchlist: the portfolio summary stops reporting numbers it does not have</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>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.</description>+ </item><item><title>Widget analytics can tell you where your visitors are again, and a shared widget link previews correctly everywhere</title><link>https://three.ws/widgets</link>diff --git a/public/features.json b/public/features.jsonindex 13f21076f..175a3a4ee 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-15T19:55:19.379Z",+ "generated_at": "2026-08-15T21:13:40.484Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",