assistant: load the chat's model on open, docs for cloud models

The canvas asks for its chat's model, else the preferred one, when it
opens and when the pick changes; a cloud id loads nothing. The paperclip
also closes the model panel, so it and the picker never stack. The plan's
Models.qml import is corrected to the one that resolves.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 files changed, 14 insertions, 6 deletions

diff --git a/desktop/modules/assistant/README.md b/desktop/modules/assistant/README.md
index 3c35dc6..9ee9736 100644
--- a/desktop/modules/assistant/README.md
+++ b/desktop/modules/assistant/README.md
@@ -15,6 +15,14 @@ The system prompt also has "Use the default". The tool environment
 saved, renames `tools/<name>.toml`
 to `<name>.toml.off`, which the daemon's `*.toml` glob skips.
 
+**Cloud** edits the daemon's `[[cloud]]` tables: name, URL and key
+command per provider. Fetch saves the page, then runs `assistant.py
+--cloud-models <name>`, which runs the key command and lists the
+provider's ids; the switches choose which the canvas offers. The key
+never reaches this page. A table holding more than the page writes (a
+multi-line array, another key) is left alone, with a note to edit it by
+hand. The saved cloud models also get Prefer in the Model list.
+
 The page also lists llama-server's models with their state. The daemon
 always answers with whichever model is loaded and never asks for one, so
 it never swaps a model out from under another client. Load is the
@@ -24,12 +32,12 @@ Prefer is the other, separate choice: the model the assistant should use,
 saved in `Prefs`. A first version made Load also set the preference, so a
 model loaded for another client became the assistant's too.
 
-Opening the assistant canvas (SUPER+Home) loads the preferred model when
-another one is resident, and the canvas header reads "loading <model>…"
-until it is in. This desktop runs one model and one client at a time, so
-opening the assistant is when its model should come back; the daemon still
-never asks for a model itself. With no preferred model set, nothing is
-swapped.
+Each chat uses the model picked in the canvas's model menu, else the
+preferred one, else whatever is loaded. Opening the canvas, or picking a
+local model for its chat, loads that model when another one is resident,
+and the canvas header reads "loading <model>…" until it is in. This
+desktop runs one model and one client at a time, so that is when the
+model should come back. A cloud model loads nothing.
 
 The daemon reads all of this only at startup, so after a change the page
 says so and offers Restart, which runs `assistant.sh restart`; a daemon that