From cd7d807a4f218fbbd87097706e5c1a49fad8d94a Mon Sep 17 00:00:00 2001 From: Luxit Date: Sat, 29 Aug 2026 23:47:15 +0200 Subject: [PATCH] Sync the self-hosting stack --- CHANGELOG.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index dcefbf9..0d8bda6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,57 @@ 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-29 — Keep several conversations on the go, and switch between them `api 0.100.0` `web 0.122.0` + +Opening a conversation used to mean being *in* it: to reach another you left it, found the one you +wanted in the list, and went in. That is a poor deal when Jarvis runs unattended for twenty minutes +against a real machine — the thing you most need to know is that a plan is blocked in a thread you +are not looking at. + +**The console now keeps a working set.** The conversations you are actually in appear in the sidebar, +under the main navigation, alongside anything of yours that is running or waiting on a decision. It +costs no width — the transcript is exactly as wide as it was — and it shows nothing at all until you +have opened something. On a phone the same list is one tap away from the top bar and from the +navigation drawer. + +**A blocked plan is decidable without opening it.** The row carries the plan's own title, its +summary, its risk, the machines it names and how long it has been waiting. Choosing it lands you on +the transcript with the approval already open, rather than on a transcript with the decision hidden +behind a panel. + +**Switching is two keystrokes.** `Ctrl+K` (or `Cmd+K`) now opens with your recent conversations +first and the previous one already selected, so `Ctrl+K` then `Enter` goes back to it. `Ctrl+\` +toggles between the last two. You can pin up to five conversations so they stay in place. + +**Your browser tab is finally named after what is in it** — the conversation and the client, rather +than "Jarvis" on every tab. If you keep two tabs open on two clients, this is the change you will +notice first. + +### Two things that were wrong, and are fixed here + +**Activity was announced to everyone in the organization.** The "Jarvis is working" marks in the +conversation list were broadcast to every member of an organization, for every conversation in it — +including private conversations they take no part in and cannot open. Nothing in the interface ever +displayed them, but the identifiers, the live state and the *name of the colleague running the +thread* were delivered to browsers that had no business receiving any of it. They now go only to the +people who take part in the conversation, and organization membership is re-checked at the moment of +sending rather than trusted to a stale row. **Take both images to close this**; the api is the half +that matters. + +**A half-typed prompt could follow you into another conversation.** Leaving a conversation +mid-sentence did not discard the text — it carried it into whichever conversation you opened next, +in a box that looked empty. Where one operator works across several clients, that is a command +written for one machine sitting one keypress away from being sent to another. Drafts are now kept +per conversation, survive a reload, and are cleared when the message is sent. + +Two smaller ones alongside them. **Deleting a conversation now takes anybody reading it off the +screen** and says why, instead of leaving them on a transcript whose every control has quietly +stopped working. And **signing out now clears what the console left on the machine** — the +notification history, which conversations had been read, and any unsent drafts. Your theme, language +and sidebar preference are deliberately kept: a preference is not a secret. + +**Nothing to do.** Take both builds. No new settings, no schema change. + ## 2026-08-29 — The conversation list shows what is running, wherever it is running `api 0.99.0` **Only affects deployments running more than one copy of the api.**