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): tell holders that shared docs links now open the page they name
nirholas499ef6d4c065
diff --git a/data/changelog.json b/data/changelog.jsonindex 68d914be0..ecd7ff1fe 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -3,13 +3,34 @@"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.",+ "title": "A shared link to a docs page now opens that page instead of stranding you",+ "summary": "Every cross-reference inside a docs page turns into a link like /docs/agent-wallets#financial-controls. Following one worked, but the URL you copied afterwards did not: on a fresh load the viewer only recognised the second half if that doc happened to be listed in the sidebar, and silently left you on the page you arrived from otherwise. Links to Financial controls, the x402 payment tutorial, and the wallet access and proof-of-custody chapters all failed that way. The viewer now asks the server whether the doc exists before giving up, so those links land where they say they will, and the browser tab takes the destination's name. Separately, /docs/3d-api was serving the 3D API landing page rather than the reference doc that the API's own discovery response, the OpenAPI license link, and the docs sidebar all point at; it now serves the reference doc, and the landing page keeps its home at /3d.","tags": [+ "fix",+ "docs"+ ],+ "link": "/docs/agent-wallets"+ },+ {+ "date": "2026-08-15",+ "title": "The 3D API and agent manifest references now match what the endpoints actually return",+ "summary": "The agent manifest page told you to validate a manifest with assertValid from @three-ws/avatar-schema. That package validates avatar manifests (mesh, skeleton, owner), not agent manifests, so the sample always threw. It now shows loadManifest from the published bundle, running against a live agent, and says plainly which document the avatar schema covers. On the 3D API page, the sample responses showed a model URL shape the service never returns, the inspect example was a stale capture of a model that has since been re-exported, and the Forge Pro tier table claimed draft and standard generations come back with no textures when every tier bakes them (1K, 2K, and 4K plus PBR at high). All three are corrected against live calls, and the page now explains why browser code should load a generated GLB through the first-party CDN path rather than the object store URL directly. The prompt art-director note is confirmed accurate and the code comment that contradicted it was fixed.",+ "tags": [+ "fix",+ "docs"+ ],+ "link": "/docs/3d-api"+ },+ {+ "date": "2026-08-15",+ "title": "The embodied AgenC demo hands you a live task, and reacts to the state a claimed task is actually in",+ "summary": "The /agenc/embodied page binds a 3D agent to a real AgenC task on Solana, and until now it opened on an empty input box: it needed a task account address and offered no way anywhere on the page to find one. It now lists real tasks three.ws itself posted, claimed, and settled on-chain, newest first, so the demo works the moment it loads; a new public read, /api/agenc/recent-tasks, serves that list. Two things it showed were also wrong. The scene coloured itself for a state named Claimed, which the chain has never used: a claimed task is In Progress on-chain, so the halo, the badge, and the per-state animation switch all sat inert through the one transition the demo exists to show. And the page named a program address that no read has touched since the protocol's interface moved; it now shows the program each live read actually ran against. Pasting an address that holds something other than a task used to report a server error, as though the platform were broken, rather than saying no such task exists there; that is now a plain not-found, with the page telling you to check the address or switch cluster. The panel has designed loading, empty, and error states throughout, the form fields have real labels, the layout no longer scrolls sideways on a phone, and a task that cannot be read is retried with a backoff instead of being re-requested every four seconds forever.",+ "tags": [+ "fix","improvement",- "fix"+ "feature"],- "link": "/agenc/room"+ "link": "/agenc/embodied"},{"date": "2026-08-15",diff --git a/prompts/swarm-100/docs-batch-26.md b/prompts/swarm-100/docs-batch-26.mddeleted file mode 100644index 1118eeb54..000000000--- a/prompts/swarm-100/docs-batch-26.md+++ /dev/null@@ -1,100 +0,0 @@-# Docs audit batch 26: /docs/3d-api through /docs/agents-vs-avatars--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/3d-api /docs/DESIGN-TOKENS /docs/agent-manifest /docs/agent-screen-control /docs/agent-shell /docs/agent-skills /docs/agent-wallets /docs/agents-vs-avatars; 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/3d-api ("Docs · The three.ws 3D API")-- /docs/DESIGN-TOKENS ("Docs · Design tokens")-- /docs/agent-manifest ("Docs · Agent manifest reference")-- /docs/agent-screen-control ("Docs · Take the wheel: drive your agent's computer")-- /docs/agent-shell ("Docs · The agent shell")-- /docs/agent-skills ("Docs · The three.ws Agent Skills pack")-- /docs/agent-wallets ("Docs · Agent wallets")-- /docs/agents-vs-avatars ("Docs · Agents vs. avatars")--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-26.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.