docs: cloud models, example provider and cloud tools

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

1 files changed, 10 insertions, 2 deletions

diff --git a/AGENTS.md b/AGENTS.md
index 8d2a91b..0044921 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -3,7 +3,8 @@
 A local text assistant daemon: questions in and streamed replies out on a
 Unix socket, answered by the model already loaded in llama-server, with
 read-only tools and a SQLite history. Nothing leaves the machine except
-what an enabled tool fetches.
+what an enabled tool fetches, and a
+chat the user switched to a cloud model (2026-10-23).
 
 Status (2026-10-16): **text daemon**. The front end is the quickshell
 canvas (`desktop/assistant/` in the quickshell repo, SUPER+Home). Voice
@@ -27,6 +28,11 @@ Tools (2026-09-26): read-only shell-command TOML files in
 built-in settings. Examples in `examples/`. Spec:
 `docs/superpowers/specs/2026-09-26-tools-and-config-design.md`.
 
+Cloud models (2026-10-23): `[[cloud]]` providers in `config.toml`, keys
+from `key_cmd`, ids `provider:model`, chosen per chat and stored on the
+conversation. Only tools with `cloud = true` go to a cloud chat. Spec:
+`docs/superpowers/specs/2026-10-23-cloud-models-design.md`.
+
 Run: `python3 assistant.py` (`--test` for the self-check), or
 `./assistant.sh restart` to replace a running one detached from the
 terminal.
@@ -859,4 +865,6 @@ kokoro-onnx GitHub release `model-files-v1.0`.
 - Ask before acting when anything is ambiguous, and before committing.
 - Package changes belong in `my-slackbuilds`, not here.
 - Never download models or voices without saying which and how big.
-- Everything stays local: no cloud STT/TTS/LLM fallbacks.
+- No silent cloud fallback, ever. A cloud model is used only when the user
+  picks it for a chat; tools reach a cloud chat only with `cloud = true`;
+  audio is always transcribed locally; no cloud STT/TTS.