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): drop the duplicate photo-mode announcement before it reaches the channel
nirholasc71cfae49adc
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex fee60eaa4..1aea5fd6a 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -31,7 +31,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Materialize will not print a weapon, a key to your door, or somebody else's brand**: Printing something is not like generating a picture of it. A refused image costs nobody anything; a printed firearm part is a crime in most of the places we ship to, and a working copy of a key is a burglary tool. So Materialize checks every order twice, and the rules are code rather than a polite request. It refuses firearm components, suppressors, ammunition and magazines, keys and lock picks, counterfeit goods and other people's brand marks, concealed and spring-loaded blades, drug paraphernalia, and realistic firearm likenesses at life size. The first check runs before you are ever asked to pay, so a refusal costs nothing, and it names the category, links the policy, and says what you can print instead. The second runs on the paid order on its way to the printer, and an order that fails it is refunded rather than quietly shipped. What this deliberately does not do is refuse the ordinary: a tabletop miniature carrying a weapon prints, a blunt prop sword prints, your own logo prints. Full policy is in the docs. (`/materialize`) `[feature, security]`- **Materialize: your generation, printed and posted to you**: Everything the forge makes has lived on a screen. Materialize prints it and ships it. Point it at any model, yours or one from the gallery, and it measures the mesh first: whether it is a closed solid, how many separate pieces it is, where the holes are, how thin the thinnest wall gets, and its exact volume. That measurement is the price, so nothing is guessed. Pick a material and a height and you get an itemized quote, every line shown, in resin, tough resin, nylon, full-colour sandstone, draft plastic or stainless steel. Before it prints, the model is rebuilt as a watertight solid, its holes filled, scaled to the size you chose, and hollowed with drain holes if that saves you money. Full-colour prints carry the colour sampled from the model's own texture, which is what lets a printer reproduce what you see on screen. Checkout is USDC on Solana, holders get up to fifteen percent off, and you can follow the order from screening to production to the tracking number. An AI agent can order one too, over x402, with nobody in the loop: as far as we know that makes this the first API where an agent pays and a real object turns up at a real address. (`/materialize`) `[feature]`- **Photo mode in the coin worlds now actually hands you the photo**: Press P in a coin world, or the camera button on the heads-up display, and you get a picture of the world on a share card: the scene itself, the three.ws mark, the coin you are standing in, and, during a live event, that event's name stamped on it. The card was there but the shutter went nowhere. Every single press answered "Couldn't photograph the world just now" and showed nothing, because of a fault in the code that builds the preview, so nobody has ever actually been handed one of these. Pressing it now opens the card, with Download and Copy image next to it. The picture is taken as a separate render rather than grabbed off the screen, so no panel, name tag or chat line is ever in the frame, and it works the same in zen mode, which is when most people will want it. It costs nothing when you are not using it: none of photo mode is loaded until the first press. Two smaller things fixed alongside: taking a second photo while the first card is open now replaces it cleanly instead of briefly stacking two sheets, where a click landing in the wrong moment could dismiss the shot you just took; and the line promising that P takes another one is true now, and visible, having previously rendered as nothing at all. The camera button also stays lit while the picture is being taken, instead of going quiet: taking the photo is real work, and on a slow phone it can run for a few seconds, which previously looked like a button that did nothing. Verified end to end in both Chrome and Safari, on a laptop frame and a phone frame, down to the pixels in the saved file, so the black rectangle that a mishandled 3D screenshot usually produces cannot come back unnoticed. (`/play`) `[fix, feature]`-- **Take a photo of your world and post it**: Press P in a /play world, or the camera button on the HUD, and the world is captured onto a share card: your view of the town with the three.ws mark, the coin you are standing in and the date along the bottom, ready to download or paste straight into a post. The interface is never in the shot. The photo is a second frame rendered off screen just for you, so the chat, the job board and the name tags stay out of the picture no matter what is on screen when you press. It works in zen mode too, which is usually exactly when the world looks worth photographing, and while an event is running the card carries that event's name. Nothing is uploaded anywhere: the card is built in your browser and it is yours. The whole feature only downloads on your first press, so a session that never takes a photo never pays for it. (`/play`) `[feature]`- **Text-to-animation is no longer rationed like a paid service**: Turning a sentence into an animation runs entirely on our own GPUs, but it was being counted against the allowance meant for services we pay a third party for: thirty a day, per person. It now uses the free allowance that lane deserves, which is eight times higher, so you can iterate on a motion prompt properly instead of running out halfway through. (`/animations`) `[improvement]`- **The 3D Studio connector for ChatGPT is documented as the eleven tools it actually serves**: The free 3D Studio connector grew to eleven tools when look_at_model landed alongside check_job, but a lot of the writing about it had not caught up: the connector page, the press kit, the partner page, the blog summary, the announcement copy, the press release and the store-submission package still said nine or ten, and the social card enumerated only nine tool names. Every one of those now matches a fresh pull from the live server, the social card lists all eleven, and the module headers inside the connector describe the real catalog including which tools spend generation quota. A test now pins the total, so the next tool to land fails the suite instead of quietly re-opening the same drift. The standalone viewer also stopped crediting the AR launch endpoint with a renderer it no longer loads. Two smaller corrections rode along: the pending-generation example now shows the field that tells a client whether the model coming back is a bare mesh or a finished rig, and the three places the platform pins the 3D viewer library are now explained in one comment, so nobody has to guess why an embed and a standalone page load different builds. (`/docs/mcp-studio`) `[docs, fix]`- **The animation gallery shows you clips instead of a spinner**: The motion library is nearly 3,000 clips and growing, and /animations used to download the entire catalog before it would draw a single card. Now the first batch of clips appears as soon as it arrives and the rest fill in behind it while you are already browsing, searching and filtering. However large the library gets, you start looking at animations after the same short wait. (`/animations`) `[improvement]`diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 92eae72bd..15dd861f0 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -119,7 +119,6 @@ bottom.| `/play` event souvenirs (a free wearable you keep for having been there) | Config `public/event.json` (`souvenir.cosmeticId`, the same file the countdown reads). Server: window/world/item resolution [multiplayer/src/event-drop.js](multiplayer/src/event-drop.js), join-time grant `_grantEventSouvenir` in [multiplayer/src/rooms/WalkRoom.js](multiplayer/src/rooms/WalkRoom.js), `event` tier + catalog entry [multiplayer/src/cosmetics-catalog.js](multiplayer/src/cosmetics-catalog.js), unlock + persistence [multiplayer/src/economy.js](multiplayer/src/economy.js). Client: drop card [src/game/event-souvenir.js](src/game/event-souvenir.js), wardrobe treatment [src/game/cosmetics-wardrobe.js](src/game/cosmetics-wardrobe.js). Asset: [public/accessories/laurel-meetup.glb](public/accessories/laurel-meetup.glb) generated by [scripts/generate-accessory-glbs.mjs](scripts/generate-accessory-glbs.mjs), poster by [scripts/render-accessory-thumbs.mjs](scripts/render-accessory-thumbs.mjs) | In-repo | Everyone who joins the event world between an event's `startsAt` and `endsAt` is granted a free commemorative wearable (the Meetup Laurel), once, forever, wearable in every coin world. After `endsAt` it is never granted again and there is no purchase path at any point: a third catalog tier, `event`, carries `price: 0`, so the boutique's `tier === 'premium' && price > 0` filter excludes it by construction and the x402 purchase ledger is filtered to premium ids so it cannot mint one. Server-authoritative and idempotent: the window and the world both come from the shared event config (never a client option), the grant is a no-op on an account that already owns it, and the one-shot `souvenir` message only fires on the not-owned to owned transition, so a reconnect produces neither a duplicate nor a second announcement. Fails open on every axis (no config, unreachable config, closed window, wrong world all mean grant nothing and never delay a join). Doc: [docs/event-souvenirs.md](docs/event-souvenirs.md). Tests: [tests/event-souvenir.test.js](tests/event-souvenir.test.js); live conformance `node scripts/play-souvenir-conformance.mjs` (real server, no browser) and `node scripts/play-souvenir-e2e.mjs` (real browser) || `/play` Coin Wars portal (in-world war door, league board, spectator screen) | Client: [src/game/war-portal.js](src/game/war-portal.js) + [src/game/war-portal.css](src/game/war-portal.css) (plaza landmark, canvas league board, queue panel, results echo), wired in [src/game/coincommunities.js](src/game/coincommunities.js); arena page [pages/play/war.html](pages/play/war.html) `→ /play/war` → [src/play/war.js](src/play/war.js) + [src/play/war-world.js](src/play/war-world.js) + [src/play/war.css](src/play/war.css). API: [api/wars.js](api/wars.js) `→ /api/wars` over [api/_lib/wars-store.js](api/_lib/wars-store.js) (ledger + queue + live registry) and [api/_lib/war-ticket.js](api/_lib/war-ticket.js) (signs a pairing). Server: [multiplayer/src/rooms/ClashRoom.js](multiplayer/src/rooms/ClashRoom.js) `clash_arena`, pairing math [multiplayer/src/war-matchmaking.js](multiplayer/src/war-matchmaking.js), ticket verify [multiplayer/src/war-ticket.js](multiplayer/src/war-ticket.js), spectator snapshots [multiplayer/src/war-live.js](multiplayer/src/war-live.js), league math [multiplayer/src/war-standings.js](multiplayer/src/war-standings.js), portal location [multiplayer/src/world-features.js](multiplayer/src/world-features.js) `WAR_PORTAL` | In-repo | F18. Coin Wars ran full community-vs-community battles with an Elo league behind it and no door into it from any world. The portal is that door: a plaza landmark whose board shows this coin's real league standing, its last battles, and any war running right now (read from `/api/wars`, folded through the arena's own standings module, never a second implementation). Press `E` to run the coin's holder gate and queue the community; the matchmaker pairs it with another waiting community, seals both sides into an HMAC war ticket, and hands the player to `/play/war` with a return link carrying the full coin identity, so walking back lands in the same world with the result already echoing on the board. While a war is live the board becomes a spectator screen (score, round clock, kill feed) off a cheap poll, and a win takes the board over for a few seconds. Costs nothing when nobody is near it: no poll fires outside `WAR_PORTAL_BOARD_REACH`. Docs: [docs/coin-wars.md](docs/coin-wars.md). Tests: [tests/war-matchmaking.test.js](tests/war-matchmaking.test.js), [tests/clash-match.test.js](tests/clash-match.test.js) || `/play` event countdown (lobby banner + in-world pill) | Self-attaching module [src/game/event-countdown.js](src/game/event-countdown.js) loaded by [pages/play.html](pages/play.html); config `public/event.json` (single source of the event window; the file is the edit surface for scheduling an event), read through the shared parser + state machine in [src/shared/event-config.js](src/shared/event-config.js). Verified end to end in a real browser by `npm run verify:event` ([scripts/verify-event-countdown.mjs](scripts/verify-event-countdown.mjs)). Campaign orders: the `event-` files in [prompts/finish/](prompts/finish/) | In-repo | While `public/event.json` describes an upcoming or live event, the lobby shows a banner (name, tagline, local-time start, ticking countdown, CTA into the event world) and the in-world view gets a dismissible top-center pill (dismissal persisted per event in localStorage). Three explicit states: upcoming, live (pulsing marker, CTA suppressed when already standing in the event world), and over (everything unmounts, the interval stops). Zero edits to `coincommunities*.js` by design (the ambient-crowd pattern): it waits for the lobby DOM and mounts nothing when the config is missing, malformed, or expired. |-| `/play` photo mode (the share card people post) | Lazy client module [src/game/photo-mode.js](src/game/photo-mode.js) (event stamp, card compositor, preview sheet); the offscreen render itself is [src/game/scene-capture.js](src/game/scene-capture.js), shared with the build thumbnail; HUD button + busy/pressed states in [src/game/coincommunities-ui.js](src/game/coincommunities-ui.js) (`#cc-photo-btn`, `setPhotoActive`/`setPhotoBusy`); `P` key and the import site in [src/game/coincommunities.js](src/game/coincommunities.js) (`_openPhotoMode()`); styles in [src/game/coincommunities.css](src/game/coincommunities.css); event stamp read from `public/event.json` | In-repo | Press `P` (or the HUD camera button) and the world is composited onto a share card: the shot, the three.ws mark, the coin and world it came from, the date, and, while an event window is open, that event's name in a pill. **The chrome is never in the shot, by construction rather than by hiding it:** the capture is one extra frame rendered into a `WebGLRenderTarget` on demand, not a read of the live canvas, so the HUD, chat and nameplates were never in the GL frame and `preserveDrawingBuffer` (a full buffer copy on EVERY frame, for the sake of a rare screenshot) stays off. That is also why it cannot black-frame: the classic `domElement.toDataURL()` bug returns black because the compositor has already cleared the drawing buffer, and this path never reads it. Works in zen mode on purpose (a world with no chrome on it is exactly the shot people want), survives a retake over an open card, and the whole module is imported on the FIRST press, so a session that never takes a photo never downloads it. Copy-to-clipboard is feature-detected per engine and says so when a browser refuses, rather than failing quietly; Download saves the same PNG either way. Nothing leaves the browser. Tests: [tests/photo-mode.test.js](tests/photo-mode.test.js) (compositor + sheet under jsdom, capture stubbed). Real-browser proof, both engines: `node scripts/play-photo-mode-check.mjs` ([scripts/play-photo-mode-check.mjs](scripts/play-photo-mode-check.mjs)); `MODE=scene` drives the shipped `takePhoto` over a real WebGLRenderer in seconds and measures the captured pixels, `MODE=world` boots the actual world and drives the key and the button. || The event landing page (`/event`) | [pages/event.html](pages/event.html) `→ /event`, page module [src/event-page.js](src/event-page.js); config `public/event.json` (the SAME file the `/play` countdown reads, never a second copy of the times); live population [api/play/population.js](api/play/population.js) `→ /api/play/population`, backed by the multiplayer server's public `/population` aggregate in [multiplayer/src/index.js](multiplayer/src/index.js) | Live | The one link the community shares before and during an event, written for someone with zero context. Hero countdown ticking off `public/event.json`, a single large CTA into the event world, a plain-language "what to expect" built only from what `/play` actually does, and the run of show rendered in the visitor's own timezone with an "Add to calendar" button that builds a real RFC 5545 `.ics` in the browser (no third-party calendar service, so the guest list never leaves the device). Four designed states: upcoming (days/hours/minutes/seconds), live (LIVE marker plus the real number of people standing in the world), ended (says it happened, relabels the agenda to "What happened", and still routes people into `/play`), and no-config (an honest "no event scheduled" with the same door). The live number is real or absent: when the multiplayer server is unreachable the panel keeps the live state and drops the count instead of inventing one. Doc: [docs/api-reference.md](docs/api-reference.md#play-population-api). || Home page event strip (`/`) | Self-attaching module [src/home-event-banner.js](src/home-event-banner.js) loaded by [pages/home.html](pages/home.html); same config `public/event.json` through [src/shared/event-config.js](src/shared/event-config.js) | Live | Puts the live event in front of everyone who lands on three.ws, not just the people who already opened `/play`. A slim announcement bar between the nav and the hero: event name, start time in the visitor's own timezone, a countdown ticking to the second, and one CTA into the $THREE world (suppressed when the visitor is already there). Same three states as the `/play` surfaces and the same auto-unmount at `endsAt`, flipping upcoming to live without a reload. Dismissal shares the `/play` pill's `cc-event-dismissed:<startsAt>` key, so waving the reminder away on the home page also clears it in-world; the `/play` lobby banner stays, because it is lobby content rather than an overlay. Styled from the home page's own tokens (mono kicker, hairline pill CTA) and light-theme aware. Verified with `npm run verify:event`. || `/play` friends, presence & verified profiles (drawer, cross-world DMs, in-world profile cards) | Client: [src/game/friends-panel.js](src/game/friends-panel.js) (shared with `/walk`), mounted in [src/game/coincommunities.js](src/game/coincommunities.js) `_openFriends()`/`_closeFriends()`, HUD button + unread badge in [src/game/coincommunities-ui.js](src/game/coincommunities-ui.js), account-level state/polling in [src/friends.js](src/friends.js), profile card in the shared inspector [src/shared/avatar-inspector.js](src/shared/avatar-inspector.js) (`renderProfile`). Server: signed ticket verify + `socialHub` registration + verified `username` on the Player schema in [multiplayer/src/rooms/WalkRoom.js](multiplayer/src/rooms/WalkRoom.js) + [multiplayer/src/schemas.js](multiplayer/src/schemas.js), ticket signer [api/_lib/presence-store.js](api/_lib/presence-store.js) / verifier [multiplayer/src/presence-token.js](multiplayer/src/presence-token.js), hub in [multiplayer/src/social-hub.js](multiplayer/src/social-hub.js) | In-repo | W09+W10 of the World Online program (program brief retired to git history). Press `J` or the HUD `Friends` button to open a right-docked drawer showing your account's friend graph; live online/offline presence per coin world, requests, and DM threads; the same graph and threads `/walk` and the standalone `/friends` page already share. `community-net.js` carries a signed presence ticket into every `walk_world` join and forwards the server's `social` push onto its own event bus, which is what makes a `/play` player visible to friends and able to receive a live DM. W10 makes the platform identity first-class in-world: the ticket also carries the account's username + display name (signed, so nobody can wear a handle they don't own), WalkRoom publishes the verified `username` on the Player schema, nameplates show the @handle, the signed-in lobby defaults to the account's display name with an @handle chip, and clicking any verified player (or `I`) opens their real three.ws profile card in the shared avatar inspector: bio, follower counts, follow/unfollow (`/api/users/:username/follow`), the right friends verb (Message → the in-world DM drawer when already friends, Add friend / Accept otherwise), their latest creations, and a link to `/u/<username>`. Works identically in `/walk` (same room, same inspector). Tests: [tests/play-friends-presence.test.js](tests/play-friends-presence.test.js), [tests/play-profile-identity.test.js](tests/play-profile-identity.test.js). |diff --git a/data/changelog.json b/data/changelog.jsonindex 26f9f6fbb..16174b62e 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,15 +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-09-02",- "title": "Take a photo of your world and post it",- "summary": "Press P in a /play world, or the camera button on the HUD, and the world is captured onto a share card: your view of the town with the three.ws mark, the coin you are standing in and the date along the bottom, ready to download or paste straight into a post. The interface is never in the shot. The photo is a second frame rendered off screen just for you, so the chat, the job board and the name tags stay out of the picture no matter what is on screen when you press. It works in zen mode too, which is usually exactly when the world looks worth photographing, and while an event is running the card carries that event's name. Nothing is uploaded anywhere: the card is built in your browser and it is yours. The whole feature only downloads on your first press, so a session that never takes a photo never pays for it.",- "tags": [- "feature"- ],- "link": "/play"- },{"date": "2026-09-02","title": "Groundwork for agents that can run your house",diff --git a/public/changelog.json b/public/changelog.jsonindex 2ac28fd9c..5ad141426 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-02T21:28:54.811Z",+ "generated_at": "2026-09-02T21:35:59.568Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -271,16 +271,6 @@"feature"]},- {- "date": "2026-09-02",- "type": "update",- "title": "Take a photo of your world and post it",- "summary": "Press P in a /play world, or the camera button on the HUD, and the world is captured onto a share card: your view of the town with the three.ws mark, the coin you are standing in and the date along the bottom, ready to download or paste straight into a post. The interface is never in the shot. The photo is a second frame rendered off screen just for you, so the chat, the job board and the name tags stay out of the picture no matter what is on screen when you press. It works in zen mode too, which is usually exactly when the world looks worth photographing, and while an event is running the card carries that event's name. Nothing is uploaded anywhere: the card is built in your browser and it is yours. The whole feature only downloads on your first press, so a session that never takes a photo never pays for it.",- "link": "/play",- "tags": [- "feature"- ]- },{"date": "2026-09-02","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex f25089612..28e08eaad 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -206,14 +206,6 @@<category>fix</category><description>Press P in a coin world, or the camera button on the heads-up display, and you get a picture of the world on a share card: the scene itself, the three.ws mark, the coin you are standing in, and, during a live event, that event's name stamped on it. The card was there but the shutter went nowhere. Every single press answered "Couldn't photograph the world just now" and showed nothing, because of a fault in the code that builds the preview, so nobody has ever actually been handed one of these. Pressing it now opens the card, with Download and Copy image next to it. The picture is taken as a separate render rather than grabbed off the screen, so no panel, name tag or chat line is ever in the frame, and it works the same in zen mode, which is when most people will want it. It costs nothing when you are not using it: none of photo mode is loaded until the first press. Two smaller things fixed alongside: taking a second photo while the first card is open now replaces it cleanly instead of briefly stacking two sheets, where a click landing in the wrong moment could dismiss the shot you just took; and the line promising that P takes another one is true now, and visible, having previously rendered as nothing at all. The camera button also stays lit while the picture is being taken, instead of going quiet: taking the photo is real work, and on a slow phone it can run for a few seconds, which previously looked like a button that did nothing. Verified end to end in both Chrome and Safari, on a laptop frame and a phone frame, down to the pixels in the saved file, so the black rectangle that a mishandled 3D screenshot usually produces cannot come back unnoticed.</description></item>- <item>- <title>Take a photo of your world and post it</title>- <link>https://three.ws/play</link>- <guid isPermaLink="false">2026-09-02:Take a photo of your world and post it</guid>- <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>- <category>feature</category>- <description>Press P in a /play world, or the camera button on the HUD, and the world is captured onto a share card: your view of the town with the three.ws mark, the coin you are standing in and the date along the bottom, ready to download or paste straight into a post. The interface is never in the shot. The photo is a second frame rendered off screen just for you, so the chat, the job board and the name tags stay out of the picture no matter what is on screen when you press. It works in zen mode too, which is usually exactly when the world looks worth photographing, and while an event is running the card carries that event's name. Nothing is uploaded anywhere: the card is built in your browser and it is yours. The whole feature only downloads on your first press, so a session that never takes a photo never pays for it.</description>- </item><item><title>Text-to-animation is no longer rationed like a paid service</title><link>https://three.ws/animations</link>diff --git a/public/features.json b/public/features.jsonindex f401f6622..ccb83ddbc 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-02T21:28:54.711Z",+ "generated_at": "2026-09-02T21:35:59.519Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",