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.

fix(embed): boot the avatar instead of throwing on a name that does not exist

nirholas91a33086bd5b
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 629fdfb29..6e12900b0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -42,6 +42,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Agent history on Base, Ethereum and Gnosis is moving again**: The cross-chain agent index had stopped advancing on three networks. A single unprintable byte inside an on-chain metadata string was rejected by the database, and because the index only records its position after a successful write, every following run re-read the same block and hit the same byte. Base had been frozen for 13 days, Gnosis for 15 and Ethereum for 4. Those bytes are now stripped on the way in, so the event is kept and the crawl moves past it. Registrations, ownership transfers, metadata edits and reputation attestations on those chains flow into agent profiles again. `[fix]`
- **Agent payments now stop themselves when the fee wallet runs dry**: The platform sponsors the network fee on every agent payment. When that wallet ran down to the point where it could not cover a single fee, the check meant to pause payments could not run, because it depended on a balance lookup and the network providers were rate-limited at the same moment. Payments kept being attempted for three hours and none of them could complete. The pause now reads its answer from the failure itself, which costs nothing and works exactly when the network is too busy to answer questions. The status page also names the real cause now, a wallet that needs funding, instead of pointing at the payment rail. `[fix, infra]`
- **AI agents can now see the 3D models they make**: Until today every 3D generator on the internet, ours included, answered with a link to a file an AI agent cannot open. A person clicks it; an agent is blind to it, which is why an agent that makes a 3D model has never been able to tell a clean one from a melted one. That changes now: ask to look at any model and it comes back rendered from four angles as actual pictures the agent sees, with the geometry explained in plain language. An agent can finally check its own work, spot that the back of the model was never finished, and try again saying exactly what was wrong. It works over MCP, over a plain web request, and through a new open-source package called @three-ws/see, and it is free, including for agents that bought a model from us and want to confirm they got what they paid for. (`/docs/3d-vision`) `[feature, sdk]`
+- **Embedded avatars load again on other people's websites**: Anyone who dropped a three.ws avatar onto their own site with the <agent-3d> tag and pointed it straight at a model file got an error panel instead of the character: the embed code referred to something that was not there and gave up at the last step, right before it would have started the idle animation. It now loads and plays as documented. Two related repairs came with it: the compression decoders three.ws hosts can finally be used by other sites (they were being blocked, so every embed quietly fell back to a third-party CDN and logged errors doing it), and the code that runs on other people's pages is now checked for this exact class of mistake before it can ship again. (`/docs/web-component`) `[fix, sdk]`
- **Every release note now shows you the code that shipped it**: Until today this site kept two separate records of the same work: a changelog written for people, and a commit feed written by engineers, neither aware of the other. The new ship log joins them. Each release note now lists the commits that produced it, and says how confident it is in each match and why it made it, in plain words you can argue with. Commits nobody ever wrote up are grouped and shown too, so the work that shipped quietly is visible instead of lost. The announcements in the Telegram channel now carry a link to the exact code behind them, the raw commit feed reads in plain language instead of engineering shorthand, and it no longer posts merges or dependency bumps. The whole thing is a free, open-source package that works on anyone's repository. (`/ship`) `[feature, sdk, improvement]`
- **Glance: your agent on your Windows home screen, in your README, and in your terminal**: Your agent now has a card: its name, what it did in the last 24 hours, when it last acted, and a tap straight back into it. Pin it to the Windows 11 widgets board and it installs with the site itself, no app store, and refreshes on its own every fifteen minutes; signed out it shows a sign-in card instead of an error, and offline it keeps showing the last card it saw. The same card is one image URL you can paste into a GitHub README, a Slack message, or any page, and it follows the reader's light or dark mode. There is a live element for websites, a command you can run in a terminal to watch an agent work, and an npm package for building your own. Android is next, then macOS and iOS. (`/glance`) `[feature, sdk]`
- **Herald: your terminal can now make a 3D character walk onto your screen and talk to you**: We took the part of three.ws where an avatar delivers a notification in person and turned it into something anyone can use, on any website. @three-ws/herald is an open library: one line of code and a 3D character walks into the corner of your page, looks at the person using it, and tells them, with a link to the thing it is about. It is not a toast library. It is an interrupt budget: an importance floor, quiet hours, a rate limit, dedupe, freshness, batch collapse, and a stable reason for every message it refuses to deliver, so you can always answer why you did not hear about something. No GPU, an iframe, or reduced motion falls back to an accessible card that screen readers announce the same moment everyone else hears it. There is also a rail: with an API key, anything that can make an HTTPS request reaches the browser tab you already have open. Run npx @three-ws/herald watch -- npm test and your avatar tells you when the build finishes, keeping the exit code. Wire the MCP server into Claude or Cursor and an agent that worked for twenty minutes can walk on and tell you it is done. An announcement always goes to your own sessions, so no key can interrupt anyone but its owner. Try the whole thing, rules engine included, at three.ws/herald. (`/herald`) `[feature, sdk]`
@@ -71,7 +72,7 @@ And all of it is public. Oracle Lab publishes the actual model: every weight, th
- **Your agent reads the checkout before you pay**: A new browser extension puts the companion on the one screen where it is worth the most: the payment page. It tells you the total against the price you were actually shown, names money the page never itemised, adds up the fees, and reads the fine print for the things that catch people out, a trial that turns into an annual charge, a renewal at a different price, a cancellation notice period. Every amount it quotes is computed rather than read off a language model, so the arithmetic still works when nothing else does, and it never calls a charge illegal or a scam because that is not a call it is in a position to make. It never reads a form field: your card number, security code and address are structurally unreadable to it, personal data is stripped in your own browser before anything is sent, only the site's hostname travels, and nothing about the page is stored anywhere. (`/companion`) `[feature, security]`
- **Your agents can now tell you why they are not doing anything**: An audit found ten of twelve autonomous trading agents had not acted in weeks while every health check reported them perfectly fine: the container was up, the feed was streaming, every strategy was armed. Liveness measures the process, but acting needs a whole chain of preconditions the process knows nothing about. A new open-source package, @three-ws/agent-vitals, models those preconditions as a causal graph and answers the real question: can this agent act right now, and if not, what is the one thing to fix. It reports root causes instead of symptoms, so a stale deployment that killed a model chain that starved a decision queue reads as one item with one command, not three red rows to guess between. Run npm run agent:vitals for the fleet, or GET /api/agents/vitals. (`/docs/agent-vitals`) `[feature, sdk, infra]`
- **Your avatar now runs in a terminal, and it can be your coding agent's face**: A new package, @three-ws/tty-avatar, draws any three.ws avatar or agent body live in a terminal window: one npx command, no browser, no GPU, 24 frames a second in colour. It has moods (thinking, working, happy, error, asleep) that work on any model without a rig, and one command wires it to Claude Code so the avatar thinks while the agent reads your prompt, nods while it edits files, shakes when a tool fails and bounces when it finishes, with a caption naming what it is doing. Every avatar and agent page now has the command in its Embed tab. (`/docs/tty-avatar`) `[feature, sdk]`
-- **Your notifications now have a body: meet your companion**: Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it. (`/companion`) `[feature, sdk, improvement]`
+- **Your notifications now have a body: meet your companion**: Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. You can answer straight from the message: a Telegram delivery carries a reply box that sends back into the same chat, so it is a conversation and not a receipt. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it. (`/companion`) `[feature, sdk, improvement]`
## 2026-08-27
diff --git a/packages/create-agent/src/scaffold.js b/packages/create-agent/src/scaffold.js
index 0a7a3ee72..fb2506929 100644
--- a/packages/create-agent/src/scaffold.js
+++ b/packages/create-agent/src/scaffold.js
@@ -22,13 +22,27 @@ export function slugify(text, fallback = 'agent') {
return slug || fallback;
}
+// A prompt is a sentence, and the subject is the part before its first
+// preposition: "a knight with worn steel armor" is a Knight. Cutting at a fixed
+// word count instead produced "Friendly Cartoon Astronaut In" on the first real
+// run, and "Knight With Worn Steel" on the second.
+const STOP_WORDS = new Set([
+ 'in', 'on', 'at', 'of', 'with', 'and', 'or', 'for', 'to', 'a', 'an', 'the', 'wearing', 'holding',
+ 'that', 'who', 'which', 'from', 'over', 'under', 'by',
+]);
+
/** A display name from a prompt: "a friendly cartoon astronaut" -> "Friendly Cartoon Astronaut". */
export function titleFrom(text, fallback = 'Agent') {
- const words = String(text || '')
+ const all = String(text || '')
.replace(/^(a|an|the)\s+/i, '')
- .split(/\s+/)
- .filter(Boolean)
- .slice(0, 4);
+ .split(/[\s,]+/)
+ .filter(Boolean);
+ const words = [];
+ for (const word of all) {
+ if (words.length && STOP_WORDS.has(word.toLowerCase())) break;
+ words.push(word);
+ if (words.length === 4) break;
+ }
if (!words.length) return fallback;
return words.map((w) => w.charAt(0).toUpperCase() + w.slice(1)).join(' ');
}
diff --git a/public/changelog.json b/public/changelog.json
index 2922fde2e..edf95a955 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T06:34:45.458Z",
+ "generated_at": "2026-08-28T06:41:40.928Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -368,6 +368,17 @@
"sdk"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "update",
+ "title": "Embedded avatars load again on other people's websites",
+ "summary": "Anyone who dropped a three.ws avatar onto their own site with the <agent-3d> tag and pointed it straight at a model file got an error panel instead of the character: the embed code referred to something that was not there and gave up at the last step, right before it would have started the idle animation. It now loads and plays as documented. Two related repairs came with it: the compression decoders three.ws hosts can finally be used by other sites (they were being blocked, so every embed quietly fell back to a third-party CDN and logged errors doing it), and the code that runs on other people's pages is now checked for this exact class of mistake before it can ship again.",
+ "link": "/docs/web-component",
+ "tags": [
+ "fix",
+ "sdk"
+ ]
+ },
{
"date": "2026-08-28",
"type": "update",
@@ -608,7 +619,7 @@
"date": "2026-08-28",
"type": "update",
"title": "Your notifications now have a body: meet your companion",
- "summary": "Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.",
+ "summary": "Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. You can answer straight from the message: a Telegram delivery carries a reply box that sends back into the same chat, so it is a conversation and not a receipt. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.",
"link": "/companion",
"tags": [
"feature",
diff --git a/public/changelog.xml b/public/changelog.xml
index 6022141b1..5669b0dd5 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -294,6 +294,14 @@
<category>feature</category>
<description>Until today every 3D generator on the internet, ours included, answered with a link to a file an AI agent cannot open. A person clicks it; an agent is blind to it, which is why an agent that makes a 3D model has never been able to tell a clean one from a melted one. That changes now: ask to look at any model and it comes back rendered from four angles as actual pictures the agent sees, with the geometry explained in plain language. An agent can finally check its own work, spot that the back of the model was never finished, and try again saying exactly what was wrong. It works over MCP, over a plain web request, and through a new open-source package called @three-ws/see, and it is free, including for agents that bought a model from us and want to confirm they got what they paid for.</description>
</item>
+ <item>
+ <title>Embedded avatars load again on other people's websites</title>
+ <link>https://three.ws/docs/web-component</link>
+ <guid isPermaLink="false">2026-08-28:Embedded avatars load again on other people's websites</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Anyone who dropped a three.ws avatar onto their own site with the &lt;agent-3d&gt; tag and pointed it straight at a model file got an error panel instead of the character: the embed code referred to something that was not there and gave up at the last step, right before it would have started the idle animation. It now loads and plays as documented. Two related repairs came with it: the compression decoders three.ws hosts can finally be used by other sites (they were being blocked, so every embed quietly fell back to a third-party CDN and logged errors doing it), and the code that runs on other people's pages is now checked for this exact class of mistake before it can ship again.</description>
+ </item>
<item>
<title>Every release note now shows you the code that shipped it</title>
<link>https://three.ws/ship</link>
@@ -476,7 +484,7 @@ And all of it is public. Oracle Lab publishes the actual model: every weight, th
<guid isPermaLink="false">2026-08-28:Your notifications now have a body: meet your companion</guid>
<pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
<category>feature</category>
- <description>Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.</description>
+ <description>Your phone buzzes forty times a day and two of those mattered. three.ws/companion is the other half of that problem. Connect what you already use, on your own keys: a Telegram bot you create, the private calendar link Google, Apple and Outlook all publish, your inbox over IMAP with an app password, or nothing at all but a token your phone, your Mac, your build script or an AI agent can post to. Everything that arrives is scored out of 100 against the things people actually want interrupting for (a saved contact asking you something, a one-time code, a meeting starting in ten minutes, a payment that failed) and the rest is kept quietly in a feed with the reason it stayed quiet. What clears your bar is delivered in person: a 3D character walks on, and if it is from someone you gave a face to, it arrives wearing their avatar and speaking in their voice. It reaches you on three.ws, as a push on your phone, and on your desktop, where a new companion app puts a character that walks across your screen and comes over to tell you. You can answer straight from the message: a Telegram delivery carries a reply box that sends back into the same chat, so it is a conversation and not a receipt. Quiet hours are absolute, the credentials are encrypted, and one button revokes every device. Developers get the whole thing as @three-ws/companion: a client, the same triage rules the server runs (so you can score your mail locally and never send the rest), a drop-in 3D stage for any page, a CLI, and an MCP server so an agent that finds something urgent can stand in front of you and say it.</description>
</item>
<item>
<title>three.ws for Seeker</title>
diff --git a/public/features.json b/public/features.json
index 22e0d27f6..d9ad1b46b 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T06:34:45.433Z",
+ "generated_at": "2026-08-28T06:41:40.917Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/src/element.js b/src/element.js
index 81fd8279d..8440edd50 100644
--- a/src/element.js
+++ b/src/element.js
@@ -1680,7 +1680,12 @@ class Agent3DElement extends HTMLElement {
// Initial playback. Chat avatars idle-loop (then walk on stream); bare
// decoration avatars honor the `clip` attribute, the clip's manifest
// loop flag, and prefers-reduced-motion via _startDecorationPlayback.
- if (bodyURI) {
+ // `bodyCandidates` is the loaded body's gateway list. This read used to
+ // name a variable that only exists in manifest.js, so every boot that
+ // reached this line threw "bodyURI is not defined" and the element
+ // showed its error overlay instead of the avatar. eslint knew (no-undef),
+ // but it was a warning, so nothing stopped it shipping.
+ if (bodyCandidates.length) {
if (this._isChatMode()) {
this._scene.playClipByName('idle', { loop: true });
} else {
diff --git a/tests/browser-entrypoints-no-undef.test.js b/tests/browser-entrypoints-no-undef.test.js
new file mode 100644
index 000000000..e2e79dd4e
--- /dev/null
+++ b/tests/browser-entrypoints-no-undef.test.js
@@ -0,0 +1,47 @@
+// The browser code that runs on OTHER people's websites must not reference an
+// identifier that does not exist.
+//
+// This is not a style rule. On 2026-08-28 `src/element.js` read `bodyURI`, a
+// variable that only exists in `src/manifest.js`, so every `<agent-3d>` boot
+// that reached that line threw "bodyURI is not defined" and the element showed
+// its error overlay instead of the avatar. eslint knew: it reports `no-undef`,
+// but as a WARNING, and nothing in the pipeline fails on warnings, so a
+// guaranteed runtime crash shipped in the published bundle.
+//
+// Repo-wide `no-undef` is still a warning (there is a backlog of other hits in
+// pages that are not third-party facing). These three files are the ones that
+// load inside someone else's page, where a crash is invisible to us and fatal
+// to them, so they are held to the stricter bar here.
+
+import { describe, it, expect } from 'vitest';
+import { execFileSync } from 'node:child_process';
+import { resolve } from 'node:path';
+
+const ENTRYPOINTS = [
+ // The <agent-3d> element: the whole embeddable product.
+ 'src/element.js',
+ // The embed loader third-party pages include directly.
+ 'public/embed/v1.js',
+ // The <agent-glance> card element, same deal.
+ 'public/glance/element.js',
+];
+
+function undefinedIdentifiersIn(file) {
+ const raw = execFileSync(
+ 'npx',
+ ['eslint', '--no-color', '--format', 'json', resolve(process.cwd(), file)],
+ { encoding: 'utf8', maxBuffer: 32 * 1024 * 1024 },
+ );
+ const [report] = JSON.parse(raw);
+ return (report?.messages || [])
+ .filter((m) => m.ruleId === 'no-undef')
+ .map((m) => `${file}:${m.line} ${m.message}`);
+}
+
+describe('third-party browser entry points', () => {
+ for (const file of ENTRYPOINTS) {
+ it(`${file} references no undefined identifier`, () => {
+ expect(undefinedIdentifiersIn(file)).toEqual([]);
+ }, 120_000);
+ }
+});
diff --git a/tests/create-agent.test.js b/tests/create-agent.test.js
index 847bd0431..057d2c99a 100644
--- a/tests/create-agent.test.js
+++ b/tests/create-agent.test.js
@@ -167,6 +167,13 @@ describe('scaffold', () => {
'a-friendly-cartoon-astronaut',
);
expect(titleFrom('a friendly cartoon astronaut')).toBe('Friendly Cartoon Astronaut');
+ // A name is the subject, not the first four words of the sentence: the
+ // real runs produced "Friendly Cartoon Astronaut In" and
+ // "Knight With Worn Steel" before this cut at the first preposition.
+ expect(titleFrom('a friendly cartoon astronaut in a glossy white suit')).toBe(
+ 'Friendly Cartoon Astronaut',
+ );
+ expect(titleFrom('a knight with worn steel armor')).toBe('Knight');
expect(slugify('!!!')).toBe('agent');
expect(titleFrom('')).toBe('Agent');
});
diff --git a/vercel.json b/vercel.json
index 4c1c81a03..f264b95bb 100644
--- a/vercel.json
+++ b/vercel.json
@@ -885,6 +885,14 @@
"src": "/three-token/?",
"dest": "/three-token.html"
},
+ {
+ "src": "/three/(draco|basis)/(.*)",
+ "headers": {
+ "access-control-allow-origin": "*",
+ "cache-control": "public, max-age=31536000, immutable"
+ },
+ "dest": "/three/$1/$2"
+ },
{
"src": "/three/?",
"dest": "/three.html"