diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 977d627bd..ee98db6d5 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "5a9c0efa548b39a66e60bb22f003421ffc17ea86",
-  "syncedAt": "2026-04-29T03:36:26.271Z"
+  "sha": "04f6ffd8beddf581e933dcd51f2d2d88439dd334",
+  "syncedAt": "2026-04-29T03:39:01.837Z"
 }
diff --git a/docs/providers/ollama.md b/docs/providers/ollama.md
index 321bdd53e..417bd99c2 100644
--- a/docs/providers/ollama.md
+++ b/docs/providers/ollama.md
@@ -192,6 +192,12 @@ When you set `OLLAMA_API_KEY` (or an auth profile) and **do not** define `models
 
 This avoids manual model entries while keeping the catalog aligned with the local Ollama instance. You can use a full ref such as `ollama/<pulled-model>:latest` in local `infer model run`; OpenClaw resolves that installed model from Ollama's live catalog without requiring a hand-written `models.json` entry.
 
+For signed-in Ollama hosts, some `:cloud` models may be usable through `/api/chat`
+and `/api/show` before they appear in `/api/tags`. When you explicitly select a
+full `ollama/<model>:cloud` ref, OpenClaw validates that exact missing model with
+`/api/show` and adds it to the runtime catalog only if Ollama confirms model
+metadata. Typos still fail as unknown models instead of being auto-created.
+
 ```bash
 # See what models are available
 ollama list