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(changelog): publish the widget, floorplan rooms and floor-skip entries

nirholascdc69c6ff5dc
diff --git a/CHANGELOG.md b/CHANGELOG.md
index fd3ce4d08..b02be5a50 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -27,6 +27,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The Animation Studio names itself for screen readers, and its empty timeline is legible on a phone**: A full audit of /pose, where you pose an avatar and keyframe an animation. The page had no top-level heading at all: assistive technology jumped straight into "Selection" with nothing saying which studio you were in, so "Animation Studio" in the breadcrumb is now the page's real heading. The status pill above the canvas is the studio's only error surface (it is what tells you an import failed, an avatar could not be loaded, or that you need a keyframe before saving) and it never announced anything; it is now a live region, so those messages are spoken as they appear. On a 320px screen the empty-timeline hint ("Pose the figure, then press K") wrapped across the ruler's second markings and both became unreadable; the ruler now stays out of the way until you have keyframes to measure, and returns the moment you add one. Loading an avatar could also fail into a dead end: the picker said "Failed to load: Failed to fetch" with no way forward, and now explains whether the request reached three.ws and offers a Try again button. Behind that, a slow first CDN could make the 3D preview library load twice and throw an error into the console; a second load is now ignored. (`/pose`) `[fix, improvement]`
- **The Coin Wars arena reconnects to its battle server, and a link with no battle now shows you where the wars are**: A full audit of /play/war, the arena where two coin communities fight to the kill cap. The page had lost the address of the multiplayer server it joins, so every player walking through a war portal landed on 'The arena server is unreachable' instead of a battlefield; the arena is wired back up. Beyond that, a link with no pairing (a shared URL, an expired ticket, a battle that already finished) used to be one sentence and a button back to the lobby, which told you nothing about where a war actually is. It is now the war room: the battles running right now with their live score and clock, the communities queued for an opponent, and the top of the Elo ladder, each one a link into that coin's world where its war portal stands. The same panel sits under every other dead end, so 'there is no battle here' always comes with 'here is where one is'. Also fixed: a failed holder check used to show an internal service error instead of telling you what to do, the Fire button announced itself as 'Firespace' to screen readers, pressing Space on the result card did nothing because the arena was eating the key, and the HUD's hover and focus animations were dead because the page never loaded the site's motion tokens. The arena now says it is playable with WASD, moves focus onto the way out when a card appears, and reads cleanly from 320px up. (`/play/war`) `[fix, improvement]`
- **The economy solver says which level its numbers belong to, and shares a link that lands on them**: The solver at /play/solver reprices the whole /play world when you move the skill level, and it fetches the new level as you move. If that fetch failed, the page dimmed its tables slightly and said nothing else: the chart marker sat at level 60 while every table below it still held level 1 figures, with no visible explanation, no way to tell which level you were reading, and no retry. The explanation existed but was written only into a region screen readers can reach, so anyone looking at the page saw a silent mismatch. A failed level now raises a banner in the open that names the level that failed, says plainly that the figures below are still the old level, and offers both a retry and a way back. A level still loading shows the same banner as a busy state with the level it is solving, so a slow connection reads as slow rather than as broken. The page also writes the level into its own address bar now: it has always read a level from a shared link, but never wrote one, so sending someone the URL after dragging to level 60 sent them level 1. And a link asking for a level past the cap settles on the cap instead of leaving the page waiting on a level that will never arrive. Alongside it, a conclusion in the model that shouted one word in capitals now reads as a normal sentence. (`/play/solver`) `[fix, improvement]`
+- **The floorplan editor can make rooms, so a home with no areas is no longer a dead end**: Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list. (`/smart-home`) `[feature, improvement]`
- **The homepage stops calling its Community strip live when no new models are arriving**: The Community strip on the homepage is headed "Made with Forge. Right now." and carries a pulsing live chip. That chip was switched on by the Fresh tab alone, so it asserted liveness no matter how old the newest model on the strip actually was. When our object storage started rejecting the platform's credential on 2026-09-07, finished generations could no longer be recorded, the strip froze on the last model stored before that, and the chip went on pulsing live over two-day-old work with nothing on the page to say otherwise. The chip is now earned by the data: it appears only when the newest model on the strip is from the last six hours, and it reads the newest timestamp in the list rather than trusting the order it arrives in. Older models still show exactly as before, because a quiet stretch is worth showing; it just is not live. (`/`) `[fix]`
- **The in-game economy page reads correctly on a phone, and the boutique shows what you are buying**: A full audit of /play/economy, the published reference for every price, prize and gate in the /play world. On a 320px screen the general store and currency panels were wider than the viewport, and because the page suppresses sideways scrolling their right edge was simply cut off: the store's price column was unreachable on the narrowest phones. Those panels now shrink to fit, and the wide tables scroll inside their own labelled box instead. The bar showing how a paid $THREE sale splits used to print its labels inside the coloured segments, where "50% holder rewards" was truncated to "50% holder re..."; the split now reads from a legend beneath the bar, which stays legible at any ratio. In the boutique, the Stetson and the Shades rendered as blank grey circles while the five colour items showed their colour, because the page ignored the thumbnail the server was already sending; both now show the item, with the colour swatch as the fallback if an image ever goes missing. The wheel's top prize is relabelled "JACKPOT: 100 Cash", and a failed load now reads as a proper sentence before the retry hint. (`/play/economy`) `[fix, improvement]`
- **The Money Pulse now tells you when its stats are down, and retries on the spot**: When the money-intelligence call behind /pulse failed, the three side panels (Top earners, Busiest wallets, Fresh launches) sat on "Loading..." forever and the 7-day activity strip went blank, which reads as "the platform is quiet" rather than "we could not fetch this". Each surface now says what went wrong, notes that the live feed itself is unaffected and that it retries every minute, and offers a Retry button that refetches immediately. First paint uses skeletons shaped like the real counters, bars and rows instead of dashes and a loading label, so nothing shifts when the numbers land. The empty states point somewhere useful now: no tips yet links to the agent directory, no wallet activity links to the agents that are online. Switching between mainnet and devnet shows the skeletons again rather than leaving the previous network's numbers under the new label. The stat cards report their filter state to screen readers, the rail cards are real headings, and the per-row explorer link is a full-size tap target that says where it goes. (`/pulse`) `[fix, improvement]`
@@ -45,6 +46,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The sniper scoreboard now links out to the pages that explain what it is showing you**: A full audit of /sniper/experiments, the live board comparing rule-driven sniper agents against LLM-judged ones on the same market. The board is dense with terms it could only gloss in a hover tooltip: earned autonomy tiers, moon bags, the reasoning ledger behind every verdict, the exit ladder. A reader who wanted the real explanation had nowhere to go. The page now ends with a row of links to the seven surfaces that write each of those up, from the live Sniper Arena floor to the earned-autonomy docs and the page where you arm your own agent. Four smaller fixes came with it. The Best arm tile printed its profit in plain white even when that number was a loss, so a losing leader read as a win at a glance; it is now coloured like every other figure on the board. An arm or a judge with no model recorded against it used to crash the whole render; it now reads as unattributed and the rest of the board keeps working. Both tables label their column headers properly, so a screen reader can pair a figure with the column it belongs to across nine columns. And the time-window buttons are declared as buttons rather than defaulting to form submits. (`/sniper/experiments`) `[improvement, fix]`
- **The spend policy dry run stops contradicting its own counters**: The simulator at /pay/simulator reports what an agent budget actually buys, and its headline sentence disagreed with the numbers directly beneath it. An endpoint that answers without asking for payment is free: it costs nothing and is never checked against your policy. The counters knew that, and the sentence did not, so the very first run on the page announced that all seven calls settle while the tile beside it said six. Calls that could not be priced at all vanished the same way, counted nowhere the reader could see. Both now have their own tile, and the verdict sentence is built from the counts it is describing, so settled, free, unpriced and refused always add up to the total in front of you. A run that fails now says why: an unusable line used to produce a bare "Simulation failed (HTTP 400)", and now quotes the endpoint the simulator could not read along with what a working line looks like. A budget left blank was quietly costed against one dollar, giving you a verdict for a budget you never proposed; the answer now says when that substitution happened. On a phone the little question marks beside each field were fifteen pixels wide and their explanations opened off the side of the screen, so the help was unreadable exactly where it was needed most: the tap targets are now large enough to hit and the explanations stay on the page at every width. (`/pay/simulator`) `[fix, improvement]`
- **The Splat Viewer keeps its recenter and download controls, and its errors say what went wrong**: Loading a scene on /splat used to erase the viewer's own controls: writing the scene label into the HUD replaced the recenter and download buttons with plain text, so from the first render onward neither existed. Both now live beside the label and survive every scene swap, and the download always offers the scene you are actually looking at rather than a previous one. The error state was worse than useless: it showed a heading over an empty space because the explanation was being written into an element that was not on the page. Now a failed load tells you what happened and what to do, including the advice to download and upload a file whose host blocks cross-origin requests. Clicking a sample or picking a file also shows the loading state immediately instead of sitting on an idle stage while the splat engine downloads in silence, and an engine that fails to load says so rather than leaving the page frozen. (`/splat`) `[fix, improvement]`
+- **The Windows 11 widget draws its card again, and a new check keeps the board honest**: The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real. (`/glance`) `[fix, infra]`
+- **When the payment wallets look empty, the self-heal now says whether they are empty or just fenced**: The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: "at or below floor". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required. `[fix, infra]`
+- **Your monthly agent turns now count, and locking up never does**: Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused. (`/smart-home/plan`) `[feature, improvement]`
- **Your private avatars load on the dashboard again, and say so when they cannot**: Avatars you have not made public were failing to load on your dashboard, with nothing on the page to say why. The dashboard was being handed a temporary direct link into our storage provider rather than a link back through three.ws. When storage stopped accepting our credential, that direct link was refused in a way browsers deliberately hide, so the page could not tell the difference between a refusal and a dead connection: it just showed nothing. Private avatars now load through three.ws itself, which checks that the avatar is yours exactly as before, and which already knows how to fall back to a second copy when storage is having a bad day. As a side effect these links no longer expire, so a dashboard tab left open for an hour still shows your avatars when you come back to it. (`/dashboard/avatars`) `[fix]`
## 2026-09-08
diff --git a/data/changelog.json b/data/changelog.json
index 7f3421548..0d8658e5d 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,45 @@
{
"$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-09",
+ "title": "Your monthly agent turns now count, and locking up never does",
+ "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.",
+ "tags": [
+ "feature",
+ "improvement"
+ ],
+ "link": "/smart-home/plan"
+ },
+ {
+ "date": "2026-09-09",
+ "title": "The Windows 11 widget draws its card again, and a new check keeps the board honest",
+ "summary": "The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.",
+ "tags": [
+ "fix",
+ "infra"
+ ],
+ "link": "/glance"
+ },
+ {
+ "date": "2026-09-09",
+ "title": "The floorplan editor can make rooms, so a home with no areas is no longer a dead end",
+ "summary": "Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list.",
+ "tags": [
+ "feature",
+ "improvement"
+ ],
+ "link": "/smart-home"
+ },
+ {
+ "date": "2026-09-09",
+ "title": "When the payment wallets look empty, the self-heal now says whether they are empty or just fenced",
+ "summary": "The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: \"at or below floor\". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required.",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-09",
"title": "The homepage stops calling its Community strip live when no new models are arriving",
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 7b3e66aad..a47cea02f 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-09-09T05:31:23.183Z",
+ "generated_at": "2026-09-09T05:43:06.259Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3617,
+ "total": 3621,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -240,6 +240,17 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The floorplan editor can make rooms, so a home with no areas is no longer a dead end",
+ "summary": "Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list.",
+ "link": "/smart-home",
+ "tags": [
+ "feature",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
@@ -437,6 +448,39 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The Windows 11 widget draws its card again, and a new check keeps the board honest",
+ "summary": "The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.",
+ "link": "/glance",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "When the payment wallets look empty, the self-heal now says whether they are empty or just fenced",
+ "summary": "The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: \"at or below floor\". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required.",
+ "link": null,
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "Your monthly agent turns now count, and locking up never does",
+ "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.",
+ "link": "/smart-home/plan",
+ "tags": [
+ "feature",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
@@ -1575,50 +1619,6 @@
"tags": [
"fix"
]
- },
- {
- "date": "2026-09-04",
- "type": "update",
- "title": "The IRL placements desk can use your location again, and only when you ask it to",
- "summary": "The page that pins your agents to real places offers to measure how far away each pin is and to drop a new one where you are standing. None of it could work: the page arrived with the browser location service switched off for it, so every attempt failed on the spot. Location is allowed on that page now. It also no longer reaches for your position the second the page opens: it reads it only when you have already granted permission, and otherwise waits for you to press one of the location buttons.",
- "link": null,
- "tags": [
- "fix",
- "improvement"
- ]
- },
- {
- "date": "2026-09-04",
- "type": "update",
- "title": "The one-line x402 script now works on your site, not just on ours",
- "summary": "Our docs tell you to make any element payable by dropping one line onto your page: a script tag pointing at three.ws/x402.js. On your own domain that line never worked. Your browser asked us whether another site was allowed to read the file and we never answered, so the script was refused and the button stayed inert. The same silence broke the runtime translation script and the language catalogs it reads, and it broke the IBM partnership page that IBM hosts on its own domain: that page keeps itself current by pulling the latest copy from us, and instead had quietly frozen on the version baked in the day it was published. All of it answers any site that asks now. The live copy also carries its own script and translation addresses with it, instead of asking your server for files only we have, and a new check loads that page from a stranger's domain so none of this can go unnoticed again.",
- "link": "/docs/x402-studio",
- "tags": [
- "fix",
- "sdk",
- "infra"
- ]
- },
- {
- "date": "2026-09-04",
- "type": "update",
- "title": "The Smart Money directory stops asking your browser for pictures it can never get",
- "summary": "Every wallet in the copy-trading Smart Money list carried a portrait link pointing at an outside image host that serves nobody but its own site. Browsers blocked all of them, so the list drew the trader initials it was designed to fall back on while quietly recording a failed request for each row on screen. That unusable link is no longer sent, so the directory looks exactly as it did with none of the wasted traffic behind it.",
- "link": null,
- "tags": [
- "fix",
- "improvement"
- ]
- },
- {
- "date": "2026-09-04",
- "type": "update",
- "title": "The Windows 11 widget now actually paints your agent on the widgets board",
- "summary": "Windows renders the Agent glance widget from a card layout the site has to hand it, and we were handing it the address of that layout instead of the layout itself, so a pinned widget had nothing to draw. The worker now fetches the card, keeps a copy so a machine that wakes up offline still renders, re-paints slots that were pinned before it took over, and registers the 15 minute refresh the widget advertises, which was never actually being scheduled. Pin it with Win + W, Add widgets, Agent glance.",
- "link": "/glance",
- "tags": [
- "fix"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index ac5a8eaa8..6f26b1048 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-09T05:31:23.137Z",
+ "generated_at": "2026-09-09T05:43:06.212Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -237,6 +237,17 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The floorplan editor can make rooms, so a home with no areas is no longer a dead end",
+ "summary": "Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list.",
+ "link": "/smart-home",
+ "tags": [
+ "feature",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
@@ -434,6 +445,39 @@
"improvement"
]
},
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "The Windows 11 widget draws its card again, and a new check keeps the board honest",
+ "summary": "The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.",
+ "link": "/glance",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "When the payment wallets look empty, the self-heal now says whether they are empty or just fenced",
+ "summary": "The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: \"at or below floor\". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required.",
+ "link": null,
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-09-09",
+ "type": "update",
+ "title": "Your monthly agent turns now count, and locking up never does",
+ "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.",
+ "link": "/smart-home/plan",
+ "tags": [
+ "feature",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-09",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index edf470948..9e28e2779 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -174,6 +174,14 @@
<category>fix</category>
<description>The solver at /play/solver reprices the whole /play world when you move the skill level, and it fetches the new level as you move. If that fetch failed, the page dimmed its tables slightly and said nothing else: the chart marker sat at level 60 while every table below it still held level 1 figures, with no visible explanation, no way to tell which level you were reading, and no retry. The explanation existed but was written only into a region screen readers can reach, so anyone looking at the page saw a silent mismatch. A failed level now raises a banner in the open that names the level that failed, says plainly that the figures below are still the old level, and offers both a retry and a way back. A level still loading shows the same banner as a busy state with the level it is solving, so a slow connection reads as slow rather than as broken. The page also writes the level into its own address bar now: it has always read a level from a shared link, but never wrote one, so sending someone the URL after dragging to level 60 sent them level 1. And a link asking for a level past the cap settles on the cap instead of leaving the page waiting on a level that will never arrive. Alongside it, a conclusion in the model that shouted one word in capitals now reads as a normal sentence.</description>
</item>
+ <item>
+ <title>The floorplan editor can make rooms, so a home with no areas is no longer a dead end</title>
+ <link>https://three.ws/smart-home</link>
+ <guid isPermaLink="false">2026-09-09:The floorplan editor can make rooms, so a home with no areas is no longer a dead end</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list.</description>
+ </item>
<item>
<title>The homepage stops calling its Community strip live when no new models are arriving</title>
<link>https://three.ws/</link>
@@ -318,6 +326,30 @@
<category>fix</category>
<description>Loading a scene on /splat used to erase the viewer's own controls: writing the scene label into the HUD replaced the recenter and download buttons with plain text, so from the first render onward neither existed. Both now live beside the label and survive every scene swap, and the download always offers the scene you are actually looking at rather than a previous one. The error state was worse than useless: it showed a heading over an empty space because the explanation was being written into an element that was not on the page. Now a failed load tells you what happened and what to do, including the advice to download and upload a file whose host blocks cross-origin requests. Clicking a sample or picking a file also shows the loading state immediately instead of sitting on an idle stage while the splat engine downloads in silence, and an engine that fails to load says so rather than leaving the page frozen.</description>
</item>
+ <item>
+ <title>The Windows 11 widget draws its card again, and a new check keeps the board honest</title>
+ <link>https://three.ws/glance</link>
+ <guid isPermaLink="false">2026-09-09:The Windows 11 widget draws its card again, and a new check keeps the board honest</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.</description>
+ </item>
+ <item>
+ <title>When the payment wallets look empty, the self-heal now says whether they are empty or just fenced</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-09-09:When the payment wallets look empty, the self-heal now says whether they are empty or just fenced</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: &quot;at or below floor&quot;. That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required.</description>
+ </item>
+ <item>
+ <title>Your monthly agent turns now count, and locking up never does</title>
+ <link>https://three.ws/smart-home/plan</link>
+ <guid isPermaLink="false">2026-09-09:Your monthly agent turns now count, and locking up never does</guid>
+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.</description>
+ </item>
<item>
<title>Your private avatars load on the dashboard again, and say so when they cannot</title>
<link>https://three.ws/dashboard/avatars</link>
diff --git a/public/features.json b/public/features.json
index 12bede223..ffec9c742 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-09T05:31:23.108Z",
+ "generated_at": "2026-09-09T05:43:06.184Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",