diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 557b2517c..bac2682fe 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
- "sha": "0da17e4f7472da4f6421b52dcb773c61d54f075c",
- "syncedAt": "2026-04-23T16:45:54.985Z"
+ "sha": "b3ca4e088ee2fcf3ccdadd0bf5bcb6e3d9dea668",
+ "syncedAt": "2026-04-23T16:49:45.129Z"
}
diff --git a/docs/providers/openai.md b/docs/providers/openai.md
index c4efcfb63..4e9d95d2c 100644
--- a/docs/providers/openai.md
+++ b/docs/providers/openai.md
@@ -502,23 +502,14 @@ Azure portal.
Azure OpenAI uses native transport and compat behavior but does not receive
-OpenClaw's hidden attribution headers. See the **Native vs OpenAI-compatible
-routes** accordion under [Advanced configuration](#advanced-configuration)
-for details.
-
+OpenClaw's hidden attribution headers — see the **Native vs OpenAI-compatible
+routes** accordion under [Advanced configuration](#advanced-configuration).
-
-For a separate Azure OpenAI Responses provider (distinct from the `openai`
-provider), see the `azure-openai-responses/*` model refs in the
-[Server-side compaction](#server-side-compaction-responses-api) accordion.
-
-
-
-Azure chat and Responses traffic need Azure-specific provider/API config in
-addition to a base URL override. If you want Azure model calls beyond image
-generation, use the onboarding flow or a provider config that sets the
-appropriate Azure API/auth shape rather than assuming `openai.baseUrl` alone
-is enough.
+For chat or Responses traffic on Azure (beyond image generation), use the
+onboarding flow or a dedicated Azure provider config — `openai.baseUrl` alone
+does not pick up the Azure API/auth shape. A separate
+`azure-openai-responses/*` provider exists; see
+[Server-side compaction](#server-side-compaction-responses-api).
## Advanced configuration
@@ -579,8 +570,6 @@ is enough.
-
-
OpenClaw exposes a shared fast-mode toggle for both `openai/*` and `openai-codex/*`: