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
chore(prompts): retire the docs-batch-40 tutorial audit work order
nirholas268508db8588
diff --git a/data/changelog.json b/data/changelog.jsonindex 4c01e38c9..2757b8bf0 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,16 +1,6 @@{"$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 AgenC task room explains itself now, instead of showing a wall of raw error text",- "summary": "The task room renders every task a wallet has posted on the AgenC coordination protocol as a 3D agent driven by its live on-chain state. It has been rebuilt around the moments where it used to leave you stuck. An unreadable wallet address, a Solana outage, and a dropped connection all used to print the raw server reply into an otherwise empty page; each now gets its own explanation, a Retry button, and a link to the docs on posting a task, and the room keeps retrying by itself when the fault is upstream and stops when it is something only you can fix. A wallet with no tasks says so and offers to check the other cluster instead of leaving you guessing. While a load is in flight you get skeleton cards rather than the word loading, and a line above the grid tells you how many tasks are showing, on which cluster, and when they were last refreshed. Card status colors now match the states the chain actually reports, so a task in progress or awaiting validation is no longer left uncolored, and each card links to its account on Solana Explorer. On a phone the wallet field no longer runs off the edge of the screen, the title no longer sits under the site logo, both form fields are labelled for screen readers, and every control has a visible focus ring. The room also stops running a 3D viewer for every card at once: avatars load as their cards come into view, up to eight at a time, and are released when you scroll past, which keeps a large board from stalling the browser and stops off-screen cards polling the chain for nothing.",- "tags": [- "improvement",- "fix"- ],- "link": "/agenc/room"- },{"date": "2026-08-15","title": "Two tutorials stop shipping code samples that quietly do nothing",diff --git a/prompts/swarm-100/docs-batch-40.md b/prompts/swarm-100/docs-batch-40.mddeleted file mode 100644index 468bb71ef..000000000--- a/prompts/swarm-100/docs-batch-40.md+++ /dev/null@@ -1,100 +0,0 @@-# Docs audit batch 40: /tutorials/build-a-site-concierge through /tutorials/pay-for-x402-service--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 /tutorials/build-a-site-concierge /tutorials/trigger-from-page-events /tutorials/upload-custom-glb /tutorials/connect-ai-brain /tutorials/create-and-edit-memory /tutorials/place-agent-irl /tutorials/voice-and-lipsync /tutorials/pay-for-x402-service; 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:--- /tutorials/build-a-site-concierge ("Tutorial · Build a site concierge from the building blocks")-- /tutorials/trigger-from-page-events ("Tutorial · Trigger the agent from page events")-- /tutorials/upload-custom-glb ("Tutorial · Upload a custom GLB avatar")-- /tutorials/connect-ai-brain ("Tutorial · Connect Anthropic or OpenAI as the brain")-- /tutorials/create-and-edit-memory ("Tutorial · Create, enhance & edit agent memory")-- /tutorials/place-agent-irl ("Tutorial · Place your agent in the real world (IRL)")-- /tutorials/voice-and-lipsync ("Tutorial · Give your agent a voice with lipsync")-- /tutorials/pay-for-x402-service ("Tutorial · Discover and pay for an x402 service")--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-40.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.