Sync the self-hosting stack

2026-08-25 22:48:42 +02:00
parent 0052e19ba8
commit fa19933a32
1 changed files with 18 additions and 0 deletions
@@ -9,6 +9,24 @@ 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-08-25 — A run gets 200 tool rounds instead of 50 `api 0.92.0`
 **If the assistant has been stopping mid-investigation with "the results above were not analysed",
 this is why.** A run that reads a config, checks a service, greps a log and correlates two hosts
 spends its budget on legitimate steps and then hits a ceiling meant for runaway loops. Asking it to
 continue re-sends the whole conversation and pays for the same work twice, which is the expensive
 outcome the ceiling was supposed to prevent.
 The ceiling exists to stop a model that has stopped making progress, and at that job 200 is as good
 as 50 — a loop that is genuinely stuck is stuck within a few rounds. Nothing else about how a run is
 governed changes: you still watch it, the autonomy level still gates every write, and anything
 consequential still asks for approval.
 **One thing to expect on very long runs.** With more rounds available, the likelier ending is now
 the model's context window rather than the round limit. That has always been reported plainly —
 "this conversation has outgrown the model's context window" — and a run that reaches it should be
 started again as a fresh conversation rather than continued.
 ## 2026-08-25 — The terminal button is on the row `web 0.119.0`
 The terminal added in the entry below was in the row's overflow menu, behind Test, Connections and