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): record the trading and MCP doc corrections from the batch 37 audit
nirholasc4653cd13d19
diff --git a/data/changelog.json b/data/changelog.jsonindex a292d978b..1528a2c59 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$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": "The trading and MCP docs now match what the code and the live API actually do",+ "summary": "An audit of eight documentation pages ran every command they print and checked every claim against the code behind it, then corrected what had drifted. The biggest one was in the trading tutorial: the command it gave you for verifying a fleet's fills on-chain asked for a field the leaderboard does not publish, so it returned an empty explorer link for every agent and the verification step could not be completed at all. It now uses the fields that exist, linking both legs of each trade straight to Solscan, and it skips agents whose wallet has not been provisioned yet instead of building a URL that goes nowhere. The MCP tool safety page undercounted the tools that share a name across two servers, which matters because that collision is exactly why a trust policy has to key on the namespaced id; it now lists all nine and prints a command that re-derives the list so it cannot go stale again. The MCP tool catalog itself had drifted from its source and was serving outdated descriptions for three tools, on a page whose whole promise is that it is generated from source and cannot drift; it has been regenerated. The package extraction guide had every version in its roster out of date along with its build and test columns, and still described a publisher field as missing that was set some time ago. The 10 SOL trading experiment page stated a risk rule in absolute terms that contradicted the setup script it tells you to run, which read as a bug in one of the two; the rule now carries the scope the code actually applies.",+ "tags": [+ "docs",+ "fix"+ ],+ "link": "/docs/mcp-safety"+ },{"date": "2026-08-15","title": "The AgenC task room explains itself now, instead of showing a wall of raw error text",@@ -11,6 +21,16 @@],"link": "/agenc/room"},+ {+ "date": "2026-08-15",+ "title": "The embed and sharing tutorials now describe the surfaces that actually exist",+ "summary": "An audit of eight beginner tutorials found several describing features the platform does not have. The avatar-swap tutorial sent readers to Widget Studio for a body swap it cannot do, through a gallery with filters, preview buttons, and a 'Bust cache' save dialog that were never built; it now documents the real one-click swap in the agent editor's Outfit panel, and explains why nothing needs a cache purge. The sharing tutorial claimed rich social previews came from the plain agent URL, which actually serves a generic card, and described a headless renderer, a 24-hour image cache, a 'Refresh preview image' button, and a private-profile toggle that do not exist; it now points at the real share URL that carries the agent's name, description, and card, and explains what genuinely controls discoverability. The AR tutorial's iframe example used an address that returns 404 for an avatar id. The embed quickstart showed an agent ID in the wrong format, overstated the bundle size, and had the effect of the shadow DOM backwards. The docs-world tutorial gained the search palette it never mentioned, and the greeting tutorial now warns that the editor's Greeting field is not what makes an embed talk. Five page descriptions were corrected too, including one promising knobs the tutorial never covered.",+ "tags": [+ "docs",+ "fix"+ ],+ "link": "/tutorials/swap-avatar-in-studio"+ },{"date": "2026-08-15","title": "Two tutorials stop shipping code samples that quietly do nothing",diff --git a/prompts/swarm-100/docs-batch-37.md b/prompts/swarm-100/docs-batch-37.mddeleted file mode 100644index d291e1bad..000000000--- a/prompts/swarm-100/docs-batch-37.md+++ /dev/null@@ -1,100 +0,0 @@-# Docs audit batch 37: /docs/package-extraction through /tutorials/getting-started--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. Confirm each path below still exists in data/pages.json; a path that was- removed there is out of scope (note it in the report, skip it).-2. Start (or reuse) the local dev server: npm run dev (vite, port 3000).-3. Probe production for each path:-- for p in /docs/package-extraction /tutorials/find-a-better-exit-policy /tutorials/read-the-trading-fleet /docs/live-steps /docs/mcp-safety /mcp-tools /docs/trading-experiment /tutorials/getting-started; do printf '%s ' "$p"; curl -so /dev/null -w '%{http_code}\n' "https://three.ws$p"; done--## Task: audit this batch of docs pages, then fix everything found--Pages in this batch:--- /docs/package-extraction ("Docs · Package extraction")-- /tutorials/find-a-better-exit-policy ("Tutorial · Find a better exit policy")-- /tutorials/read-the-trading-fleet ("Tutorial · Read the trading fleet")-- /docs/live-steps ("Docs · Live steps: documentation that runs")-- /docs/mcp-safety ("Docs · MCP tool safety")-- /mcp-tools ("MCP Tool Catalog")-- /docs/trading-experiment ("Docs · The 10 SOL trading experiment")-- /tutorials/getting-started ("Tutorial · Getting started (hosted)")--For every page, in a real headless browser against localhost:--1. HTTP 200, zero console errors, zero unhandled failed requests.-2. Every link on the page resolves (internal paths exist in the route table;- anchors have targets). Fix or remove dead ones.-3. Content accuracy: the page documents current behavior. Spot-check its claims against the code it describes; where it names a command, run the command; where it shows a code sample, the sample must actually run. Fix stale claims in the same change.-4. Title tag and meta description present and specific.-5. Fix defects at their root and re-run until clean.--## Definition of done--- [ ] Every page in the batch loads locally with HTTP 200 and zero console- errors.-- [ ] Zero dead links across the batch.-- [ ] Every named command and code sample on these pages verified runnable, or corrected.-- [ ] Title and meta description verified on every page.-- [ ] npm run check:rules -- --paths <touched files> exits 0; npm test passes- if you touched code.-- [ ] Production status per page recorded in the report.--## 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/docs-batch-37.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.