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
fix(autopilot): say whether a rule saved, and stop losing a typed threshold
nirholasd14f2e07f858
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 175e4e774..7f56d5655 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -20,6 +20,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Avatar link previews stop rebuilding themselves, and two feeds answer a bad page link plainly**: An audit of the chat, media and board endpoints found three real breaks. When you share an avatar link, the preview image is drawn once and then kept, so every later share is instant. A mix-up between the stored image and its address meant every freshly drawn preview was mistaken for an old broken one: the saved copy was thrown away and the picture was redrawn from scratch on every single share. The preview is now kept, as it always should have been, and genuinely broken old records are repaired the next time they are drawn. Separately, the character directory answered a hand-edited or stale "next page" link with a server error instead of saying the value was not a timestamp, and the bounty board did the same when the page size in the address was not a number. Both now answer plainly, and the board simply falls back to its normal page size. (`/characters`) `[fix]`- **Avatar Studio trait library: the mirror can no longer be pointed at someone else's server**: Avatar Studio loads its hair, clothing and accessory traits through a three.ws address that mirrors the open-source trait library, so your browser never talks to an outside CDN. The list of where those traits live was being written using the address in the incoming request, and that address can be set by whoever sends the request. Because the mirror is cached at the edge for a day, one crafted request could have left every Avatar Studio visitor loading trait files from a stranger's server for the next 24 hours. That list is now written the same way for everybody, with no part of it taken from the request, so there is nothing left to steer. Three smaller repairs went in alongside it: asking the mirror how big a file is no longer answers with the compressed size (a trait manifest claimed 2 KB and delivered 20 KB), the mirror will not hand back a web page or script even if the upstream library ever served one, and a failure at the library now answers plainly as either not found or mirror is down instead of passing its raw status through as ours. (`/avatar-studio`) `[security, fix]`- **Avatars no longer lose their preview picture forever because a server had a bad minute**: Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue. (`/gallery`) `[fix]`+- **Coin Autopilot tells you whether your rules actually saved**: Coin Autopilot is where you set the floors that decide when your coin buys itself back and when it pays creator fees out to holders, so a rule that looks set but never reached the database costs you real money. Two ways that could happen are fixed. A threshold you typed was only sent when the field lost focus, so typing a new floor and then closing the tab or hitting back threw it away silently; it now saves shortly after you stop typing, and anything still in flight is sent as the page closes. And the only confirmation was a toast that vanished after a couple of seconds, which meant a failed write left the switch showing a setting the server had never accepted. Each coin card now reports its own save: Saving, then Saved, or a Not saved marker that names the reason and stays put with a Retry button until the write lands. A coin you have never configured is marked Defaults, so the platform's inherited settings can no longer be mistaken for rules you chose. If the service goes down the page says so in both columns instead of leaving loading placeholders spinning, and it restores itself when the service returns rather than waiting for you to press Retry. Signed out, it stops retrying an endpoint that will keep refusing. Screen reader and keyboard fixes throughout: every switch and floor field is now named, save results are announced, the loading state is cleared when the data arrives, and the number fields have a visible focus ring. (`/autopilot`) `[fix, improvement]`- **Community-voted models reach our Sketchfab showcase with a real name**: Models made from a picture rather than a written description carry no prompt to name them by, so they were labelled with the internal route name instead. Models the community voted for skip the usual title checks on purpose, since a winning model should never be dropped over its title, which meant a winner made from a picture was one run away from being published to the official three.ws Sketchfab account under the name Image-To-3d. It was, in fact, the second model queued to go out. Those models are now named from their category, or given a plain generic name when the category says nothing useful. (`/forge`) `[fix]`- **Corrected stale numbers across the avatar and animation docs**: An audit of eight documentation pages against the code they describe turned up four claims that had drifted. The Animations page said the motion-capture library held about 2,000 clips when it actually serves 2,874, so both the intro and the gallery section now quote the real size and point at the count the API itself returns. The selfie-to-avatar page listed the wrong default for the face-morph displacement clamp and credited a single tuning sweep instead of the two that chose it. The avatar-creation walkthrough still told people to pick a body type on the selfie flow, a control that was deliberately removed because it changed nothing, and named the wrong fields on the event the page dispatches. The architecture page now says plainly that the whitelist trust mode is reserved rather than enforced. (`/docs/animations`) `[docs]`- **Creator subscription tiers save their edits again, and a mistyped subscription link says so plainly**: Editing an existing subscription tier from the creator dashboard silently failed: the save never reached the server, so the new name, price or status was lost every time. Saving works now. Alongside it, a mistyped or truncated subscription or tier link used to answer with a generic server failure; it now says the id is not valid, which is what a reader can actually act on. Tier pages are also directly addressable, so a single tier can be linked and read on its own, with unpublished drafts still visible only to the creator who wrote them. `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex 59840c1a1..d7340b195 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -2,6 +2,15 @@"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.","entries": [{+ "date": "2026-08-16",+ "title": "Coin Autopilot tells you whether your rules actually saved",+ "summary": "Coin Autopilot is where you set the floors that decide when your coin buys itself back and when it pays creator fees out to holders, so a rule that looks set but never reached the database costs you real money. Two ways that could happen are fixed. A threshold you typed was only sent when the field lost focus, so typing a new floor and then closing the tab or hitting back threw it away silently; it now saves shortly after you stop typing, and anything still in flight is sent as the page closes. And the only confirmation was a toast that vanished after a couple of seconds, which meant a failed write left the switch showing a setting the server had never accepted. Each coin card now reports its own save: Saving, then Saved, or a Not saved marker that names the reason and stays put with a Retry button until the write lands. A coin you have never configured is marked Defaults, so the platform's inherited settings can no longer be mistaken for rules you chose. If the service goes down the page says so in both columns instead of leaving loading placeholders spinning, and it restores itself when the service returns rather than waiting for you to press Retry. Signed out, it stops retrying an endpoint that will keep refusing. Screen reader and keyboard fixes throughout: every switch and floor field is now named, save results are announced, the loading state is cleared when the data arrives, and the number fields have a visible focus ring.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/autopilot"+ }, {"date": "2026-08-16","title": "Crypto Categories is searchable, and opens in a fraction of the time","summary": "The sector leaderboard at /categories renders every category the market data provider reports, and that list has grown past 750. All of them were being drawn into the page at once, roughly 2,250 coin icons in a single paint, and the only way to find a sector was to scroll past every one ranked above it. The table now opens with the top 50 and pages in 50 more at a time, and a search box narrows the whole list by name before you ever need to page. Full category names are shown too, instead of being cut off mid-word on a wide screen with half the row empty. The three things that can go wrong now read differently and each offers a way out: a failed load says the data provider did not answer and gives you a Try again button that refetches, a provider reporting nothing says so plainly, and a search that matches nothing offers to clear itself. Sortable column headers now announce themselves to screen readers, and keyboard focus stays on the column you just sorted instead of being dropped back to the top of the page.",diff --git a/docs/autopilot.md b/docs/autopilot.mdindex fb62e4309..eb2191e10 100644--- a/docs/autopilot.md+++ b/docs/autopilot.md@@ -37,7 +37,7 @@ Auth is a session cookie or a bearer token. Every read and write is rate-limited3. Use the master switch on a card to turn Autopilot on or off for that coin. "Autopilot on" means its rules run; "Paused" means the crons skip it.4. Set the **Buyback and burn** rule: toggle it on, set a minimum USDC floor, and choose whether fees are swapped into the token before burning or burned directly.5. Set the **Distribute to holders** rule: toggle it on and set its minimum USDC floor. Enable "Narrate this coin's actions on the live feed" to have the agent speak its moves.-6. Every change autosaves (checkboxes immediately, number fields after a short debounce). A toast confirms "Autopilot updated".+6. Every change autosaves: checkboxes the moment you flip one, number fields a short debounce after you stop typing (you do not have to leave the field, and a value typed right before you navigate away is still sent). The card itself reports the write as `Saving` then `Saved`, and a toast confirms "Autopilot updated". If the write fails, the card keeps a `Not saved` marker with the reason and a **Retry** button until it lands, so a rule you believe you set is never silently missing from the database.7. Watch the activity feed and the narrator. As fees accumulate past your thresholds, the crons act, and each buyback or distribution appears with its status and a Solscan link to the on-chain transaction.## Examples@@ -79,12 +79,12 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp- **Ownership scoped.** Every read and write is filtered to coins whose `user_id` is yours. Posting a policy for a mint you do not own returns `404 not_found`.- **Floors are the safety valve.** A buyback or distribution only fires once the relevant vault clears the USDC floor you set. Set a floor to zero and it acts whenever the vault is non-empty; raise it to batch actions.-- **Merge semantics.** Partial POSTs only change the fields present. A missing policy row reports legacy defaults (everything enabled, zero floors, narrate on) with `configured: false`.+- **Merge semantics.** Partial POSTs only change the fields present. A missing policy row reports legacy defaults (everything enabled, zero floors, narrate on) with `configured: false`. The card marks that coin **Defaults** so an inherited "Autopilot on" is never mistaken for a rule you chose; the badge clears as soon as your first change saves.- **Signed out** renders a "Sign in to manage autopilot" state; `GET` returns `401` and the page routes you to the dashboard.- **Empty state** appears when you own no coins, pointing you to the launcher rather than showing a blank void.-- **Error and retry.** A network or server error renders an inline "Couldn't load" card with a Retry button; a transient poll failure keeps the last good render and retries on the next tick.-- **Live refresh** polls every 20 seconds and only refreshes the activity feed and narrator, never the control inputs you may be editing, so a poll can never overwrite your keystrokes.-- **Atomics are integers.** Thresholds are clamped to non-negative integer atomic strings server-side; a decimal is truncated, a negative or non-numeric value falls back to zero.+- **Error and retry.** A network or server error renders an inline "Couldn't load your coins" card with a Retry button, and the activity column says why it is empty instead of leaving loading skeletons on screen. You do not have to press Retry: the poll re-runs the full load while the page is in that state, so it restores itself the moment the API is reachable again.+- **Live refresh** polls every 20 seconds. Once your cards are on screen it refreshes only the activity feed and narrator, never the control inputs you may be editing, so a poll can never overwrite your keystrokes. A session that expires under the page swaps in the signed-out state rather than leaving controls that can no longer save. Signed out, the poll stops entirely instead of retrying an endpoint that will keep refusing.+- **Atomics are integers.** Thresholds are clamped to non-negative integer atomic strings server-side; a decimal is truncated, a negative or non-numeric value falls back to zero. The field shows you that clamp when you leave it, so what you see is what was stored.- **On-chain actions are the crons', not the page's.** The console never signs a transaction. It only writes policy rows; the buyback and distribute crons are what move funds, on their own schedule, within the vault floors you set.## Relateddiff --git a/prompts/swarm-100/route-autopilot.md b/prompts/swarm-100/route-autopilot.mddeleted file mode 100644index dc7141d67..000000000--- a/prompts/swarm-100/route-autopilot.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /autopilot (Coin Autopilot)--How to run: paste this file's repo path into a fresh Claude Code chat in this-repository and say "run this work order". This file is fully self-contained:-it depends on no other prompt file anywhere. If neighboring files in-prompts/swarm-100/ are gone, that work is done; if present, ignore them.-Every claim below rots; step 0 re-measures, and what you measure wins.--## Operating clause (binding)--- Read CLAUDE.md first. Its rules override everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option- list, or an unexecuted plan. A judgment call goes in one line of the final- report; it never becomes a question that halts work.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real- funds or any irreversible on-chain write, git push or a production deploy,- committing content that references a crypto project other than $THREE, and- destroying unrecoverable data.-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no- commented-out code. Real APIs and real integrations only.-- The em-dash and en-dash characters are banned in everything you write.-- Concurrent agents share this worktree: stage explicit paths only (never a- bare add-everything), and commit finished work promptly.-- Before committing, run: npm run check:rules -- --paths <files you touched>.- It must exit 0.--## Step 0: re-derive the current state--1. This route's declared entry (path, description, added date):-- node -e "const p=require('./data/pages.json');for(const s of p.sections)for(const g of s.pages)if(g.path==='/autopilot')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/autopilot" in vercel.json (the live- route table server/index.mjs boots from), then list matching files in- pages/ and src/. STRUCTURE.md maps every surface to its directory if the- grep is ambiguous.-3. Production right now:-- curl -so /dev/null -w '%{http_code}\n' https://three.ws/autopilot--4. Start (or reuse) the local dev server: npm run dev (vite, port 3000).--## Task: audit this one route end to end, then fix everything found--Route: /autopilot ("Coin Autopilot", section "main").-Declared purpose: A hands-off token cockpit: set the rules: buys, sells, and guardrails: and let your agent run the coin autonomously.--Drive the page in a real headless browser. Playwright is already a dev-dependency; keep your probe script in the session scratchpad, never in the-repo.--1. Load http://localhost:3000/autopilot. Record the HTTP status, every console- error and warning, and every failed network request.-2. Exercise it like a first-time user: click the primary actions, run the- primary flow if one exists, follow the page's internal links. Every button- must do something real; every link must resolve. If the page renders data,- prove in the network log that it came from a live endpoint, not a baked-in- fallback array.-3. States: verify populated, empty, loading, and error states are designed and- reachable. Block the page's primary fetch in Playwright and confirm an- actionable error state appears, not a blank void or a raw exception.-4. Responsive: render at 320, 768, and 1440 px. No horizontal page scroll, no- overlapping or clipped controls.-5. Accessibility basics: one h1; interactive elements are real buttons or- links with visible focus states; images carry alt text; form fields have- labels.-6. Head: a specific title tag and meta description that match the declared- purpose above.-7. Fix every defect at its root in the page's real source files and re-run the- probe until clean. Defects in shared modules are in scope when this route- exercises them.--## Definition of done--- [ ] Local load of /autopilot: HTTP 200, zero console errors, zero unhandled- failed requests (a third-party outage must land in a designed fallback,- not a broken page).-- [ ] No dead interactive element on the page: no stub href="#", no button- without a handler, no link to a missing path.-- [ ] Empty, loading, error, and populated states verified.-- [ ] 320 / 768 / 1440 px renders verified clean.-- [ ] Title and meta description present and specific.-- [ ] npm test passes; npm run check:rules -- --paths <touched files> exits 0.-- [ ] Production status from step 0 recorded in the report; if production- needs a deploy to pick up a fix, the report says so (deploys stay- owner-gated).--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |-| Playwright browser missing | npx playwright install chromium |-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in- front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares).-3. Delete this prompt file in that same commit:-- git rm prompts/swarm-100/route-autopilot.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.diff --git a/public/changelog.json b/public/changelog.jsonindex ad3a5283c..2e1d38d35 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T19:53:52.096Z",+ "generated_at": "2026-08-16T20:17:45.645Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -153,6 +153,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "Coin Autopilot tells you whether your rules actually saved",+ "summary": "Coin Autopilot is where you set the floors that decide when your coin buys itself back and when it pays creator fees out to holders, so a rule that looks set but never reached the database costs you real money. Two ways that could happen are fixed. A threshold you typed was only sent when the field lost focus, so typing a new floor and then closing the tab or hitting back threw it away silently; it now saves shortly after you stop typing, and anything still in flight is sent as the page closes. And the only confirmation was a toast that vanished after a couple of seconds, which meant a failed write left the switch showing a setting the server had never accepted. Each coin card now reports its own save: Saving, then Saved, or a Not saved marker that names the reason and stays put with a Retry button until the write lands. A coin you have never configured is marked Defaults, so the platform's inherited settings can no longer be mistaken for rules you chose. If the service goes down the page says so in both columns instead of leaving loading placeholders spinning, and it restores itself when the service returns rather than waiting for you to press Retry. Signed out, it stops retrying an endpoint that will keep refusing. Screen reader and keyboard fixes throughout: every switch and floor field is now named, save results are announced, the loading state is cleared when the data arrives, and the number fields have a visible focus ring.",+ "link": "/autopilot",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 3429c0407..1984b4fa2 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -118,6 +118,14 @@<category>fix</category><description>Every public avatar gets a preview picture rendered for it in the background, and an avatar that fails to render three times is given up on permanently. The problem was what counted as a failure. If the machine ran out of memory and could not start the renderer at all, or if the picture store was unreachable, that counted against the avatar, even though nothing was wrong with the avatar itself. Four avatars had already been written off that way for a fault that lasted seconds, and a longer outage would have written off every remaining one inside a quarter of an hour, because the whole batch fails together. A fault in the machinery is now told apart from a genuinely broken model: the avatar keeps its chances and the job simply waits for the machine to be healthy. The two background jobs also stop and do nothing when the picture store is switched off, instead of working through the queue and burning everyone's chances on an error they could not have avoided. The four avatars written off in error have been put back in the queue.</description></item>+ <item>+ <title>Coin Autopilot tells you whether your rules actually saved</title>+ <link>https://three.ws/autopilot</link>+ <guid isPermaLink="false">2026-08-16:Coin Autopilot tells you whether your rules actually saved</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Coin Autopilot is where you set the floors that decide when your coin buys itself back and when it pays creator fees out to holders, so a rule that looks set but never reached the database costs you real money. Two ways that could happen are fixed. A threshold you typed was only sent when the field lost focus, so typing a new floor and then closing the tab or hitting back threw it away silently; it now saves shortly after you stop typing, and anything still in flight is sent as the page closes. And the only confirmation was a toast that vanished after a couple of seconds, which meant a failed write left the switch showing a setting the server had never accepted. Each coin card now reports its own save: Saving, then Saved, or a Not saved marker that names the reason and stays put with a Retry button until the write lands. A coin you have never configured is marked Defaults, so the platform's inherited settings can no longer be mistaken for rules you chose. If the service goes down the page says so in both columns instead of leaving loading placeholders spinning, and it restores itself when the service returns rather than waiting for you to press Retry. Signed out, it stops retrying an endpoint that will keep refusing. Screen reader and keyboard fixes throughout: every switch and floor field is now named, save results are announced, the loading state is cleared when the data arrives, and the number fields have a visible focus ring.</description>+ </item><item><title>Community-voted models reach our Sketchfab showcase with a real name</title><link>https://three.ws/forge</link>diff --git a/public/features.json b/public/features.jsonindex afd5378b6..d732e9338 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T19:53:51.899Z",+ "generated_at": "2026-08-16T20:17:45.173Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",