Skip to content

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.

5.9 KB
Raw Blame

Announcement pack: A 3D assistant on any site, from one script tag

Surface: /assistant · Stage: drafted · Slot: 2026-09-22 · Announced externally: never

Ranked 48 of 330 never-announced surfaces by npm run announce:rank (score 66). Drafted by hand and packed by npm run announce:kit, from the evidence brief data/announce-plan/briefs/assistant.json (a local build artifact: data/announce-plan/ is gitignored, so regenerate it with npm run announce:kit -- --id assistant --brief-only), against the announcement voice. Every fact below comes from that brief; nothing in this pack was written from memory.


At a glance

Field Value
Pack id assistant
Publish slot 2026-09-22. The minute is decided at send time from the production schedule seed, so it is not knowable from this repository
Lane and pattern developer / clip
Audience Engineers who will read the code
Primary channel X, @trythreews, through the reviewed content queue
Secondary channels Telegram (@three_ws), the surface's own docs page
Proof https://three.ws/assistant
Tracked links Telegram https://three.ws/assistant?utm_source=telegram&utm_medium=community&utm_campaign=announce-assistant&utm_content=announcement. The X post links the bare URL on purpose: X wraps every link in t.co and the queue's own ledger records the send, so a tagged link buys nothing and reads like marketing.
The single CTA Open /assistant and use it
Media assistant-hero, motion loop
KPI loop completions and profile visits, then route sessions on the day

Why this one, and why now

The ranker scored it on signals measured against our own archive, not on taste:

  • reach (16): sitemap priority 0.80, which is what we already decided this surface is worth
  • visual (25): a showcase surface, so its frame can be a motion loop
  • novelty (20): on the coverage audit's hand-picked shortlist of strongest candidates
  • depth (5): documented in the tree, so there is enough to write a mechanism about and link proof for

The coverage audit's note on it: The AI concierge and assistant widgets: the embeddable business story beyond avatars.

It shipped on 2026-07-18 and has never been posted about.

The changelog has 4 entries about it, the most recent from 2026-08-16: "The assistant widget now tells you the truth when its chat lane is busy".

The claim, and where it is checked

One script tag puts a 3D avatar assistant in the corner of any site. Pick a body, a background, and what it knows about your page. three.ws/assistant

Every checkable part of that is declared as a claim in the queue item, and the verifier re-checks each one against the live surface before the post can be approved:

Claim Checked against
The live preview runs in the corner of the page while you configure it, and every change above re-mounts it. live page shows "Live preview running in the corner. Every change above re-mounts it."
Use a built-in body, any three.ws avatar id, a GLB URL, or an agent's body. live page shows "Use a built-in body, any three.ws avatar id (make one in Forge), a GLB URL, or an agent's body via data-agent."

Media

Captured from the live route by npm run announce:media, which drives the real page in a real Chromium and writes provenance (route, commit, time, sha256) beside the pixels in public/announce/media-manifest.json.

Shot File Notes
assistant-hero /announce/img/assistant-hero.webp Motion loop of the live route.

Alt text, required on the post:

The assistant builder page: a Configure column with avatar, background, mode, name and greeting fields on the left, the one-line script snippet on the right, and the widget's round launcher button in the bottom corner.

The post

Pattern: clip. 154 weighted characters, inside the 100 to 179 band that measured a 3.0x lift. Postable file: assistant.post.txt, which is the byte-for-byte source the queue item points at.

One script tag puts a 3D avatar assistant in the corner of any site. Pick a body, a background, and what it knows about your page. three.ws/assistant

Why it is written that way

The post leads on the first move a developer makes and what comes back: configure, watch the preview re-mount, copy one tag. That is the whole product, and it is the shortest path from reading to shipping an avatar on a real site.

Thread

2/ (108)

The live preview runs in the corner of the page while you configure it, and every change above re-mounts it.

3/ (154)

Use a built-in body, any three.ws avatar id, a GLB URL, or an agent's body. It answers in chat, or speaks what you type in a speech bubble.

Telegram (@three_ws)

The same facts in the channel's longer register. The changelog cron posts release notes there automatically; this is the announcement register, sent by hand or queued alongside the post.

The assistant widget puts a talking 3D avatar on any website with one script tag. Pick a body, a background, and what the chatbot should know about your site, and the live preview in the corner re-mounts on every change. Use a built-in body, any three.ws avatar id, a GLB URL, or an agent's body, then copy the tag. three.ws/assistant

Ship it

npm run announce:media -- --only assistant-hero   # capture the frame from the live route
npm run x:content -- review assistant               # lint, live fact checks, AI editor
npm run x:content -- run --dry-run --id assistant   # exactly what would be sent to X

The queue item is assistant in data/x-content/queue.json, at status draft. It becomes eligible to publish when a passing review record exists and the owner sets its status to approved; the Cloud Scheduler tick then sends it at its slot. Nothing here posts on its own.