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.

docs(home): announce the household and the assistant-agnostic house

nirholasf9d09844cbbc
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f90cf8b25..53e53182f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,11 +17,13 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **three.ws Drive** (`/drive`): Your 3D agent in the car: voice-first, glanceable, and built to the rules CarPlay and Android Auto enforce. Runs on a head unit, a phone in the cradle, or inside the native car shell.
- **Voice satellite** (`/smart-home/satellite`): Give your existing Home Assistant voice assistant a face. Pair a three.ws satellite and the same pipeline you already use gains a 3D agent that lip-syncs its answers and reacts, on any screen in the house. Home Assistant keeps the wake word, the speech recognition and the answer; closing the page never stops the voice working.
- **A stranger cannot make your agent open your front door**: The home lane now has a written threat model and eleven security checks that run with every build, and the standard they hold is a lock, not a database row. The big fix: the address you give for your house is now resolved and pinned on our side before anything dials it, so a web address that secretly points back into our own network is refused instead of connected to, and it is re-checked every time your house reconnects rather than trusted from the day you added it. A device or integration in your house cannot talk your agent into anything either: we wrote an unlock instruction into a real room name, a real device name and a real scene name, ran a real agent against that house, and the front door stayed locked. Your privacy page is now rate limited like everything else, so nobody can hammer the export or the delete. (`/smart-home`) `[security, improvement]`
+- **Any assistant can now run your house, and it still will not open your door**: There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do. (`/smart-home`) `[feature, sdk, docs]`
- **Connect your house to your agent, and see every way it can go wrong**: The /smart-home page now takes you from "I have a Home Assistant somewhere" to a connected house, and it is honest at every step. An address that only exists on your home network is refused the moment you type it, with the two real ways round it, instead of spinning for fifteen seconds. A rejected token says so and puts the cursor back in the token box. A house that stops answering keeps its rooms on screen, marked stale with how long ago it last replied, rather than blanking out. Your access token is sent once, encrypted at rest, and never comes back to the page: it is not in your browser storage, not in a URL, and not in any response. Disconnecting says plainly that the stored token is erased and reminds you to delete it in Home Assistant too. (`/smart-home`) `[feature]`
- **See, export and delete everything a connected home stores**: Connecting a house to three.ws hands over a key to a physical building, so the answer to "what do you keep, and for how long" is now a page you can read and an endpoint you can call. Every piece of data a connected home creates is listed with why it exists and what removes it, including the parts we deliberately never store: the names of your rooms and devices, their states, and any audio from voice control. There is no record of which lights were on, or when. The log of what the agent did in your home is yours: it keeps 90 days by default, you can shorten it to a single day and the old entries go immediately, and an operator who has to keep records for longer can, with a written reason. One endpoint shows you what is stored, downloads all of it as JSON, and deletes one home or every trace of all of them. (`/docs/home-privacy`) `[feature, security, docs]`
- **The status page can tell one dark house from an outage**: Connected homes now report on the public status page at /status, and the hard part was making that number honest. If your Home Assistant is switched off, your token expired or your internet dropped, that is your house: it shows up in your own home view, not as a three.ws outage and not as an alert to anyone. It takes at least ten homes failing at once before the platform will call it a problem on our side, because with three homes connected one holiday cottage losing power would look like a third of everything being broken. One thing is treated as an emergency at a count of one: an action that can open a building (a lock, a garage door, an alarm) recorded as having run without someone saying yes. That has no acceptable rate. (`/status`) `[infra, improvement]`
- **The tour atlas counts its stops correctly again**: The atlas at /tour/atlas is the map of the guided tour: one card per stop, numbered in the order you would walk them. Two hundred and three of those cards were still carrying numbers from an older version of the tour, so the grid showed duplicate stop numbers, skipped others, and put cards out of order, under a heading that claimed one more stop than the grid actually held. Every card is now numbered by its real position in the tour and the count above the grid matches what is under it. Nothing about the stops themselves changed: same pages, same screenshots, same highlights. (`/tour/atlas`) `[fix]`
- **three.ws Drive: your agent, in the car**: There is a new page at /drive built for a car screen instead of a desk. Your agent is on it full size, you hold one big button and talk, and it answers out loud in its own voice with its face moving. It shows you one line of what it said rather than a wall of chat, because you are driving. It starts dark, because a bright panel at night is glare, and it will switch to a day palette on one press or one sentence. The keyboard stays out of the way while you are moving: if your browser can tell how fast you are going, text entry locks itself the moment you pull away and comes back when you have properly stopped. A few things you say never leave the car at all, so "repeat that", "stop talking", "louder" and "night mode" happen instantly, while "stop at the next charger" still goes to your agent like any other question. It works today on a head unit browser, on a phone in a cradle, and on Android Automotive. The Apple CarPlay version is built and waiting on Apple's approval for voice assistants in the car. One thing this fixed for everyone: an avatar used to answer in silence if you were not signed in, and now it always has a voice. (`/drive`) `[feature, improvement]`
+- **Your home is a household now, and a house sitter still cannot open your front door**: A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer. (`/smart-home`) `[feature, security]`
- **Your house reads in your language, in your units, at a size a finger can hit**: Three fixes to the smart home page, all of them things you would have noticed. It now speaks all 87 languages: the page was written to be translated but never loaded the piece that does the translating, so everyone got English, and Arabic and Hebrew never flipped to right to left. Temperatures now come from your house rather than from an assumption. If your Home Assistant is set to Fahrenheit, every room reads in Fahrenheit, and a room at 70 no longer shows as blazing hot because the comfort range was written in Celsius. A house that mixes a Celsius sensor with a Fahrenheit thermostat is converted before it is averaged, so the number you see belongs to a real scale. The small print at the top of the page also got lighter so it clears the contrast standard, in both the light and dark themes, and the Show button next to the token field is now big enough to tap without missing. (`/smart-home`) `[fix, improvement]`
## 2026-09-02
diff --git a/data/changelog.json b/data/changelog.json
index 88f8d69e0..bc97118dc 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -25904,6 +25904,27 @@
"improvement"
],
"link": "/smart-home"
+ },
+ {
+ "date": "2026-09-03",
+ "title": "Any assistant can now run your house, and it still will not open your door",
+ "summary": "There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do.",
+ "tags": [
+ "feature",
+ "sdk",
+ "docs"
+ ],
+ "link": "/smart-home"
+ },
+ {
+ "date": "2026-09-03",
+ "title": "Your home is a household now, and a house sitter still cannot open your front door",
+ "summary": "A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under \u201cWho can reach this home\u201d you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so \u201cwho did what\u201d has a real answer.",
+ "tags": [
+ "feature",
+ "security"
+ ],
+ "link": "/smart-home"
}
]
}
diff --git a/docs/home-households.md b/docs/home-households.md
index 431801a0e..127087f77 100644
--- a/docs/home-households.md
+++ b/docs/home-households.md
@@ -186,6 +186,37 @@ one home and one role.
- **Ownership is never invitable.** `createInvite` throws on `role: 'owner'` and the schema's check
constraint refuses the row.
+## Using it
+
+The household lives on each home's card at [/smart-home](https://three.ws/smart-home), under **Who
+can reach this home**. It is collapsed until you open it, because a person with six houses should
+not pay six extra round trips to see a roster that in most homes is one line long.
+
+What it shows, in order: your own role and what it means, then everybody else with the same
+sentence under each of them, then any invitation still waiting, then the invite form if your role
+can send one. Every control comes from the server's answer, not from a rule the browser applies:
+the roster response carries your role, the roles you may hand out, and a per-member flag for
+whether you may administer that person, so a button that would be refused is never drawn.
+
+A member with no roster authority still sees the household. Hiding the fact that other people hold
+keys to the house you are in would be the wrong secret to keep.
+
+Sending an invitation shows the link once, at that moment, with a copy button. There is no way to
+see it again: the server keeps only a hash, so "check the invitations list for the link" would be a
+promise this system cannot keep, and the UI says so rather than letting somebody discover it.
+
+The link opens [/smart-home/join](https://three.ws/smart-home/join). That page inspects the
+invitation without spending it, so it can say which home, which role, what that role will let the
+holder do and what it will never let them do, all before anyone is asked to identify themselves. A
+visitor with no account is sent through the existing register flow with `next` pointing back at the
+same invitation, so they land on it again rather than on a dashboard wondering what happened to the
+email they clicked. Nothing is accepted on page load: a link preview fetcher must not be able to
+spend somebody's invitation.
+
+Its four dead ends are four different screens. "This expired", "somebody already used this", "this
+was withdrawn" and "this link is not valid" need different words and different next steps, and
+collapsing them into one error is how a person ends up mailing support to ask which one happened.
+
## Removing somebody
`removeMember` deletes the membership row **and every standing allowance that member authorised, in
@@ -307,6 +338,9 @@ automatic today: an IdP deactivating a user stops them signing in and does not b
| The role matrix, scope, invitations, deprovisioning | `api/_lib/home/members.js` |
| The roster endpoint | `api/home/[id]/members.js` |
| Invite redemption | `api/home/invites/[token].js` |
+| The household panel | `src/home/members.js`, mounted by `src/home/manage.js` |
+| The join page | `pages/smart-home-join.html`, `src/home/join.js` |
+| The browser half of the API | `src/home/api.js` |
| The matrix as an executable test | `tests/home-roles.test.js` |
The owner row is created by a database trigger on `home_connections`, not by the application. "A
diff --git a/docs/smart-home.md b/docs/smart-home.md
index 27070f2c8..f0ece8982 100644
--- a/docs/smart-home.md
+++ b/docs/smart-home.md
@@ -241,6 +241,7 @@ below exists, and anything that does not exist says so.
| Households: roles, per-member scopes, invites | [`api/_lib/home/members.js`](../api/_lib/home/members.js), [docs/home-households.md](home-households.md) |
| Privacy, retention, export and deletion | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js), [docs/home-privacy.md](home-privacy.md) |
| The dial-out relay for LAN-only houses | [`services/home-relay/`](../services/home-relay/README.md) plus [`home-assistant-integration/`](../home-assistant-integration) |
+| The browser voice loop: wake word, barge-in, a confirmation grammar speech cannot satisfy | [`src/voice/home-voice.js`](../src/voice/home-voice.js), [`home-voice-ui.js`](../src/voice/home-voice-ui.js), surfaced at `/voice/home` |
| The Wyoming voice satellite | [`services/home-satellite/`](../services/home-satellite/README.md) |
| A standalone MCP server, so any assistant can run a house | [`packages/home-mcp/`](../packages/home-mcp/README.md) |
| A real Home Assistant on demand, for every live test | [`scripts/home-test-instance.mjs`](../scripts/home-test-instance.mjs) |
@@ -253,8 +254,6 @@ below exists, and anything that does not exist says so.
robots, and it is the same protocol either way. Nothing of it is in the tree.
- **A floorplan editor.** The 3D scene derives its layout from the area graph. Authoring and
persisting a hand-drawn floorplan is not built.
-- **Voice on the `/smart-home` page itself.** Voice today is the household's own Home Assistant
- Assist pipeline, which the satellite gives a face to. The page is text.
## 6. What was actually verified
diff --git a/docs/tutorials/connect-your-home.md b/docs/tutorials/connect-your-home.md
index 24f85718c..099f8caf6 100644
--- a/docs/tutorials/connect-your-home.md
+++ b/docs/tutorials/connect-your-home.md
@@ -208,16 +208,42 @@ That is deliberate. Firing the nearest scene is how a "good night" turns into an
## 5. Your first command, by voice
+There are two voice paths, and they are for different rooms.
+
+### In the browser, on three.ws
+
+Open [three.ws/voice/home](https://three.ws/voice/home), or the voice panel on your connected
+home, and turn listening on. Say your wake word, then say what you want. The loop is:
+
+```
+mic -> voice activity detection -> wake word -> capture -> transcription
+ -> the agent, with your home tools -> speech -> your agent's face, lip synced
+```
+
+Three things about it are worth knowing before you switch it on:
+
+1. **Nothing about listening runs until you opt in.** The detector, the wake-word matcher, the
+ runtime and every model byte are behind imports that are only reached when you enable it. A
+ page that has the panel on it and that you never enable downloads none of that.
+2. **Mute really is mute.** It stops the microphone tracks, so your browser's own recording
+ indicator goes out and the track reads `ended`. It is not a flag hiding a dot.
+3. **Speech cannot open your door on its own.** The confirmation is a narrow grammar against a
+ confirmation the server minted, and on a surface with no display a guarded action is refused
+ outright rather than confirmed by voice. Recognisers mishear, and the failure mode of
+ mishearing "confirm" is an open front door.
+
+### In the rest of the house, through Home Assistant
+
Voice already works in your house, and it is Home Assistant's own: the **Assist** pipeline, with
-wake word, speech to text and text to speech all running on your own hardware. three.ws does not
-replace any of it. What it adds is a face.
+wake word, speech to text and text to speech all on your own hardware. three.ws does not replace
+any of it. What it adds is a face.
[`services/home-satellite`](../../services/home-satellite/README.md) registers as a
-[Wyoming](https://github.com/rhasspy/wyoming) satellite, which is a thing Home Assistant already
-knows how to talk to. Run it beside your instance, point Home Assistant's **Wyoming Protocol**
-integration at `host:10700`, and assign it to a pipeline like any other satellite. It supplies a
-microphone (from a browser showing the agent) and a speaker (that browser's audio, with the
-agent's face moving in front of it). Say your wake word, and the agent looks at you and answers.
+[Wyoming](https://github.com/rhasspy/wyoming) satellite, which Home Assistant already knows how to
+talk to. Run it beside your instance, point Home Assistant's **Wyoming Protocol** integration at
+`host:10700`, and assign it to a pipeline like any other satellite. It supplies a microphone (from
+a browser showing the agent) and a speaker (that browser's audio, with the agent's face moving in
+front of it). Say your wake word, and the agent looks at you and answers.
One rule shapes that whole service: **the pipeline never depends on the face.** Close the browser
tab and Home Assistant keeps working exactly as it did before three.ws was installed. A satellite
diff --git a/public/changelog.json b/public/changelog.json
index 461cde9d5..9ced7a932 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T03:57:33.265Z",
+ "generated_at": "2026-09-03T03:59:18.737Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -117,6 +117,18 @@
"improvement"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Any assistant can now run your house, and it still will not open your door",
+ "summary": "There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do.",
+ "link": "/smart-home",
+ "tags": [
+ "feature",
+ "sdk",
+ "docs"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
@@ -171,6 +183,17 @@
"improvement"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Your home is a household now, and a house sitter still cannot open your front door",
+ "summary": "A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer.",
+ "link": "/smart-home",
+ "tags": [
+ "feature",
+ "security"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 1306618b8..6c2a3d5f4 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -94,6 +94,14 @@
<category>security</category>
<description>The home lane now has a written threat model and eleven security checks that run with every build, and the standard they hold is a lock, not a database row. The big fix: the address you give for your house is now resolved and pinned on our side before anything dials it, so a web address that secretly points back into our own network is refused instead of connected to, and it is re-checked every time your house reconnects rather than trusted from the day you added it. A device or integration in your house cannot talk your agent into anything either: we wrote an unlock instruction into a real room name, a real device name and a real scene name, ran a real agent against that house, and the front door stayed locked. Your privacy page is now rate limited like everything else, so nobody can hammer the export or the delete.</description>
</item>
+ <item>
+ <title>Any assistant can now run your house, and it still will not open your door</title>
+ <link>https://three.ws/smart-home</link>
+ <guid isPermaLink="false">2026-09-03:Any assistant can now run your house, and it still will not open your door</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do.</description>
+ </item>
<item>
<title>Connect your house to your agent, and see every way it can go wrong</title>
<link>https://three.ws/smart-home</link>
@@ -134,6 +142,14 @@
<category>feature</category>
<description>There is a new page at /drive built for a car screen instead of a desk. Your agent is on it full size, you hold one big button and talk, and it answers out loud in its own voice with its face moving. It shows you one line of what it said rather than a wall of chat, because you are driving. It starts dark, because a bright panel at night is glare, and it will switch to a day palette on one press or one sentence. The keyboard stays out of the way while you are moving: if your browser can tell how fast you are going, text entry locks itself the moment you pull away and comes back when you have properly stopped. A few things you say never leave the car at all, so &quot;repeat that&quot;, &quot;stop talking&quot;, &quot;louder&quot; and &quot;night mode&quot; happen instantly, while &quot;stop at the next charger&quot; still goes to your agent like any other question. It works today on a head unit browser, on a phone in a cradle, and on Android Automotive. The Apple CarPlay version is built and waiting on Apple's approval for voice assistants in the car. One thing this fixed for everyone: an avatar used to answer in silence if you were not signed in, and now it always has a voice.</description>
</item>
+ <item>
+ <title>Your home is a household now, and a house sitter still cannot open your front door</title>
+ <link>https://three.ws/smart-home</link>
+ <guid isPermaLink="false">2026-09-03:Your home is a household now, and a house sitter still cannot open your front door</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer.</description>
+ </item>
<item>
<title>Your house reads in your language, in your units, at a size a finger can hit</title>
<link>https://three.ws/smart-home</link>
diff --git a/public/features.json b/public/features.json
index 5884dbea3..a1109a661 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T03:57:33.231Z",
+ "generated_at": "2026-09-03T03:59:18.663Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/public/llms-full.txt b/public/llms-full.txt
index f578c6e9f..f0a93931f 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -744,6 +744,12 @@ URL: https://three.ws/materialize
Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from the mesh's own measured volume, and USDC checkout on Solana.
+### Join a home
+
+URL: https://three.ws/smart-home/join
+
+Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let you do, before you sign in. It works once and it expires.
+
### Home plan
URL: https://three.ws/smart-home/plan
@@ -1989,6 +1995,12 @@ URL: https://three.ws/docs/home-households
Sharing a connected house without sharing a login: the five roles and what each one may do, per-member entity scopes that narrow the house a member can even see, how invitations are issued and accepted, what happens to somebody's access when they leave, and the rule everything hangs off, that a guest can never confirm an action that opens a building.
+### Docs · Home security
+
+URL: https://three.ws/docs/home-security
+
+The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate is the load-bearing control and prompt filtering is depth, the eleven checks that run with every build, the SSRF guard every server-side dial goes through and why a hostname check is not one, the prompt-injection proof that ends by asking a real lock whether it opened, and the residuals accepted on purpose.
+
### Docs · Home privacy and retention
URL: https://three.ws/docs/home-privacy
diff --git a/public/llms.txt b/public/llms.txt
index 5937bfd78..fcd0bde68 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -150,6 +150,7 @@ Create and customize an agent.
- [TRELLIS NIM Forge](https://three.ws/nim-forge): Drop in a photo, get a textured 3D model, reconstructed on a self-hosted Microsoft TRELLIS NIM. Single-hop image to GLB.
- [Avatar SDK](https://three.ws/avatar-sdk): The @three-ws/avatar package: embed the platform 3D avatars in any site with a few lines of JavaScript.
- [Materialize](https://three.ws/materialize): Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from the mesh's own measured volume, and USDC checkout on Solana.
+- [Join a home](https://three.ws/smart-home/join): Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let you do, before you sign in. It works once and it expires.
- [Home plan](https://three.ws/smart-home/plan): What your plan covers for connected homes: homes, household seats, live screens, voice minutes and agent turns, each with what you have used and when it resets. Pause and resume which homes are live without disconnecting any of them. Locking up, closing a garage and arming an alarm are never limited.
- [Smart home](https://three.ws/smart-home): Connect a Home Assistant house to your three.ws agent. Your agent reads every room and device, runs the scenes you already built, and stops to ask before it unlocks, opens or disarms anything.
- [Voice satellite](https://three.ws/smart-home/satellite): Give your existing Home Assistant voice assistant a face. Pair a three.ws satellite and the same pipeline you already use gains a 3D agent that lip-syncs its answers and reacts, on any screen in the house. Home Assistant keeps the wake word, the speech recognition and the answer; closing the page never stops the voice working.
@@ -367,6 +368,7 @@ Docs, tutorials, and reference.
- [Docs · Avatar Artifact viewer](https://three.ws/docs/avatar-artifact): The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.
- [Docs · three.ws Home](https://three.ws/docs/smart-home): How a three.ws agent connects to a real house: the open-source smart-home landscape measured and shortlisted, why Home Assistant owns the device layer, the two channels the @three-ws/home-bridge package speaks, the physical-action gate that never lets an unlock through unasked, and the road from here to voice in every room.
- [Docs · Home households and roles](https://three.ws/docs/home-households): Sharing a connected house without sharing a login: the five roles and what each one may do, per-member entity scopes that narrow the house a member can even see, how invitations are issued and accepted, what happens to somebody's access when they leave, and the rule everything hangs off, that a guest can never confirm an action that opens a building.
+- [Docs · Home security](https://three.ws/docs/home-security): The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate is the load-bearing control and prompt filtering is depth, the eleven checks that run with every build, the SSRF guard every server-side dial goes through and why a hostname check is not one, the prompt-injection proof that ends by asking a real lock whether it opened, and the residuals accepted on purpose.
- [Docs · Home privacy and retention](https://three.ws/docs/home-privacy): Everything three.ws stores about a home you connect, why, for how long, and what removes it: the full inventory, the promise that room names and device states are never persisted, the 90-day action-log window and the control that changes it, the export and deletion paths, the logging rules, and the disclosure text shown at connect and at the voice opt-in.
- [Docs · three.ws Drive](https://three.ws/docs/carplay): How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and why it grants no drawing surface, the open-source in-car projects worth adopting and the copyleft ones that are not, and how the /drive surface, the native CarPlay scene, and an open head unit share one implementation.
- [Docs · Terminal avatar](https://three.ws/docs/tty-avatar): The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index 5aae60bf3..22dc9b68b 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -83,7 +83,7 @@
<main class="sm-wrap">
<div class="sm-hero">
<h1>Sitemap</h1>
- <p>All 894 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
+ <p>All 896 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
<div class="sm-formats">
<a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>
<a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>
@@ -95,7 +95,7 @@
</div>
<div class="sm-filter">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>
- <input id="sm-filter-input" type="search" placeholder="Filter 894 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 896 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
<kbd aria-hidden="true">/</kbd>
</div>
<p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>
@@ -119,6 +119,14 @@
<span class="sm-desc">Talk to your house without finding a phone: a wake word matched on your own device, real barge-in mid-sentence, and a spoken confirmation that a background yes can never satisfy.</span>
</a>
</li>
+ <li>
+ <a href="/smart-home/join">
+ <span class="sm-new-date">Sep 3, 2026</span>
+ <span class="sm-title">Join a home</span>
+ <span class="sm-path">/smart-home/join</span>
+ <span class="sm-desc">Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let you do, before you sign in. It works once and it expires.</span>
+ </a>
+ </li>
<li>
<a href="/smart-home/plan">
<span class="sm-new-date">Sep 3, 2026</span>
@@ -152,27 +160,19 @@
</a>
</li>
<li>
- <a href="/docs/home-privacy">
+ <a href="/docs/home-security">
<span class="sm-new-date">Sep 3, 2026</span>
- <span class="sm-title">Docs · Home privacy and retention</span>
- <span class="sm-path">/docs/home-privacy</span>
- <span class="sm-desc">Everything three.ws stores about a home you connect, why, for how long, and what removes it: the full inventory, the promise that room names and device states are never persisted, the 90-day action-log window and the control that changes it, the export and deletion paths, the logging rules, and the disclosure text shown at connect and at the voice opt-in.</span>
+ <span class="sm-title">Docs · Home security</span>
+ <span class="sm-path">/docs/home-security</span>
+ <span class="sm-desc">The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate is the load-bearing control and prompt filtering is depth, the eleven checks that run with every build, the SSRF guard every server-side dial goes through and why a hostname check is not one, the prompt-injection proof that ends by asking a real lock whether it opened, and the residuals accepted on purpose.</span>
</a>
</li>
<li>
- <a href="/docs/carplay">
+ <a href="/docs/home-privacy">
<span class="sm-new-date">Sep 3, 2026</span>
- <span class="sm-title">Docs · three.ws Drive</span>
- <span class="sm-path">/docs/carplay</span>
- <span class="sm-desc">How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and why it grants no drawing surface, the open-source in-car projects worth adopting and the copyleft ones that are not, and how the /drive surface, the native CarPlay scene, and an open head unit share one implementation.</span>
- </a>
- </li>
- <li>
- <a href="/materialize">
- <span class="sm-new-date">Sep 2, 2026</span>
- <span class="sm-title">Materialize</span>
- <span class="sm-path">/materialize</span>
- <span class="sm-desc">Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from the mesh's own measured volume, and USDC checkout on Solana.</span>
+ <span class="sm-title">Docs · Home privacy and retention</span>
+ <span class="sm-path">/docs/home-privacy</span>
+ <span class="sm-desc">Everything three.ws stores about a home you connect, why, for how long, and what removes it: the full inventory, the promise that room names and device states are never persisted, the 90-day action-log window and the control that changes it, the export and deletion paths, the logging rules, and the disclosure text shown at connect and at the voice opt-in.</span>
</a>
</li>
</ul>
@@ -600,7 +600,7 @@
<section class="sm-section" id="build">
<header>
- <h2>Build<span class="sm-count" data-count>75</span></h2>
+ <h2>Build<span class="sm-count" data-count>76</span></h2>
<p class="sm-section-desc">Create and customize an agent.</p>
</header>
<ul class="sm-list">
@@ -1045,6 +1045,13 @@
<span class="sm-desc">Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from the mesh's own measured volume, and USDC checkout on Solana.</span>
</a>
</li>
+ <li>
+ <a href="/smart-home/join">
+ <span class="sm-title">Join a home</span>
+ <span class="sm-path">/smart-home/join</span>
+ <span class="sm-desc">Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let you do, before you sign in. It works once and it expires.</span>
+ </a>
+ </li>
<li>
<a href="/smart-home/plan">
<span class="sm-title">Home plan</span>
@@ -2451,7 +2458,7 @@
<section class="sm-section" id="learn">
<header>
- <h2>Learn<span class="sm-count" data-count>406</span></h2>
+ <h2>Learn<span class="sm-count" data-count>407</span></h2>
<p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
@@ -2497,6 +2504,13 @@
<span class="sm-desc">Sharing a connected house without sharing a login: the five roles and what each one may do, per-member entity scopes that narrow the house a member can even see, how invitations are issued and accepted, what happens to somebody's access when they leave, and the rule everything hangs off, that a guest can never confirm an action that opens a building.</span>
</a>
</li>
+ <li>
+ <a href="/docs/home-security">
+ <span class="sm-title">Docs · Home security</span>
+ <span class="sm-path">/docs/home-security</span>
+ <span class="sm-desc">The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate is the load-bearing control and prompt filtering is depth, the eleven checks that run with every build, the SSRF guard every server-side dial goes through and why a hostname check is not one, the prompt-injection proof that ends by asking a real lock whether it opened, and the residuals accepted on purpose.</span>
+ </a>
+ </li>
<li>
<a href="/docs/home-privacy">
<span class="sm-title">Docs · Home privacy and retention</span>