Sync the self-hosting stack

This commit is contained in:
2026-10-22 15:05:53 +02:00
parent d50eea2038
commit 1d01a6bbe7
+16
View File
@@ -9,6 +9,22 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
cannot be published without its entry.
## 2026-10-22 — The assistant sees every asset of a large scope `api 2.1.2`
**A conversation scoped to more than 60 assets no longer loses the rest.** The assistant was given the
names of 60 of them and could call any other out of scope, so a question about the 61st machine of a
large fleet got a refusal.
- **The assistant has a `find_assets` tool** whenever the scope is larger than that. It pages through
every asset by name, counts them by type, folder and reachability — which machines' agents are
online or offline — and searches them by name, type, folder or reachability. Every asset it finds
can be operated with the usual tools; only one it cannot find is out of scope.
- **Requests stay small however large the scope.** The tool definitions no longer repeat every asset
id; the api still checks each call against the conversation's scope, as before.
Conversations of 60 assets or fewer are unchanged. Update the API image. No web or agent update is
required.
## 2026-10-22 — A large fleet no longer slows the console down `api 2.1.1` `web 2.1.4`
**With hundreds of machines enrolled, the console stays responsive.** Every machine reports its