docs: fix active memory gateway command

.agents/skills/openclaw-parallels-smoke/SKILL.md

@@ -29,13 +29,7 @@ Use this skill for Parallels guest workflows and smoke interpretation. Do not lo
 ## npm install then update
 
 - Preferred entrypoint: `pnpm test:parallels:npm-update`
-- Required coverage: every release/update regression run must include both lanes:
-  - fresh snapshot -> install requested package/baseline -> smoke
-  - same guest baseline -> run the guest's installed `openclaw update ...` command -> smoke again
-- The update lane must exercise OpenClaw's internal updater. Do not count a direct `npm install -g <tgz-or-spec>` or harness-side package swap as update-flow coverage; those are install smokes only.
-- For published targets, install the old baseline package first (for example `openclaw@2026.4.9`), then run the installed guest CLI with the intended channel/tag (for example `openclaw update --channel beta --yes --json`) and verify `openclaw --version`, `openclaw update status --json`, gateway RPC, and an agent turn after the command.
-- For unpublished targets, pack the candidate on the host, serve the `.tgz` over the harness HTTP server, and point the guest updater at that served package. Prefer `openclaw update --tag http://<host-ip>:<port>/openclaw-<version>.tgz --yes --json`; when channel persistence also matters, pass `--channel <stable|beta>` and set `OPENCLAW_UPDATE_PACKAGE_SPEC` to the same served URL in the guest update environment. The command under test must still be `openclaw update`, not direct npm.
-- For unpublished local-fix validation, remember the old baseline updater code still controls the first hop. A fix that lives only in the new updater code cannot change that already-running old process; the served candidate must either keep package/plugin metadata compatible with the baseline host or the baseline itself must include the updater fix.
+- Flow: fresh snapshot -> install npm package baseline -> smoke -> install current main tgz on the same guest -> smoke again.
 - For beta/stable verification, resolve the tag immediately before the run (`npm view openclaw@beta version dist.tarball` or `npm view openclaw@latest ...`). Tags can move while a long VM matrix is already running; restart the matrix when the intended prerelease appears after an earlier registry 404/tag-lag check.
 - Source Peter's profile in the host shell (`set -a; source "$HOME/.profile"; set +a`) before OpenAI/Anthropic lanes. Do not print profile contents or env dumps; pass provider secrets through the guest exec environment.
 - Same-guest update verification should set the default model explicitly to `openai/gpt-5.4` before the agent turn and use a fresh explicit `--session-id` so old session model state does not leak into the check.

.github/workflows/ci.yml

@@ -694,7 +694,7 @@ jobs:
           EOF
 
   checks-node-core-test:
-    name: checks-node-core
+    name: checks-node-core-test
     needs: [preflight, checks-node-core-test-shard]
     if: always() && needs.preflight.outputs.run_checks == 'true'
     runs-on: blacksmith-16vcpu-ubuntu-2404
@@ -894,11 +894,6 @@ jobs:
         continue-on-error: true
         run: pnpm check:import-cycles
 
-      - name: Run madge import cycle guard
-        id: madge_import_cycles
-        continue-on-error: true
-        run: pnpm check:madge-import-cycles
-
       - name: Upload gateway watch regression artifacts
         if: always()
         uses: actions/upload-artifact@v7
@@ -932,7 +927,6 @@ jobs:
           CONTROL_UI_I18N_OUTCOME: ${{ steps.control_ui_i18n.outcome == 'skipped' && 'success' || steps.control_ui_i18n.outcome }}
           GATEWAY_WATCH_REGRESSION_OUTCOME: ${{ steps.gateway_watch_regression.outcome }}
           IMPORT_CYCLES_OUTCOME: ${{ steps.import_cycles.outcome }}
-          MADGE_IMPORT_CYCLES_OUTCOME: ${{ steps.madge_import_cycles.outcome }}
         run: |
           failures=0
           for result in \
@@ -957,8 +951,7 @@ jobs:
             "lint:ui:no-raw-window-open|$NO_RAW_WINDOW_OPEN_OUTCOME" \
             "ui:i18n:check|$CONTROL_UI_I18N_OUTCOME" \
             "gateway-watch-regression|$GATEWAY_WATCH_REGRESSION_OUTCOME" \
-            "check:import-cycles|$IMPORT_CYCLES_OUTCOME" \
-            "check:madge-import-cycles|$MADGE_IMPORT_CYCLES_OUTCOME"; do
+            "check:import-cycles|$IMPORT_CYCLES_OUTCOME"; do
             name="${result%%|*}"
             outcome="${result#*|}"
             if [ "$outcome" != "success" ]; then

.github/workflows/install-smoke.yml

@@ -194,13 +194,6 @@ jobs:
           push: false
           provenance: false
 
-      - name: Setup Node environment for local pack smoke
-        uses: ./.github/actions/setup-node-env
-        with:
-          install-bun: "false"
-          install-deps: "true"
-          use-sticky-disk: "false"
-
       - name: Run installer docker tests
         env:
           OPENCLAW_INSTALL_URL: https://openclaw.ai/install.sh

.github/workflows/openclaw-npm-release.yml

@@ -493,7 +493,6 @@ jobs:
           RELEASE_VERSION: ${{ env.RELEASE_VERSION }}
         run: |
           set -euo pipefail
-          printf '//registry.npmjs.org/:_authToken=%s\n' "${NODE_AUTH_TOKEN}" > "${HOME}/.npmrc"
           npm whoami >/dev/null
           npm dist-tag add "openclaw@${RELEASE_VERSION}" latest
           promoted_latest="$(npm view openclaw dist-tags.latest)"

.oxfmtrc.jsonc

@@ -20,7 +20,6 @@
     "pnpm-lock.yaml/",
     "src/gateway/server-methods/CLAUDE.md",
     "src/auto-reply/reply/export-html/",
-    "src/canvas-host/a2ui/a2ui.bundle.js",
     "Swabble/",
     "vendor/",
   ],

.vscode/settings.json

@@ -17,5 +17,6 @@
   "typescript.preferences.importModuleSpecifierEnding": "js",
   "typescript.reportStyleChecksAsWarnings": false,
   "typescript.updateImportsOnFileMove.enabled": "always",
-  "typescript.tsdk": "node_modules/typescript/lib"
+  "typescript.tsdk": "node_modules/typescript/lib",
+  "typescript.experimental.useTsgo": true
 }

AGENTS.md

@@ -30,16 +30,11 @@
   - `src/plugins/*` = plugin discovery, manifest validation, loader, registry, and contract enforcement
   - `src/gateway/protocol/*` = typed Gateway control-plane and node wire protocol
 - Progressive disclosure lives in local boundary guides:
-  - repo root `AGENTS.md`
-  - bundled-plugin-tree `extensions/AGENTS.md`
+  - bundled-plugin-tree `AGENTS.md`
   - `src/plugin-sdk/AGENTS.md`
   - `src/channels/AGENTS.md`
   - `src/plugins/AGENTS.md`
   - `src/gateway/protocol/AGENTS.md`
-- Workflow hygiene:
-  - Do not grep or existence-check every `docs/*.md`, `AGENTS.md`, or guide path mentioned in this file before starting work.
-  - Read only the guides and docs that are directly relevant to the files or boundary you are touching.
-  - Only do full broken-link or missing-guide sweeps when the task is explicitly about docs or repo-instruction maintenance.
 - Plugin and extension boundary:
   - Public docs: `docs/plugins/building-plugins.md`, `docs/plugins/architecture.md`, `docs/plugins/sdk-overview.md`, `docs/plugins/sdk-entrypoints.md`, `docs/plugins/sdk-runtime.md`, `docs/plugins/manifest.md`, `docs/plugins/sdk-channel-plugins.md`, `docs/plugins/sdk-provider-plugins.md`
   - Definition files: `src/plugin-sdk/plugin-entry.ts`, `src/plugin-sdk/core.ts`, `src/plugin-sdk/provider-entry.ts`, `src/plugin-sdk/channel-contract.ts`, `scripts/lib/plugin-sdk-entrypoints.json`, `package.json`
@@ -73,7 +68,7 @@
   - `hooks.internal.entries` is the canonical public hook config model. `hooks.internal.handlers` is compatibility-only input and must not be re-exposed in public schema/help/baseline surfaces.
 - Bundled plugin contract boundary:
   - Public docs: `docs/plugins/architecture.md`, `docs/plugins/manifest.md`, `docs/plugins/sdk-overview.md`
-  - Definition files: `src/plugins/contracts/registry.ts`, `src/plugins/types.ts`, `src/plugins/public-artifacts.ts`
+- Definition files: `src/plugins/contracts/registry.ts`, `src/plugins/types.ts`, `src/plugins/public-artifacts.ts`
   - Rule: keep manifest metadata, runtime registration, public SDK exports, and contract tests aligned. Do not create a hidden path around the declared plugin interfaces.
 - Extension test boundary:
   - Keep extension-owned onboarding/config/provider coverage under the owning bundled plugin package when feasible.
@@ -81,25 +76,37 @@
   - Shared helpers under `test/helpers/**` are part of that same boundary. Do not hardcode repo-relative `extensions/**` imports there, and do not keep plugin-local deep mocks in shared helpers just because multiple tests use them.
   - When core tests or shared helpers need bundled plugin public surfaces, use `src/test-utils/bundled-plugin-public-surface.ts` for `api.ts`, `runtime-api.ts`, `contract-api.ts`, `test-api.ts`, plugin entrypoint `index.js`, and resolved module ids for dynamic import or mocking.
   - If a core test is asserting extension-specific behavior instead of a generic contract, move it to the owning extension package.
-- Scoped guides still matter:
-  - `extensions/AGENTS.md` expands extension/plugin boundary rules.
-  - `src/channels/AGENTS.md` expands core channel boundary and hot-path rules.
-  - `src/plugin-sdk/AGENTS.md` expands public SDK contract rules.
-  - `src/plugins/AGENTS.md` expands plugin loading, registry, and manifest rules.
-  - `src/gateway/protocol/AGENTS.md` expands typed Gateway protocol rules.
-  - `test/helpers/AGENTS.md` and `test/helpers/channels/AGENTS.md` expand shared test helper boundary rules.
-- Plugin architecture direction:
-  - Keep a manifest-first control plane: discovery, validation, enablement, setup hints, and activation planning should stay metadata-driven by default.
-  - Keep runtime execution separate: actual provider/channel/tool execution should resolve through narrow targeted loaders, not broad registry materialization.
-  - Host loads plugins; plugins do not load host internals. Prefer a small versioned host/kernel seam plus documented SDK entrypoints over ambient reachability.
-  - Treat broad runtime registries and mutable global plugin state as transitional compatibility surfaces, not the target architecture.
-  - If a setup or config flow truly needs plugin runtime, make that explicit instead of silently importing runtime code on the cold path.
 
-## Scoped Workflow Guides
+## Docs Linking (Mintlify)
 
-- `docs/AGENTS.md` owns Mintlify docs, docs links, and docs i18n rules.
-- `ui/AGENTS.md` owns Control UI i18n and generated locale rules.
-- `scripts/AGENTS.md` owns script-runner, local-check lock, and test/lint wrapper rules.
+- Docs are hosted on Mintlify (docs.openclaw.ai).
+- Internal doc links in `docs/**/*.md`: root-relative, no `.md`/`.mdx` (example: `[Config](/configuration)`).
+- When working with documentation, read the mintlify skill.
+- For docs, UI copy, and picker lists, order services/providers alphabetically unless the section is explicitly describing runtime behavior (for example auto-detection or execution order).
+- Section cross-references: use anchors on root-relative paths (example: `[Hooks](/configuration#hooks)`).
+- Doc headings and anchors: avoid em dashes and apostrophes in headings because they break Mintlify anchor links.
+- When the user asks for links, reply with full `https://docs.openclaw.ai/...` URLs (not root-relative).
+- When you touch docs, end the reply with the `https://docs.openclaw.ai/...` URLs you referenced.
+- README (GitHub): keep absolute docs URLs (`https://docs.openclaw.ai/...`) so links work on GitHub.
+- Docs content must be generic: no personal device names/hostnames/paths; use placeholders like `user@gateway-host` and “gateway host”.
+
+## Docs i18n (generated publish locales)
+
+- Foreign-language docs are not maintained in this repo. The generated publish output lives in the separate `openclaw/docs` repo (often cloned locally as the sibling `openclaw-docs` directory); do not add or edit localized docs under `docs/<locale>/**` here.
+- Those localized docs are autogenerated. Treat this repo's English docs plus glossary files as the source of truth, and let the publish/translation pipeline update `openclaw/docs`.
+- Pipeline: update English docs here → adjust the matching `docs/.i18n/glossary.<locale>.json` entries → let the publish-repo sync + `scripts/docs-i18n` run in `openclaw/docs` / local `openclaw-docs` clone → apply targeted fixes only if instructed.
+- Before rerunning `scripts/docs-i18n`, add glossary entries for any new technical terms, page titles, or short nav labels that must stay in English or use a fixed translation (for example `Doctor` or `Polls`).
+- `pnpm docs:check-i18n-glossary` enforces glossary coverage for changed English doc titles and short internal doc labels before translation reruns.
+- Translation memory lives in generated `docs/.i18n/*.tm.jsonl` files in the publish repo.
+- See `docs/.i18n/README.md`.
+- The pipeline can be slow/inefficient; if it’s dragging, ping @jospalmbier on Discord instead of hacking around it.
+
+## Control UI i18n (generated in repo)
+
+- Control UI foreign-language locale bundles are generated in this repo; do not hand-edit `ui/src/i18n/locales/*.ts` for non-English locales or `ui/src/i18n/.i18n/*` unless a targeted generated-output fix is explicitly requested.
+- Source of truth is `ui/src/i18n/locales/en.ts` plus the generator/runtime wiring in `scripts/control-ui-i18n.ts`, `ui/src/i18n/lib/types.ts`, and `ui/src/i18n/lib/registry.ts`.
+- Pipeline: update English control UI strings and locale wiring here → run `pnpm ui:i18n:sync` (or let `Control UI Locale Refresh` do it) → commit the regenerated locale bundles and `.i18n` metadata.
+- If the control UI locale outputs drift, regenerate them; do not manually translate or hand-maintain the generated locale files by default.
 
 ## exe.dev VM ops (general)
 
@@ -179,7 +186,6 @@
 - New runtime control-flow code should not branch on `error: string` or `reason: string` when a closed code union would be reasonable.
 - Dynamic import guardrail: do not mix `await import("x")` and static `import ... from "x"` for the same module in production code paths. If you need lazy loading, create a dedicated `*.runtime.ts` boundary (that re-exports from `x`) and dynamically import that boundary from lazy callers only.
 - Dynamic import verification: after refactors that touch lazy-loading/module boundaries, run `pnpm build` and check for `[INEFFECTIVE_DYNAMIC_IMPORT]` warnings before submitting.
-- Circular dependencies: keep both `pnpm check:import-cycles` and `pnpm check:madge-import-cycles` green; do not reintroduce runtime import cycles or madge-detected import loops.
 - Extension SDK self-import guardrail: inside an extension package, do not import that same extension via `openclaw/plugin-sdk/<extension>` from production files. Route internal imports through a local barrel such as `./api.ts` or `./runtime-api.ts`, and keep the `plugin-sdk/<extension>` path as the external contract only.
 - Extension package boundary guardrail: inside a bundled plugin package, do not use relative imports/exports that resolve outside that same package root. If shared code belongs in the plugin SDK, import `openclaw/plugin-sdk/<subpath>` instead of reaching into `src/plugin-sdk/**` or other repo paths via `../`.
 - Extension API surface rule: `openclaw/plugin-sdk/<subpath>` is the only public cross-package contract for extension-facing SDK code. If an extension needs a new seam, add a public subpath first; do not reach into `src/plugin-sdk/**` by relative path.
@@ -309,7 +315,7 @@
   - Only ask when changes are semantic (logic/data/behavior).
 - **Multi-agent safety:** focus reports on your edits; avoid guard-rail disclaimers unless truly blocked; when multiple agents touch the same file, continue if safe; end with a brief “other files present” note only if relevant.
 - Bug investigations: read source code of relevant npm dependencies and all related local code before concluding; aim for high-confidence root cause.
-- Code style: add brief comments for tricky logic; keep files under ~700 LOC when feasible (split/refactor as needed).
+- Code style: add brief comments for tricky logic; keep files under ~500 LOC when feasible (split/refactor as needed).
 - Tool schema guardrails (google-antigravity): avoid `Type.Union` in tool input schemas; no `anyOf`/`oneOf`/`allOf`. Use `stringEnum`/`optionalStringEnum` (Type.Unsafe enum) for string lists, and `Type.Optional(...)` instead of `... | null`. Keep top-level tool schema as `type: "object"` with `properties`.
 - Tool schema guardrails: avoid raw `format` property names in tool schemas; some validators treat `format` as a reserved keyword and reject the schema.
 - Never send streaming/partial replies to external messaging surfaces (WhatsApp, Telegram); only final replies should be delivered there. Streaming/tool events may still go to internal UIs/control channel.

CHANGELOG.md

@@ -8,50 +8,6 @@ Docs: https://docs.openclaw.ai
 
 ### Fixes
 
-- Memory/active-memory+dreaming: keep active-memory recall runs on the strongest resolved channel, consume managed dreaming heartbeat events exactly once, stop dreaming from re-ingesting its own narrative transcripts, and add explicit repair/dedupe recovery flows in CLI, doctor, and the Dreams UI.
-- Matrix/mentions: keep room mention gating strict while accepting visible `@displayName` Matrix URI labels, so `requireMention` works for non-OpenClaw Matrix clients again. (#64796) Thanks @hclsys.
-- Doctor: warn when on-disk agent directories still exist under `~/.openclaw/agents/<id>/agent` but the matching `agents.list[]` entries are missing from config. (#65113) Thanks @neeravmakwana.
-- Telegram: route approval button callback queries onto a separate sequentializer lane so plugin approval clicks can resolve immediately instead of deadlocking behind the blocked agent turn. (#64979) Thanks @nk3750.
-- Agents/Anthropic replay: preserve immutable signed-thinking replay safety across stored and live reruns, keep non-thinking embedded `tool_result` user blocks intact, and drop conflicting preserved tool IDs before validation so retries stop degrading into omitted tool calls. (#65126) Thanks @shakkernerd.
-- Telegram/direct sessions: keep commentary-only assistant fallback payloads out of visible direct delivery, so Codex planning chatter cannot leak into Telegram DMs when a run has no `final_answer` text. (#65112) Thanks @vincentkoc.
-- Infra/net: fix multipart FormData fields (including `model`) being silently dropped when a guarded runtime fetch body crosses a FormData implementation boundary, restoring OpenAI audio transcription requests that failed with HTTP 400. (#64349) Thanks @petr-sloup.
-- Plugins/memory: restore cached memory capability public artifacts on plugin-registry cache hits so memory-backed artifact surfaces stay visible after warm loads. Thanks @sercada and @vincentkoc.
-- Gateway/cron: preserve requested isolated-agent config across runtime reloads so subagent jobs and heartbeat overrides keep the right workspace and heartbeat settings when the hot-loaded snapshot is stale. Thanks @l0cka and @vincentkoc.
-- Cron/isolated sessions: persist the right transcript path for each isolated run, including fresh session rollovers, so cron runs stop appending to stale session files. Thanks @samrusani and @vincentkoc.
-
-## 2026.4.11
-
-### Changes
-
-- Dreaming/memory-wiki: add ChatGPT import ingestion plus new `Imported Insights` and `Memory Palace` diary subtabs so Dreaming can inspect imported source chats, compiled wiki pages, and full source pages directly from the UI. (#64505)
-- Control UI/webchat: render assistant media/reply/voice directives as structured chat bubbles, add the `[embed ...]` rich output tag, and gate external embed URLs behind config. (#64104)
-- Tools/video_generate: add URL-only generated asset delivery, typed `providerOptions`, reference audio inputs, per-asset role hints, `adaptive` aspect-ratio support, and a higher image-input cap so video providers can expose richer generation modes without forcing large files into memory. (#61987, #61988) Thanks @xieyongliang.
-- Feishu: improve document comment sessions with richer context parsing, comment reactions, and typing feedback so document-thread conversations behave more like chat conversations. (#63785)
-- Microsoft Teams: add reaction support, reaction listing, Graph pagination, and delegated OAuth setup for sending reactions while preserving application-auth read paths. (#51646)
-- Plugins: allow plugin manifests to declare activation and setup descriptors so plugin setup flows can describe required auth, pairing, and configuration steps without hardcoded core special cases. (#64780)
-- Ollama: cache `/api/show` context-window and capability metadata during model discovery so repeated picker refreshes stop refetching unchanged models, while still retrying after empty responses and invalidating on digest changes. (#64753) Thanks @ImLukeF.
-- Models/providers: surface how configured OpenAI-compatible endpoints are classified in embedded-agent debug logs, so local and proxy routing issues are easier to diagnose. (#64754) Thanks @ImLukeF.
-- QA/parity: add the GPT-5.4 vs Opus 4.6 agentic parity report gate with shared scenario coverage checks, stricter evidence heuristics, and skipped-scenario accounting for maintainer review. (#64441) Thanks @100yenadmin.
-
-### Fixes
-
-- OpenAI/Codex OAuth: stop rewriting the upstream authorize URL scopes so new Codex sign-ins do not fail with `invalid_scope` before returning an authorization code. (#64713) Thanks @fuller-stack-dev.
-- Audio transcription: disable pinned DNS only for OpenAI-compatible multipart requests, while still validating hostnames, so OpenAI, Groq, and Mistral transcription works again without weakening other request paths. (#64766) Thanks @GodsBoy.
-- macOS/Talk Mode: after granting microphone permission on first enable, continue starting Talk Mode instead of requiring a second toggle. (#62459) Thanks @ggarber.
-- Control UI/webchat: persist agent-run TTS audio replies into webchat history and preserve interleaved tool card pairing so generated audio and mixed tool output stay attached to the right messages. (#63514) Thanks @bittoby.
-- WhatsApp: honor the configured default account when the active listener helper is used without an explicit account id, so named default accounts do not get registered under `default`. (#53918) Thanks @yhyatt.
-- ACP/agents: suppress commentary-phase child assistant relay text in ACP parent stream updates, so spawned child runs stop leaking internal progress chatter into the parent session. Thanks @vincentkoc.
-- Agents/timeouts: honor explicit run timeouts in the LLM idle watchdog and align default timeout config so slow models can keep working until the configured limit instead of using the wrong idle window.
-- Config: include `asyncCompletion` in the generated zod schema so documented async completion config no longer fails with an unrecognized-key error. (#63618)
-- Google/Veo: stop sending the unsupported `numberOfVideos` request field so Gemini Developer API Veo runs do not fail before OpenClaw can complete the intended Google video generation path. (#64723) Thanks @velvet-shark.
-- QA/packaging: stop packaged CLI startup and completion cache generation from reading repo-only QA scenario markdown, ship the bundled QA scenario pack in npm releases, and keep `openclaw completion --write-state` working even if QA setup is broken. (#64648) Thanks @obviyus.
-- Codex/QA: keep Codex app-server coordination chatter out of visible replies, add a live QA leak scenario, and classify leaked harness meta text as a QA failure instead of a successful reply. Thanks @vincentkoc.
-- WhatsApp: route `message react` through the gateway-owned action path so reactions use the live WhatsApp listener in both DM and group chats, matching `message send` and `message poll`. Thanks @mcaxtr.
-- Auto-reply/WhatsApp: preserve inbound image attachment notes after media understanding so image edits keep the real saved media path instead of hallucinating a missing local path. (#64918) Thanks @ngutman.
-- Telegram/sessions: keep topic-scoped session initialization on the canonical topic transcript path when inbound turns omit `MessageThreadId`, so one topic session no longer alternates between bare and topic-qualified transcript files. (#64869) Thanks @jalehman.
-- Agents/failover: scope assistant-side fallback classification and surfaced provider errors to the current attempt instead of stale session history, so cross-provider fallback runs stop inheriting the previous provider's failure. (#62907) Thanks @stainlu.
-- MiniMax/OAuth: write `api: "anthropic-messages"` and `authHeader: true` into the `minimax-portal` config patch during `openclaw configure`, so re-authenticated portal setups keep Bearer auth routing working. (#64964) Thanks @ryanlee666.
-
 ## 2026.4.10
 
 ### Changes
@@ -68,14 +24,11 @@ Docs: https://docs.openclaw.ai
 - Gateway: add a `commands.list` RPC so remote gateway clients can discover runtime-native, text, skill, and plugin commands with surface-aware naming and serialized argument metadata. (#62656) Thanks @samzong.
 - Models/providers: add per-provider `models.providers.*.request.allowPrivateNetwork` for trusted self-hosted OpenAI-compatible endpoints, keep the opt-in scoped to model request surfaces, and refresh cached WebSocket managers when request transport overrides change. (#63671) Thanks @qas.
 - Feishu: standardize request user agents and register the bot as an AI agent so Feishu deployments identify OpenClaw consistently. (#63835) Thanks @evandance.
-- Docs i18n: chunk raw doc translation, reject truncated tagged outputs, avoid ambiguous body-only wrapper unwrapping, and recover from terminated Pi translation sessions without changing the default `openai/gpt-5.4` path. (#62969, #63808) Thanks @hxy91819.
-- Gateway: split startup and runtime seams so gateway lifecycle sequencing, reload state, and shutdown behavior stay easier to maintain without changing observed behavior. (#63975) Thanks @gumadeiras.
-- Control UI/webchat: normalize assistant `MEDIA:`/reply/voice directives into structured bubble rendering, rename the unreleased rich web shortcode to `[embed ...]`, and surface session runtime roots so hosted web content is written to the correct document path instead of guessed local files.
 - Matrix/partial streaming: add MSC4357 live markers to draft preview sends and edits so supporting Matrix clients can render a live/typewriter animation and stop it when the final edit lands. (#63513) Thanks @TigerInYourDream.
 - Control UI/dreaming: simplify the Scene and Diary surfaces, preserve unknown phase state for partial status payloads, and stabilize waiting-entry recency ordering so Dreaming status and review lists stay clear and deterministic. (#64035) Thanks @davemorin.
 - Agents: add an opt-in strict-agentic embedded Pi execution contract for GPT-5-family runs so plan-only or filler turns keep acting until they hit a real blocker. (#64241) Thanks @100yenadmin.
 - Agents/OpenAI: add provider-owned OpenAI/Codex tool schema compatibility and surface embedded-run replay/liveness state for long-running runs. (#64300) Thanks @100yenadmin.
-- Dreaming/memory-wiki: add ChatGPT import ingestion plus new `Imported Insights` and `Memory Palace` diary subtabs so Dreaming can inspect imported source chats, compiled wiki pages, and full source pages directly from the UI. (#64505)
+- Docs i18n: chunk raw doc translation, reject truncated tagged outputs, avoid ambiguous body-only wrapper unwrapping, and recover from terminated Pi translation sessions without changing the default `openai/gpt-5.4` path. (#62969, #63808) Thanks @hxy91819.
 
 ### Fixes
 
@@ -162,20 +115,12 @@ Docs: https://docs.openclaw.ai
 - Daemon/gateway: prevent systemd restart storms on configuration errors by exiting with `EX_CONFIG` and adding generated unit restart-prevention guards. (#63913) Thanks @neo1027144-creator.
 - Agents/exec: prevent gateway crash ("Agent listener invoked outside active run") when a subagent exec tool produces stdout/stderr after the agent run has ended or been aborted. (#62821) Thanks @openperf.
 - Gateway/OpenAI compat: return real `usage` for non-stream `/v1/chat/completions` responses, emit the final usage chunk when `stream_options.include_usage=true`, and bound usage-gated stream finalization after lifecycle end. (#62986) Thanks @Lellansin.
-- Matrix/migration: keep packaged warning-only crypto migrations from being misclassified as actionable when only helper chunks are present, so startup and doctor stay on the warning-only path instead of creating unnecessary migration snapshots. (#64373) Thanks @gumadeiras.
-- Matrix/ACP thread bindings: preserve canonical room casing and parent conversation routing during ACP session spawn so mixed-case room ids bind correctly from top-level rooms and existing Matrix threads. (#64343) Thanks @gumadeiras.
 - Agents/subagents: deduplicate delivered completion announces so retry or re-entry cleanup does not inject duplicate internal-context completion turns into the parent session. (#61525) Thanks @100yenadmin.
 - Agents/exec: keep sandboxed `tools.exec.host=auto` sessions from honoring per-call `host=node` or `host=gateway` overrides while a sandbox runtime is active, and stop advertising node routing in that state so exec stays on the sandbox host. (#63880)
 - Agents/subagents: preserve archived delete-mode runs until `sessions.delete` succeeds and prevent overlapping archive sweeps from duplicating in-flight cleanup attempts. (#61801) Thanks @100yenadmin.
 - Cron/isolated agent: run scheduled agent turns as non-owner senders so owner-only tools stay unavailable during cron execution. (#63878)
 - Discord/sandbox: include `image` in sandbox media param normalization so Discord event cover images cannot bypass sandbox path rewriting. (#64377) Thanks @mmaps.
 - Agents/exec: extend exec completion detection to cover local background exec formats so the owner-downgrade fires correctly for all exec paths. (#64376) Thanks @mmaps.
-- Security/dependencies: pin axios to 1.15.0 and add a plugin install dependency denylist that blocks known malicious packages before install. (#63891) Thanks @mmaps.
-- Browser/security: apply three-phase interaction navigation guard to pressKey and type(submit) so delayed JS redirects from keypress cannot bypass SSRF policy. (#63889) Thanks @mmaps.
-
-- Browser/security: guard existing-session Chrome MCP interaction routes with SSRF post-checks so delayed navigation from click, type, press, and evaluate cannot bypass the configured policy. (#64370) Thanks @eleqtrizit.
-- Browser/security: default browser SSRF policy to strict mode so unconfigured installs block private-network navigation, and align external-content marker span mapping so ZWS-injected boundary spoofs are fully sanitized. (#63885) Thanks @eleqtrizit.
-- Browser/security: apply SSRF navigation policy to subframe document navigations so iframe-targeted private-network hops are blocked without quarantining the parent page. (#64371) Thanks @eleqtrizit.
 - Hooks/security: mark agent hook system events as untrusted and sanitize hook display names before cron metadata reuse. (#64372) Thanks @eleqtrizit.
 - Daemon/launchd: keep `openclaw gateway stop` persistent without uninstalling the macOS LaunchAgent, re-enable it on explicit restart or repair, and harden launchd label handling. (#64447) Thanks @ngutman.
 - Plugins/context engines: preserve `plugins.slots.contextEngine` through normalization and keep explicitly selected workspace context-engine plugins enabled, so loader diagnostics and plugin activation stop dropping that slot selection. (#64192) Thanks @hclsys.
@@ -186,9 +131,6 @@ Docs: https://docs.openclaw.ai
 - Media/security: honor sender-scoped `toolsBySender` policy for outbound host-media reads so denied senders cannot trigger host file disclosure via attachment hydration. (#64459) Thanks @eleqtrizit.
 - Browser/security: reject strict-policy hostname navigation unless the hostname is an explicit allowlist exception or IP literal, and route CDP HTTP discovery through the pinned SSRF fetch path. (#64367) Thanks @eleqtrizit.
 - Models/vLLM: ignore empty `tool_calls` arrays from reasoning-model OpenAI-compatible replies, reset false `toolUse` stop reasons when no actual tool calls were parsed, and stop sending `tool_choice` unless tools are present so vLLM reasoning responses no longer hang indefinitely. (#61197, #61534) Thanks @balajisiva.
-- Heartbeat/scheduling: spread interval heartbeats across stable per-agent phases derived from gateway identity, so provider traffic is distributed more uniformly across the configured interval instead of clustering around startup-relative times. (#64560) Thanks @odysseus0.
-- Config/media: accept `tools.media.asyncCompletion.directSend` in strict config validation so gateways no longer reject the generated-schema-backed async media completion setting at startup. (#63618) Thanks @qiziAI.
-- Telegram/exec: preserve delayed exec completion routing for forum topics by pinning background exec completions to the topic where the run started even if the session route later drifts. (#64580) thanks @jalehman.
 
 ## 2026.4.9
 
@@ -199,7 +141,6 @@ Docs: https://docs.openclaw.ai
 - QA/lab: add character-vibes evaluation reports with model selection and parallel runs so live QA can compare candidate behavior faster.
 - Plugins/provider-auth: let provider manifests declare `providerAuthAliases` so provider variants can share env vars, auth profiles, config-backed auth, and API-key onboarding choices without core-specific wiring.
 - iOS: pin release versioning to an explicit CalVer in `apps/ios/version.json`, keep TestFlight iteration on the same short version until maintainers intentionally promote the next gateway version, and add the documented `pnpm ios:version:pin -- --from-gateway` workflow for release trains. (#63001) Thanks @ngutman.
-- Tools/video_generate: extend the tool and the Plugin SDK with `providerOptions` (vendor-specific options forwarded as a JSON object), `inputAudios` / `audioRef` / `audioRefs` reference audio inputs, per-asset semantic role hints (`imageRoles` / `videoRoles` / `audioRoles`) using a typed `VideoGenerationAssetRole` union, a new `"adaptive"` aspect-ratio sentinel, and `maxInputAudios` provider capability declarations. Providers opt into `providerOptions` by declaring a typed `capabilities.providerOptions` schema (`{ seed: "number", draft: "boolean", ... }`); unknown keys and type mismatches cause the runtime fallback loop to skip the candidate with a visible warning and an `attempts` entry, so vendor-specific options never silently reach the wrong provider. Also raises the in-tool image input cap to 9 and updates the docs table to list all new parameters. (#61987) Thanks @xieyongliang.
 
 ### Fixes
 
@@ -361,9 +302,6 @@ Docs: https://docs.openclaw.ai
 - Reply execution: prefer the active runtime snapshot over stale queued reply config during embedded reply and follow-up execution so SecretRef-backed reply turns stop crashing after secrets have already resolved. (#62693) Thanks @mbelinky.
 - Android/manual connect: allow blank port input only for TLS manual gateway endpoints so standard HTTPS Tailscale hosts default to `443` without silently changing cleartext manual connects. (#63134) Thanks @Tyler-RNG.
 - Matrix/agents: hide owner-only `set-profile` from embedded agent channel-action discovery so non-owner runs stop advertising profile updates they cannot execute. (#62662) Thanks @eleqtrizit.
-- iOS/gateway: replace string-matched connection error UI with structured gateway connection problems, preserve actionable pairing/auth failures over later generic disconnect noise, and surface reusable problem banners and details across onboarding, settings, and root status surfaces. (#62650) Thanks @ngutman.
-- Git/env sanitization: block additional Git repository-plumbing env variables such as `GIT_DIR`, `GIT_WORK_TREE`, `GIT_COMMON_DIR`, `GIT_INDEX_FILE`, `GIT_OBJECT_DIRECTORY`, `GIT_ALTERNATE_OBJECT_DIRECTORIES`, and `GIT_NAMESPACE` so host-run Git commands cannot be redirected to attacker-chosen repository state through inherited or request-scoped env. (#62002) Thanks @eleqtrizit.
-- Host exec/env sanitization: block additional request-scoped credential and config-path overrides such as `KUBECONFIG`, cloud credential-path env, `CARGO_HOME`, and `HELM_HOME` so host-run tools can no longer be redirected to attacker-chosen config or state. (#59119) Thanks @eleqtrizit.
 
 ## 2026.4.5
 
@@ -693,7 +631,6 @@ Docs: https://docs.openclaw.ai
 - Gateway/OpenAI HTTP: restore default operator scopes for bearer-authenticated requests that omit `x-openclaw-scopes`, so headless `/v1/chat/completions` and session-history callers work again after the recent method-scope hardening. (#57596) Thanks @openperf.
 - Gateway/attachments: offload large inbound images without leaking `media://` markers into text-only runs, preserve mixed attachment order for model input/transcripts, and fail closed when model image capability cannot be resolved. (#55513) Thanks @Syysean.
 - Telegram/outbound chunking: use static markdown chunking when Telegram runtime state is unavailable so long outbound Telegram messages still split correctly after cold starts. (#57816) Thanks @ForestDengHK.
-- Update/Corepack: disable interactive Corepack download prompts during update preflight install unless `COREPACK_ENABLE_DOWNLOAD_PROMPT` is already explicitly set, so `openclaw update` can fetch the repo-pinned pnpm version non-interactively. (#61456) Thanks @p6l-richard.
 
 ## 2026.4.2
 

CONTRIBUTING.md

@@ -95,7 +95,6 @@ For coordinated change sets that genuinely need more than 10 PRs, join the **#cl
 
 - Test locally with your OpenClaw instance
 - Run tests: `pnpm build && pnpm check && pnpm test`
-- For iterative local commits, `scripts/committer --fast "message" <files...>` passes `FAST_COMMIT=1` through to the pre-commit hook so it skips the repo-wide `pnpm check`. Only use it when you've already run equivalent targeted validation for the touched surface.
 - For extension/plugin changes, run the fast local lane first:
   - `pnpm test:extension <extension-name>`
   - `pnpm test:extension --list` to see valid extension ids

INCIDENT_RESPONSE.md

@@ -6,6 +6,7 @@ We monitor security signals from:
 
 - GitHub Security Advisories (GHSA) and private vulnerability reports.
 - Public GitHub issues/discussions when reports are not sensitive.
+- Official plublic discussion groups and channels (i.e. Discord and X).
 - Automated signals (for example Dependabot, CodeQL, npm advisories, and secret scanning).
 
 Initial triage:

appcast.xml

@@ -2,193 +2,6 @@
 <rss xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" version="2.0">
     <channel>
         <title>OpenClaw</title>
-        <item>
-            <title>2026.4.11</title>
-            <pubDate>Sun, 12 Apr 2026 00:37:09 +0000</pubDate>
-            <link>https://raw.githubusercontent.com/openclaw/openclaw/main/appcast.xml</link>
-            <sparkle:version>2026041190</sparkle:version>
-            <sparkle:shortVersionString>2026.4.11</sparkle:shortVersionString>
-            <sparkle:minimumSystemVersion>15.0</sparkle:minimumSystemVersion>
-            <description><![CDATA[<h2>OpenClaw 2026.4.11</h2>
-<h3>Changes</h3>
-<ul>
-<li>Dreaming/memory-wiki: add ChatGPT import ingestion plus new <code>Imported Insights</code> and <code>Memory Palace</code> diary subtabs so Dreaming can inspect imported source chats, compiled wiki pages, and full source pages directly from the UI. (#64505)</li>
-<li>Control UI/webchat: render assistant media/reply/voice directives as structured chat bubbles, add the <code>[embed ...]</code> rich output tag, and gate external embed URLs behind config. (#64104)</li>
-<li>Tools/video_generate: add URL-only generated asset delivery, typed <code>providerOptions</code>, reference audio inputs, per-asset role hints, <code>adaptive</code> aspect-ratio support, and a higher image-input cap so video providers can expose richer generation modes without forcing large files into memory. (#61987, #61988) Thanks @xieyongliang.</li>
-<li>Feishu: improve document comment sessions with richer context parsing, comment reactions, and typing feedback so document-thread conversations behave more like chat conversations. (#63785)</li>
-<li>Microsoft Teams: add reaction support, reaction listing, Graph pagination, and delegated OAuth setup for sending reactions while preserving application-auth read paths. (#51646)</li>
-<li>Plugins: allow plugin manifests to declare activation and setup descriptors so plugin setup flows can describe required auth, pairing, and configuration steps without hardcoded core special cases. (#64780)</li>
-<li>Ollama: cache <code>/api/show</code> context-window and capability metadata during model discovery so repeated picker refreshes stop refetching unchanged models, while still retrying after empty responses and invalidating on digest changes. (#64753) Thanks @ImLukeF.</li>
-<li>Models/providers: surface how configured OpenAI-compatible endpoints are classified in embedded-agent debug logs, so local and proxy routing issues are easier to diagnose. (#64754) Thanks @ImLukeF.</li>
-<li>QA/parity: add the GPT-5.4 vs Opus 4.6 agentic parity report gate with shared scenario coverage checks, stricter evidence heuristics, and skipped-scenario accounting for maintainer review. (#64441) Thanks @100yenadmin.</li>
-</ul>
-<h3>Fixes</h3>
-<ul>
-<li>OpenAI/Codex OAuth: stop rewriting the upstream authorize URL scopes so new Codex sign-ins do not fail with <code>invalid_scope</code> before returning an authorization code. (#64713) Thanks @fuller-stack-dev.</li>
-<li>Audio transcription: disable pinned DNS only for OpenAI-compatible multipart requests, while still validating hostnames, so OpenAI, Groq, and Mistral transcription works again without weakening other request paths. (#64766) Thanks @GodsBoy.</li>
-<li>macOS/Talk Mode: after granting microphone permission on first enable, continue starting Talk Mode instead of requiring a second toggle. (#62459) Thanks @ggarber.</li>
-<li>Control UI/webchat: persist agent-run TTS audio replies into webchat history and preserve interleaved tool card pairing so generated audio and mixed tool output stay attached to the right messages. (#63514) Thanks @bittoby.</li>
-<li>WhatsApp: honor the configured default account when the active listener helper is used without an explicit account id, so named default accounts do not get registered under <code>default</code>. (#53918) Thanks @yhyatt.</li>
-<li>ACP/agents: suppress commentary-phase child assistant relay text in ACP parent stream updates, so spawned child runs stop leaking internal progress chatter into the parent session. Thanks @vincentkoc.</li>
-<li>Agents/timeouts: honor explicit run timeouts in the LLM idle watchdog and align default timeout config so slow models can keep working until the configured limit instead of using the wrong idle window.</li>
-<li>Config: include <code>asyncCompletion</code> in the generated zod schema so documented async completion config no longer fails with an unrecognized-key error. (#63618)</li>
-<li>Google/Veo: stop sending the unsupported <code>numberOfVideos</code> request field so Gemini Developer API Veo runs do not fail before OpenClaw can complete the intended Google video generation path. (#64723) Thanks @velvet-shark.</li>
-<li>QA/packaging: stop packaged CLI startup and completion cache generation from reading repo-only QA scenario markdown, ship the bundled QA scenario pack in npm releases, and keep <code>openclaw completion --write-state</code> working even if QA setup is broken. (#64648) Thanks @obviyus.</li>
-<li>Codex/QA: keep Codex app-server coordination chatter out of visible replies, add a live QA leak scenario, and classify leaked harness meta text as a QA failure instead of a successful reply. Thanks @vincentkoc.</li>
-<li>WhatsApp: route <code>message react</code> through the gateway-owned action path so reactions use the live WhatsApp listener in both DM and group chats, matching <code>message send</code> and <code>message poll</code>. Thanks @mcaxtr.</li>
-<li>Auto-reply/WhatsApp: preserve inbound image attachment notes after media understanding so image edits keep the real saved media path instead of hallucinating a missing local path. (#64918) Thanks @ngutman.</li>
-<li>Telegram/sessions: keep topic-scoped session initialization on the canonical topic transcript path when inbound turns omit <code>MessageThreadId</code>, so one topic session no longer alternates between bare and topic-qualified transcript files. (#64869) Thanks @jalehman.</li>
-<li>Agents/failover: scope assistant-side fallback classification and surfaced provider errors to the current attempt instead of stale session history, so cross-provider fallback runs stop inheriting the previous provider's failure. (#62907) Thanks @stainlu.</li>
-<li>MiniMax/OAuth: write <code>api: "anthropic-messages"</code> and <code>authHeader: true</code> into the <code>minimax-portal</code> config patch during <code>openclaw configure</code>, so re-authenticated portal setups keep Bearer auth routing working. (#64964) Thanks @ryanlee666.</li>
-</ul>
-<p><a href="https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md">View full changelog</a></p>
-]]></description>
-            <enclosure url="https://github.com/openclaw/openclaw/releases/download/v2026.4.11/OpenClaw-2026.4.11.zip" length="47317969" type="application/octet-stream" sparkle:edSignature="v9bUsh1mBBPtpMn7kKYAvO8MNJHAeMj7UkmkkuDSC8NvwPx2Fo3+NEeyAyA9s9Vax6L7i+eHSpwzAmtwpnHcCA=="/>
-        </item>
-        <item>
-            <title>2026.4.10</title>
-            <pubDate>Sat, 11 Apr 2026 03:17:02 +0000</pubDate>
-            <link>https://raw.githubusercontent.com/openclaw/openclaw/main/appcast.xml</link>
-            <sparkle:version>2026041090</sparkle:version>
-            <sparkle:shortVersionString>2026.4.10</sparkle:shortVersionString>
-            <sparkle:minimumSystemVersion>15.0</sparkle:minimumSystemVersion>
-            <description><![CDATA[<h2>OpenClaw 2026.4.10</h2>
-<h3>Changes</h3>
-<ul>
-<li>Models/Codex: add the bundled Codex provider and plugin-owned app-server harness so <code>codex/gpt-*</code> models use Codex-managed auth, native threads, model discovery, and compaction while <code>openai/gpt-*</code> stays on the normal OpenAI provider path. (#64298)</li>
-<li>Memory/Active Memory: add a new optional Active Memory plugin that gives OpenClaw a dedicated memory sub-agent right before the main reply, so ongoing chats can automatically pull in relevant preferences, context, and past details without making users remember to manually say "remember this" or "search memory" first. Includes configurable message/recent/full context modes, live <code>/verbose</code> inspection, advanced prompt/thinking overrides for tuning, and opt-in transcript persistence for debugging. Docs: https://docs.openclaw.ai/concepts/active-memory. (#63286) Thanks @Takhoffman.</li>
-<li>macOS/Talk: add an experimental local MLX speech provider for Talk Mode, with explicit provider selection, local utterance playback, interruption handling, and system-voice fallback. (#63539) Thanks @ImLukeF.</li>
-<li>Tools/video generation: add Seedance 2.0 model refs to the bundled fal provider and submit the provider-specific duration, resolution, audio, and seed metadata fields needed for live Seedance 2.0 runs.</li>
-<li>Microsoft Teams: add message actions for pin, unpin, read, react, and listing reactions. (#53432) Thanks @sudie-codes.</li>
-<li>QA/Matrix: add a live <code>openclaw qa matrix</code> lane backed by a disposable Matrix homeserver, shared live-transport seams, and Matrix-specific transport coverage for threading, reactions, restart, and allowlist behavior. (#64489) Thanks @gumadeiras.</li>
-<li>QA/Telegram: add a live <code>openclaw qa telegram</code> lane for private-group bot-to-bot checks, harden its artifact handling, and preserve native Telegram command reply threading for QA verification. (#64303) Thanks @obviyus.</li>
-<li>QA/testing: add a <code>--runner multipass</code> lane for <code>openclaw qa suite</code> so repo-backed QA scenarios can run inside a disposable Linux VM and write back the usual report, summary, and VM logs. (#63426) Thanks @shakkernerd.</li>
-<li>CLI/exec policy: add a local <code>openclaw exec-policy</code> command with <code>show</code>, <code>preset</code>, and <code>set</code> subcommands for synchronizing requested <code>tools.exec.*</code> config with the local exec approvals file, plus follow-up hardening for node-host rejection, rollback safety, and sync conflict detection. (#64050)</li>
-<li>Gateway: add a <code>commands.list</code> RPC so remote gateway clients can discover runtime-native, text, skill, and plugin commands with surface-aware naming and serialized argument metadata. (#62656) Thanks @samzong.</li>
-<li>Models/providers: add per-provider <code>models.providers.*.request.allowPrivateNetwork</code> for trusted self-hosted OpenAI-compatible endpoints, keep the opt-in scoped to model request surfaces, and refresh cached WebSocket managers when request transport overrides change. (#63671) Thanks @qas.</li>
-<li>Feishu: standardize request user agents and register the bot as an AI agent so Feishu deployments identify OpenClaw consistently. (#63835) Thanks @evandance.</li>
-<li>Matrix/partial streaming: add MSC4357 live markers to draft preview sends and edits so supporting Matrix clients can render a live/typewriter animation and stop it when the final edit lands. (#63513) Thanks @TigerInYourDream.</li>
-<li>Control UI/dreaming: simplify the Scene and Diary surfaces, preserve unknown phase state for partial status payloads, and stabilize waiting-entry recency ordering so Dreaming status and review lists stay clear and deterministic. (#64035) Thanks @davemorin.</li>
-<li>Agents: add an opt-in strict-agentic embedded Pi execution contract for GPT-5-family runs so plan-only or filler turns keep acting until they hit a real blocker. (#64241) Thanks @100yenadmin.</li>
-<li>Agents/OpenAI: add provider-owned OpenAI/Codex tool schema compatibility and surface embedded-run replay/liveness state for long-running runs. (#64300) Thanks @100yenadmin.</li>
-<li>Docs i18n: chunk raw doc translation, reject truncated tagged outputs, avoid ambiguous body-only wrapper unwrapping, and recover from terminated Pi translation sessions without changing the default <code>openai/gpt-5.4</code> path. (#62969, #63808) Thanks @hxy91819.</li>
-</ul>
-<h3>Fixes</h3>
-<ul>
-<li>Browser/security: tighten browser and sandbox navigation defenses across strict SSRF defaults, hostname allowlists, interaction-driven redirects, subframes, CDP discovery, existing sessions, tab actions, noVNC, marker-span sanitization, and Docker CDP source-range enforcement. (#61404, #63332, #63882, #63885, #63889, #64367, #64370, #64371)</li>
-<li>Security/tools: harden exec preflight reads, host env denylisting, node output boundaries, outbound host-media reads, profile-mutation authorization, plugin install dependency scanning, ACPX tool hooks, Gmail watcher token redaction, and oversized realtime WebSocket frame handling. (#62333, #62661, #62662, #63277, #63551, #63553, #63886, #63890, #63891, #64459)</li>
-<li>OpenAI/Codex: add required Codex OAuth scopes, classify provider/runtime failures more clearly, stop suggesting <code>/elevated full</code> when auto-approved host exec is unavailable, add OpenAI/Codex tool-schema compatibility, and preserve embedded-run replay/liveness truth across compaction retries and mutating side effects. (#64300, #64439) Thanks @100yenadmin.</li>
-<li>CLI/WhatsApp media sends: route gateway-mode outbound sends with <code>--media</code> through the channel <code>sendMedia</code> path and preserve media access context, so WhatsApp document and attachment sends stop silently dropping the file while still delivering the caption. (#64478, #64492) Thanks @ShionEria.</li>
-<li>Microsoft Teams: restore media downloads for personal DMs, Bot Framework <code>a:</code> conversations, OneDrive/SharePoint shared files, and Graph-backed chat IDs; accept Bot Framework audience tokens; prevent feedback-learning filename collisions; keep long tool chains alive with typing indicators; add SSO sign-in callbacks; inject parent context for thread replies; and deliver cron announcements to Teams conversation IDs. (#54932, #55383, #55386, #58001, #58249, #58774, #59731, #60956, #62219, #62674, #63063, #63942, #63945, #63949, #63951, #63953, #64087, #64088, #64089)</li>
-<li>Gateway/tailscale: start Tailscale exposure and the gateway update check before awaiting channel and plugin sidecar startup so remote operators are not locked out when startup sidecars stall.</li>
-<li>Gateway/startup: keep WebSocket RPC available while channels and plugin sidecars start, hold <code>chat.history</code> unavailable until startup sidecars finish so synchronous history reads cannot stall startup (reported in #63450), refresh advertised gateway methods after deferred plugin reloads, and enforce the pre-auth WebSocket upgrade budget before the no-handler 503 path so upgrade floods cannot bypass connection limits during that window. (#63480) Thanks @neeravmakwana.</li>
-<li>WhatsApp: keep inbound replies, media, composing indicators, and queued outbound deliveries attached to the current socket across reconnect gaps, including fresh retry-eligible sends after the listener comes back. (#30806, #46299, #62892, #63916) Thanks @mcaxtr.</li>
-<li>Gateway/thread routing: preserve Slack, Telegram, Mattermost, Matrix, ACP, restart-sentinel, and agent announce delivery targets so subagent, cron, stream-relay, session fallback, and restart messages land back in the originating thread, topic, or room casing. (#54840, #57056, #63143, #63228, #63506, #64343, #64391)</li>
-<li>Models/fallback: preserve <code>/models</code> selection across transient primary-model failures and config reloads, allow timeout cooldown probes, classify OpenRouter no-endpoints responses, detect llama.cpp context overflows, and keep provider/runtime context metadata stable through reloads. (#61472, #64196, #64471)</li>
-<li>Agents/BTW: keep <code>/btw</code> side questions working after tool-use turns by stripping replayed tool blocks, hidden reasoning, and malformed image payloads, omitting empty tool arrays, allowing Bedrock <code>auth: "aws-sdk"</code>, and routing Feishu <code>/btw</code> plus <code>/stop</code> through bounded out-of-band lanes. (#64218, #64219, #64225, #64324) Thanks @ngutman.</li>
-<li>Control UI/BTW: render <code>/btw</code> side results as dismissible ephemeral cards in the browser, send <code>/btw</code> immediately during active runs, and clear stale BTW cards on reset flows so webchat matches the intended detached side-question behavior. (#64290) Thanks @ngutman.</li>
-<li>Commands/targeting: use the selected agent or session for command output, send policy, usage/cost, context reports, model lists, bash sandbox hints, BTW/compact working directories, plugin commands, and session exports so multi-agent commands describe and mutate the intended target instead of the requester.</li>
-<li>Conversation bindings: normalize focused/current conversation ids, preserve binding metadata on account and Discord rebinds, avoid stale Discord lifecycle windows, and keep generic activity touches persisted so reply routing survives rebinds and restarts.</li>
-<li>iMessage/self-chat: distinguish normal DM outbound rows from true self-chat using <code>destination_caller_id</code> plus chat participants, preserve multi-handle self-chat aliases, drop ambiguous reflected echoes, and strip wrapped imsg RPC text fields. (#61619, #63868, #63980, #63989, #64000) Thanks @neeravmakwana.</li>
-<li>Matrix: keep multi-account room scoping consistent, keep packaged crypto migrations warning-only when appropriate, preserve ordered block streaming, add explicit Matrix block-streaming opt-in, and resolve verification/bootstrap from the packaged runtime entry. (#58449, #59249, #59266, #64373) Thanks @gumadeiras.</li>
-<li>Telegram/security: tighten Telegram <code>allowFrom</code> sender validation and keep <code>/whoami</code> allowlist reporting in sync with command auth checks.</li>
-<li>Agents/timeouts: extend the default LLM idle window to 120s and keep silent no-token idle timeouts on recovery paths, so slow models can retry or fall back before users see an error.</li>
-<li>Gateway/agents: preserve configured model selection and richer <code>IDENTITY.md</code> content across agent create/update flows and workspace moves, and fail safely instead of silently overwriting unreadable identity files. (#61577) Thanks @samzong.</li>
-<li>Skills/TaskFlow: restore valid frontmatter fences for the bundled <code>taskflow</code> and <code>taskflow-inbox-triage</code> skills and copy bundled <code>SKILL.md</code> files as hard dist-runtime copies so skills stay discoverable and loadable after updates. (#64166, #64469) Thanks @extrasmall0.</li>
-<li>Skills: respect overridden home directories when loading personal skills so service, test, and custom launch environments read the intended user skill directory instead of the process home.</li>
-<li>Windows/exec: settle supervisor waits from child exit state after stdout and stderr drain even when <code>close</code> never arrives, so CLI commands stop hanging or dying with forced <code>SIGKILL</code> on Windows. (#64072) Thanks @obviyus.</li>
-<li>Browser/sandbox: prevent sandbox browser CDP startup hangs by recreating containers when the browser security hash changes and by waiting on the correct sandbox browser lifecycle. (#62873) Thanks @Syysean.</li>
-<li>QQBot/streaming: make block streaming configurable per QQ bot account via <code>streaming.mode</code> (<code>"partial"</code> | <code>"off"</code>, default <code>"partial"</code>) instead of hardcoding it off, so responses can be delivered incrementally. (#63746)</li>
-<li>QQBot/config: allow extra fields in <code>channels.qqbot</code> and <code>channels.qqbot.accounts.*</code> so extended qqbot builds can add new config options without gateway startup failing on schema validation. (#64075) Thanks @WideLee.</li>
-<li>Dreaming/gateway: require <code>operator.admin</code> for persistent <code>/dreaming on|off</code> changes and treat missing gateway client scopes as unprivileged instead of silently allowing config writes. (#63872) Thanks @mbelinky.</li>
-<li>Gateway/pairing: prefer explicit QR bootstrap auth over earlier Tailscale auth classification so iOS <code>/pair qr</code> silent bootstrap pairing does not fall through to <code>pairing required</code>. (#59232) Thanks @ngutman.</li>
-<li>Browser/control: auto-generate browser-control auth tokens for <code>none</code> and <code>trusted-proxy</code> modes, and route browser auth/profile/doctor helpers through the public browser plugin facades. (#63280, #63957) Thanks @pgondhi987.</li>
-<li>Browser/act: centralize <code>/act</code> request normalization and execution dispatch while adding stable machine-readable route-level error codes for invalid requests, selector misuse, evaluate-disabled gating, target mismatch, and existing-session unsupported actions. (#63977) Thanks @joshavant.</li>
-<li>Security/QQBot: enforce media storage boundaries for all outbound local file paths and route image-size probes through SSRF-guarded media fetching instead of raw <code>fetch()</code>. (#63271, #63495) Thanks @pgondhi987.</li>
-<li>Channel setup: ignore workspace plugin shadows when resolving trusted channel setup catalog entries so onboarding and setup flows keep using the bundled, trusted setup contract.</li>
-<li>Gateway/memory startup: load the explicitly selected memory-slot plugin during gateway startup, while keeping restrictive allowlists and implicit default memory slots from auto-starting unrelated memory plugins. (#64423) Thanks @EronFan.</li>
-<li>Config/plugins: let config writes keep disabled plugin entries without forcing required plugin config schemas or crashing raw plugin validation, and avoid re-activating plugin registry state during schema checks. (#54971, #63296) Thanks @fuller-stack-dev.</li>
-<li>Config validation: surface the actual offending field for strict-schema union failures in bindings, including top-level unexpected keys on the matching ACP branch. (#40841) Thanks @Hollychou924.</li>
-<li>Wizard/plugin config: coerce integer-typed plugin config fields from interactive text input so integer schema values persist as numbers instead of failing validation. (#63346) Thanks @jalehman.</li>
-<li>Daemon/gateway install: preserve safe custom service env vars on forced reinstall, merge prior custom PATH segments behind the managed service PATH, and stop removed managed env keys from persisting as custom carryover. (#63136) Thanks @WarrenJones.</li>
-<li>Cron/scheduling: treat <code>nextRunAtMs <= 0</code> as invalid across cron update, maintenance, timer, and stale-delivery paths so corrupted zero timestamps self-heal instead of causing immediate runs or skipped deliveries. (#63507) Thanks @WarrenJones.</li>
-<li>Cron/auth: resolve auth profiles consistently for isolated cron jobs so scheduled runs use the same configured provider credentials as interactive sessions. (#62797) Thanks @neeravmakwana.</li>
-<li>Tasks: let <code>openclaw tasks cancel</code> cancel stuck background tasks that never reached a normal terminal state. (#62506) Thanks @neeravmakwana.</li>
-<li>Sessions/model selection: preserve catalog-backed session model labels, provider-qualified context limits, and already-qualified session model refs when catalog metadata is unavailable, so model selection and memory/context budgets survive reloads without bogus provider prefixes. (#61382, #62493) Thanks @Mule-ME.</li>
-<li>Status: show configured fallback models in <code>/status</code> and shared session status cards so per-agent fallback configuration is visible before a live failover happens. (#33111) Thanks @AnCoSONG.</li>
-<li><code>/context detail</code> now compares the tracked prompt estimate with cached context usage and surfaces untracked provider/runtime overhead when present. (#28391) Thanks @ImLukeF.</li>
-<li>Gateway/sessions: scope bare <code>sessions.create</code> aliases like <code>main</code> to the requested agent while preserving the canonical <code>global</code> and <code>unknown</code> sentinel keys. (#58207) Thanks @jalehman.</li>
-<li>Gateway/session reset: emit the typed <code>before_reset</code> hook for gateway <code>/new</code> and <code>/reset</code>, preserving reset-hook behavior even when the previous transcript has already been archived. (#53872) Thanks @VACInc.</li>
-<li>Plugins/commands: pass the active host <code>sessionKey</code> into plugin command contexts, and include <code>sessionId</code> when it is already available from the active session entry, so bundled and third-party commands can resolve the current conversation reliably. (#59044) Thanks @jalehman.</li>
-<li>Agents/auth: honor <code>models.providers.*.authHeader</code> for pi embedded runner model requests by injecting <code>Authorization: Bearer <apiKey></code> when requested. (#54390) Thanks @lndyzwdxhs.</li>
-<li>Claude CLI: clear inherited Anthropic auth/header environment aliases before spawning Claude Code and add sanitized CLI backend auth-env diagnostics for debugging gateway-run provider selection.</li>
-<li>Agents/failover: classify AbortError and stream-abort messages as timeout so Ollama NDJSON stream aborts stop showing <code>reason=unknown</code> in model fallback logs. (#58324) Thanks @yelog.</li>
-<li>Fireworks/FirePass: disable Kimi K2.5 Turbo reasoning output by forcing thinking off on the FirePass path and hardening the provider wrapper so hidden reasoning no longer leaks into visible replies. (#63607) Thanks @frankekn.</li>
-<li>Discord: update Carbon to v0.15.0. Thanks @thewilloftheshadow.</li>
-<li>Config/Discord: coerce safe integer numeric Discord IDs to strings during config validation, keep unsafe or precision-losing numeric snowflakes rejected, and align <code>openclaw doctor</code> repair guidance with the same fail-closed behavior. (#45125) Thanks @moliendocode.</li>
-<li>BlueBubbles/config: accept <code>enrichGroupParticipantsFromContacts</code> in the core strict config schema so gateways no longer fail validation or startup when the BlueBubbles plugin writes that field. (#56889) Thanks @zqchris.</li>
-<li>Feishu/webhooks: read webhook bodies through the pre-auth guard so unauthenticated webhook traffic stays under the same body budget as other protected channel ingress paths.</li>
-<li>Tools/web_fetch: add an opt-in <code>tools.web.fetch.ssrfPolicy.allowRfc2544BenchmarkRange</code> config so fake-IP proxy environments that resolve public sites into <code>198.18.0.0/15</code> can use <code>web_fetch</code> without weakening the default SSRF block. (#61830) Thanks @xing-xing-coder.</li>
-<li>Dreaming/cron: reconcile managed dreaming cron from startup config and runtime lifecycle changes, but only recover managed dreaming cron state during heartbeat-triggered dreaming checks so ordinary chat traffic does not recreate removed jobs. (#63873, #63929, #63938) Thanks @mbelinky.</li>
-<li>Memory/lancedb: accept <code>dreaming</code> config when <code>memory-lancedb</code> owns the memory slot so Dreaming surfaces can read slot-owner settings without schema rejection. (#63874) Thanks @mbelinky.</li>
-<li>Control UI/dreaming: keep the Dreaming trace area contained and scrollable so overlays no longer cover tabs or blow out the page layout. (#63875) Thanks @mbelinky.</li>
-<li>Dreaming/narrative: harden request-scoped diary fallback so scheduled dreaming only falls back on the dedicated subagent-runtime error, stop trusting spoofable raw error-code objects, and avoid leaking workspace paths when local fallback writes fail. (#64156) Thanks @mbelinky.</li>
-<li>Dreaming/diary: add idempotent narrative subagent runs, preserve restrictive <code>DREAMS.md</code> permissions during atomic writes, and surface temp cleanup failures so repeated sweeps do not double-run the same narrative request or silently weaken diary safety. (#63876) Thanks @mbelinky.</li>
-<li>Heartbeats/sessions: remove stale accumulated isolated heartbeat session keys when the next tick converges them back to the canonical sibling, so repaired sessions stop showing orphaned <code>:heartbeat:heartbeat</code> variants in session listings. (#59606) Thanks @rogerdigital.</li>
-<li>Gateway/run cleanup: fix stale run-context TTL cleanup so the new maintenance sweep resets orphaned run sequence state and prevents unbounded run-context growth. (#52731) Thanks @artwalker.</li>
-<li>UI/compaction: keep the compaction indicator in a retry-pending state until the run actually finishes, so the UI does not show <code>Context compacted</code> before compaction actually finishes. (#55132) Thanks @mpz4life.</li>
-<li>Cron/tool schemas: keep cron tool schemas strict-model-friendly while still preserving <code>failureAlert=false</code>, nullable <code>agentId</code>/<code>sessionKey</code>, and flattened add/update recovery for the newly exposed cron job fields. (#55043) Thanks @brunolorente.</li>
-<li>Git metadata: read commit ids from packed refs as well as loose refs so version and status metadata stay accurate after repository maintenance. (#63943)</li>
-<li>Gateway: keep <code>commands.list</code> skill entries categorized under tools and include provider-aware plugin <code>nativeName</code> metadata even when <code>scope=text</code>, so remote clients can group skills correctly and map text-surface plugin commands back to native aliases. (#64147)</li>
-<li>TUI: reset footer activity to idle when switching sessions so a stale streaming indicator cannot persist after the selection changes. (#63988) Thanks @neeravmakwana.</li>
-<li>Claude CLI: stop marking spawned Claude Code runs as host-managed so they keep using normal CLI subscription behavior. (#64023) Thanks @Alex-Alaniz.</li>
-<li>Codex auth: brand Codex OAuth flows as OpenClaw in user-visible auth prompts and diagnostics.</li>
-<li>Gateway/pairing: fail closed for paired device records that have no device tokens, and reject pairing approvals whose requested scopes do not match the requested device roles.</li>
-<li>ACP/gateway chat: classify lifecycle errors before forwarding them to ACP clients so refusals use ACP's refusal stop reason while transient backend errors continue to finish as normal turns.</li>
-<li>Claude CLI/skills: pass eligible OpenClaw skills into CLI runs, including native Claude Code skill resolution via a temporary plugin plus per-run skill env/API key injection. (#62686, #62723) Thanks @zomars.</li>
-<li>Discord: keep generated auto-thread names working with reasoning models by giving title generation enough output budget for thinking plus visible title text. (#64172) Thanks @hanamizuki.</li>
-<li>Heartbeat: ignore doc-only Markdown fence markers in the default <code>HEARTBEAT.md</code> template so comment-only heartbeat scaffolds skip API calls again. (#61690, #63434) Thanks @ravyg.</li>
-<li>Reply/skills: keep resolved skill and memory secret config stable through embedded reply runs so raw SecretRefs in secondary skill settings no longer crash replies when the gateway already has the live env. (#64249) Thanks @mbelinky.</li>
-<li>Dreaming/startup: keep plugin-registered startup hooks alive across workspace hook reloads and include dreaming startup owners in the gateway startup plugin scope, so managed Dreaming cron registration comes back reliably after gateway boot. (#62327, #64258) Thanks @mbelinky.</li>
-<li>Plugins: treat duplicate <code>registerService</code> calls from the same plugin id as idempotent so snapshot and activation loads no longer emit spurious <code>service already registered</code> diagnostics. (#62033, #64128) Thanks @ly85206559.</li>
-<li>Discord/TTS: route auto voice replies through the native voice-note path so Discord receives Opus voice messages instead of regular audio attachments. (#64096) Thanks @LiuHuaize.</li>
-<li>Config/plugins: use plugin-owned command alias metadata when <code>plugins.allow</code> contains runtime command names like <code>dreaming</code>, and point users at the owning plugin instead of stale plugin-not-found guidance. (#64191, #64242) Thanks @feiskyer.</li>
-<li>Agents/Gemini: strip orphaned <code>required</code> entries from Gemini tool schemas so provider validation no longer rejects tools after schema cleanup or union flattening. (#64284) Thanks @xxxxxmax.</li>
-<li>Assistant text: strip Qwen-style XML tool call payloads from visible replies so web and channel messages no longer show raw <code><tool_call><function=...></code> output. (#63999, #64214) Thanks @MoerAI.</li>
-<li>Daemon/gateway: prevent systemd restart storms on configuration errors by exiting with <code>EX_CONFIG</code> and adding generated unit restart-prevention guards. (#63913) Thanks @neo1027144-creator.</li>
-<li>Agents/exec: prevent gateway crash ("Agent listener invoked outside active run") when a subagent exec tool produces stdout/stderr after the agent run has ended or been aborted. (#62821) Thanks @openperf.</li>
-<li>Gateway/OpenAI compat: return real <code>usage</code> for non-stream <code>/v1/chat/completions</code> responses, emit the final usage chunk when <code>stream_options.include_usage=true</code>, and bound usage-gated stream finalization after lifecycle end. (#62986) Thanks @Lellansin.</li>
-<li>Matrix/migration: keep packaged warning-only crypto migrations from being misclassified as actionable when only helper chunks are present, so startup and doctor stay on the warning-only path instead of creating unnecessary migration snapshots. (#64373) Thanks @gumadeiras.</li>
-<li>Matrix/ACP thread bindings: preserve canonical room casing and parent conversation routing during ACP session spawn so mixed-case room ids bind correctly from top-level rooms and existing Matrix threads. (#64343) Thanks @gumadeiras.</li>
-<li>Agents/subagents: deduplicate delivered completion announces so retry or re-entry cleanup does not inject duplicate internal-context completion turns into the parent session. (#61525) Thanks @100yenadmin.</li>
-<li>Agents/exec: keep sandboxed <code>tools.exec.host=auto</code> sessions from honoring per-call <code>host=node</code> or <code>host=gateway</code> overrides while a sandbox runtime is active, and stop advertising node routing in that state so exec stays on the sandbox host. (#63880)</li>
-<li>Agents/subagents: preserve archived delete-mode runs until <code>sessions.delete</code> succeeds and prevent overlapping archive sweeps from duplicating in-flight cleanup attempts. (#61801) Thanks @100yenadmin.</li>
-<li>Cron/isolated agent: run scheduled agent turns as non-owner senders so owner-only tools stay unavailable during cron execution. (#63878)</li>
-<li>Discord/sandbox: include <code>image</code> in sandbox media param normalization so Discord event cover images cannot bypass sandbox path rewriting. (#64377) Thanks @mmaps.</li>
-<li>Agents/exec: extend exec completion detection to cover local background exec formats so the owner-downgrade fires correctly for all exec paths. (#64376) Thanks @mmaps.</li>
-<li>Security/dependencies: pin axios to 1.15.0 and add a plugin install dependency denylist that blocks known malicious packages before install. (#63891) Thanks @mmaps.</li>
-<li>Browser/security: apply three-phase interaction navigation guard to pressKey and type(submit) so delayed JS redirects from keypress cannot bypass SSRF policy. (#63889) Thanks @mmaps.</li>
-</ul>
-<ul>
-<li>Browser/security: guard existing-session Chrome MCP interaction routes with SSRF post-checks so delayed navigation from click, type, press, and evaluate cannot bypass the configured policy. (#64370) Thanks @eleqtrizit.</li>
-<li>Browser/security: default browser SSRF policy to strict mode so unconfigured installs block private-network navigation, and align external-content marker span mapping so ZWS-injected boundary spoofs are fully sanitized. (#63885) Thanks @eleqtrizit.</li>
-<li>Browser/security: apply SSRF navigation policy to subframe document navigations so iframe-targeted private-network hops are blocked without quarantining the parent page. (#64371) Thanks @eleqtrizit.</li>
-<li>Hooks/security: mark agent hook system events as untrusted and sanitize hook display names before cron metadata reuse. (#64372) Thanks @eleqtrizit.</li>
-<li>Daemon/launchd: keep <code>openclaw gateway stop</code> persistent without uninstalling the macOS LaunchAgent, re-enable it on explicit restart or repair, and harden launchd label handling. (#64447) Thanks @ngutman.</li>
-<li>Plugins/context engines: preserve <code>plugins.slots.contextEngine</code> through normalization and keep explicitly selected workspace context-engine plugins enabled, so loader diagnostics and plugin activation stop dropping that slot selection. (#64192) Thanks @hclsys.</li>
-<li>Heartbeat: stop top-level <code>interval:</code> and <code>prompt:</code> fields outside the <code>tasks:</code> block from bleeding into the last parsed heartbeat task. (#64488) Thanks @Rahulkumar070.</li>
-<li>Agents/OpenAI replay: preserve malformed function-call arguments in stored assistant history, avoid double-encoding preserved raw strings on replay, and coerce replayed string args back to objects at Anthropic and Google provider boundaries. (#61956) Thanks @100yenadmin.</li>
-<li>Heartbeat/config: accept and honor <code>agents.defaults.heartbeat.timeoutSeconds</code> and per-agent heartbeat timeout overrides for heartbeat agent turns. (#64491) Thanks @cedillarack.</li>
-<li>CLI/devices: make implicit <code>openclaw devices approve</code> selection preview-only and require approving the exact request ID, preventing latest-request races during device pairing. (#64160) Thanks @coygeek.</li>
-<li>Media/security: honor sender-scoped <code>toolsBySender</code> policy for outbound host-media reads so denied senders cannot trigger host file disclosure via attachment hydration. (#64459) Thanks @eleqtrizit.</li>
-<li>Browser/security: reject strict-policy hostname navigation unless the hostname is an explicit allowlist exception or IP literal, and route CDP HTTP discovery through the pinned SSRF fetch path. (#64367) Thanks @eleqtrizit.</li>
-<li>Models/vLLM: ignore empty <code>tool_calls</code> arrays from reasoning-model OpenAI-compatible replies, reset false <code>toolUse</code> stop reasons when no actual tool calls were parsed, and stop sending <code>tool_choice</code> unless tools are present so vLLM reasoning responses no longer hang indefinitely. (#61197, #61534) Thanks @balajisiva.</li>
-<li>Heartbeat/scheduling: spread interval heartbeats across stable per-agent phases derived from gateway identity, so provider traffic is distributed more uniformly across the configured interval instead of clustering around startup-relative times. (#64560) Thanks @odysseus0.</li>
-</ul>
-<p><a href="https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md">View full changelog</a></p>
-]]></description>
-            <enclosure url="https://github.com/openclaw/openclaw/releases/download/v2026.4.10/OpenClaw-2026.4.10.zip" length="47259509" type="application/octet-stream" sparkle:edSignature="XY9FHxx09r2O9rlFs3t5UV9Zk2rGXSpWw5InazJhb661kgp6OKiOrrNTV631b2StWze5tnSEPXakkOCXq7O6DQ=="/>
-        </item>
         <item>
             <title>2026.4.9</title>
             <pubDate>Thu, 09 Apr 2026 02:38:08 +0000</pubDate>
@@ -246,5 +59,135 @@
 ]]></description>
             <enclosure url="https://github.com/openclaw/openclaw/releases/download/v2026.4.9/OpenClaw-2026.4.9.zip" length="25336730" type="application/octet-stream" sparkle:edSignature="zFKTcKpejPyGEHj6Bdop3EBDfRrHyQMtJzrpVKsIkBq3I/jbTNvsxQveKEy9r7dqkZVsldFYv7eSunP3SUmaAw=="/>
         </item>
+        <item>
+            <title>2026.4.8</title>
+            <pubDate>Wed, 08 Apr 2026 06:12:50 +0000</pubDate>
+            <link>https://raw.githubusercontent.com/openclaw/openclaw/main/appcast.xml</link>
+            <sparkle:version>2026040890</sparkle:version>
+            <sparkle:shortVersionString>2026.4.8</sparkle:shortVersionString>
+            <sparkle:minimumSystemVersion>15.0</sparkle:minimumSystemVersion>
+            <description><![CDATA[<h2>OpenClaw 2026.4.8</h2>
+<h3>Fixes</h3>
+<ul>
+<li>Telegram/setup: load setup and secret contracts through packaged top-level sidecars so installed npm builds no longer try to import missing <code>dist/extensions/telegram/src/*</code> files during gateway startup.</li>
+<li>Bundled channels/setup: load shared secret contracts through packaged top-level sidecars across BlueBubbles, Feishu, Google Chat, IRC, Matrix, Mattermost, Microsoft Teams, Nextcloud Talk, Slack, and Zalo so installed npm builds no longer rely on missing <code>dist/extensions/*/src/*</code> files during gateway startup.</li>
+<li>Bundled plugins: align packaged plugin compatibility metadata with the release version so bundled channels and providers load on OpenClaw 2026.4.8.</li>
+<li>Agents/progress: keep <code>update_plan</code> available for OpenAI-family runs while returning compact success payloads and allowing <code>tools.experimental.planTool=false</code> to opt out.</li>
+<li>Agents/exec: keep <code>/exec</code> current-default reporting aligned with real runtime behavior so <code>host=auto</code> sessions surface the correct host-aware fallback policy (<code>full/off</code> on gateway or node, <code>deny/off</code> on sandbox) instead of stale stricter defaults.</li>
+<li>Slack: honor ambient HTTP(S) proxy settings for Socket Mode WebSocket connections, including NO_PROXY exclusions, so proxy-only deployments can connect without a monkey patch. (#62878) Thanks @mjamiv.</li>
+<li>Slack/actions: pass the already resolved read token into <code>downloadFile</code> so SecretRef-backed bot tokens no longer fail after a raw config re-read. (#62097) Thanks @martingarramon.</li>
+<li>Network/fetch guard: skip target DNS pinning when trusted env-proxy mode is active so proxy-only sandboxes can let the trusted proxy resolve outbound hosts. (#59007) Thanks @cluster2600.</li>
+</ul>
+<p><a href="https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md">View full changelog</a></p>
+]]></description>
+            <enclosure url="https://github.com/openclaw/openclaw/releases/download/v2026.4.8/OpenClaw-2026.4.8.zip" length="25324810" type="application/octet-stream" sparkle:edSignature="aogl3hJf+FeRvQj0W4WDGMQnIRPpxXPQam50U7SBT3ljA1CeSbIGsnaj20aLF0Qc9DikPEXt5AEg7LMOen4+BQ=="/>
+        </item>
+        <item>
+            <title>2026.4.7</title>
+            <pubDate>Wed, 08 Apr 2026 02:54:26 +0000</pubDate>
+            <link>https://raw.githubusercontent.com/openclaw/openclaw/main/appcast.xml</link>
+            <sparkle:version>2026040790</sparkle:version>
+            <sparkle:shortVersionString>2026.4.7</sparkle:shortVersionString>
+            <sparkle:minimumSystemVersion>15.0</sparkle:minimumSystemVersion>
+            <description><![CDATA[<h2>OpenClaw 2026.4.7</h2>
+<h3>Changes</h3>
+<ul>
+<li>CLI/infer: add a first-class <code>openclaw infer ...</code> hub for provider-backed inference workflows across model, media, web, and embedding tasks. Thanks @Takhoffman.</li>
+<li>Tools/media generation: auto-fallback across auth-backed image, music, and video providers by default, preserve intent during provider switches, remap size/aspect/resolution/duration hints to the closest supported option, and surface provider capabilities plus mode-aware video-to-video support.</li>
+<li>Memory/wiki: restore the bundled <code>memory-wiki</code> stack with plugin, CLI, sync/query/apply tooling, memory-host integration, structured claim/evidence fields, compiled digest retrieval, claim-health linting, contradiction clustering, staleness dashboards, and freshness-weighted search. Thanks @vincentkoc.</li>
+<li>Plugins/webhooks: add a bundled webhook ingress plugin so external automation can create and drive bound TaskFlows through per-route shared-secret endpoints. (#61892) Thanks @mbelinky.</li>
+<li>Gateway/sessions: add persisted compaction checkpoints plus Sessions UI branch/restore actions so operators can inspect and recover pre-compaction session state. (#62146) Thanks @scoootscooob.</li>
+<li>Compaction: add pluggable compaction provider registry so plugins can replace the built-in summarization pipeline. Configure via <code>agents.defaults.compaction.provider</code>; falls back to LLM summarization on provider failure. (#56224) Thanks @DhruvBhatia0.</li>
+<li>Agents/system prompt: add <code>agents.defaults.systemPromptOverride</code> for controlled prompt experiments plus heartbeat prompt-section controls so heartbeat runtime behavior can stay enabled without injecting heartbeat instructions every turn.</li>
+<li>Providers/Google: add Gemma 4 model support and keep Google fallback resolution on the requested provider path so native Google Gemma routes work again. (#61507) Thanks @eyjohn.</li>
+<li>Providers/Google: preserve explicit thinking-off semantics for Gemma 4 while still enabling Gemma reasoning support in compatibility wrappers. (#62127) Thanks @romgenie.</li>
+<li>Providers/Arcee AI: add a bundled Arcee AI provider plugin with Trinity catalog entries, OpenRouter support, and updated onboarding/auth guidance. (#62068) Thanks @arthurbr11.</li>
+<li>Providers/Anthropic: restore Claude CLI as the preferred local Anthropic path in onboarding, model-auth guidance, doctor flows, and Docker Claude CLI live lanes again.</li>
+<li>Providers/Ollama: detect vision capability from the <code>/api/show</code> response and set image input on models that support it so Ollama vision models accept image attachments. (#62193) Thanks @BruceMacD.</li>
+<li>Memory/dreaming: ingest redacted session transcripts into the dreaming corpus with per-day session-corpus notes, cursor checkpointing, and promotion/doctor support. (#62227) Thanks @vignesh07.</li>
+<li>Providers/inferrs: add string-content compatibility for stricter OpenAI-compatible chat backends, document <code>inferrs</code> setup with a full config example, and add troubleshooting guidance for local backends that pass direct probes but fail on full agent-runtime prompts.</li>
+<li>Agents/context engine: expose prompt-cache runtime context to context engines and keep current-turn prompt-cache usage aligned with the active attempt instead of stale prior-turn assistant state. (#62179) Thanks @jalehman.</li>
+<li>Plugin SDK/context engines: pass <code>availableTools</code> and <code>citationsMode</code> into <code>assemble()</code>, and expose memory-artifact and memory-prompt seams so companion plugins and non-legacy context engines can consume active memory state without reaching into internals. Thanks @vincentkoc.</li>
+<li>ACP/ACPX plugin: bump the bundled <code>acpx</code> pin to <code>0.5.1</code> so plugin-local installs and strict version checks pick up the latest published runtime release. (#62148) Thanks @onutc.</li>
+<li>Discord/events: allow <code>event-create</code> to accept a cover image URL or local file path, load and validate PNG/JPG/GIF event cover media, and pass the encoded image payload through Discord admin action/runtime paths. (#60883) Thanks @bittoby.</li>
+</ul>
+<h3>Fixes</h3>
+<ul>
+<li>CLI/infer: keep provider-backed infer behavior aligned with actual runtime execution by fixing explicit TTS override handling, profile-aware gateway TTS prefs resolution, per-request transcription <code>prompt</code>/<code>language</code> overrides, image output MIME/extension mismatches, configured web-search fallback behavior, and agent-vs-CLI web-search execution drift.</li>
+<li>Plugins/media: when <code>plugins.allow</code> is set, capability fallback now merges bundled capability plugin ids into the allowlist (not only <code>plugins.entries</code>), so media understanding providers such as OpenAI-compatible STT load for voice transcription without requiring <code>openai</code> in <code>plugins.allow</code>. (#62205) Thanks @neeravmakwana.</li>
+<li>Agents/history and replies: buffer phaseless OpenAI WS text until a real assistant phase arrives, keep replay and SSE history sequence tracking aligned, hide commentary and leaked tool XML from user-visible history, and keep history-based follow-up replies on <code>final_answer</code> text only. (#61729, #61747, #61829, #61855, #61954) Thanks @100yenadmin and contributors.</li>
+<li>Control UI: show <code>/tts</code> audio replies in webchat, detect mistaken <code>?token=</code> auth links with the correct <code>#token=</code> hint, and keep Copy, Canvas, and mobile exec-approval UI from covering chat content on narrow screens. (#54842, #61514, #61598) Thanks @neeravmakwana.</li>
+<li>iOS/gateway: replace string-matched connection error UI with structured gateway connection problems, preserve actionable pairing/auth failures over later generic disconnect noise, and surface reusable problem banners and details across onboarding, settings, and root status surfaces. (#62650) Thanks @ngutman.</li>
+<li>TUI: route <code>/status</code> through the shared session-status command, keep commentary hidden in history, strip raw envelope metadata from async command notices, preserve fallback streaming before per-attempt failures finalize, and restore Kitty keyboard state on exit or fatal crashes. (#49130, #59985, #60043, #61463) Thanks @biefan and contributors.</li>
+<li>iOS/Watch exec approvals: keep Apple Watch review and approval recovery working while the iPhone is locked or backgrounded, including reconnect recovery, pending approval persistence, notification cleanup, and APNs-backed watch refresh recovery. (#61757) Thanks @ngutman.</li>
+<li>Agents/context overflow: combine oversized and aggregate tool-result recovery in one pass and restore a total-context overflow backstop so recoverable sessions retry instead of failing early. (#61651) Thanks @Takhoffman.</li>
+<li>Auth/OpenAI Codex OAuth: reload fresh on-disk credentials inside the locked refresh path and retry once after <code>refresh_token_reused</code> rotates only the stored refresh token, so relogin/restart recovery stops getting stuck on stale cached auth state. Thanks @owen-ever.</li>
+<li>Auth/OpenAI Codex OAuth: keep native <code>/model ...@profile</code> selections on the target session and honor explicit user-locked auth profiles even when per-agent auth order excludes them. (#62744) Thanks @jalehman.</li>
+<li>Providers/Anthropic: preserve thinking blocks for Claude Opus 4.5+, Sonnet 4.5+, and newer Claude 4-family models so prompt-cache prefixes keep matching, and skip <code>service_tier</code> injection on OAuth-authenticated stream wrapper requests so Claude OAuth streaming stops failing with HTTP 401. (#60356, #61793)</li>
+<li>Agents/Claude CLI: surface nested API error messages from structured CLI output so billing/auth/provider failures show the real provider error instead of an opaque CLI failure.</li>
+<li>Agents/exec: preserve explicit <code>host=node</code> routing under elevated defaults when <code>tools.exec.host=auto</code>, fail loud on invalid elevated cross-host overrides, and keep <code>strictInlineEval</code> commands blocked after approval timeouts instead of falling through to automatic execution. (#61739) Thanks @obviyus.</li>
+<li>Nodes/exec approvals: keep <code>host=node</code> POSIX transport shell wrappers (<code>/bin/sh -lc ...</code>) aligned with inner-command allowlist analysis so allowlisted scripts stop prompting unnecessarily, while Windows <code>cmd.exe</code> wrapper runs stay approval-gated. (#62401) Thanks @ngutman.</li>
+<li>Nodes/exec approvals: keep Windows <code>cmd.exe /c</code> wrapper runs approval-gated even when <code>env</code> carriers, including env-assignment carriers, wrap the shell invocation. (#62439) Thanks @ngutman.</li>
+<li>Gateway tool/exec config: block model-facing <code>gateway config.apply</code> and <code>config.patch</code> writes from changing exec approval paths such as <code>safeBins</code>, <code>safeBinProfiles</code>, <code>safeBinTrustedDirs</code>, and <code>strictInlineEval</code>, while still allowing unchanged structured values through. (#62001) Thanks @eleqtrizit.</li>
+<li>Host exec/env sanitization: block dangerous Java, Rust, Cargo, Git, Kubernetes, cloud credential, config-path, and Helm env overrides so host-run tools cannot be redirected to attacker-chosen code, config, credentials, or repository state. (#59119, #62002, #62291) Thanks @eleqtrizit and contributors.</li>
+<li>Commands/allowlist: require owner authorization for <code>/allowlist add</code> and <code>/allowlist remove</code> before channel resolution, so non-owner but command-authorized senders can no longer persistently rewrite allowlist policy state. (#62383) Thanks @pgondhi987.</li>
+<li>Feishu/docx uploads: honor <code>tools.fs.workspaceOnly</code> for local <code>upload_file</code> and <code>upload_image</code> paths by forwarding workspace-constrained <code>localRoots</code> into the media loader, so docx uploads can no longer read host-local files outside the workspace when workspace-only mode is active. (#62369) Thanks @pgondhi987.</li>
+<li>Network/fetch guard: drop request bodies and body-describing headers on cross-origin <code>307</code> and <code>308</code> redirects by default, so attacker-controlled redirect hops cannot receive secret-bearing POST payloads from SSRF-guarded fetch flows unless a caller explicitly opts in. (#62357) Thanks @pgondhi987.</li>
+<li>Browser/SSRF: treat main-frame <code>document</code> redirect hops as navigations even when Playwright does not flag them as <code>isNavigationRequest()</code>, so strict private-network blocking still stops forbidden redirect pivots before the browser reaches the internal target. (#62355) Thanks @pgondhi987.</li>
+<li>Browser/node invoke: block persistent browser profile create, reset, and delete mutations through <code>browser.proxy</code> on both gateway-forwarded <code>node.invoke</code> and the node-host proxy path, even when no profile allowlist is configured. (#60489)</li>
+<li>Gateway/node pairing: require a fresh pairing request when a previously paired node reconnects with additional declared commands, and keep the live session pinned to the earlier approved command set until the upgrade is approved. (#62658) Thanks @eleqtrizit.</li>
+<li>Gateway/auth: invalidate existing shared-token and password WebSocket sessions when the configured secret rotates, so stale authenticated sockets cannot stay attached after token or password changes. (#62350) Thanks @pgondhi987.</li>
+<li>MS Teams/security: validate file-consent upload URLs against HTTPS, Microsoft/SharePoint host allowlists, and private-IP DNS checks before uploading attachments, blocking SSRF-style consent-upload abuse. (#23596)</li>
+<li>Media/base64 decode guards: enforce byte limits before decoding missed base64-backed Teams, Signal, QQ Bot, and image-tool payloads so oversized inbound media and data URLs no longer bypass pre-decode size checks. (#62007) Thanks @eleqtrizit.</li>
+<li>Runtime event trust: mark background <code>notifyOnExit</code> summaries, ACP parent-stream relays, and wake-hook payloads as untrusted system events so lower-trust runtime output no longer re-enters later turns as trusted <code>System:</code> text. (#62003)</li>
+<li>Auto-reply/media: allow managed generated-media <code>MEDIA:</code> paths from normal reply text again while still blocking arbitrary host-local media and document paths, so generated media keep delivering without reopening host-path injection holes.</li>
+<li>Gateway/status and containers: auto-bind to <code>0.0.0.0</code> inside Docker and Podman environments, and probe local TLS gateways over <code>wss://</code> with self-signed fingerprint forwarding so container startup and loopback TLS status checks work again. (#61818, #61935) Thanks @openperf and contributors.</li>
+<li>Gateway/OpenAI-compatible HTTP: abort in-flight <code>/v1/chat/completions</code> and <code>/v1/responses</code> turns when clients disconnect so abandoned HTTP requests stop wasting agent runtime. (#54388) Thanks @Lellansin.</li>
+<li>macOS/gateway version: strip trailing commit metadata from CLI version output before semver parsing so the Mac app recognizes installed gateway versions like <code>OpenClaw 2026.4.2 (d74a122)</code> again. (#61111) Thanks @oliviareid-svg.</li>
+<li>Sessions/model selection: resolve the explicitly selected session model separately from runtime fallback resolution so session status and live model switching stay aligned with the chosen model.</li>
+<li>Discord/ACP bindings: canonicalize DM conversation identity across inbound messages, component interactions, native commands, and current-conversation binding resolution so <code>--bind here</code> in Discord DMs keeps routing follow-up replies to the bound agent instead of falling back to the default agent.</li>
+<li>Discord: recover forwarded referenced message text and attachments when snapshots are missing, use <code>ws://</code> again for gateway monitor sockets, stop forcing a hardcoded temperature for Codex-backed auto-thread titles, and harden voice receive recovery so rapid speaker restarts keep their next utterance. (#41536, #61670) Thanks @artwalker and contributors.</li>
+<li>Slack/thread mentions: add <code>channels.slack.thread.requireExplicitMention</code> so Slack channels that already require mentions can also require explicit <code>@bot</code> mentions inside bot-participated threads. (#58276) Thanks @praktika-engineer.</li>
+<li>Slack/threading: keep legacy thread stickiness for real replies when older callers omit <code>isThreadReply</code>, while still honoring <code>replyToMode</code> for Slack's auto-created top-level <code>thread_ts</code>. (#61835) Thanks @kaonash.</li>
+<li>Slack/media: keep attachment downloads on the SSRF-guarded dispatcher path so Slack media fetching works on Node 22 without dropping pinned transport enforcement. (#62239) Thanks @openperf.</li>
+<li>Matrix/onboarding: add an invite auto-join setup step with explicit off warnings and strict stable-target validation so new Matrix accounts stop silently ignoring invited rooms and fresh DM-style invites unless operators opt in. (#62168) Thanks @gumadeiras.</li>
+<li>Matrix/formatting: preserve multi-paragraph and loose-list rendering in Element so numbered and bulleted Markdown keeps their content attached to the correct list item. (#60997) Thanks @gucasbrg.</li>
+<li>Telegram/doctor: keep top-level access-control fallback in place during multi-account normalization while still promoting legacy default auth into <code>accounts.default</code>, so existing named bots keep inherited allowlists without dropping the legacy default bot. (#62263) Thanks @obviyus.</li>
+<li>Plugins/loaders: centralize bundled <code>dist/**</code> Jiti native-load policy and keep channel, public-surface, facade, and config-metadata loader seams off native Jiti on Windows so onboarding and configure flows stop tripping <code>ERR_UNSUPPORTED_ESM_URL_SCHEME</code>. (#62286) Thanks @chen-zhang-cs-code.</li>
+<li>Plugins/channels: keep bundled channel artifact and secret-contract loading stable under lazy loading, preserve plugin-schema defaults during install, and fix Windows <code>file://</code> plus native-Jiti plugin loader paths so onboarding, doctor, <code>openclaw secret</code>, and bundled plugin installs work again. (#61832, #61836, #61853, #61856) Thanks @Zeesejo and contributors.</li>
+<li>Plugins/ClawHub: verify downloaded plugin archives against version metadata SHA-256, fail closed when archive integrity metadata is missing or malformed, and tighten fallback ZIP verification so plugin installs cannot proceed on mismatched or incomplete ClawHub package metadata. (#60517) Thanks @mappel-nv.</li>
+<li>Plugins/provider hooks: stop recursive provider snapshot loads from overflowing the stack during plugin initialization, while still preserving cached nested provider-hook results. (#61922, #61938, #61946, #61951)</li>
+<li>Docker/plugins: stop forcing bundled plugin discovery to <code>/app/extensions</code> in runtime images so packaged installs use compiled <code>dist/extensions</code> artifacts again and Node 24 containers do not boot through source-only plugin entry paths. Fixes #62044. (#62316) Thanks @gumadeiras.</li>
+<li>Providers/Ollama: honor the selected provider's <code>baseUrl</code> during streaming so multi-Ollama setups stop routing every stream to the first configured Ollama endpoint. (#61678)</li>
+<li>Providers/Ollama: stop warning that Ollama could not be reached when discovery only sees empty default local stubs, while still keeping real explicit Ollama overrides loud when the endpoint is unreachable.</li>
+<li>Providers/xAI: recognize <code>api.grok.x.ai</code> as an xAI-native endpoint again and keep legacy <code>x_search</code> auth resolution working so older xAI web-search configs continue to load. (#61377) Thanks @jjjojoj.</li>
+<li>Providers/Mistral: send <code>reasoning_effort</code> for <code>mistral/mistral-small-latest</code> (Mistral Small 4) with thinking-level mapping, and mark the catalog entry as reasoning-capable so adjustable reasoning matches Mistral’s Chat Completions API. (#62162) Thanks @neeravmakwana.</li>
+<li>OpenAI TTS/Groq: send <code>wav</code> to Groq-compatible speech endpoints, honor explicit <code>responseFormat</code> overrides on OpenAI-compatible paths, and only mark voice-note output as voice-compatible when the actual format is <code>opus</code>. (#62233) Thanks @neeravmakwana.</li>
+<li>Tools/web_fetch and web_search: fix <code>TypeError: fetch failed</code> caused by undici 8.0 enabling HTTP/2 by default; pinned SSRF-guard dispatchers now explicitly set <code>allowH2: false</code> to restore HTTP/1.1 behavior and keep the custom DNS-pinning lookup compatible. (#61738, #61777) Thanks @zozo123.</li>
+<li>Tools/web search/Exa: show Exa Search in onboarding and configure provider pickers again by marking the bundled Exa provider as setup-visible. Thanks @vincentkoc.</li>
+<li>Memory/vector recall: surface explicit warnings when <code>sqlite-vec</code> is unavailable or vector writes are degraded, and strip managed Light Sleep and REM blocks before daily-note ingestion so memory indexing and dreaming stop reporting false-success or re-ingesting staged output. (#61720) Thanks @MonkeyLeeT.</li>
+<li>Memory/dreaming: make Dreams config reads and writes respect the selected memory slot plugin instead of always targeting <code>memory-core</code>. (#62275) Thanks @SnowSky1.</li>
+<li>QQ Bot/media: route gateway-side attachment and fallback downloads through guarded QQ/Tencent HTTPS fetches so QQ media handling no longer follows arbitrary remote hosts.</li>
+<li>Browser/remote CDP: retry the DevTools websocket once after remote browser restarts so healthy remote browser profiles do not fail availability checks during CDP warm-up. (#57397) Thanks @ThanhNguyxn07.</li>
+<li>UI/light mode: target both root and nested WebKit scrollbar thumbs in the light theme so page-level and container scrollbars stay visible on light backgrounds. (#61753) Thanks @chziyue.</li>
+<li>Agents/subagents: honor <code>sessions_spawn(lightContext: true)</code> for spawned subagent runs by preserving lightweight bootstrap context through the gateway and embedded runner instead of silently falling back to full workspace bootstrap injection. (#62264) Thanks @theSamPadilla.</li>
+<li>Cron: load <code>jobId</code> into <code>id</code> when the on-disk store omits <code>id</code>, matching doctor migration and fixing <code>unknown cron job id</code> for hand-edited <code>jobs.json</code>. (#62246) Thanks @neeravmakwana.</li>
+<li>Agents/model fallback: classify minimal HTTP 404 API errors (for example <code>404 status code (no body)</code>) as <code>model_not_found</code> so assistant failures throw into the fallback chain instead of stopping at the first fallback candidate. (#62119) Thanks @neeravmakwana.</li>
+<li>BlueBubbles/network: respect explicit private-network opt-out for loopback and private <code>serverUrl</code> values across account resolution, status probes, monitor startup, and attachment downloads, while keeping public-host attachment hostname pinning intact. (#59373) Thanks @jpreagan.</li>
+<li>Agents/heartbeat: keep heartbeat runs pinned to the main session so active subagent transcripts are not overwritten by heartbeat status messages. (#61803) Thanks @100yenadmin.</li>
+<li>Agents/heartbeat: respect disabled heartbeat prompt guidance so operators can suppress heartbeat prompt instructions without disabling heartbeat runtime behavior.</li>
+<li>Agents/compaction: stop compaction-wait aborts from re-entering prompt failover and replaying completed tool turns. (#62600) Thanks @i-dentifier.</li>
+<li>Approvals/runtime: move native approval lifecycle assembly into shared core bootstrap/runtime seams driven by channel capabilities and runtime contexts, and remove the legacy bundled approval fallback wiring. (#62135) Thanks @gumadeiras.</li>
+<li>Security/fetch-guard: stop rejecting operator-configured proxy hostnames against the target-scoped hostname allowlist in SSRF-guarded fetches, restoring proxy-based media downloads for Telegram and other channels. (#62312) Thanks @ademczuk.</li>
+<li>Logging: make <code>logging.level</code> and <code>logging.consoleLevel</code> honor the documented severity threshold ordering again, and keep child loggers inheriting the parent <code>minLevel</code>. (#44646) Thanks @zhumengzhu.</li>
+<li>Agents/sessions_send: pass <code>threadId</code> through announce delivery so cross-session notifications land in the correct Telegram forum topic instead of the group's general thread. (#62758) Thanks @jalehman.</li>
+<li>Daemon/systemd: keep sudo systemctl calls scoped to the invoking user when machine-scoped systemctl fails, while still avoiding machine fallback for permission-denied user bus errors. (#62337) Thanks @Aftabbs.</li>
+<li>Docs/i18n: relocalize final localized-page links after translation and remove the zh-CN homepage redirect override so localized Mintlify pages resolve to the correct language roots again. (#61796) Thanks @hxy91819.</li>
+<li>Agents/exec: keep timed-out shell-backgrounded commands on the failed path and point long-running jobs to exec background/yield sessions so process polling is only suggested for registered sessions.</li>
+</ul>
+<p><a href="https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md">View full changelog</a></p>
+]]></description>
+            <enclosure url="https://github.com/openclaw/openclaw/releases/download/v2026.4.7/OpenClaw-2026.4.7.zip" length="25324827" type="application/octet-stream" sparkle:edSignature="RyFWRz1trE/qvOiInD4vR6je9wx7fUTtHpZ94W8rMlZDByux9CyXOm/Anai96b9KyjTeQyC7YnJp5SRnYY3iCg=="/>
+        </item>
     </channel>
 </rss>

apps/android/app/build.gradle.kts

@@ -65,8 +65,8 @@ android {
         applicationId = "ai.openclaw.app"
         minSdk = 31
         targetSdk = 36
-        versionCode = 2026041101
-        versionName = "2026.4.11"
+        versionCode = 2026041001
+        versionName = "2026.4.10"
         ndk {
             // Support all major ABIs — native libs are tiny (~47 KB per ABI)
             abiFilters += listOf("armeabi-v7a", "arm64-v8a", "x86", "x86_64")

apps/ios/CHANGELOG.md

@@ -1,8 +1,12 @@
 # OpenClaw iOS Changelog
 
-## 2026.4.11 - 2026-04-11
+## Unreleased
 
-Maintenance update for the current OpenClaw release.
+### Added
+
+### Changed
+
+### Fixed
 
 ## 2026.4.10 - 2026-04-10
 

apps/ios/Config/Version.xcconfig

@@ -2,8 +2,8 @@
 // Source of truth: apps/ios/version.json
 // Generated by scripts/ios-sync-versioning.ts.
 
-OPENCLAW_IOS_VERSION = 2026.4.11
-OPENCLAW_MARKETING_VERSION = 2026.4.11
+OPENCLAW_IOS_VERSION = 2026.4.10
+OPENCLAW_MARKETING_VERSION = 2026.4.10
 OPENCLAW_BUILD_VERSION = 1
 
 #include? "../build/Version.xcconfig"

apps/ios/version.json

@@ -1,3 +1,3 @@
 {
-  "version": "2026.4.11"
+  "version": "2026.4.10"
 }

apps/macos/Sources/OpenClaw/Resources/Info.plist

@@ -15,9 +15,9 @@
     <key>CFBundlePackageType</key>
     <string>APPL</string>
     <key>CFBundleShortVersionString</key>
-    <string>2026.4.11</string>
+    <string>2026.4.10</string>
     <key>CFBundleVersion</key>
-    <string>2026041101</string>
+    <string>2026041001</string>
     <key>CFBundleIconFile</key>
     <string>OpenClaw</string>
     <key>CFBundleURLTypes</key>

apps/macos/Sources/OpenClaw/ShellExecutor.swift

@@ -11,40 +11,6 @@ enum ShellExecutor {
         var errorMessage: String?
     }
 
-    private final class CompletionBox: @unchecked Sendable {
-        private let lock = NSLock()
-        private var finished = false
-        private let continuation: CheckedContinuation<ShellResult, Never>
-
-        init(continuation: CheckedContinuation<ShellResult, Never>) {
-            self.continuation = continuation
-        }
-
-        func finish(_ result: ShellResult) {
-            self.lock.lock()
-            defer { self.lock.unlock() }
-            guard !self.finished else { return }
-            self.finished = true
-            self.continuation.resume(returning: result)
-        }
-    }
-
-    private static func completedResult(
-        status: Int,
-        outTask: Task<Data, Never>,
-        errTask: Task<Data, Never>) async -> ShellResult
-    {
-        let out = await outTask.value
-        let err = await errTask.value
-        return ShellResult(
-            stdout: String(bytes: out, encoding: .utf8) ?? "",
-            stderr: String(bytes: err, encoding: .utf8) ?? "",
-            exitCode: status,
-            timedOut: false,
-            success: status == 0,
-            errorMessage: status == 0 ? nil : "exit \(status)")
-    }
-
     static func runDetailed(
         command: [String],
         cwd: String?,
@@ -72,53 +38,6 @@ enum ShellExecutor {
         process.standardOutput = stdoutPipe
         process.standardError = stderrPipe
 
-        let outTask = Task { stdoutPipe.fileHandleForReading.readToEndSafely() }
-        let errTask = Task { stderrPipe.fileHandleForReading.readToEndSafely() }
-
-        if let timeout, timeout > 0 {
-            return await withCheckedContinuation { continuation in
-                let completion = CompletionBox(continuation: continuation)
-
-                process.terminationHandler = { terminatedProcess in
-                    let status = Int(terminatedProcess.terminationStatus)
-                    Task {
-                        let result = await self.completedResult(
-                            status: status,
-                            outTask: outTask,
-                            errTask: errTask)
-                        completion.finish(result)
-                    }
-                }
-
-                do {
-                    try process.run()
-                } catch {
-                    completion.finish(
-                        ShellResult(
-                            stdout: "",
-                            stderr: "",
-                            exitCode: nil,
-                            timedOut: false,
-                            success: false,
-                            errorMessage: "failed to start: \(error.localizedDescription)"))
-                    return
-                }
-
-                DispatchQueue.global(qos: .userInitiated).asyncAfter(deadline: .now() + timeout) {
-                    guard process.isRunning else { return }
-                    process.terminate()
-                    completion.finish(
-                        ShellResult(
-                            stdout: "",
-                            stderr: "",
-                            exitCode: nil,
-                            timedOut: true,
-                            success: false,
-                            errorMessage: "timeout"))
-                }
-            }
-        }
-
         do {
             try process.run()
         } catch {
@@ -131,11 +50,48 @@ enum ShellExecutor {
                 errorMessage: "failed to start: \(error.localizedDescription)")
         }
 
-        process.waitUntilExit()
-        return await self.completedResult(
-            status: Int(process.terminationStatus),
-            outTask: outTask,
-            errTask: errTask)
+        let outTask = Task { stdoutPipe.fileHandleForReading.readToEndSafely() }
+        let errTask = Task { stderrPipe.fileHandleForReading.readToEndSafely() }
+
+        let waitTask = Task { () -> ShellResult in
+            process.waitUntilExit()
+            let out = await outTask.value
+            let err = await errTask.value
+            let status = Int(process.terminationStatus)
+            return ShellResult(
+                stdout: String(bytes: out, encoding: .utf8) ?? "",
+                stderr: String(bytes: err, encoding: .utf8) ?? "",
+                exitCode: status,
+                timedOut: false,
+                success: status == 0,
+                errorMessage: status == 0 ? nil : "exit \(status)")
+        }
+
+        if let timeout, timeout > 0 {
+            let nanos = UInt64(timeout * 1_000_000_000)
+            return await withTaskGroup(of: ShellResult.self) { group in
+                group.addTask { await waitTask.value }
+                group.addTask {
+                    try? await Task.sleep(nanoseconds: nanos)
+                    guard process.isRunning else {
+                        return await waitTask.value
+                    }
+                    process.terminate()
+                    return ShellResult(
+                        stdout: "",
+                        stderr: "",
+                        exitCode: nil,
+                        timedOut: true,
+                        success: false,
+                        errorMessage: "timeout")
+                }
+                let first = await group.next()!
+                group.cancelAll()
+                return first
+            }
+        }
+
+        return await waitTask.value
     }
 
     static func run(command: [String], cwd: String?, env: [String: String]?, timeout: Double?) async -> Response {

apps/macos/Sources/OpenClaw/TalkModeRuntime.swift

@@ -128,9 +128,8 @@ actor TalkModeRuntime {
     private func start() async {
         let gen = self.lifecycleGeneration
         guard voiceWakeSupported else { return }
-
-        guard await PermissionManager.ensureVoiceWakePermissions(interactive: true) else {
-            self.logger.error("talk runtime not starting: permissions missing")
+        guard PermissionManager.voiceWakePermissionsGranted() else {
+            self.logger.debug("talk runtime not starting: permissions missing")
             return
         }
         await self.reloadConfig()

apps/macos/Sources/OpenClawProtocol/GatewayModels.swift

@@ -401,60 +401,6 @@ public struct AgentEvent: Codable, Sendable {
     }
 }
 
-public struct MessageActionParams: Codable, Sendable {
-    public let channel: String
-    public let action: String
-    public let params: [String: AnyCodable]
-    public let accountid: String?
-    public let requestersenderid: String?
-    public let senderisowner: Bool?
-    public let sessionkey: String?
-    public let sessionid: String?
-    public let agentid: String?
-    public let toolcontext: [String: AnyCodable]?
-    public let idempotencykey: String
-
-    public init(
-        channel: String,
-        action: String,
-        params: [String: AnyCodable],
-        accountid: String?,
-        requestersenderid: String?,
-        senderisowner: Bool?,
-        sessionkey: String?,
-        sessionid: String?,
-        agentid: String?,
-        toolcontext: [String: AnyCodable]?,
-        idempotencykey: String)
-    {
-        self.channel = channel
-        self.action = action
-        self.params = params
-        self.accountid = accountid
-        self.requestersenderid = requestersenderid
-        self.senderisowner = senderisowner
-        self.sessionkey = sessionkey
-        self.sessionid = sessionid
-        self.agentid = agentid
-        self.toolcontext = toolcontext
-        self.idempotencykey = idempotencykey
-    }
-
-    private enum CodingKeys: String, CodingKey {
-        case channel
-        case action
-        case params
-        case accountid = "accountId"
-        case requestersenderid = "requesterSenderId"
-        case senderisowner = "senderIsOwner"
-        case sessionkey = "sessionKey"
-        case sessionid = "sessionId"
-        case agentid = "agentId"
-        case toolcontext = "toolContext"
-        case idempotencykey = "idempotencyKey"
-    }
-}
-
 public struct SendParams: Codable, Sendable {
     public let to: String
     public let message: String?

apps/shared/OpenClawKit/Sources/OpenClawProtocol/GatewayModels.swift

@@ -401,60 +401,6 @@ public struct AgentEvent: Codable, Sendable {
     }
 }
 
-public struct MessageActionParams: Codable, Sendable {
-    public let channel: String
-    public let action: String
-    public let params: [String: AnyCodable]
-    public let accountid: String?
-    public let requestersenderid: String?
-    public let senderisowner: Bool?
-    public let sessionkey: String?
-    public let sessionid: String?
-    public let agentid: String?
-    public let toolcontext: [String: AnyCodable]?
-    public let idempotencykey: String
-
-    public init(
-        channel: String,
-        action: String,
-        params: [String: AnyCodable],
-        accountid: String?,
-        requestersenderid: String?,
-        senderisowner: Bool?,
-        sessionkey: String?,
-        sessionid: String?,
-        agentid: String?,
-        toolcontext: [String: AnyCodable]?,
-        idempotencykey: String)
-    {
-        self.channel = channel
-        self.action = action
-        self.params = params
-        self.accountid = accountid
-        self.requestersenderid = requestersenderid
-        self.senderisowner = senderisowner
-        self.sessionkey = sessionkey
-        self.sessionid = sessionid
-        self.agentid = agentid
-        self.toolcontext = toolcontext
-        self.idempotencykey = idempotencykey
-    }
-
-    private enum CodingKeys: String, CodingKey {
-        case channel
-        case action
-        case params
-        case accountid = "accountId"
-        case requestersenderid = "requesterSenderId"
-        case senderisowner = "senderIsOwner"
-        case sessionkey = "sessionKey"
-        case sessionid = "sessionId"
-        case agentid = "agentId"
-        case toolcontext = "toolContext"
-        case idempotencykey = "idempotencyKey"
-    }
-}
-
 public struct SendParams: Codable, Sendable {
     public let to: String
     public let message: String?

docs/.generated/config-baseline.sha256

@@ -1,4 +1,4 @@
-fce3cbf24274016e01324082ad8ffe81fe2fb41a6e6314aa6efcdbe6689fd628  config-baseline.json
-fb6f0ef881fb591d2791d2adca43c7e88d48f8b562457683092ab6e767aece78  config-baseline.core.json
-3bb312dc9c39a374ca92613abf21606c25dc571287a3941dac71ff57b2b5c519  config-baseline.channel.json
+228031f16ad06580bfd137f092d70d03f2796515e723b8b6618ed69d285465fa  config-baseline.json
+bad0a5bb247a62b8fb9ed9fc2b2720eacf3e0913077ac351b5d26ae2723335ad  config-baseline.core.json
+e1f94346a8507ce3dec763b598e79f3bb89ff2e33189ce977cc87d3b05e71c1d  config-baseline.channel.json
 6c19997f1fb2aff4315f2cb9c7d9e299b403fbc0f9e78e3412cc7fe1c655f222  config-baseline.plugin.json

docs/.generated/plugin-sdk-api-baseline.sha256

@@ -1,2 +1,2 @@
-f0d71b70eb54d67fdc35dde8a5051e527c8a910b7b981f5075d78a5160dd08fa  plugin-sdk-api-baseline.json
-e305bb63072efa680951babd1eb1f419e9965d8a4bdabfc9bf3cafe24a8551df  plugin-sdk-api-baseline.jsonl
+ee16273fa5ad8c5408e9dad8d96fde86dfa666ef8eb44840b78135814ff97173  plugin-sdk-api-baseline.json
+2bd0d5edf23e6a889d6bedb74d0d06411dd7750dac6ebf24971c789f8a69253a  plugin-sdk-api-baseline.jsonl

docs/.i18n/glossary.ar.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.de.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.es.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.fr.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.id.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.it.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.ja-JP.json

@@ -1,98 +1,14 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Getting Started",
-    "target": "はじめに"
-  },
-  {
-    "source": "Getting started",
-    "target": "はじめに"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "local loopback",
-    "target": "local loopback"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "Onboarding",
-    "target": "オンボーディング"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Quick start",
-    "target": "クイックスタート"
-  },
-  {
-    "source": "Quick Start",
-    "target": "クイックスタート"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  },
-  {
-    "source": "wizard",
-    "target": "ウィザード"
-  }
+  { "source": "OpenClaw", "target": "OpenClaw" },
+  { "source": "Gateway", "target": "Gateway" },
+  { "source": "Pi", "target": "Pi" },
+  { "source": "Skills", "target": "Skills" },
+  { "source": "local loopback", "target": "local loopback" },
+  { "source": "Tailscale", "target": "Tailscale" },
+  { "source": "Getting Started", "target": "はじめに" },
+  { "source": "Getting started", "target": "はじめに" },
+  { "source": "Quick start", "target": "クイックスタート" },
+  { "source": "Quick Start", "target": "クイックスタート" },
+  { "source": "Onboarding", "target": "オンボーディング" },
+  { "source": "wizard", "target": "ウィザード" }
 ]

docs/.i18n/glossary.ko.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.pl.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.pt-BR.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.tr.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/.i18n/glossary.uk.json

@@ -1,78 +1,5 @@
 [
-  {
-    "source": "ACP",
-    "target": "ACP"
-  },
-  {
-    "source": "Active Memory",
-    "target": "Active Memory"
-  },
-  {
-    "source": "ClawHub",
-    "target": "ClawHub"
-  },
-  {
-    "source": "CLI",
-    "target": "CLI"
-  },
-  {
-    "source": "Compaction",
-    "target": "Compaction"
-  },
-  {
-    "source": "Cron",
-    "target": "Cron"
-  },
-  {
-    "source": "Dreaming",
-    "target": "Dreaming"
-  },
-  {
-    "source": "Gateway",
-    "target": "Gateway"
-  },
-  {
-    "source": "Heartbeat",
-    "target": "Heartbeat"
-  },
-  {
-    "source": "Mintlify",
-    "target": "Mintlify"
-  },
-  {
-    "source": "Node",
-    "target": "Node"
-  },
-  {
-    "source": "OpenClaw",
-    "target": "OpenClaw"
-  },
-  {
-    "source": "Pi",
-    "target": "Pi"
-  },
-  {
-    "source": "Plugin",
-    "target": "Plugin"
-  },
-  {
-    "source": "Skills",
-    "target": "Skills"
-  },
-  {
-    "source": "Tailscale",
-    "target": "Tailscale"
-  },
-  {
-    "source": "TaskFlow",
-    "target": "TaskFlow"
-  },
-  {
-    "source": "TUI",
-    "target": "TUI"
-  },
-  {
-    "source": "Webhook",
-    "target": "Webhook"
-  }
+  { "source": "CLI", "target": "CLI" },
+  { "source": "Mintlify", "target": "Mintlify" },
+  { "source": "OpenClaw", "target": "OpenClaw" }
 ]

docs/AGENTS.md

@@ -1,28 +0,0 @@
-# Docs Guide
-
-This directory owns docs authoring, Mintlify link rules, and docs i18n policy.
-
-## Mintlify Rules
-
-- Docs are hosted on Mintlify (`https://docs.openclaw.ai`).
-- Internal doc links in `docs/**/*.md` must stay root-relative with no `.md` or `.mdx` suffix (example: `[Config](/configuration)`).
-- Section cross-references should use anchors on root-relative paths (example: `[Hooks](/configuration#hooks)`).
-- Doc headings should avoid em dashes and apostrophes because Mintlify anchor generation is brittle there.
-- README and other GitHub-rendered docs should keep absolute docs URLs so links work outside Mintlify.
-- Docs content must stay generic: no personal device names, hostnames, or local paths; use placeholders like `user@gateway-host`.
-
-## Docs Content Rules
-
-- For docs, UI copy, and picker lists, order services/providers alphabetically unless the section is explicitly describing runtime order or auto-detection order.
-- Keep bundled plugin naming consistent with the repo-wide plugin terminology rules in the root `AGENTS.md`.
-
-## Docs i18n
-
-- Foreign-language docs are not maintained in this repo. The generated publish output lives in the separate `openclaw/docs` repo (often cloned locally as `../openclaw-docs`).
-- Do not add or edit localized docs under `docs/<locale>/**` here.
-- Treat English docs in this repo plus glossary files as the source of truth.
-- Pipeline: update English docs here, update `docs/.i18n/glossary.<locale>.json` as needed, then let the publish-repo sync and `scripts/docs-i18n` run in `openclaw/docs`.
-- Before rerunning `scripts/docs-i18n`, add glossary entries for any new technical terms, page titles, or short nav labels that must stay in English or use a fixed translation.
-- `pnpm docs:check-i18n-glossary` is the guard for changed English doc titles and short internal doc labels.
-- Translation memory lives in generated `docs/.i18n/*.tm.jsonl` files in the publish repo.
-- See `docs/.i18n/README.md`.

docs/CLAUDE.md

@@ -1 +0,0 @@
-AGENTS.md

docs/automation/cron-jobs.md

@@ -62,18 +62,6 @@ Timestamps without a timezone are treated as UTC. Add `--tz America/New_York` fo
 
 Recurring top-of-hour expressions are automatically staggered by up to 5 minutes to reduce load spikes. Use `--exact` to force precise timing or `--stagger 30s` for an explicit window.
 
-### Day-of-month and day-of-week use OR logic
-
-Cron expressions are parsed by [croner](https://github.com/Hexagon/croner). When both the day-of-month and day-of-week fields are non-wildcard, croner matches when **either** field matches — not both. This is standard Vixie cron behavior.
-
-```
-# Intended: "9 AM on the 15th, only if it's a Monday"
-# Actual:   "9 AM on every 15th, AND 9 AM on every Monday"
-0 9 15 * 1
-```
-
-This fires ~5–6 times per month instead of 0–1 times per month. OpenClaw uses Croner's default OR behavior here. To require both conditions, use Croner's `+` day-of-week modifier (`0 9 15 * +1`) or schedule on one field and guard the other in your job's prompt or command.
-
 ## Execution styles
 
 | Style           | `--session` value   | Runs in                  | Best for                        |

docs/channels/msteams.md

@@ -9,7 +9,7 @@ title: "Microsoft Teams"
 
 > "Abandon all hope, ye who enter here."
 
-Updated: 2026-03-25
+Updated: 2026-01-21
 
 Status: text + DM attachments are supported; channel/group file sending requires `sharePointSiteId` + Graph permissions (see [Sending files in group chats](#sending-files-in-group-chats)). Polls are sent via Adaptive Cards. Message actions expose explicit `upload-file` for file-first sends.
 
@@ -43,7 +43,7 @@ Details: [Plugins](/tools/plugin)
 4. Expose `/api/messages` (port 3978 by default) via a public URL or tunnel.
 5. Install the Teams app package and start the gateway.
 
-Minimal config (client secret):
+Minimal config:
 
 ```json5
 {
@@ -59,8 +59,6 @@ Minimal config (client secret):
 }
 ```
 
-For production deployments, consider using [federated authentication](#federated-authentication-certificate--managed-identity) (certificate or managed identity) instead of client secrets.
-
 Note: group chats are blocked by default (`channels.msteams.groupPolicy: "allowlist"`). To allow group replies, set `channels.msteams.groupAllowFrom` (or use `groupPolicy: "open"` to allow any member, mention-gated).
 
 ## Goals
@@ -192,148 +190,6 @@ Before configuring OpenClaw, you need to create an Azure Bot resource.
 2. Click **Microsoft Teams** → Configure → Save
 3. Accept the Terms of Service
 
-## Federated Authentication (Certificate + Managed Identity)
-
-> Added in 2026.3.24
-
-For production deployments, OpenClaw supports **federated authentication** as a more secure alternative to client secrets. Two methods are available:
-
-### Option A: Certificate-based authentication
-
-Use a PEM certificate registered with your Entra ID app registration.
-
-**Setup:**
-
-1. Generate or obtain a certificate (PEM format with private key).
-2. In Entra ID → App Registration → **Certificates & secrets** → **Certificates** → Upload the public certificate.
-
-**Config:**
-
-```json5
-{
-  channels: {
-    msteams: {
-      enabled: true,
-      appId: "<APP_ID>",
-      tenantId: "<TENANT_ID>",
-      authType: "federated",
-      certificatePath: "/path/to/cert.pem",
-      webhook: { port: 3978, path: "/api/messages" },
-    },
-  },
-}
-```
-
-**Env vars:**
-
-- `MSTEAMS_AUTH_TYPE=federated`
-- `MSTEAMS_CERTIFICATE_PATH=/path/to/cert.pem`
-
-### Option B: Azure Managed Identity
-
-Use Azure Managed Identity for passwordless authentication. This is ideal for deployments on Azure infrastructure (AKS, App Service, Azure VMs) where a managed identity is available.
-
-**How it works:**
-
-1. The bot pod/VM has a managed identity (system-assigned or user-assigned).
-2. A **federated identity credential** links the managed identity to the Entra ID app registration.
-3. At runtime, OpenClaw uses `@azure/identity` to acquire tokens from the Azure IMDS endpoint (`169.254.169.254`).
-4. The token is passed to the Teams SDK for bot authentication.
-
-**Prerequisites:**
-
-- Azure infrastructure with managed identity enabled (AKS workload identity, App Service, VM)
-- Federated identity credential created on the Entra ID app registration
-- Network access to IMDS (`169.254.169.254:80`) from the pod/VM
-
-**Config (system-assigned managed identity):**
-
-```json5
-{
-  channels: {
-    msteams: {
-      enabled: true,
-      appId: "<APP_ID>",
-      tenantId: "<TENANT_ID>",
-      authType: "federated",
-      useManagedIdentity: true,
-      webhook: { port: 3978, path: "/api/messages" },
-    },
-  },
-}
-```
-
-**Config (user-assigned managed identity):**
-
-```json5
-{
-  channels: {
-    msteams: {
-      enabled: true,
-      appId: "<APP_ID>",
-      tenantId: "<TENANT_ID>",
-      authType: "federated",
-      useManagedIdentity: true,
-      managedIdentityClientId: "<MI_CLIENT_ID>",
-      webhook: { port: 3978, path: "/api/messages" },
-    },
-  },
-}
-```
-
-**Env vars:**
-
-- `MSTEAMS_AUTH_TYPE=federated`
-- `MSTEAMS_USE_MANAGED_IDENTITY=true`
-- `MSTEAMS_MANAGED_IDENTITY_CLIENT_ID=<client-id>` (only for user-assigned)
-
-### AKS Workload Identity Setup
-
-For AKS deployments using workload identity:
-
-1. **Enable workload identity** on your AKS cluster.
-2. **Create a federated identity credential** on the Entra ID app registration:
-
-   ```bash
-   az ad app federated-credential create --id <APP_OBJECT_ID> --parameters '{
-     "name": "my-bot-workload-identity",
-     "issuer": "<AKS_OIDC_ISSUER_URL>",
-     "subject": "system:serviceaccount:<NAMESPACE>:<SERVICE_ACCOUNT>",
-     "audiences": ["api://AzureADTokenExchange"]
-   }'
-   ```
-
-3. **Annotate the Kubernetes service account** with the app client ID:
-
-   ```yaml
-   apiVersion: v1
-   kind: ServiceAccount
-   metadata:
-     name: my-bot-sa
-     annotations:
-       azure.workload.identity/client-id: "<APP_CLIENT_ID>"
-   ```
-
-4. **Label the pod** for workload identity injection:
-
-   ```yaml
-   metadata:
-     labels:
-       azure.workload.identity/use: "true"
-   ```
-
-5. **Ensure network access** to IMDS (`169.254.169.254`) — if using NetworkPolicy, add an egress rule allowing traffic to `169.254.169.254/32` on port 80.
-
-### Auth type comparison
-
-| Method               | Config                                         | Pros                               | Cons                                  |
-| -------------------- | ---------------------------------------------- | ---------------------------------- | ------------------------------------- |
-| **Client secret**    | `appPassword`                                  | Simple setup                       | Secret rotation required, less secure |
-| **Certificate**      | `authType: "federated"` + `certificatePath`    | No shared secret over network      | Certificate management overhead       |
-| **Managed Identity** | `authType: "federated"` + `useManagedIdentity` | Passwordless, no secrets to manage | Azure infrastructure required         |
-
-**Default behavior:** When `authType` is not set, OpenClaw defaults to client secret authentication. Existing configurations continue to work without changes.
-
 ## Local Development (Tunneling)
 
 Teams can't reach `localhost`. Use a tunnel for local development:
@@ -423,11 +279,6 @@ This is often easier than hand-editing JSON manifests.
    - `MSTEAMS_APP_ID`
    - `MSTEAMS_APP_PASSWORD`
    - `MSTEAMS_TENANT_ID`
-   - `MSTEAMS_AUTH_TYPE` (optional: `"secret"` or `"federated"`)
-   - `MSTEAMS_CERTIFICATE_PATH` (federated + certificate)
-   - `MSTEAMS_CERTIFICATE_THUMBPRINT` (optional, not required for auth)
-   - `MSTEAMS_USE_MANAGED_IDENTITY` (federated + managed identity)
-   - `MSTEAMS_MANAGED_IDENTITY_CLIENT_ID` (user-assigned MI only)
 
 5. **Bot endpoint**
    - Set the Azure Bot Messaging Endpoint to:
@@ -641,11 +492,6 @@ Key settings (see `/gateway/configuration` for shared channel patterns):
 - `toolsBySender` keys should use explicit prefixes:
   `id:`, `e164:`, `username:`, `name:` (legacy unprefixed keys still map to `id:` only).
 - `channels.msteams.actions.memberInfo`: enable or disable the Graph-backed member info action (default: enabled when Graph credentials are available).
-- `channels.msteams.authType`: authentication type — `"secret"` (default) or `"federated"`.
-- `channels.msteams.certificatePath`: path to PEM certificate file (federated + certificate auth).
-- `channels.msteams.certificateThumbprint`: certificate thumbprint (optional, not required for auth).
-- `channels.msteams.useManagedIdentity`: enable managed identity auth (federated mode).
-- `channels.msteams.managedIdentityClientId`: client ID for user-assigned managed identity.
 - `channels.msteams.sharePointSiteId`: SharePoint site ID for file uploads in group chats/channels (see [Sending files in group chats](#sending-files-in-group-chats)).
 
 ## Routing & Sessions

docs/channels/slack.md

@@ -282,279 +282,7 @@ openclaw gateway
   </Tab>
 </Tabs>
 
-### Additional manifest settings
-
-Surface different features that extend the above defaults.
-
 <AccordionGroup>
-  <Accordion title="Optional native slash commands">
-
-    Multiple [native slash commands](#commands-and-slash-behavior) can be used instead of a single configured command with nuance:
-
-    - Use `/agentstatus` instead of `/status` because the `/status` command is reserved.
-    - No more than 25 slash commands can be made available at once.
-
-    Replace your existing `features.slash_commands` section with a subset of [available commands](/tools/slash-commands#command-list):
-
-    <Tabs>
-      <Tab title="Socket Mode (default)">
-
-```json
-    "slash_commands": [
-      {
-        "command": "/new",
-        "description": "Start a new session",
-        "usage_hint": "[model]"
-      },
-      {
-        "command": "/reset",
-        "description": "Reset the current session"
-      },
-      {
-        "command": "/compact",
-        "description": "Compact the session context",
-        "usage_hint": "[instructions]"
-      },
-      {
-        "command": "/stop",
-        "description": "Stop the current run"
-      },
-      {
-        "command": "/session",
-        "description": "Manage thread-binding expiry",
-        "usage_hint": "idle <duration|off> or max-age <duration|off>"
-      },
-      {
-        "command": "/think",
-        "description": "Set the thinking level",
-        "usage_hint": "<off|minimal|low|medium|high|xhigh>"
-      },
-      {
-        "command": "/verbose",
-        "description": "Toggle verbose output",
-        "usage_hint": "on|off|full"
-      },
-      {
-        "command": "/fast",
-        "description": "Show or set fast mode",
-        "usage_hint": "[status|on|off]"
-      },
-      {
-        "command": "/reasoning",
-        "description": "Toggle reasoning visibility",
-        "usage_hint": "[on|off|stream]"
-      },
-      {
-        "command": "/elevated",
-        "description": "Toggle elevated mode",
-        "usage_hint": "[on|off|ask|full]"
-      },
-      {
-        "command": "/exec",
-        "description": "Show or set exec defaults",
-        "usage_hint": "host=<auto|sandbox|gateway|node> security=<deny|allowlist|full> ask=<off|on-miss|always> node=<id>"
-      },
-      {
-        "command": "/model",
-        "description": "Show or set the model",
-        "usage_hint": "[name|#|status]"
-      },
-      {
-        "command": "/models",
-        "description": "List providers or models for a provider",
-        "usage_hint": "[provider] [page] [limit=<n>|size=<n>|all]"
-      },
-      {
-        "command": "/help",
-        "description": "Show the short help summary"
-      },
-      {
-        "command": "/commands",
-        "description": "Show the generated command catalog"
-      },
-      {
-        "command": "/tools",
-        "description": "Show what the current agent can use right now",
-        "usage_hint": "[compact|verbose]"
-      },
-      {
-        "command": "/agentstatus",
-        "description": "Show runtime status, including provider usage/quota when available"
-      },
-      {
-        "command": "/tasks",
-        "description": "List active/recent background tasks for the current session"
-      },
-      {
-        "command": "/context",
-        "description": "Explain how context is assembled",
-        "usage_hint": "[list|detail|json]"
-      },
-      {
-        "command": "/whoami",
-        "description": "Show your sender identity"
-      },
-      {
-        "command": "/skill",
-        "description": "Run a skill by name",
-        "usage_hint": "<name> [input]"
-      },
-      {
-        "command": "/btw",
-        "description": "Ask a side question without changing session context",
-        "usage_hint": "<question>"
-      },
-      {
-        "command": "/usage",
-        "description": "Control the usage footer or show cost summary",
-        "usage_hint": "off|tokens|full|cost"
-      }
-    ]
-```
-
-      </Tab>
-      <Tab title="HTTP Request URLs">
-
-```json
-    "slash_commands": [
-      {
-        "command": "/new",
-        "description": "Start a new session",
-        "usage_hint": "[model]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/reset",
-        "description": "Reset the current session",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/compact",
-        "description": "Compact the session context",
-        "usage_hint": "[instructions]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/stop",
-        "description": "Stop the current run",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/session",
-        "description": "Manage thread-binding expiry",
-        "usage_hint": "idle <duration|off> or max-age <duration|off>",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/think",
-        "description": "Set the thinking level",
-        "usage_hint": "<off|minimal|low|medium|high|xhigh>",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/verbose",
-        "description": "Toggle verbose output",
-        "usage_hint": "on|off|full",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/fast",
-        "description": "Show or set fast mode",
-        "usage_hint": "[status|on|off]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/reasoning",
-        "description": "Toggle reasoning visibility",
-        "usage_hint": "[on|off|stream]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/elevated",
-        "description": "Toggle elevated mode",
-        "usage_hint": "[on|off|ask|full]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/exec",
-        "description": "Show or set exec defaults",
-        "usage_hint": "host=<auto|sandbox|gateway|node> security=<deny|allowlist|full> ask=<off|on-miss|always> node=<id>",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/model",
-        "description": "Show or set the model",
-        "usage_hint": "[name|#|status]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/models",
-        "description": "List providers or models for a provider",
-        "usage_hint": "[provider] [page] [limit=<n>|size=<n>|all]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/help",
-        "description": "Show the short help summary",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/commands",
-        "description": "Show the generated command catalog",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/tools",
-        "description": "Show what the current agent can use right now",
-        "usage_hint": "[compact|verbose]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/agentstatus",
-        "description": "Show runtime status, including provider usage/quota when available",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/tasks",
-        "description": "List active/recent background tasks for the current session",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/context",
-        "description": "Explain how context is assembled",
-        "usage_hint": "[list|detail|json]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/whoami",
-        "description": "Show your sender identity",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/skill",
-        "description": "Run a skill by name",
-        "usage_hint": "<name> [input]",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/btw",
-        "description": "Ask a side question without changing session context",
-        "usage_hint": "<question>",
-        "url": "https://gateway-host.example.com/slack/events"
-      },
-      {
-        "command": "/usage",
-        "description": "Control the usage footer or show cost summary",
-        "usage_hint": "off|tokens|full|cost",
-        "url": "https://gateway-host.example.com/slack/events"
-      }
-    ]
-```
-
-      </Tab>
-    </Tabs>
-
-  </Accordion>
   <Accordion title="Optional authorship scopes (write operations)">
     Add the `chat:write.customize` bot scope if you want outgoing messages to use the active agent identity (custom username and icon) instead of the default Slack app identity.
 
@@ -808,37 +536,30 @@ Notes:
 
 ## Commands and slash behavior
 
-Slash commands appear in Slack as either a single configured command or multiple native commands. Configure `channels.slack.slashCommand` to change command defaults:
+- Native command auto-mode is **off** for Slack (`commands.native: "auto"` does not enable Slack native commands).
+- Enable native Slack command handlers with `channels.slack.commands.native: true` (or global `commands.native: true`).
+- When native commands are enabled, register matching slash commands in Slack (`/<command>` names), with one exception:
+  - register `/agentstatus` for the status command (Slack reserves `/status`)
+- If native commands are not enabled, you can run a single configured slash command via `channels.slack.slashCommand`.
+- Native arg menus now adapt their rendering strategy:
+  - up to 5 options: button blocks
+  - 6-100 options: static select menu
+  - more than 100 options: external select with async option filtering when interactivity options handlers are available
+  - if encoded option values exceed Slack limits, the flow falls back to buttons
+- For long option payloads, Slash command argument menus use a confirm dialog before dispatching a selected value.
+
+Default slash command settings:
 
 - `enabled: false`
 - `name: "openclaw"`
 - `sessionPrefix: "slack:slash"`
 - `ephemeral: true`
 
-```txt
-/openclaw /help
-```
+Slash sessions use isolated keys:
 
-Native commands require [additional manifest settings](#additional-manifest-settings) in your Slack app and are enabled with `channels.slack.commands.native: true` or `commands.native: true` in global configurations instead.
+- `agent:<agentId>:slack:slash:<userId>`
 
-- Native command auto-mode is **off** for Slack so `commands.native: "auto"` does not enable Slack native commands.
-
-```txt
-/help
-```
-
-Native argument menus use an adaptive rendering strategy that shows a confirmation modal before dispatching a selected option value:
-
-- up to 5 options: button blocks
-- 6-100 options: static select menu
-- more than 100 options: external select with async option filtering when interactivity options handlers are available
-- exceeded Slack limits: encoded option values fall back to buttons
-
-```txt
-/think
-```
-
-Slash sessions use isolated keys like `agent:<agentId>:slack:slash:<userId>` and still route command executions to the target conversation session using `CommandTargetSessionKey`.
+and still route command execution against the target conversation session (`CommandTargetSessionKey`).
 
 ## Interactive replies
 

docs/concepts/active-memory.md

@@ -35,7 +35,7 @@ self-contained, safe-default setup:
           enabled: true,
           agents: ["main"],
           allowedChatTypes: ["direct"],
-          modelFallback: "google/gemini-3-flash",
+          modelFallbackPolicy: "default-remote",
           queryMode: "recent",
           promptStyle: "balanced",
           timeoutMs: 15000,
@@ -51,7 +51,7 @@ self-contained, safe-default setup:
 
 This turns the plugin on for the `main` agent, keeps it limited to direct-message
 style sessions by default, lets it inherit the current session model first, and
-uses the configured fallback model only if no explicit or inherited model is
+still allows the built-in remote fallback if no explicit or inherited model is
 available.
 
 After that, restart the gateway:
@@ -85,7 +85,7 @@ Start with this in `openclaw.json`:
         config: {
           agents: ["main"],
           allowedChatTypes: ["direct"],
-          modelFallback: "google/gemini-3-flash",
+          modelFallbackPolicy: "default-remote",
           queryMode: "recent",
           promptStyle: "balanced",
           timeoutMs: 15000,
@@ -111,7 +111,7 @@ What this means:
 - `config.agents: ["main"]` opts only the `main` agent into active memory
 - `config.allowedChatTypes: ["direct"]` keeps active memory on for direct-message style sessions only by default
 - if `config.model` is unset, active memory inherits the current session model first
-- `config.modelFallback` optionally provides your own fallback provider/model for recall
+- `config.modelFallbackPolicy: "default-remote"` keeps the built-in remote fallback as the default when no explicit or inherited model is available
 - `config.promptStyle: "balanced"` uses the default general-purpose prompt style for `recent` mode
 - active memory still runs only on eligible interactive persistent chat sessions
 
@@ -335,22 +335,26 @@ If `config.model` is unset, Active Memory tries to resolve a model in this order
 explicit plugin model
 -> current session model
 -> agent primary model
--> optional configured fallback model
+-> optional built-in remote fallback
 ```
 
-`config.modelFallback` controls the configured fallback step.
+`config.modelFallbackPolicy` controls the last step.
 
-Optional custom fallback:
+Default:
 
 ```json5
-modelFallback: "google/gemini-3-flash"
+modelFallbackPolicy: "default-remote"
 ```
 
-If no explicit, inherited, or configured fallback model resolves, Active Memory
-skips recall for that turn.
+Other option:
 
-`config.modelFallbackPolicy` is retained only as a deprecated compatibility
-field for older configs. It no longer changes runtime behavior.
+```json5
+modelFallbackPolicy: "resolved-only"
+```
+
+Use `resolved-only` if you want Active Memory to skip recall instead of falling
+back to the built-in remote default when no explicit or inherited model is
+available.
 
 ## Advanced escape hatches
 

docs/concepts/system-prompt.md

@@ -110,12 +110,9 @@ heartbeats are disabled for the default agent or
 files concise — especially `MEMORY.md`, which can grow over time and lead to
 unexpectedly high context usage and more frequent compaction.
 
-> **Note:** `memory/*.md` daily files are **not** part of the normal bootstrap
-> Project Context. On ordinary turns they are accessed on demand via the
-> `memory_search` and `memory_get` tools, so they do not count against the
-> context window unless the model explicitly reads them. Bare `/new` and
-> `/reset` turns are the exception: the runtime can prepend recent daily memory
-> as a one-shot startup-context block for that first turn.
+> **Note:** `memory/*.md` daily files are **not** injected automatically. They
+> are accessed on demand via the `memory_search` and `memory_get` tools, so they
+> do not count against the context window unless the model explicitly reads them.
 
 Large files are truncated with a marker. The max per-file size is controlled by
 `agents.defaults.bootstrapMaxChars` (default: 20000). Total injected bootstrap

docs/docs.json

@@ -52,10 +52,6 @@
     ]
   },
   "redirects": [
-    {
-      "source": "/mcp",
-      "destination": "/cli/mcp"
-    },
     {
       "source": "/providers/modelstudio",
       "destination": "/providers/qwen"
@@ -1120,8 +1116,6 @@
                   "plugins/codex-harness",
                   "plugins/webhooks",
                   "plugins/voice-call",
-                  "plugins/memory-wiki",
-                  "plugins/zalouser",
                   {
                     "group": "Building Plugins",
                     "pages": [
@@ -1194,7 +1188,6 @@
                       "tools/gemini-search",
                       "tools/grok-search",
                       "tools/kimi-search",
-                      "tools/minimax-search",
                       "tools/ollama-search",
                       "tools/perplexity-search",
                       "tools/searxng-search",
@@ -1244,24 +1237,22 @@
                 "group": "Providers",
                 "pages": [
                   "providers/alibaba",
-                  "providers/bedrock",
-                  "providers/bedrock-mantle",
                   "providers/anthropic",
                   "providers/arcee",
+                  "providers/bedrock",
+                  "providers/bedrock-mantle",
                   "providers/chutes",
+                  "providers/comfy",
                   "providers/claude-max-api-proxy",
                   "providers/cloudflare-ai-gateway",
-                  "providers/comfy",
                   "providers/deepgram",
                   "providers/deepseek",
                   "providers/fal",
-                  "providers/fireworks",
                   "providers/github-copilot",
                   "providers/glm",
                   "providers/google",
                   "providers/groq",
                   "providers/huggingface",
-                  "providers/inferrs",
                   "providers/kilocode",
                   "providers/litellm",
                   "providers/minimax",
@@ -1283,9 +1274,9 @@
                   "providers/together",
                   "providers/venice",
                   "providers/vercel-ai-gateway",
+                  "providers/vydra",
                   "providers/vllm",
                   "providers/volcengine",
-                  "providers/vydra",
                   "providers/xai",
                   "providers/xiaomi",
                   "providers/zai"
@@ -1464,7 +1455,6 @@
                       "cli/agent",
                       "cli/agents",
                       "cli/hooks",
-                      "cli/infer",
                       "cli/memory",
                       "cli/message",
                       "cli/models",
@@ -1515,8 +1505,7 @@
                       "cli/completion",
                       "cli/dns",
                       "cli/docs",
-                      "cli/mcp",
-                      "cli/wiki"
+                      "cli/mcp"
                     ]
                   }
                 ]
@@ -1550,7 +1539,6 @@
                   "reference/api-usage-costs",
                   "reference/transcript-hygiene",
                   "reference/memory-config",
-                  "reference/rich-output-protocol",
                   "date-time"
                 ]
               },

docs/gateway/configuration-reference.md

@@ -2895,8 +2895,6 @@ See [Plugins](/tools/plugin).
       enabled: true,
       basePath: "/openclaw",
       // root: "dist/control-ui",
-      // embedSandbox: "scripts", // strict | scripts | trusted
-      // allowExternalEmbedUrls: false, // dangerous: allow absolute external http(s) embed URLs
       // allowedOrigins: ["https://control.example.com"], // required for non-loopback Control UI
       // dangerouslyAllowHostHeaderOriginFallback: false, // dangerous Host-header origin fallback mode
       // allowInsecureAuth: false,

docs/help/gpt54-codex-agentic-parity-maintainers.md

@@ -1,164 +0,0 @@
-# GPT-5.4 / Codex Parity Maintainer Notes
-
-This note explains how to review the GPT-5.4 / Codex parity program as four merge units without losing the original six-contract architecture.
-
-## Merge units
-
-### PR A: strict-agentic execution
-
-Owns:
-
-- `executionContract`
-- GPT-5-first same-turn follow-through
-- `update_plan` as non-terminal progress tracking
-- explicit blocked states instead of plan-only silent stops
-
-Does not own:
-
-- auth/runtime failure classification
-- permission truthfulness
-- replay/continuation redesign
-- parity benchmarking
-
-### PR B: runtime truthfulness
-
-Owns:
-
-- Codex OAuth scope correctness
-- typed provider/runtime failure classification
-- truthful `/elevated full` availability and blocked reasons
-
-Does not own:
-
-- tool schema normalization
-- replay/liveness state
-- benchmark gating
-
-### PR C: execution correctness
-
-Owns:
-
-- provider-owned OpenAI/Codex tool compatibility
-- parameter-free strict schema handling
-- replay-invalid surfacing
-- paused, blocked, and abandoned long-task state visibility
-
-Does not own:
-
-- self-elected continuation
-- generic Codex dialect behavior outside provider hooks
-- benchmark gating
-
-### PR D: parity harness
-
-Owns:
-
-- first-wave GPT-5.4 vs Opus 4.6 scenario pack
-- parity documentation
-- parity report and release-gate mechanics
-
-Does not own:
-
-- runtime behavior changes outside QA-lab
-- auth/proxy/DNS simulation inside the harness
-
-## Mapping back to the original six contracts
-
-| Original contract                        | Merge unit |
-| ---------------------------------------- | ---------- |
-| Provider transport/auth correctness      | PR B       |
-| Tool contract/schema compatibility       | PR C       |
-| Same-turn execution                      | PR A       |
-| Permission truthfulness                  | PR B       |
-| Replay/continuation/liveness correctness | PR C       |
-| Benchmark/release gate                   | PR D       |
-
-## Review order
-
-1. PR A
-2. PR B
-3. PR C
-4. PR D
-
-PR D is the proof layer. It should not be the reason runtime-correctness PRs are delayed.
-
-## What to look for
-
-### PR A
-
-- GPT-5 runs act or fail closed instead of stopping at commentary
-- `update_plan` no longer looks like progress by itself
-- behavior stays GPT-5-first and embedded-Pi scoped
-
-### PR B
-
-- auth/proxy/runtime failures stop collapsing into generic “model failed” handling
-- `/elevated full` is only described as available when it is actually available
-- blocked reasons are visible to both the model and the user-facing runtime
-
-### PR C
-
-- strict OpenAI/Codex tool registration behaves predictably
-- parameter-free tools do not fail strict schema checks
-- replay and compaction outcomes preserve truthful liveness state
-
-### PR D
-
-- the scenario pack is understandable and reproducible
-- the pack includes a mutating replay-safety lane, not only read-only flows
-- reports are readable by humans and automation
-- parity claims are evidence-backed, not anecdotal
-
-Expected artifacts from PR D:
-
-- `qa-suite-report.md` / `qa-suite-summary.json` for each model run
-- `qa-agentic-parity-report.md` with aggregate and scenario-level comparison
-- `qa-agentic-parity-summary.json` with a machine-readable verdict
-
-## Release gate
-
-Do not claim GPT-5.4 parity or superiority over Opus 4.6 until:
-
-- PR A, PR B, and PR C are merged
-- PR D runs the first-wave parity pack cleanly
-- runtime-truthfulness regression suites remain green
-- the parity report shows no fake-success cases and no regression in stop behavior
-
-```mermaid
-flowchart LR
-    A["PR A-C merged"] --> B["Run GPT-5.4 parity pack"]
-    A --> C["Run Opus 4.6 parity pack"]
-    B --> D["qa-suite-summary.json"]
-    C --> E["qa-suite-summary.json"]
-    D --> F["qa parity-report"]
-    E --> F
-    F --> G["Markdown report + JSON verdict"]
-    G --> H{"Pass?"}
-    H -- "yes" --> I["Parity claim allowed"]
-    H -- "no" --> J["Keep runtime fixes / review loop open"]
-```
-
-The parity harness is not the only evidence source. Keep this split explicit in review:
-
-- PR D owns the scenario-based GPT-5.4 vs Opus 4.6 comparison
-- PR B deterministic suites still own auth/proxy/DNS and full-access truthfulness evidence
-
-## Goal-to-evidence map
-
-| Completion gate item                     | Primary owner | Review artifact                                                     |
-| ---------------------------------------- | ------------- | ------------------------------------------------------------------- |
-| No plan-only stalls                      | PR A          | strict-agentic runtime tests and `approval-turn-tool-followthrough` |
-| No fake progress or fake tool completion | PR A + PR D   | parity fake-success count plus scenario-level report details        |
-| No false `/elevated full` guidance       | PR B          | deterministic runtime-truthfulness suites                           |
-| Replay/liveness failures remain explicit | PR C + PR D   | lifecycle/replay suites plus `compaction-retry-mutating-tool`       |
-| GPT-5.4 matches or beats Opus 4.6        | PR D          | `qa-agentic-parity-report.md` and `qa-agentic-parity-summary.json`  |
-
-## Reviewer shorthand: before vs after
-
-| User-visible problem before                                 | Review signal after                                                                     |
-| ----------------------------------------------------------- | --------------------------------------------------------------------------------------- |
-| GPT-5.4 stopped after planning                              | PR A shows act-or-block behavior instead of commentary-only completion                  |
-| Tool use felt brittle with strict OpenAI/Codex schemas      | PR C keeps tool registration and parameter-free invocation predictable                  |
-| `/elevated full` hints were sometimes misleading            | PR B ties guidance to actual runtime capability and blocked reasons                     |
-| Long tasks could disappear into replay/compaction ambiguity | PR C emits explicit paused, blocked, abandoned, and replay-invalid state                |
-| Parity claims were anecdotal                                | PR D produces a report plus JSON verdict with the same scenario coverage on both models |

docs/help/gpt54-codex-agentic-parity.md

@@ -1,219 +0,0 @@
-# GPT-5.4 / Codex Agentic Parity in OpenClaw
-
-OpenClaw already worked well with tool-using frontier models, but GPT-5.4 and Codex-style models were still underperforming in a few practical ways:
-
-- they could stop after planning instead of doing the work
-- they could use strict OpenAI/Codex tool schemas incorrectly
-- they could ask for `/elevated full` even when full access was impossible
-- they could lose long-running task state during replay or compaction
-- parity claims against Claude Opus 4.6 were based on anecdotes instead of repeatable scenarios
-
-This parity program fixes those gaps in four reviewable slices.
-
-## What changed
-
-### PR A: strict-agentic execution
-
-This slice adds an opt-in `strict-agentic` execution contract for embedded Pi GPT-5 runs.
-
-When enabled, OpenClaw stops accepting plan-only turns as “good enough” completion. If the model only says what it intends to do and does not actually use tools or make progress, OpenClaw retries with an act-now steer and then fails closed with an explicit blocked state instead of silently ending the task.
-
-This improves the GPT-5.4 experience most on:
-
-- short “ok do it” follow-ups
-- code tasks where the first step is obvious
-- flows where `update_plan` should be progress tracking rather than filler text
-
-### PR B: runtime truthfulness
-
-This slice makes OpenClaw tell the truth about two things:
-
-- why the provider/runtime call failed
-- whether `/elevated full` is actually available
-
-That means GPT-5.4 gets better runtime signals for missing scope, auth refresh failures, HTML 403 auth failures, proxy issues, DNS or timeout failures, and blocked full-access modes. The model is less likely to hallucinate the wrong remediation or keep asking for a permission mode the runtime cannot provide.
-
-### PR C: execution correctness
-
-This slice improves two kinds of correctness:
-
-- provider-owned OpenAI/Codex tool-schema compatibility
-- replay and long-task liveness surfacing
-
-The tool-compat work reduces schema friction for strict OpenAI/Codex tool registration, especially around parameter-free tools and strict object-root expectations. The replay/liveness work makes long-running tasks more observable, so paused, blocked, and abandoned states are visible instead of disappearing into generic failure text.
-
-### PR D: parity harness
-
-This slice adds the first-wave QA-lab parity pack so GPT-5.4 and Opus 4.6 can be exercised through the same scenarios and compared using shared evidence.
-
-The parity pack is the proof layer. It does not change runtime behavior by itself.
-
-After you have two `qa-suite-summary.json` artifacts, generate the release-gate comparison with:
-
-```bash
-pnpm openclaw qa parity-report \
-  --repo-root . \
-  --candidate-summary .artifacts/qa-e2e/gpt54/qa-suite-summary.json \
-  --baseline-summary .artifacts/qa-e2e/opus46/qa-suite-summary.json \
-  --output-dir .artifacts/qa-e2e/parity
-```
-
-That command writes:
-
-- a human-readable Markdown report
-- a machine-readable JSON verdict
-- an explicit `pass` / `fail` gate result
-
-## Why this improves GPT-5.4 in practice
-
-Before this work, GPT-5.4 on OpenClaw could feel less agentic than Opus in real coding sessions because the runtime tolerated behaviors that are especially harmful for GPT-5-style models:
-
-- commentary-only turns
-- schema friction around tools
-- vague permission feedback
-- silent replay or compaction breakage
-
-The goal is not to make GPT-5.4 imitate Opus. The goal is to give GPT-5.4 a runtime contract that rewards real progress, supplies cleaner tool and permission semantics, and turns failure modes into explicit machine- and human-readable states.
-
-That changes the user experience from:
-
-- “the model had a good plan but stopped”
-
-to:
-
-- “the model either acted, or OpenClaw surfaced the exact reason it could not”
-
-## Before vs after for GPT-5.4 users
-
-| Before this program                                                                            | After PR A-D                                                                             |
-| ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| GPT-5.4 could stop after a reasonable plan without taking the next tool step                   | PR A turns “plan only” into “act now or surface a blocked state”                         |
-| Strict tool schemas could reject parameter-free or OpenAI/Codex-shaped tools in confusing ways | PR C makes provider-owned tool registration and invocation more predictable              |
-| `/elevated full` guidance could be vague or wrong in blocked runtimes                          | PR B gives GPT-5.4 and the user truthful runtime and permission hints                    |
-| Replay or compaction failures could feel like the task silently disappeared                    | PR C surfaces paused, blocked, abandoned, and replay-invalid outcomes explicitly         |
-| “GPT-5.4 feels worse than Opus” was mostly anecdotal                                           | PR D turns that into the same scenario pack, the same metrics, and a hard pass/fail gate |
-
-## Architecture
-
-```mermaid
-flowchart TD
-    A["User request"] --> B["Embedded Pi runtime"]
-    B --> C["Strict-agentic execution contract"]
-    B --> D["Provider-owned tool compatibility"]
-    B --> E["Runtime truthfulness"]
-    B --> F["Replay and liveness state"]
-    C --> G["Tool call or explicit blocked state"]
-    D --> G
-    E --> G
-    F --> G
-    G --> H["QA-lab parity pack"]
-    H --> I["Scenario report and parity gate"]
-```
-
-## Release flow
-
-```mermaid
-flowchart LR
-    A["Merged runtime slices (PR A-C)"] --> B["Run GPT-5.4 parity pack"]
-    A --> C["Run Opus 4.6 parity pack"]
-    B --> D["qa-suite-summary.json"]
-    C --> E["qa-suite-summary.json"]
-    D --> F["openclaw qa parity-report"]
-    E --> F
-    F --> G["qa-agentic-parity-report.md"]
-    F --> H["qa-agentic-parity-summary.json"]
-    H --> I{"Gate pass?"}
-    I -- "yes" --> J["Evidence-backed parity claim"]
-    I -- "no" --> K["Keep runtime/review loop open"]
-```
-
-## Scenario pack
-
-The first-wave parity pack currently covers five scenarios:
-
-### `approval-turn-tool-followthrough`
-
-Checks that the model does not stop at “I’ll do that” after a short approval. It should take the first concrete action in the same turn.
-
-### `model-switch-tool-continuity`
-
-Checks that tool-using work remains coherent across model/runtime switching boundaries instead of resetting into commentary or losing execution context.
-
-### `source-docs-discovery-report`
-
-Checks that the model can read source and docs, synthesize findings, and continue the task agentically rather than producing a thin summary and stopping early.
-
-### `image-understanding-attachment`
-
-Checks that mixed-mode tasks involving attachments remain actionable and do not collapse into vague narration.
-
-### `compaction-retry-mutating-tool`
-
-Checks that a task with a real mutating write keeps replay-unsafety explicit instead of quietly looking replay-safe if the run compacts, retries, or loses reply state under pressure.
-
-## Scenario matrix
-
-| Scenario                           | What it tests                           | Good GPT-5.4 behavior                                                          | Failure signal                                                                 |
-| ---------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
-| `approval-turn-tool-followthrough` | Short approval turns after a plan       | Starts the first concrete tool action immediately instead of restating intent  | plan-only follow-up, no tool activity, or blocked turn without a real blocker  |
-| `model-switch-tool-continuity`     | Runtime/model switching under tool use  | Preserves task context and continues acting coherently                         | resets into commentary, loses tool context, or stops after switch              |
-| `source-docs-discovery-report`     | Source reading + synthesis + action     | Finds sources, uses tools, and produces a useful report without stalling       | thin summary, missing tool work, or incomplete-turn stop                       |
-| `image-understanding-attachment`   | Attachment-driven agentic work          | Interprets the attachment, connects it to tools, and continues the task        | vague narration, attachment ignored, or no concrete next action                |
-| `compaction-retry-mutating-tool`   | Mutating work under compaction pressure | Performs a real write and keeps replay-unsafety explicit after the side effect | mutating write happens but replay safety is implied, missing, or contradictory |
-
-## Release gate
-
-GPT-5.4 can only be considered at parity or better when the merged runtime passes the parity pack and the runtime-truthfulness regressions at the same time.
-
-Required outcomes:
-
-- no plan-only stall when the next tool action is clear
-- no fake completion without real execution
-- no incorrect `/elevated full` guidance
-- no silent replay or compaction abandonment
-- parity-pack metrics that are at least as strong as the agreed Opus 4.6 baseline
-
-For the first-wave harness, the gate compares:
-
-- completion rate
-- unintended-stop rate
-- valid-tool-call rate
-- fake-success count
-
-Parity evidence is intentionally split across two layers:
-
-- PR D proves same-scenario GPT-5.4 vs Opus 4.6 behavior with QA-lab
-- PR B deterministic suites prove auth, proxy, DNS, and `/elevated full` truthfulness outside the harness
-
-## Goal-to-evidence matrix
-
-| Completion gate item                                     | Owning PR   | Evidence source                                                    | Pass signal                                                                              |
-| -------------------------------------------------------- | ----------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- |
-| GPT-5.4 no longer stalls after planning                  | PR A        | `approval-turn-tool-followthrough` plus PR A runtime suites        | approval turns trigger real work or an explicit blocked state                            |
-| GPT-5.4 no longer fakes progress or fake tool completion | PR A + PR D | parity report scenario outcomes and fake-success count             | no suspicious pass results and no commentary-only completion                             |
-| GPT-5.4 no longer gives false `/elevated full` guidance  | PR B        | deterministic truthfulness suites                                  | blocked reasons and full-access hints stay runtime-accurate                              |
-| Replay/liveness failures stay explicit                   | PR C + PR D | PR C lifecycle/replay suites plus `compaction-retry-mutating-tool` | mutating work keeps replay-unsafety explicit instead of silently disappearing            |
-| GPT-5.4 matches or beats Opus 4.6 on the agreed metrics  | PR D        | `qa-agentic-parity-report.md` and `qa-agentic-parity-summary.json` | same scenario coverage and no regression on completion, stop behavior, or valid tool use |
-
-## How to read the parity verdict
-
-Use the verdict in `qa-agentic-parity-summary.json` as the final machine-readable decision for the first-wave parity pack.
-
-- `pass` means GPT-5.4 covered the same scenarios as Opus 4.6 and did not regress on the agreed aggregate metrics.
-- `fail` means at least one hard gate tripped: weaker completion, worse unintended stops, weaker valid tool use, any fake-success case, or mismatched scenario coverage.
-- “shared/base CI issue” is not itself a parity result. If CI noise outside PR D blocks a run, the verdict should wait for a clean merged-runtime execution instead of being inferred from branch-era logs.
-- Auth, proxy, DNS, and `/elevated full` truthfulness still come from PR B’s deterministic suites, so the final release claim needs both: a passing PR D parity verdict and green PR B truthfulness coverage.
-
-## Who should enable `strict-agentic`
-
-Use `strict-agentic` when:
-
-- the agent is expected to act immediately when a next step is obvious
-- GPT-5.4 or Codex-family models are the primary runtime
-- you prefer explicit blocked states over “helpful” recap-only replies
-
-Keep the default contract when:
-
-- you want the existing looser behavior
-- you are not using GPT-5-family models
-- you are testing prompts rather than runtime enforcement

docs/plugins/architecture.md

@@ -519,28 +519,10 @@ The manifest is the control-plane source of truth. OpenClaw uses it to:
 - validate `plugins.entries.<id>.config`
 - augment Control UI labels/placeholders
 - show install/catalog metadata
-- preserve cheap activation and setup descriptors without loading plugin runtime
 
 For native plugins, the runtime module is the data-plane part. It registers
 actual behavior such as hooks, tools, commands, or provider flows.
 
-Optional manifest `activation` and `setup` blocks stay on the control plane.
-They are metadata-only descriptors for activation planning and setup discovery;
-they do not replace runtime registration, `register(...)`, or `setupEntry`.
-The first live activation consumers now use manifest command and provider hints
-to narrow plugin loading before broader registry materialization:
-
-- CLI loading narrows to plugins that own the requested primary command
-- explicit provider setup/runtime resolution narrows to plugins that own the
-  requested provider id
-
-Setup discovery now prefers descriptor-owned ids such as `setup.providers` and
-`setup.cliBackends` to narrow candidate plugins before it falls back to
-`setup-api` for plugins that still need setup-time runtime hooks. If more than
-one discovered plugin claims the same normalized setup provider or CLI backend
-id, setup lookup refuses the ambiguous owner instead of relying on discovery
-order.
-
 ### What the loader caches
 
 OpenClaw keeps short in-process caches for:

docs/plugins/manifest.md

@@ -47,10 +47,6 @@ Use it for:
 - config validation
 - auth and onboarding metadata that should be available without booting plugin
   runtime
-- cheap activation hints that control-plane surfaces can inspect before runtime
-  loads
-- cheap setup descriptors that setup/onboarding surfaces can inspect before
-  runtime loads
 - alias and auto-enable metadata that should resolve before plugin runtime loads
 - shorthand model-family ownership metadata that should auto-activate the
   plugin before runtime loads
@@ -156,8 +152,6 @@ Those belong in your plugin code and `package.json`.
 | `providerAuthAliases`               | No       | `Record<string, string>`         | Provider ids that should reuse another provider id for auth lookup, for example a coding provider that shares the base provider API key and auth profiles.                                                   |
 | `channelEnvVars`                    | No       | `Record<string, string[]>`       | Cheap channel env metadata that OpenClaw can inspect without loading plugin code. Use this for env-driven channel setup or auth surfaces that generic startup/config helpers should see.                     |
 | `providerAuthChoices`               | No       | `object[]`                       | Cheap auth-choice metadata for onboarding pickers, preferred-provider resolution, and simple CLI flag wiring.                                                                                                |
-| `activation`                        | No       | `object`                         | Cheap activation hints for provider, command, channel, route, and capability-triggered loading. Metadata only; plugin runtime still owns actual behavior.                                                    |
-| `setup`                             | No       | `object`                         | Cheap setup/onboarding descriptors that discovery and setup surfaces can inspect without loading plugin runtime.                                                                                             |
 | `contracts`                         | No       | `object`                         | Static bundled capability snapshot for speech, realtime transcription, realtime voice, media-understanding, image-generation, music-generation, video-generation, web-fetch, web search, and tool ownership. |
 | `channelConfigs`                    | No       | `Record<string, object>`         | Manifest-owned channel config metadata merged into discovery and validation surfaces before runtime loads.                                                                                                   |
 | `skills`                            | No       | `string[]`                       | Skill directories to load, relative to the plugin root.                                                                                                                                                      |
@@ -214,99 +208,6 @@ uses this metadata for diagnostics without importing plugin runtime code.
 | `kind`       | No       | `"runtime-slash"` | Marks the alias as a chat slash command rather than a root CLI command. |
 | `cliCommand` | No       | `string`          | Related root CLI command to suggest for CLI operations, if one exists.  |
 
-## activation reference
-
-Use `activation` when the plugin can cheaply declare which control-plane events
-should activate it later.
-
-This block is metadata only. It does not register runtime behavior, and it does
-not replace `register(...)`, `setupEntry`, or other runtime/plugin entrypoints.
-Current consumers use it as a narrowing hint before broader plugin loading, so
-missing activation metadata usually only costs performance; it should not
-change correctness while legacy manifest ownership fallbacks still exist.
-
-```json
-{
-  "activation": {
-    "onProviders": ["openai"],
-    "onCommands": ["models"],
-    "onChannels": ["web"],
-    "onRoutes": ["gateway-webhook"],
-    "onCapabilities": ["provider", "tool"]
-  }
-}
-```
-
-| Field            | Required | Type                                                 | What it means                                                     |
-| ---------------- | -------- | ---------------------------------------------------- | ----------------------------------------------------------------- |
-| `onProviders`    | No       | `string[]`                                           | Provider ids that should activate this plugin when requested.     |
-| `onCommands`     | No       | `string[]`                                           | Command ids that should activate this plugin.                     |
-| `onChannels`     | No       | `string[]`                                           | Channel ids that should activate this plugin.                     |
-| `onRoutes`       | No       | `string[]`                                           | Route kinds that should activate this plugin.                     |
-| `onCapabilities` | No       | `Array<"provider" \| "channel" \| "tool" \| "hook">` | Broad capability hints used by control-plane activation planning. |
-
-Current live consumers:
-
-- command-triggered CLI planning falls back to legacy
-  `commandAliases[].cliCommand` or `commandAliases[].name`
-- provider-triggered setup/runtime planning falls back to legacy
-  `providers[]` and top-level `cliBackends[]` ownership when explicit provider
-  activation metadata is missing
-
-## setup reference
-
-Use `setup` when setup and onboarding surfaces need cheap plugin-owned metadata
-before runtime loads.
-
-```json
-{
-  "setup": {
-    "providers": [
-      {
-        "id": "openai",
-        "authMethods": ["api-key"],
-        "envVars": ["OPENAI_API_KEY"]
-      }
-    ],
-    "cliBackends": ["openai-cli"],
-    "configMigrations": ["legacy-openai-auth"],
-    "requiresRuntime": false
-  }
-}
-```
-
-Top-level `cliBackends` stays valid and continues to describe CLI inference
-backends. `setup.cliBackends` is the setup-specific descriptor surface for
-control-plane/setup flows that should stay metadata-only.
-
-When present, `setup.providers` and `setup.cliBackends` are the preferred
-descriptor-first lookup surface for setup discovery. If the descriptor only
-narrows the candidate plugin and setup still needs richer setup-time runtime
-hooks, set `requiresRuntime: true` and keep `setup-api` in place as the
-fallback execution path.
-
-Because setup lookup can execute plugin-owned `setup-api` code, normalized
-`setup.providers[].id` and `setup.cliBackends[]` values must stay unique across
-discovered plugins. Ambiguous ownership fails closed instead of picking a
-winner from discovery order.
-
-### setup.providers reference
-
-| Field         | Required | Type       | What it means                                                                        |
-| ------------- | -------- | ---------- | ------------------------------------------------------------------------------------ |
-| `id`          | Yes      | `string`   | Provider id exposed during setup or onboarding. Keep normalized ids globally unique. |
-| `authMethods` | No       | `string[]` | Setup/auth method ids this provider supports without loading full runtime.           |
-| `envVars`     | No       | `string[]` | Env vars that generic setup/status surfaces can check before plugin runtime loads.   |
-
-### setup fields
-
-| Field              | Required | Type       | What it means                                                                                       |
-| ------------------ | -------- | ---------- | --------------------------------------------------------------------------------------------------- |
-| `providers`        | No       | `object[]` | Provider setup descriptors exposed during setup and onboarding.                                     |
-| `cliBackends`      | No       | `string[]` | Setup-time backend ids used for descriptor-first setup lookup. Keep normalized ids globally unique. |
-| `configMigrations` | No       | `string[]` | Config migration ids owned by this plugin's setup surface.                                          |
-| `requiresRuntime`  | No       | `boolean`  | Whether setup still needs `setup-api` execution after descriptor lookup.                            |
-
 ## uiHints reference
 
 `uiHints` is a map from config field names to small rendering hints.

docs/plugins/sdk-agent-harness.md

@@ -133,25 +133,6 @@ OpenClaw requires Codex app-server `0.118.0` or newer. The Codex plugin checks
 the app-server initialize handshake and blocks older or unversioned servers so
 OpenClaw only runs against the protocol surface it has been tested with.
 
-### Native Codex harness mode
-
-The bundled `codex` harness is the native Codex mode for embedded OpenClaw
-agent turns. Enable the bundled `codex` plugin first, and include `codex` in
-`plugins.allow` if your config uses a restrictive allowlist. It is different
-from `openai-codex/*`:
-
-- `openai-codex/*` uses ChatGPT/Codex OAuth through the normal OpenClaw provider
-  path.
-- `codex/*` uses the bundled Codex provider and routes the turn through Codex
-  app-server.
-
-When this mode runs, Codex owns the native thread id, resume behavior,
-compaction, and app-server execution. OpenClaw still owns the chat channel,
-visible transcript mirror, tool policy, approvals, media delivery, and session
-selection. Use `embeddedHarness.runtime: "codex"` with
-`embeddedHarness.fallback: "none"` when you need to prove that the Codex
-app-server path is used and PI fallback is not hiding a broken native harness.
-
 ## Disable PI fallback
 
 By default, OpenClaw runs embedded agents with `agents.defaults.embeddedHarness`

docs/providers/alibaba.md

@@ -16,101 +16,57 @@ Alibaba Model Studio / DashScope.
 - Also accepted: `DASHSCOPE_API_KEY`, `QWEN_API_KEY`
 - API: DashScope / Model Studio async video generation
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set an API key">
-    ```bash
-    openclaw onboard --auth-choice qwen-standard-api-key
-    ```
-  </Step>
-  <Step title="Set a default video model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "alibaba/wan2.6-t2v",
-          },
-        },
+1. Set an API key:
+
+```bash
+openclaw onboard --auth-choice qwen-standard-api-key
+```
+
+2. Set a default video model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "alibaba/wan2.6-t2v",
       },
-    }
-    ```
-  </Step>
-  <Step title="Verify the provider is available">
-    ```bash
-    openclaw models list --provider alibaba
-    ```
-  </Step>
-</Steps>
-
-<Note>
-Any of the accepted auth keys (`MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`, `QWEN_API_KEY`) will work. The `qwen-standard-api-key` onboarding choice configures the shared DashScope credential.
-</Note>
+    },
+  },
+}
+```
 
 ## Built-in Wan models
 
 The bundled `alibaba` provider currently registers:
 
-| Model ref                  | Mode                      |
-| -------------------------- | ------------------------- |
-| `alibaba/wan2.6-t2v`       | Text-to-video             |
-| `alibaba/wan2.6-i2v`       | Image-to-video            |
-| `alibaba/wan2.6-r2v`       | Reference-to-video        |
-| `alibaba/wan2.6-r2v-flash` | Reference-to-video (fast) |
-| `alibaba/wan2.7-r2v`       | Reference-to-video        |
+- `alibaba/wan2.6-t2v`
+- `alibaba/wan2.6-i2v`
+- `alibaba/wan2.6-r2v`
+- `alibaba/wan2.6-r2v-flash`
+- `alibaba/wan2.7-r2v`
 
 ## Current limits
 
-| Parameter             | Limit                                                     |
-| --------------------- | --------------------------------------------------------- |
-| Output videos         | Up to **1** per request                                   |
-| Input images          | Up to **1**                                               |
-| Input videos          | Up to **4**                                               |
-| Duration              | Up to **10 seconds**                                      |
-| Supported controls    | `size`, `aspectRatio`, `resolution`, `audio`, `watermark` |
-| Reference image/video | Remote `http(s)` URLs only                                |
+- Up to **1** output video per request
+- Up to **1** input image
+- Up to **4** input videos
+- Up to **10 seconds** duration
+- Supports `size`, `aspectRatio`, `resolution`, `audio`, and `watermark`
+- Reference image/video mode currently requires **remote http(s) URLs**
 
-<Warning>
-Reference image/video mode currently requires **remote http(s) URLs**. Local file paths are not supported for reference inputs.
-</Warning>
+## Relationship to Qwen
 
-## Advanced configuration
+The bundled `qwen` provider also uses Alibaba-hosted DashScope endpoints for
+Wan video generation. Use:
 
-<AccordionGroup>
-  <Accordion title="Relationship to Qwen">
-    The bundled `qwen` provider also uses Alibaba-hosted DashScope endpoints for
-    Wan video generation. Use:
-
-    - `qwen/...` when you want the canonical Qwen provider surface
-    - `alibaba/...` when you want the direct vendor-owned Wan video surface
-
-    See the [Qwen provider docs](/providers/qwen) for more detail.
-
-  </Accordion>
-
-  <Accordion title="Auth key priority">
-    OpenClaw checks for auth keys in this order:
-
-    1. `MODELSTUDIO_API_KEY` (preferred)
-    2. `DASHSCOPE_API_KEY`
-    3. `QWEN_API_KEY`
-
-    Any of these will authenticate the `alibaba` provider.
-
-  </Accordion>
-</AccordionGroup>
+- `qwen/...` when you want the canonical Qwen provider surface
+- `alibaba/...` when you want the direct vendor-owned Wan video surface
 
 ## Related
 
-<CardGroup cols={2}>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Qwen" href="/providers/qwen" icon="microchip">
-    Qwen provider setup and DashScope integration.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">
-    Agent defaults and model configuration.
-  </Card>
-</CardGroup>
+- [Video Generation](/tools/video-generation)
+- [Qwen](/providers/qwen)
+- [Configuration Reference](/gateway/configuration-reference#agent-defaults)

docs/providers/anthropic.md

@@ -7,117 +7,83 @@ title: "Anthropic"
 
 # Anthropic (Claude)
 
-Anthropic builds the **Claude** model family. OpenClaw supports two auth routes:
-
-- **API key** — direct Anthropic API access with usage-based billing (`anthropic/*` models)
-- **Claude CLI** — reuse an existing Claude CLI login on the same host
+Anthropic builds the **Claude** model family and provides access via an API and
+Claude CLI. In OpenClaw, Anthropic API keys and Claude CLI reuse are both
+supported. Existing legacy Anthropic token profiles are still honored at
+runtime if they are already configured.
 
 <Warning>
 Anthropic staff told us OpenClaw-style Claude CLI usage is allowed again, so
-OpenClaw treats Claude CLI reuse and `claude -p` usage as sanctioned unless
-Anthropic publishes a new policy.
+OpenClaw treats Claude CLI reuse and `claude -p` usage as sanctioned for this
+integration unless Anthropic publishes a new policy.
 
 For long-lived gateway hosts, Anthropic API keys are still the clearest and
-most predictable production path.
+most predictable production path. If you already use Claude CLI on the host,
+OpenClaw can reuse that login directly.
 
 Anthropic's current public docs:
 
 - [Claude Code CLI reference](https://code.claude.com/docs/en/cli-reference)
 - [Claude Agent SDK overview](https://platform.claude.com/docs/en/agent-sdk/overview)
+
 - [Using Claude Code with your Pro or Max plan](https://support.claude.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan)
 - [Using Claude Code with your Team or Enterprise plan](https://support.anthropic.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan/)
-  </Warning>
 
-## Getting started
+If you want the clearest billing path, use an Anthropic API key instead.
+OpenClaw also supports other subscription-style options, including [OpenAI
+Codex](/providers/openai), [Qwen Cloud Coding Plan](/providers/qwen),
+[MiniMax Coding Plan](/providers/minimax), and [Z.AI / GLM Coding
+Plan](/providers/glm).
+</Warning>
 
-<Tabs>
-  <Tab title="API key">
-    **Best for:** standard API access and usage-based billing.
+## Option A: Anthropic API key
 
-    <Steps>
-      <Step title="Get your API key">
-        Create an API key in the [Anthropic Console](https://console.anthropic.com/).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard
-        # choose: Anthropic API key
-        ```
+**Best for:** standard API access and usage-based billing.
+Create your API key in the Anthropic Console.
 
-        Or pass the key directly:
+### CLI setup
 
-        ```bash
-        openclaw onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider anthropic
-        ```
-      </Step>
-    </Steps>
+```bash
+openclaw onboard
+# choose: Anthropic API key
 
-    ### Config example
+# or non-interactive
+openclaw onboard --anthropic-api-key "$ANTHROPIC_API_KEY"
+```
 
-    ```json5
-    {
-      env: { ANTHROPIC_API_KEY: "sk-ant-..." },
-      agents: { defaults: { model: { primary: "anthropic/claude-opus-4-6" } } },
-    }
-    ```
+### Anthropic config snippet
 
-  </Tab>
-
-  <Tab title="Claude CLI">
-    **Best for:** reusing an existing Claude CLI login without a separate API key.
-
-    <Steps>
-      <Step title="Ensure Claude CLI is installed and logged in">
-        Verify with:
-
-        ```bash
-        claude --version
-        ```
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard
-        # choose: Claude CLI
-        ```
-
-        OpenClaw detects and reuses the existing Claude CLI credentials.
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider anthropic
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Setup and runtime details for the Claude CLI backend are in [CLI Backends](/gateway/cli-backends).
-    </Note>
-
-    <Tip>
-    If you want the clearest billing path, use an Anthropic API key instead. OpenClaw also supports subscription-style options from [OpenAI Codex](/providers/openai), [Qwen Cloud](/providers/qwen), [MiniMax](/providers/minimax), and [Z.AI / GLM](/providers/glm).
-    </Tip>
-
-  </Tab>
-</Tabs>
+```json5
+{
+  env: { ANTHROPIC_API_KEY: "sk-ant-..." },
+  agents: { defaults: { model: { primary: "anthropic/claude-opus-4-6" } } },
+}
+```
 
 ## Thinking defaults (Claude 4.6)
 
-Claude 4.6 models default to `adaptive` thinking in OpenClaw when no explicit thinking level is set.
+- Anthropic Claude 4.6 models default to `adaptive` thinking in OpenClaw when no explicit thinking level is set.
+- You can override per-message (`/think:<level>`) or in model params:
+  `agents.defaults.models["anthropic/<model>"].params.thinking`.
+- Related Anthropic docs:
+  - [Adaptive thinking](https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking)
+  - [Extended thinking](https://platform.claude.com/docs/en/build-with-claude/extended-thinking)
 
-Override per-message with `/think:<level>` or in model params:
+## Fast mode (Anthropic API)
+
+OpenClaw's shared `/fast` toggle also supports direct public Anthropic traffic, including API-key and OAuth-authenticated requests sent to `api.anthropic.com`.
+
+- `/fast on` maps to `service_tier: "auto"`
+- `/fast off` maps to `service_tier: "standard_only"`
+- Config default:
 
 ```json5
 {
   agents: {
     defaults: {
       models: {
-        "anthropic/claude-opus-4-6": {
-          params: { thinking: "adaptive" },
+        "anthropic/claude-sonnet-4-6": {
+          params: { fastMode: true },
         },
       },
     },
@@ -125,21 +91,25 @@ Override per-message with `/think:<level>` or in model params:
 }
 ```
 
-<Note>
-Related Anthropic docs:
-- [Adaptive thinking](https://platform.claude.com/docs/en/build-with-claude/adaptive-thinking)
-- [Extended thinking](https://platform.claude.com/docs/en/build-with-claude/extended-thinking)
-</Note>
+Important limits:
 
-## Prompt caching
+- OpenClaw only injects Anthropic service tiers for direct `api.anthropic.com` requests. If you route `anthropic/*` through a proxy or gateway, `/fast` leaves `service_tier` untouched.
+- Explicit Anthropic `serviceTier` or `service_tier` model params override the `/fast` default when both are set.
+- Anthropic reports the effective tier on the response under `usage.service_tier`. On accounts without Priority Tier capacity, `service_tier: "auto"` may still resolve to `standard`.
 
-OpenClaw supports Anthropic's prompt caching feature for API-key auth.
+## Prompt caching (Anthropic API)
 
-| Value               | Cache duration | Description                            |
-| ------------------- | -------------- | -------------------------------------- |
-| `"short"` (default) | 5 minutes      | Applied automatically for API-key auth |
-| `"long"`            | 1 hour         | Extended cache                         |
-| `"none"`            | No caching     | Disable prompt caching                 |
+OpenClaw supports Anthropic's prompt caching feature. This is **API-only**; legacy Anthropic token auth does not honor cache settings.
+
+### Configuration
+
+Use the `cacheRetention` parameter in your model config:
+
+| Value   | Cache Duration | Description              |
+| ------- | -------------- | ------------------------ |
+| `none`  | No caching     | Disable prompt caching   |
+| `short` | 5 minutes      | Default for API Key auth |
+| `long`  | 1 hour         | Extended cache           |
 
 ```json5
 {
@@ -155,156 +125,122 @@ OpenClaw supports Anthropic's prompt caching feature for API-key auth.
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="Per-agent cache overrides">
-    Use model-level params as your baseline, then override specific agents via `agents.list[].params`:
+### Defaults
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "anthropic/claude-opus-4-6" },
-          models: {
-            "anthropic/claude-opus-4-6": {
-              params: { cacheRetention: "long" },
-            },
-          },
-        },
-        list: [
-          { id: "research", default: true },
-          { id: "alerts", params: { cacheRetention: "none" } },
-        ],
-      },
-    }
-    ```
+When using Anthropic API Key authentication, OpenClaw automatically applies `cacheRetention: "short"` (5-minute cache) for all Anthropic models. You can override this by explicitly setting `cacheRetention` in your config.
 
-    Config merge order:
+### Per-agent cacheRetention overrides
 
-    1. `agents.defaults.models["provider/model"].params`
-    2. `agents.list[].params` (matching `id`, overrides by key)
+Use model-level params as your baseline, then override specific agents via `agents.list[].params`.
 
-    This lets one agent keep a long-lived cache while another agent on the same model disables caching for bursty/low-reuse traffic.
-
-  </Accordion>
-
-  <Accordion title="Bedrock Claude notes">
-    - Anthropic Claude models on Bedrock (`amazon-bedrock/*anthropic.claude*`) accept `cacheRetention` pass-through when configured.
-    - Non-Anthropic Bedrock models are forced to `cacheRetention: "none"` at runtime.
-    - API-key smart defaults also seed `cacheRetention: "short"` for Claude-on-Bedrock refs when no explicit value is set.
-  </Accordion>
-</AccordionGroup>
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Fast mode">
-    OpenClaw's shared `/fast` toggle supports direct Anthropic traffic (API-key and OAuth to `api.anthropic.com`).
-
-    | Command | Maps to |
-    |---------|---------|
-    | `/fast on` | `service_tier: "auto"` |
-    | `/fast off` | `service_tier: "standard_only"` |
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "anthropic/claude-sonnet-4-6": {
-              params: { fastMode: true },
-            },
-          },
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "anthropic/claude-opus-4-6" },
+      models: {
+        "anthropic/claude-opus-4-6": {
+          params: { cacheRetention: "long" }, // baseline for most agents
         },
       },
-    }
-    ```
+    },
+    list: [
+      { id: "research", default: true },
+      { id: "alerts", params: { cacheRetention: "none" } }, // override for this agent only
+    ],
+  },
+}
+```
 
-    <Note>
-    - Only injected for direct `api.anthropic.com` requests. Proxy routes leave `service_tier` untouched.
-    - Explicit `serviceTier` or `service_tier` params override `/fast` when both are set.
-    - On accounts without Priority Tier capacity, `service_tier: "auto"` may resolve to `standard`.
-    </Note>
+Config merge order for cache-related params:
 
-  </Accordion>
+1. `agents.defaults.models["provider/model"].params`
+2. `agents.list[].params` (matching `id`, overrides by key)
 
-  <Accordion title="Media understanding (image and PDF)">
-    The bundled Anthropic plugin registers image and PDF understanding. OpenClaw
-    auto-resolves media capabilities from the configured Anthropic auth — no
-    additional config is needed.
+This lets one agent keep a long-lived cache while another agent on the same model disables caching to avoid write costs on bursty/low-reuse traffic.
 
-    | Property       | Value                |
-    | -------------- | -------------------- |
-    | Default model  | `claude-opus-4-6`    |
-    | Supported input | Images, PDF documents |
+### Bedrock Claude notes
 
-    When an image or PDF is attached to a conversation, OpenClaw automatically
-    routes it through the Anthropic media understanding provider.
+- Anthropic Claude models on Bedrock (`amazon-bedrock/*anthropic.claude*`) accept `cacheRetention` pass-through when configured.
+- Non-Anthropic Bedrock models are forced to `cacheRetention: "none"` at runtime.
+- Anthropic API-key smart defaults also seed `cacheRetention: "short"` for Claude-on-Bedrock model refs when no explicit value is set.
 
-  </Accordion>
+## 1M context window (Anthropic beta)
 
-  <Accordion title="1M context window (beta)">
-    Anthropic's 1M context window is beta-gated. Enable it per model:
+Anthropic's 1M context window is beta-gated. In OpenClaw, enable it per model
+with `params.context1m: true` for supported Opus/Sonnet models.
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "anthropic/claude-opus-4-6": {
-              params: { context1m: true },
-            },
-          },
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "anthropic/claude-opus-4-6": {
+          params: { context1m: true },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    OpenClaw maps this to `anthropic-beta: context-1m-2025-08-07` on requests.
+OpenClaw maps this to `anthropic-beta: context-1m-2025-08-07` on Anthropic
+requests.
 
-    <Warning>
-    Requires long-context access on your Anthropic credential. Legacy token auth (`sk-ant-oat-*`) is rejected for 1M context requests — OpenClaw logs a warning and falls back to the standard context window.
-    </Warning>
+This only activates when `params.context1m` is explicitly set to `true` for
+that model.
 
-  </Accordion>
-</AccordionGroup>
+Requirement: Anthropic must allow long-context usage on that credential.
+
+Note: Anthropic currently rejects `context-1m-*` beta requests when using
+legacy Anthropic token auth (`sk-ant-oat-*`). If you configure
+`context1m: true` with that legacy auth mode, OpenClaw logs a warning and
+falls back to the standard context window by skipping the context1m beta
+header while keeping the required OAuth betas.
+
+## Claude CLI backend
+
+The bundled Anthropic `claude-cli` backend is supported in OpenClaw.
+
+- Anthropic staff told us this usage is allowed again.
+- OpenClaw therefore treats Claude CLI reuse and `claude -p` usage as
+  sanctioned for this integration unless Anthropic publishes a new policy.
+- Anthropic API keys remain the clearest production path for always-on gateway
+  hosts and explicit server-side billing control.
+- Setup and runtime details are in [/gateway/cli-backends](/gateway/cli-backends).
+
+## Notes
+
+- Anthropic's public Claude Code docs still document direct CLI usage such as
+  `claude -p`, and Anthropic staff told us OpenClaw-style Claude CLI usage is
+  allowed again. We are treating that guidance as settled unless Anthropic
+  publishes a new policy change.
+- Anthropic setup-token remains available in OpenClaw as a supported token-auth path, but OpenClaw now prefers Claude CLI reuse and `claude -p` when available.
+- Auth details + reuse rules are in [/concepts/oauth](/concepts/oauth).
 
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="401 errors / token suddenly invalid">
-    Anthropic token auth can expire or be revoked. For new setups, migrate to an Anthropic API key.
-  </Accordion>
+**401 errors / token suddenly invalid**
 
-  <Accordion title='No API key found for provider "anthropic"'>
-    Auth is **per agent**. New agents don't inherit the main agent's keys. Re-run onboarding for that agent, or configure an API key on the gateway host, then verify with `openclaw models status`.
-  </Accordion>
+- Anthropic token auth can expire or be revoked.
+- For new setup, migrate to an Anthropic API key.
 
-  <Accordion title='No credentials found for profile "anthropic:default"'>
-    Run `openclaw models status` to see which auth profile is active. Re-run onboarding, or configure an API key for that profile path.
-  </Accordion>
+**No API key found for provider "anthropic"**
 
-  <Accordion title="No available auth profile (all in cooldown)">
-    Check `openclaw models status --json` for `auth.unusableProfiles`. Anthropic rate-limit cooldowns can be model-scoped, so a sibling Anthropic model may still be usable. Add another Anthropic profile or wait for cooldown.
-  </Accordion>
-</AccordionGroup>
+- Auth is **per agent**. New agents don’t inherit the main agent’s keys.
+- Re-run onboarding for that agent, or configure an API key on the gateway
+  host, then verify with `openclaw models status`.
 
-<Note>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Note>
+**No credentials found for profile `anthropic:default`**
 
-## Related
+- Run `openclaw models status` to see which auth profile is active.
+- Re-run onboarding, or configure an API key for that profile path.
 
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="CLI backends" href="/gateway/cli-backends" icon="terminal">
-    Claude CLI backend setup and runtime details.
-  </Card>
-  <Card title="Prompt caching" href="/reference/prompt-caching" icon="database">
-    How prompt caching works across providers.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-</CardGroup>
+**No available auth profile (all in cooldown/unavailable)**
+
+- Check `openclaw models status --json` for `auth.unusableProfiles`.
+- Anthropic rate-limit cooldowns can be model-scoped, so a sibling Anthropic
+  model may still be usable even when the current one is cooling down.
+- Add another Anthropic profile or wait for cooldown.
+
+More: [/gateway/troubleshooting](/gateway/troubleshooting) and [/help/faq](/help/faq).

docs/providers/arcee.md

@@ -12,89 +12,58 @@ read_when:
 
 Arcee AI models can be accessed directly via the Arcee platform or through [OpenRouter](/providers/openrouter).
 
-| Property | Value                                                                                 |
-| -------- | ------------------------------------------------------------------------------------- |
-| Provider | `arcee`                                                                               |
-| Auth     | `ARCEEAI_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter)                   |
-| API      | OpenAI-compatible                                                                     |
-| Base URL | `https://api.arcee.ai/api/v1` (direct) or `https://openrouter.ai/api/v1` (OpenRouter) |
+- Provider: `arcee`
+- Auth: `ARCEEAI_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter)
+- API: OpenAI-compatible
+- Base URL: `https://api.arcee.ai/api/v1` (direct) or `https://openrouter.ai/api/v1` (OpenRouter)
 
-## Getting started
+## Quick start
 
-<Tabs>
-  <Tab title="Direct (Arcee platform)">
-    <Steps>
-      <Step title="Get an API key">
-        Create an API key at [Arcee AI](https://chat.arcee.ai/).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice arceeai-api-key
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "arcee/trinity-large-thinking" },
-            },
-          },
-        }
-        ```
-      </Step>
-    </Steps>
-  </Tab>
+1. Get an API key from [Arcee AI](https://chat.arcee.ai/) or [OpenRouter](https://openrouter.ai/keys).
 
-  <Tab title="Via OpenRouter">
-    <Steps>
-      <Step title="Get an API key">
-        Create an API key at [OpenRouter](https://openrouter.ai/keys).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice arceeai-openrouter
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "arcee/trinity-large-thinking" },
-            },
-          },
-        }
-        ```
+2. Set the API key (recommended: store it for the Gateway):
 
-        The same model refs work for both direct and OpenRouter setups (for example `arcee/trinity-large-thinking`).
-      </Step>
-    </Steps>
+```bash
+# Direct (Arcee platform)
+openclaw onboard --auth-choice arceeai-api-key
 
-  </Tab>
-</Tabs>
+# Via OpenRouter
+openclaw onboard --auth-choice arceeai-openrouter
+```
 
-## Non-interactive setup
+3. Set a default model:
 
-<Tabs>
-  <Tab title="Direct (Arcee platform)">
-    ```bash
-    openclaw onboard --non-interactive \
-      --mode local \
-      --auth-choice arceeai-api-key \
-      --arceeai-api-key "$ARCEEAI_API_KEY"
-    ```
-  </Tab>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "arcee/trinity-large-thinking" },
+    },
+  },
+}
+```
 
-  <Tab title="Via OpenRouter">
-    ```bash
-    openclaw onboard --non-interactive \
-      --mode local \
-      --auth-choice arceeai-openrouter \
-      --openrouter-api-key "$OPENROUTER_API_KEY"
-    ```
-  </Tab>
-</Tabs>
+## Non-interactive example
+
+```bash
+# Direct (Arcee platform)
+openclaw onboard --non-interactive \
+  --mode local \
+  --auth-choice arceeai-api-key \
+  --arceeai-api-key "$ARCEEAI_API_KEY"
+
+# Via OpenRouter
+openclaw onboard --non-interactive \
+  --mode local \
+  --auth-choice arceeai-openrouter \
+  --openrouter-api-key "$OPENROUTER_API_KEY"
+```
+
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure `ARCEEAI_API_KEY`
+(or `OPENROUTER_API_KEY`) is available to that process (for example, in
+`~/.openclaw/.env` or via `env.shellEnv`).
 
 ## Built-in catalog
 
@@ -106,41 +75,13 @@ OpenClaw currently ships this bundled Arcee catalog:
 | `arcee/trinity-large-preview`  | Trinity Large Preview  | text  | 128K    | $0.25 / $1.00        | General-purpose; 400B params, 13B active  |
 | `arcee/trinity-mini`           | Trinity Mini 26B       | text  | 128K    | $0.045 / $0.15       | Fast and cost-efficient; function calling |
 
-<Tip>
+The same model refs work for both direct and OpenRouter setups (for example `arcee/trinity-large-thinking`).
+
 The onboarding preset sets `arcee/trinity-large-thinking` as the default model.
-</Tip>
 
 ## Supported features
 
-| Feature                                       | Supported                    |
-| --------------------------------------------- | ---------------------------- |
-| Streaming                                     | Yes                          |
-| Tool use / function calling                   | Yes                          |
-| Structured output (JSON mode and JSON schema) | Yes                          |
-| Extended thinking                             | Yes (Trinity Large Thinking) |
-
-<AccordionGroup>
-  <Accordion title="Environment note">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `ARCEEAI_API_KEY`
-    (or `OPENROUTER_API_KEY`) is available to that process (for example, in
-    `~/.openclaw/.env` or via `env.shellEnv`).
-  </Accordion>
-
-  <Accordion title="OpenRouter routing">
-    When using Arcee models via OpenRouter, the same `arcee/*` model refs apply.
-    OpenClaw handles routing transparently based on your auth choice. See the
-    [OpenRouter provider docs](/providers/openrouter) for OpenRouter-specific
-    configuration details.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="OpenRouter" href="/providers/openrouter" icon="shuffle">
-    Access Arcee models and many others through a single API key.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>
+- Streaming
+- Tool use / function calling
+- Structured output (JSON mode and JSON schema)
+- Extended thinking (Trinity Large Thinking)

docs/providers/bedrock-mantle.md

@@ -13,95 +13,55 @@ the Mantle OpenAI-compatible endpoint. Mantle hosts open-source and
 third-party models (GPT-OSS, Qwen, Kimi, GLM, and similar) through a standard
 `/v1/chat/completions` surface backed by Bedrock infrastructure.
 
-| Property       | Value                                                                               |
-| -------------- | ----------------------------------------------------------------------------------- |
-| Provider ID    | `amazon-bedrock-mantle`                                                             |
-| API            | `openai-completions` (OpenAI-compatible)                                            |
-| Auth           | Explicit `AWS_BEARER_TOKEN_BEDROCK` or IAM credential-chain bearer-token generation |
-| Default region | `us-east-1` (override with `AWS_REGION` or `AWS_DEFAULT_REGION`)                    |
+## What OpenClaw supports
 
-## Getting started
-
-Choose your preferred auth method and follow the setup steps.
-
-<Tabs>
-  <Tab title="Explicit bearer token">
-    **Best for:** environments where you already have a Mantle bearer token.
-
-    <Steps>
-      <Step title="Set the bearer token on the gateway host">
-        ```bash
-        export AWS_BEARER_TOKEN_BEDROCK="..."
-        ```
-
-        Optionally set a region (defaults to `us-east-1`):
-
-        ```bash
-        export AWS_REGION="us-west-2"
-        ```
-      </Step>
-      <Step title="Verify models are discovered">
-        ```bash
-        openclaw models list
-        ```
-
-        Discovered models appear under the `amazon-bedrock-mantle` provider. No
-        additional config is required unless you want to override defaults.
-      </Step>
-    </Steps>
-
-  </Tab>
-
-  <Tab title="IAM credentials">
-    **Best for:** using AWS SDK-compatible credentials (shared config, SSO, web identity, instance or task roles).
-
-    <Steps>
-      <Step title="Configure AWS credentials on the gateway host">
-        Any AWS SDK-compatible auth source works:
-
-        ```bash
-        export AWS_PROFILE="default"
-        export AWS_REGION="us-west-2"
-        ```
-      </Step>
-      <Step title="Verify models are discovered">
-        ```bash
-        openclaw models list
-        ```
-
-        OpenClaw generates a Mantle bearer token from the credential chain automatically.
-      </Step>
-    </Steps>
-
-    <Tip>
-    When `AWS_BEARER_TOKEN_BEDROCK` is not set, OpenClaw mints the bearer token for you from the AWS default credential chain, including shared credentials/config profiles, SSO, web identity, and instance or task roles.
-    </Tip>
-
-  </Tab>
-</Tabs>
+- Provider: `amazon-bedrock-mantle`
+- API: `openai-completions` (OpenAI-compatible)
+- Auth: explicit `AWS_BEARER_TOKEN_BEDROCK` or IAM credential-chain bearer-token generation
+- Region: `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`)
 
 ## Automatic model discovery
 
 When `AWS_BEARER_TOKEN_BEDROCK` is set, OpenClaw uses it directly. Otherwise,
 OpenClaw attempts to generate a Mantle bearer token from the AWS default
-credential chain. It then discovers available Mantle models by querying the
-region's `/v1/models` endpoint.
+credential chain, including shared credentials/config profiles, SSO, web
+identity, and instance or task roles. It then discovers available Mantle
+models by querying the region's `/v1/models` endpoint. Discovery results are
+cached for 1 hour, and IAM-derived bearer tokens are refreshed hourly.
 
-| Behavior          | Detail                    |
-| ----------------- | ------------------------- |
-| Discovery cache   | Results cached for 1 hour |
-| IAM token refresh | Hourly                    |
-
-<Note>
-The bearer token is the same `AWS_BEARER_TOKEN_BEDROCK` used by the standard [Amazon Bedrock](/providers/bedrock) provider.
-</Note>
-
-### Supported regions
-
-`us-east-1`, `us-east-2`, `us-west-2`, `ap-northeast-1`,
+Supported regions: `us-east-1`, `us-east-2`, `us-west-2`, `ap-northeast-1`,
 `ap-south-1`, `ap-southeast-3`, `eu-central-1`, `eu-west-1`, `eu-west-2`,
 `eu-south-1`, `eu-north-1`, `sa-east-1`.
 
+## Onboarding
+
+1. Choose one auth path on the **gateway host**:
+
+Explicit bearer token:
+
+```bash
+export AWS_BEARER_TOKEN_BEDROCK="..."
+# Optional (defaults to us-east-1):
+export AWS_REGION="us-west-2"
+```
+
+IAM credentials:
+
+```bash
+# Any AWS SDK-compatible auth source works here, for example:
+export AWS_PROFILE="default"
+export AWS_REGION="us-west-2"
+```
+
+2. Verify models are discovered:
+
+```bash
+openclaw models list
+```
+
+Discovered models appear under the `amazon-bedrock-mantle` provider. No
+additional config is required unless you want to override defaults.
+
 ## Manual configuration
 
 If you prefer explicit config instead of auto-discovery:
@@ -132,46 +92,13 @@ If you prefer explicit config instead of auto-discovery:
 }
 ```
 
-## Advanced notes
+## Notes
 
-<AccordionGroup>
-  <Accordion title="Reasoning support">
-    Reasoning support is inferred from model IDs containing patterns like
-    `thinking`, `reasoner`, or `gpt-oss-120b`. OpenClaw sets `reasoning: true`
-    automatically for matching models during discovery.
-  </Accordion>
-
-  <Accordion title="Endpoint unavailability">
-    If the Mantle endpoint is unavailable or returns no models, the provider is
-    silently skipped. OpenClaw does not error; other configured providers
-    continue to work normally.
-  </Accordion>
-
-  <Accordion title="Relationship to Amazon Bedrock provider">
-    Bedrock Mantle is a separate provider from the standard
-    [Amazon Bedrock](/providers/bedrock) provider. Mantle uses an
-    OpenAI-compatible `/v1` surface, while the standard Bedrock provider uses
-    the native Bedrock API.
-
-    Both providers share the same `AWS_BEARER_TOKEN_BEDROCK` credential when
-    present.
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Amazon Bedrock" href="/providers/bedrock" icon="cloud">
-    Native Bedrock provider for Anthropic Claude, Titan, and other models.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    Common issues and how to resolve them.
-  </Card>
-</CardGroup>
+- OpenClaw can mint the Mantle bearer token for you from AWS SDK-compatible
+  IAM credentials when `AWS_BEARER_TOKEN_BEDROCK` is not set.
+- The bearer token is the same `AWS_BEARER_TOKEN_BEDROCK` used by the standard
+  [Amazon Bedrock](/providers/bedrock) provider.
+- Reasoning support is inferred from model IDs containing patterns like
+  `thinking`, `reasoner`, or `gpt-oss-120b`.
+- If the Mantle endpoint is unavailable or returns no models, the provider is
+  silently skipped.

docs/providers/bedrock.md

@@ -8,130 +8,16 @@ title: "Amazon Bedrock"
 
 # Amazon Bedrock
 
-OpenClaw can use **Amazon Bedrock** models via pi-ai's **Bedrock Converse**
+OpenClaw can use **Amazon Bedrock** models via pi‑ai’s **Bedrock Converse**
 streaming provider. Bedrock auth uses the **AWS SDK default credential chain**,
 not an API key.
 
-| Property | Value                                                       |
-| -------- | ----------------------------------------------------------- |
-| Provider | `amazon-bedrock`                                            |
-| API      | `bedrock-converse-stream`                                   |
-| Auth     | AWS credentials (env vars, shared config, or instance role) |
-| Region   | `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`) |
+## What pi-ai supports
 
-## Getting started
-
-Choose your preferred auth method and follow the setup steps.
-
-<Tabs>
-  <Tab title="Access keys / env vars">
-    **Best for:** developer machines, CI, or hosts where you manage AWS credentials directly.
-
-    <Steps>
-      <Step title="Set AWS credentials on the gateway host">
-        ```bash
-        export AWS_ACCESS_KEY_ID="AKIA..."
-        export AWS_SECRET_ACCESS_KEY="..."
-        export AWS_REGION="us-east-1"
-        # Optional:
-        export AWS_SESSION_TOKEN="..."
-        export AWS_PROFILE="your-profile"
-        # Optional (Bedrock API key/bearer token):
-        export AWS_BEARER_TOKEN_BEDROCK="..."
-        ```
-      </Step>
-      <Step title="Add a Bedrock provider and model to your config">
-        No `apiKey` is required. Configure the provider with `auth: "aws-sdk"`:
-
-        ```json5
-        {
-          models: {
-            providers: {
-              "amazon-bedrock": {
-                baseUrl: "https://bedrock-runtime.us-east-1.amazonaws.com",
-                api: "bedrock-converse-stream",
-                auth: "aws-sdk",
-                models: [
-                  {
-                    id: "us.anthropic.claude-opus-4-6-v1:0",
-                    name: "Claude Opus 4.6 (Bedrock)",
-                    reasoning: true,
-                    input: ["text", "image"],
-                    cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                    contextWindow: 200000,
-                    maxTokens: 8192,
-                  },
-                ],
-              },
-            },
-          },
-          agents: {
-            defaults: {
-              model: { primary: "amazon-bedrock/us.anthropic.claude-opus-4-6-v1:0" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list
-        ```
-      </Step>
-    </Steps>
-
-    <Tip>
-    With env-marker auth (`AWS_ACCESS_KEY_ID`, `AWS_PROFILE`, or `AWS_BEARER_TOKEN_BEDROCK`), OpenClaw auto-enables the implicit Bedrock provider for model discovery without extra config.
-    </Tip>
-
-  </Tab>
-
-  <Tab title="EC2 instance roles (IMDS)">
-    **Best for:** EC2 instances with an IAM role attached, using the instance metadata service for authentication.
-
-    <Steps>
-      <Step title="Enable discovery explicitly">
-        When using IMDS, OpenClaw cannot detect AWS auth from env markers alone, so you must opt in:
-
-        ```bash
-        openclaw config set plugins.entries.amazon-bedrock.config.discovery.enabled true
-        openclaw config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
-        ```
-      </Step>
-      <Step title="Optionally add an env marker for auto mode">
-        If you also want the env-marker auto-detection path to work (for example, for `openclaw status` surfaces):
-
-        ```bash
-        export AWS_PROFILE=default
-        export AWS_REGION=us-east-1
-        ```
-
-        You do **not** need a fake API key.
-      </Step>
-      <Step title="Verify models are discovered">
-        ```bash
-        openclaw models list
-        ```
-      </Step>
-    </Steps>
-
-    <Warning>
-    The IAM role attached to your EC2 instance must have the following permissions:
-
-    - `bedrock:InvokeModel`
-    - `bedrock:InvokeModelWithResponseStream`
-    - `bedrock:ListFoundationModels` (for automatic discovery)
-    - `bedrock:ListInferenceProfiles` (for inference profile discovery)
-
-    Or attach the managed policy `AmazonBedrockFullAccess`.
-    </Warning>
-
-    <Note>
-    You only need `AWS_PROFILE=default` if you specifically want an env marker for auto mode or status surfaces. The actual Bedrock runtime auth path uses the AWS SDK default chain, so IMDS instance-role auth works even without env markers.
-    </Note>
-
-  </Tab>
-</Tabs>
+- Provider: `amazon-bedrock`
+- API: `bedrock-converse-stream`
+- Auth: AWS credentials (env vars, shared config, or instance role)
+- Region: `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`)
 
 ## Automatic model discovery
 
@@ -152,52 +38,127 @@ How the implicit provider is enabled:
   shared config, SSO, and IMDS instance-role auth can work even when discovery
   needed `enabled: true` to opt in.
 
-<Note>
-For explicit `models.providers["amazon-bedrock"]` entries, OpenClaw can still resolve Bedrock env-marker auth early from AWS env markers such as `AWS_BEARER_TOKEN_BEDROCK` without forcing full runtime auth loading. The actual model-call auth path still uses the AWS SDK default chain.
-</Note>
+Config options live under `plugins.entries.amazon-bedrock.config.discovery`:
 
-<AccordionGroup>
-  <Accordion title="Discovery config options">
-    Config options live under `plugins.entries.amazon-bedrock.config.discovery`:
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          "amazon-bedrock": {
-            config: {
-              discovery: {
-                enabled: true,
-                region: "us-east-1",
-                providerFilter: ["anthropic", "amazon"],
-                refreshInterval: 3600,
-                defaultContextWindow: 32000,
-                defaultMaxTokens: 4096,
-              },
-            },
+```json5
+{
+  plugins: {
+    entries: {
+      "amazon-bedrock": {
+        config: {
+          discovery: {
+            enabled: true,
+            region: "us-east-1",
+            providerFilter: ["anthropic", "amazon"],
+            refreshInterval: 3600,
+            defaultContextWindow: 32000,
+            defaultMaxTokens: 4096,
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    | Option | Default | Description |
-    | ------ | ------- | ----------- |
-    | `enabled` | auto | In auto mode, OpenClaw only enables the implicit Bedrock provider when it sees a supported AWS env marker. Set `true` to force discovery. |
-    | `region` | `AWS_REGION` / `AWS_DEFAULT_REGION` / `us-east-1` | AWS region used for discovery API calls. |
-    | `providerFilter` | (all) | Matches Bedrock provider names (for example `anthropic`, `amazon`). |
-    | `refreshInterval` | `3600` | Cache duration in seconds. Set to `0` to disable caching. |
-    | `defaultContextWindow` | `32000` | Context window used for discovered models (override if you know your model limits). |
-    | `defaultMaxTokens` | `4096` | Max output tokens used for discovered models (override if you know your model limits). |
+Notes:
 
-  </Accordion>
-</AccordionGroup>
+- `enabled` defaults to auto mode. In auto mode, OpenClaw only enables the
+  implicit Bedrock provider when it sees a supported AWS env marker.
+- `region` defaults to `AWS_REGION` or `AWS_DEFAULT_REGION`, then `us-east-1`.
+- `providerFilter` matches Bedrock provider names (for example `anthropic`).
+- `refreshInterval` is seconds; set to `0` to disable caching.
+- `defaultContextWindow` (default: `32000`) and `defaultMaxTokens` (default: `4096`)
+  are used for discovered models (override if you know your model limits).
+- For explicit `models.providers["amazon-bedrock"]` entries, OpenClaw can still
+  resolve Bedrock env-marker auth early from AWS env markers such as
+  `AWS_BEARER_TOKEN_BEDROCK` without forcing full runtime auth loading. The
+  actual model-call auth path still uses the AWS SDK default chain.
+
+## Onboarding
+
+1. Ensure AWS credentials are available on the **gateway host**:
+
+```bash
+export AWS_ACCESS_KEY_ID="AKIA..."
+export AWS_SECRET_ACCESS_KEY="..."
+export AWS_REGION="us-east-1"
+# Optional:
+export AWS_SESSION_TOKEN="..."
+export AWS_PROFILE="your-profile"
+# Optional (Bedrock API key/bearer token):
+export AWS_BEARER_TOKEN_BEDROCK="..."
+```
+
+2. Add a Bedrock provider and model to your config (no `apiKey` required):
+
+```json5
+{
+  models: {
+    providers: {
+      "amazon-bedrock": {
+        baseUrl: "https://bedrock-runtime.us-east-1.amazonaws.com",
+        api: "bedrock-converse-stream",
+        auth: "aws-sdk",
+        models: [
+          {
+            id: "us.anthropic.claude-opus-4-6-v1:0",
+            name: "Claude Opus 4.6 (Bedrock)",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 200000,
+            maxTokens: 8192,
+          },
+        ],
+      },
+    },
+  },
+  agents: {
+    defaults: {
+      model: { primary: "amazon-bedrock/us.anthropic.claude-opus-4-6-v1:0" },
+    },
+  },
+}
+```
+
+## EC2 Instance Roles
+
+When running OpenClaw on an EC2 instance with an IAM role attached, the AWS SDK
+can use the instance metadata service (IMDS) for authentication. For Bedrock
+model discovery, OpenClaw only auto-enables the implicit provider from AWS env
+markers unless you explicitly set
+`plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
+
+Recommended setup for IMDS-backed hosts:
+
+- Set `plugins.entries.amazon-bedrock.config.discovery.enabled` to `true`.
+- Set `plugins.entries.amazon-bedrock.config.discovery.region` (or export `AWS_REGION`).
+- You do **not** need a fake API key.
+- You only need `AWS_PROFILE=default` if you specifically want an env marker
+  for auto mode or status surfaces.
+
+```bash
+# Recommended: explicit discovery enable + region
+openclaw config set plugins.entries.amazon-bedrock.config.discovery.enabled true
+openclaw config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
+
+# Optional: add an env marker if you want auto mode without explicit enable
+export AWS_PROFILE=default
+export AWS_REGION=us-east-1
+```
+
+**Required IAM permissions** for the EC2 instance role:
+
+- `bedrock:InvokeModel`
+- `bedrock:InvokeModelWithResponseStream`
+- `bedrock:ListFoundationModels` (for automatic discovery)
+- `bedrock:ListInferenceProfiles` (for inference profile discovery)
+
+Or attach the managed policy `AmazonBedrockFullAccess`.
 
 ## Quick setup (AWS path)
 
-This walkthrough creates an IAM role, attaches Bedrock permissions, associates
-the instance profile, and enables OpenClaw discovery on the EC2 host.
-
 ```bash
 # 1. Create IAM role and instance profile
 aws iam create-role --role-name EC2-Bedrock-Access \
@@ -236,127 +197,106 @@ source ~/.bashrc
 openclaw models list
 ```
 
-## Advanced configuration
+## Inference profiles
 
-<AccordionGroup>
-  <Accordion title="Inference profiles">
-    OpenClaw discovers **regional and global inference profiles** alongside
-    foundation models. When a profile maps to a known foundation model, the
-    profile inherits that model's capabilities (context window, max tokens,
-    reasoning, vision) and the correct Bedrock request region is injected
-    automatically. This means cross-region Claude profiles work without manual
-    provider overrides.
+OpenClaw discovers **regional and global inference profiles** alongside
+foundation models. When a profile maps to a known foundation model, the
+profile inherits that model's capabilities (context window, max tokens,
+reasoning, vision) and the correct Bedrock request region is injected
+automatically. This means cross-region Claude profiles work without manual
+provider overrides.
 
-    Inference profile IDs look like `us.anthropic.claude-opus-4-6-v1:0` (regional)
-    or `anthropic.claude-opus-4-6-v1:0` (global). If the backing model is already
-    in the discovery results, the profile inherits its full capability set;
-    otherwise safe defaults apply.
+Inference profile IDs look like `us.anthropic.claude-opus-4-6-v1:0` (regional)
+or `anthropic.claude-opus-4-6-v1:0` (global). If the backing model is already
+in the discovery results, the profile inherits its full capability set;
+otherwise safe defaults apply.
 
-    No extra configuration is needed. As long as discovery is enabled and the IAM
-    principal has `bedrock:ListInferenceProfiles`, profiles appear alongside
-    foundation models in `openclaw models list`.
+No extra configuration is needed. As long as discovery is enabled and the IAM
+principal has `bedrock:ListInferenceProfiles`, profiles appear alongside
+foundation models in `openclaw models list`.
 
-  </Accordion>
+## Notes
 
-  <Accordion title="Guardrails">
-    You can apply [Amazon Bedrock Guardrails](https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails.html)
-    to all Bedrock model invocations by adding a `guardrail` object to the
-    `amazon-bedrock` plugin config. Guardrails let you enforce content filtering,
-    topic denial, word filters, sensitive information filters, and contextual
-    grounding checks.
+- Bedrock requires **model access** enabled in your AWS account/region.
+- Automatic discovery needs the `bedrock:ListFoundationModels` and
+  `bedrock:ListInferenceProfiles` permissions.
+- If you rely on auto mode, set one of the supported AWS auth env markers on the
+  gateway host. If you prefer IMDS/shared-config auth without env markers, set
+  `plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
+- OpenClaw surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
+  then `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, then `AWS_PROFILE`, then the
+  default AWS SDK chain.
+- Reasoning support depends on the model; check the Bedrock model card for
+  current capabilities.
+- If you prefer a managed key flow, you can also place an OpenAI‑compatible
+  proxy in front of Bedrock and configure it as an OpenAI provider instead.
 
-    ```json5
-    {
-      plugins: {
-        entries: {
-          "amazon-bedrock": {
-            config: {
-              guardrail: {
-                guardrailIdentifier: "abc123", // guardrail ID or full ARN
-                guardrailVersion: "1", // version number or "DRAFT"
-                streamProcessingMode: "sync", // optional: "sync" or "async"
-                trace: "enabled", // optional: "enabled", "disabled", or "enabled_full"
-              },
-            },
+## Guardrails
+
+You can apply [Amazon Bedrock Guardrails](https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails.html)
+to all Bedrock model invocations by adding a `guardrail` object to the
+`amazon-bedrock` plugin config. Guardrails let you enforce content filtering,
+topic denial, word filters, sensitive information filters, and contextual
+grounding checks.
+
+```json5
+{
+  plugins: {
+    entries: {
+      "amazon-bedrock": {
+        config: {
+          guardrail: {
+            guardrailIdentifier: "abc123", // guardrail ID or full ARN
+            guardrailVersion: "1", // version number or "DRAFT"
+            streamProcessingMode: "sync", // optional: "sync" or "async"
+            trace: "enabled", // optional: "enabled", "disabled", or "enabled_full"
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    | Option | Required | Description |
-    | ------ | -------- | ----------- |
-    | `guardrailIdentifier` | Yes | Guardrail ID (e.g. `abc123`) or full ARN (e.g. `arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123`). |
-    | `guardrailVersion` | Yes | Published version number, or `"DRAFT"` for the working draft. |
-    | `streamProcessingMode` | No | `"sync"` or `"async"` for guardrail evaluation during streaming. If omitted, Bedrock uses its default. |
-    | `trace` | No | `"enabled"` or `"enabled_full"` for debugging; omit or set `"disabled"` for production. |
+- `guardrailIdentifier` (required) accepts a guardrail ID (e.g. `abc123`) or a
+  full ARN (e.g. `arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123`).
+- `guardrailVersion` (required) specifies which published version to use, or
+  `"DRAFT"` for the working draft.
+- `streamProcessingMode` (optional) controls whether guardrail evaluation runs
+  synchronously (`"sync"`) or asynchronously (`"async"`) during streaming. If
+  omitted, Bedrock uses its default behavior.
+- `trace` (optional) enables guardrail trace output in the API response. Set to
+  `"enabled"` or `"enabled_full"` for debugging; omit or set `"disabled"` for
+  production.
 
-    <Warning>
-    The IAM principal used by the gateway must have the `bedrock:ApplyGuardrail` permission in addition to the standard invoke permissions.
-    </Warning>
+The IAM principal used by the gateway must have the `bedrock:ApplyGuardrail`
+permission in addition to the standard invoke permissions.
 
-  </Accordion>
+## Embeddings for memory search
 
-  <Accordion title="Embeddings for memory search">
-    Bedrock can also serve as the embedding provider for
-    [memory search](/concepts/memory-search). This is configured separately from the
-    inference provider -- set `agents.defaults.memorySearch.provider` to `"bedrock"`:
+Bedrock can also serve as the embedding provider for
+[memory search](/concepts/memory-search). This is configured separately from the
+inference provider — set `agents.defaults.memorySearch.provider` to `"bedrock"`:
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          memorySearch: {
-            provider: "bedrock",
-            model: "amazon.titan-embed-text-v2:0", // default
-          },
-        },
+```json5
+{
+  agents: {
+    defaults: {
+      memorySearch: {
+        provider: "bedrock",
+        model: "amazon.titan-embed-text-v2:0", // default
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    Bedrock embeddings use the same AWS SDK credential chain as inference (instance
-    roles, SSO, access keys, shared config, and web identity). No API key is
-    needed. When `provider` is `"auto"`, Bedrock is auto-detected if that
-    credential chain resolves successfully.
+Bedrock embeddings use the same AWS SDK credential chain as inference (instance
+roles, SSO, access keys, shared config, and web identity). No API key is
+needed. When `provider` is `"auto"`, Bedrock is auto-detected if that
+credential chain resolves successfully.
 
-    Supported embedding models include Amazon Titan Embed (v1, v2), Amazon Nova
-    Embed, Cohere Embed (v3, v4), and TwelveLabs Marengo. See
-    [Memory configuration reference -- Bedrock](/reference/memory-config#bedrock-embedding-config)
-    for the full model list and dimension options.
-
-  </Accordion>
-
-  <Accordion title="Notes and caveats">
-    - Bedrock requires **model access** enabled in your AWS account/region.
-    - Automatic discovery needs the `bedrock:ListFoundationModels` and
-      `bedrock:ListInferenceProfiles` permissions.
-    - If you rely on auto mode, set one of the supported AWS auth env markers on the
-      gateway host. If you prefer IMDS/shared-config auth without env markers, set
-      `plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
-    - OpenClaw surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
-      then `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, then `AWS_PROFILE`, then the
-      default AWS SDK chain.
-    - Reasoning support depends on the model; check the Bedrock model card for
-      current capabilities.
-    - If you prefer a managed key flow, you can also place an OpenAI-compatible
-      proxy in front of Bedrock and configure it as an OpenAI provider instead.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Memory search" href="/concepts/memory-search" icon="magnifying-glass">
-    Bedrock embeddings for memory search configuration.
-  </Card>
-  <Card title="Memory config reference" href="/reference/memory-config#bedrock-embedding-config" icon="database">
-    Full Bedrock embedding model list and dimension options.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+Supported embedding models include Amazon Titan Embed (v1, v2), Amazon Nova
+Embed, Cohere Embed (v3, v4), and TwelveLabs Marengo. See
+[Memory configuration reference — Bedrock](/reference/memory-config#bedrock-embedding-config)
+for the full model list and dimension options.

docs/providers/chutes.md

@@ -13,58 +13,44 @@ read_when:
 OpenAI-compatible API. OpenClaw supports both browser OAuth and direct API-key
 auth for the bundled `chutes` provider.
 
-| Property | Value                        |
-| -------- | ---------------------------- |
-| Provider | `chutes`                     |
-| API      | OpenAI-compatible            |
-| Base URL | `https://llm.chutes.ai/v1`   |
-| Auth     | OAuth or API key (see below) |
+- Provider: `chutes`
+- API: OpenAI-compatible
+- Base URL: `https://llm.chutes.ai/v1`
+- Auth:
+  - OAuth via `openclaw onboard --auth-choice chutes`
+  - API key via `openclaw onboard --auth-choice chutes-api-key`
+  - Runtime env vars: `CHUTES_API_KEY`, `CHUTES_OAUTH_TOKEN`
 
-## Getting started
+## Quick start
 
-<Tabs>
-  <Tab title="OAuth">
-    <Steps>
-      <Step title="Run the OAuth onboarding flow">
-        ```bash
-        openclaw onboard --auth-choice chutes
-        ```
-        OpenClaw launches the browser flow locally, or shows a URL + redirect-paste
-        flow on remote/headless hosts. OAuth tokens auto-refresh through OpenClaw auth
-        profiles.
-      </Step>
-      <Step title="Verify the default model">
-        After onboarding, the default model is set to
-        `chutes/zai-org/GLM-4.7-TEE` and the bundled Chutes catalog is
-        registered.
-      </Step>
-    </Steps>
-  </Tab>
-  <Tab title="API key">
-    <Steps>
-      <Step title="Get an API key">
-        Create a key at
-        [chutes.ai/settings/api-keys](https://chutes.ai/settings/api-keys).
-      </Step>
-      <Step title="Run the API key onboarding flow">
-        ```bash
-        openclaw onboard --auth-choice chutes-api-key
-        ```
-      </Step>
-      <Step title="Verify the default model">
-        After onboarding, the default model is set to
-        `chutes/zai-org/GLM-4.7-TEE` and the bundled Chutes catalog is
-        registered.
-      </Step>
-    </Steps>
-  </Tab>
-</Tabs>
+### OAuth
 
-<Note>
-Both auth paths register the bundled Chutes catalog and set the default model to
-`chutes/zai-org/GLM-4.7-TEE`. Runtime environment variables: `CHUTES_API_KEY`,
-`CHUTES_OAUTH_TOKEN`.
-</Note>
+```bash
+openclaw onboard --auth-choice chutes
+```
+
+OpenClaw launches the browser flow locally, or shows a URL + redirect-paste
+flow on remote/headless hosts. OAuth tokens auto-refresh through OpenClaw auth
+profiles.
+
+Optional OAuth overrides:
+
+- `CHUTES_CLIENT_ID`
+- `CHUTES_CLIENT_SECRET`
+- `CHUTES_OAUTH_REDIRECT_URI`
+- `CHUTES_OAUTH_SCOPES`
+
+### API key
+
+```bash
+openclaw onboard --auth-choice chutes-api-key
+```
+
+Get your key at
+[chutes.ai/settings/api-keys](https://chutes.ai/settings/api-keys).
+
+Both auth paths register the bundled Chutes catalog and set the default model
+to `chutes/zai-org/GLM-4.7-TEE`.
 
 ## Discovery behavior
 
@@ -74,28 +60,25 @@ back to a bundled static catalog so onboarding and startup still work.
 
 ## Default aliases
 
-OpenClaw registers three convenience aliases for the bundled Chutes catalog:
+OpenClaw also registers three convenience aliases for the bundled Chutes
+catalog:
 
-| Alias           | Target model                                          |
-| --------------- | ----------------------------------------------------- |
-| `chutes-fast`   | `chutes/zai-org/GLM-4.7-FP8`                          |
-| `chutes-pro`    | `chutes/deepseek-ai/DeepSeek-V3.2-TEE`                |
-| `chutes-vision` | `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506` |
+- `chutes-fast` -> `chutes/zai-org/GLM-4.7-FP8`
+- `chutes-pro` -> `chutes/deepseek-ai/DeepSeek-V3.2-TEE`
+- `chutes-vision` -> `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506`
 
 ## Built-in starter catalog
 
-The bundled fallback catalog includes current Chutes refs:
+The bundled fallback catalog includes current Chutes refs such as:
 
-| Model ref                                             |
-| ----------------------------------------------------- |
-| `chutes/zai-org/GLM-4.7-TEE`                          |
-| `chutes/zai-org/GLM-5-TEE`                            |
-| `chutes/deepseek-ai/DeepSeek-V3.2-TEE`                |
-| `chutes/deepseek-ai/DeepSeek-R1-0528-TEE`             |
-| `chutes/moonshotai/Kimi-K2.5-TEE`                     |
-| `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506` |
-| `chutes/Qwen/Qwen3-Coder-Next-TEE`                    |
-| `chutes/openai/gpt-oss-120b-TEE`                      |
+- `chutes/zai-org/GLM-4.7-TEE`
+- `chutes/zai-org/GLM-5-TEE`
+- `chutes/deepseek-ai/DeepSeek-V3.2-TEE`
+- `chutes/deepseek-ai/DeepSeek-R1-0528-TEE`
+- `chutes/moonshotai/Kimi-K2.5-TEE`
+- `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506`
+- `chutes/Qwen/Qwen3-Coder-Next-TEE`
+- `chutes/openai/gpt-oss-120b-TEE`
 
 ## Config example
 
@@ -113,42 +96,8 @@ The bundled fallback catalog includes current Chutes refs:
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="OAuth overrides">
-    You can customize the OAuth flow with optional environment variables:
+## Notes
 
-    | Variable | Purpose |
-    | -------- | ------- |
-    | `CHUTES_CLIENT_ID` | Custom OAuth client ID |
-    | `CHUTES_CLIENT_SECRET` | Custom OAuth client secret |
-    | `CHUTES_OAUTH_REDIRECT_URI` | Custom redirect URI |
-    | `CHUTES_OAUTH_SCOPES` | Custom OAuth scopes |
-
-    See the [Chutes OAuth docs](https://chutes.ai/docs/sign-in-with-chutes/overview)
-    for redirect-app requirements and help.
-
-  </Accordion>
-
-  <Accordion title="Notes">
-    - API-key and OAuth discovery both use the same `chutes` provider id.
-    - Chutes models are registered as `chutes/<model-id>`.
-    - If discovery fails at startup, the bundled static catalog is used automatically.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Provider rules, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider settings.
-  </Card>
-  <Card title="Chutes" href="https://chutes.ai" icon="arrow-up-right-from-square">
-    Chutes dashboard and API docs.
-  </Card>
-  <Card title="Chutes API keys" href="https://chutes.ai/settings/api-keys" icon="key">
-    Create and manage Chutes API keys.
-  </Card>
-</CardGroup>
+- OAuth help and redirect-app requirements: [Chutes OAuth docs](https://chutes.ai/docs/sign-in-with-chutes/overview)
+- API-key and OAuth discovery both use the same `chutes` provider id.
+- Chutes models are registered as `chutes/<model-id>`.

docs/providers/claude-max-api-proxy.md

@@ -17,7 +17,7 @@ usage outside Claude Code in the past. You must decide for yourself whether to u
 it and verify Anthropic's current terms before relying on it.
 </Warning>
 
-## Why use this?
+## Why Use This?
 
 | Approach                | Cost                                                | Best For                                   |
 | ----------------------- | --------------------------------------------------- | ------------------------------------------ |
@@ -26,7 +26,7 @@ it and verify Anthropic's current terms before relying on it.
 
 If you have a Claude Max subscription and want to use it with OpenAI-compatible tools, this proxy may reduce cost for some workflows. API keys remain the clearer policy path for production use.
 
-## How it works
+## How It Works
 
 ```
 Your App → claude-max-api-proxy → Claude Code CLI → Anthropic (via subscription)
@@ -39,65 +39,71 @@ The proxy:
 2. Converts them to Claude Code CLI commands
 3. Returns responses in OpenAI format (streaming supported)
 
-## Getting started
+## Installation
 
-<Steps>
-  <Step title="Install the proxy">
-    Requires Node.js 20+ and Claude Code CLI.
+```bash
+# Requires Node.js 20+ and Claude Code CLI
+npm install -g claude-max-api-proxy
 
-    ```bash
-    npm install -g claude-max-api-proxy
+# Verify Claude CLI is authenticated
+claude --version
+```
 
-    # Verify Claude CLI is authenticated
-    claude --version
-    ```
+## Usage
 
-  </Step>
-  <Step title="Start the server">
-    ```bash
-    claude-max-api
-    # Server runs at http://localhost:3456
-    ```
-  </Step>
-  <Step title="Test the proxy">
-    ```bash
-    # Health check
-    curl http://localhost:3456/health
+### Start the server
 
-    # List models
-    curl http://localhost:3456/v1/models
+```bash
+claude-max-api
+# Server runs at http://localhost:3456
+```
 
-    # Chat completion
-    curl http://localhost:3456/v1/chat/completions \
-      -H "Content-Type: application/json" \
-      -d '{
-        "model": "claude-opus-4",
-        "messages": [{"role": "user", "content": "Hello!"}]
-      }'
-    ```
+### Test it
 
-  </Step>
-  <Step title="Configure OpenClaw">
-    Point OpenClaw at the proxy as a custom OpenAI-compatible endpoint:
+```bash
+# Health check
+curl http://localhost:3456/health
 
-    ```json5
-    {
-      env: {
-        OPENAI_API_KEY: "not-needed",
-        OPENAI_BASE_URL: "http://localhost:3456/v1",
-      },
-      agents: {
-        defaults: {
-          model: { primary: "openai/claude-opus-4" },
-        },
-      },
-    }
-    ```
+# List models
+curl http://localhost:3456/v1/models
 
-  </Step>
-</Steps>
+# Chat completion
+curl http://localhost:3456/v1/chat/completions \
+  -H "Content-Type: application/json" \
+  -d '{
+    "model": "claude-opus-4",
+    "messages": [{"role": "user", "content": "Hello!"}]
+  }'
+```
 
-## Available models
+### With OpenClaw
+
+You can point OpenClaw at the proxy as a custom OpenAI-compatible endpoint:
+
+```json5
+{
+  env: {
+    OPENAI_API_KEY: "not-needed",
+    OPENAI_BASE_URL: "http://localhost:3456/v1",
+  },
+  agents: {
+    defaults: {
+      model: { primary: "openai/claude-opus-4" },
+    },
+  },
+}
+```
+
+This path uses the same proxy-style OpenAI-compatible route as other custom
+`/v1` backends:
+
+- native OpenAI-only request shaping does not apply
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on the proxy URL
+
+## Available Models
 
 | Model ID          | Maps To         |
 | ----------------- | --------------- |
@@ -105,55 +111,38 @@ The proxy:
 | `claude-sonnet-4` | Claude Sonnet 4 |
 | `claude-haiku-4`  | Claude Haiku 4  |
 
-## Advanced
+## Auto-Start on macOS
 
-<AccordionGroup>
-  <Accordion title="Proxy-style OpenAI-compatible notes">
-    This path uses the same proxy-style OpenAI-compatible route as other custom
-    `/v1` backends:
+Create a LaunchAgent to run the proxy automatically:
 
-    - Native OpenAI-only request shaping does not apply
-    - No `service_tier`, no Responses `store`, no prompt-cache hints, and no
-      OpenAI reasoning-compat payload shaping
-    - Hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
-      are not injected on the proxy URL
+```bash
+cat > ~/Library/LaunchAgents/com.claude-max-api.plist << 'EOF'
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>com.claude-max-api</string>
+  <key>RunAtLoad</key>
+  <true/>
+  <key>KeepAlive</key>
+  <true/>
+  <key>ProgramArguments</key>
+  <array>
+    <string>/usr/local/bin/node</string>
+    <string>/usr/local/lib/node_modules/claude-max-api-proxy/dist/server/standalone.js</string>
+  </array>
+  <key>EnvironmentVariables</key>
+  <dict>
+    <key>PATH</key>
+    <string>/usr/local/bin:/opt/homebrew/bin:~/.local/bin:/usr/bin:/bin</string>
+  </dict>
+</dict>
+</plist>
+EOF
 
-  </Accordion>
-
-  <Accordion title="Auto-start on macOS with LaunchAgent">
-    Create a LaunchAgent to run the proxy automatically:
-
-    ```bash
-    cat > ~/Library/LaunchAgents/com.claude-max-api.plist << 'EOF'
-    <?xml version="1.0" encoding="UTF-8"?>
-    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
-    <plist version="1.0">
-    <dict>
-      <key>Label</key>
-      <string>com.claude-max-api</string>
-      <key>RunAtLoad</key>
-      <true/>
-      <key>KeepAlive</key>
-      <true/>
-      <key>ProgramArguments</key>
-      <array>
-        <string>/usr/local/bin/node</string>
-        <string>/usr/local/lib/node_modules/claude-max-api-proxy/dist/server/standalone.js</string>
-      </array>
-      <key>EnvironmentVariables</key>
-      <dict>
-        <key>PATH</key>
-        <string>/usr/local/bin:/opt/homebrew/bin:~/.local/bin:/usr/bin:/bin</string>
-      </dict>
-    </dict>
-    </plist>
-    EOF
-
-    launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.claude-max-api.plist
-    ```
-
-  </Accordion>
-</AccordionGroup>
+launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.claude-max-api.plist
+```
 
 ## Links
 
@@ -168,23 +157,7 @@ The proxy:
 - The proxy runs locally and does not send data to any third-party servers
 - Streaming responses are fully supported
 
-<Note>
-For native Anthropic integration with Claude CLI or API keys, see [Anthropic provider](/providers/anthropic). For OpenAI/Codex subscriptions, see [OpenAI provider](/providers/openai).
-</Note>
+## See Also
 
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Anthropic provider" href="/providers/anthropic" icon="bolt">
-    Native OpenClaw integration with Claude CLI or API keys.
-  </Card>
-  <Card title="OpenAI provider" href="/providers/openai" icon="robot">
-    For OpenAI/Codex subscriptions.
-  </Card>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration" href="/gateway/configuration" icon="gear">
-    Full config reference.
-  </Card>
-</CardGroup>
+- [Anthropic provider](/providers/anthropic) - Native OpenClaw integration with Claude CLI or API keys
+- [OpenAI provider](/providers/openai) - For OpenAI/Codex subscriptions

docs/providers/cloudflare-ai-gateway.md

@@ -10,55 +10,35 @@ read_when:
 
 Cloudflare AI Gateway sits in front of provider APIs and lets you add analytics, caching, and controls. For Anthropic, OpenClaw uses the Anthropic Messages API through your Gateway endpoint.
 
-| Property      | Value                                                                                    |
-| ------------- | ---------------------------------------------------------------------------------------- |
-| Provider      | `cloudflare-ai-gateway`                                                                  |
-| Base URL      | `https://gateway.ai.cloudflare.com/v1/<account_id>/<gateway_id>/anthropic`               |
-| Default model | `cloudflare-ai-gateway/claude-sonnet-4-5`                                                |
-| API key       | `CLOUDFLARE_AI_GATEWAY_API_KEY` (your provider API key for requests through the Gateway) |
+- Provider: `cloudflare-ai-gateway`
+- Base URL: `https://gateway.ai.cloudflare.com/v1/<account_id>/<gateway_id>/anthropic`
+- Default model: `cloudflare-ai-gateway/claude-sonnet-4-5`
+- API key: `CLOUDFLARE_AI_GATEWAY_API_KEY` (your provider API key for requests through the Gateway)
 
-<Note>
-For Anthropic models routed through Cloudflare AI Gateway, use your **Anthropic API key** as the provider key.
-</Note>
+For Anthropic models, use your Anthropic API key.
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set the provider API key and Gateway details">
-    Run onboarding and choose the Cloudflare AI Gateway auth option:
+1. Set the provider API key and Gateway details:
 
-    ```bash
-    openclaw onboard --auth-choice cloudflare-ai-gateway-api-key
-    ```
+```bash
+openclaw onboard --auth-choice cloudflare-ai-gateway-api-key
+```
 
-    This prompts for your account ID, gateway ID, and API key.
+2. Set a default model:
 
-  </Step>
-  <Step title="Set a default model">
-    Add the model to your OpenClaw config:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "cloudflare-ai-gateway/claude-sonnet-4-5" },
-        },
-      },
-    }
-    ```
-
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider cloudflare-ai-gateway
-    ```
-  </Step>
-</Steps>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "cloudflare-ai-gateway/claude-sonnet-4-5" },
+    },
+  },
+}
+```
 
 ## Non-interactive example
 
-For scripted or CI setups, pass all values on the command line:
-
 ```bash
 openclaw onboard --non-interactive \
   --mode local \
@@ -68,49 +48,24 @@ openclaw onboard --non-interactive \
   --cloudflare-ai-gateway-api-key "$CLOUDFLARE_AI_GATEWAY_API_KEY"
 ```
 
-## Advanced configuration
+## Authenticated gateways
 
-<AccordionGroup>
-  <Accordion title="Authenticated gateways">
-    If you enabled Gateway authentication in Cloudflare, add the `cf-aig-authorization` header. This is **in addition to** your provider API key.
+If you enabled Gateway authentication in Cloudflare, add the `cf-aig-authorization` header (this is in addition to your provider API key).
 
-    ```json5
-    {
-      models: {
-        providers: {
-          "cloudflare-ai-gateway": {
-            headers: {
-              "cf-aig-authorization": "Bearer <cloudflare-ai-gateway-token>",
-            },
-          },
+```json5
+{
+  models: {
+    providers: {
+      "cloudflare-ai-gateway": {
+        headers: {
+          "cf-aig-authorization": "Bearer <cloudflare-ai-gateway-token>",
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Tip>
-    The `cf-aig-authorization` header authenticates with the Cloudflare Gateway itself, while the provider API key (for example, your Anthropic key) authenticates with the upstream provider.
-    </Tip>
+## Environment note
 
-  </Accordion>
-
-  <Accordion title="Environment note">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `CLOUDFLARE_AI_GATEWAY_API_KEY` is available to that process.
-
-    <Warning>
-    A key sitting only in `~/.profile` will not help a launchd/systemd daemon unless that environment is imported there as well. Set the key in `~/.openclaw/.env` or via `env.shellEnv` to ensure the gateway process can read it.
-    </Warning>
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+If the Gateway runs as a daemon (launchd/systemd), make sure `CLOUDFLARE_AI_GATEWAY_API_KEY` is available to that process (for example, in `~/.openclaw/.env` or via `env.shellEnv`).

docs/providers/comfy.md

@@ -9,15 +9,13 @@ read_when:
 
 # ComfyUI
 
-OpenClaw ships a bundled `comfy` plugin for workflow-driven ComfyUI runs. The plugin is entirely workflow-driven, so OpenClaw does not try to map generic `size`, `aspectRatio`, `resolution`, `durationSeconds`, or TTS-style controls onto your graph.
+OpenClaw ships a bundled `comfy` plugin for workflow-driven ComfyUI runs.
 
-| Property        | Detail                                                                           |
-| --------------- | -------------------------------------------------------------------------------- |
-| Provider        | `comfy`                                                                          |
-| Models          | `comfy/workflow`                                                                 |
-| Shared surfaces | `image_generate`, `video_generate`, `music_generate`                             |
-| Auth            | None for local ComfyUI; `COMFY_API_KEY` or `COMFY_CLOUD_API_KEY` for Comfy Cloud |
-| API             | ComfyUI `/prompt` / `/history` / `/view` and Comfy Cloud `/api/*`                |
+- Provider: `comfy`
+- Models: `comfy/workflow`
+- Shared surfaces: `image_generate`, `video_generate`, `music_generate`
+- Auth: none for local ComfyUI; `COMFY_API_KEY` or `COMFY_CLOUD_API_KEY` for Comfy Cloud
+- API: ComfyUI `/prompt` / `/history` / `/view` and Comfy Cloud `/api/*`
 
 ## What it supports
 
@@ -28,140 +26,14 @@ OpenClaw ships a bundled `comfy` plugin for workflow-driven ComfyUI runs. The pl
 - Music or audio generation through the shared `music_generate` tool
 - Output download from a configured node or all matching output nodes
 
-## Getting started
+The bundled plugin is workflow-driven, so OpenClaw does not try to map generic
+`size`, `aspectRatio`, `resolution`, `durationSeconds`, or TTS-style controls
+onto your graph.
 
-Choose between running ComfyUI on your own machine or using Comfy Cloud.
+## Config layout
 
-<Tabs>
-  <Tab title="Local">
-    **Best for:** running your own ComfyUI instance on your machine or LAN.
-
-    <Steps>
-      <Step title="Start ComfyUI locally">
-        Make sure your local ComfyUI instance is running (defaults to `http://127.0.0.1:8188`).
-      </Step>
-      <Step title="Prepare your workflow JSON">
-        Export or create a ComfyUI workflow JSON file. Note the node IDs for the prompt input node and the output node you want OpenClaw to read from.
-      </Step>
-      <Step title="Configure the provider">
-        Set `mode: "local"` and point at your workflow file. Here is a minimal image example:
-
-        ```json5
-        {
-          models: {
-            providers: {
-              comfy: {
-                mode: "local",
-                baseUrl: "http://127.0.0.1:8188",
-                image: {
-                  workflowPath: "./workflows/flux-api.json",
-                  promptNodeId: "6",
-                  outputNodeId: "9",
-                },
-              },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Set the default model">
-        Point OpenClaw at the `comfy/workflow` model for the capability you configured:
-
-        ```json5
-        {
-          agents: {
-            defaults: {
-              imageGenerationModel: {
-                primary: "comfy/workflow",
-              },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify">
-        ```bash
-        openclaw models list --provider comfy
-        ```
-      </Step>
-    </Steps>
-
-  </Tab>
-
-  <Tab title="Comfy Cloud">
-    **Best for:** running workflows on Comfy Cloud without managing local GPU resources.
-
-    <Steps>
-      <Step title="Get an API key">
-        Sign up at [comfy.org](https://comfy.org) and generate an API key from your account dashboard.
-      </Step>
-      <Step title="Set the API key">
-        Provide your key through one of these methods:
-
-        ```bash
-        # Environment variable (preferred)
-        export COMFY_API_KEY="your-key"
-
-        # Alternative environment variable
-        export COMFY_CLOUD_API_KEY="your-key"
-
-        # Or inline in config
-        openclaw config set models.providers.comfy.apiKey "your-key"
-        ```
-      </Step>
-      <Step title="Prepare your workflow JSON">
-        Export or create a ComfyUI workflow JSON file. Note the node IDs for the prompt input node and the output node.
-      </Step>
-      <Step title="Configure the provider">
-        Set `mode: "cloud"` and point at your workflow file:
-
-        ```json5
-        {
-          models: {
-            providers: {
-              comfy: {
-                mode: "cloud",
-                image: {
-                  workflowPath: "./workflows/flux-api.json",
-                  promptNodeId: "6",
-                  outputNodeId: "9",
-                },
-              },
-            },
-          },
-        }
-        ```
-
-        <Tip>
-        Cloud mode defaults `baseUrl` to `https://cloud.comfy.org`. You only need to set `baseUrl` if you use a custom cloud endpoint.
-        </Tip>
-      </Step>
-      <Step title="Set the default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              imageGenerationModel: {
-                primary: "comfy/workflow",
-              },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify">
-        ```bash
-        openclaw models list --provider comfy
-        ```
-      </Step>
-    </Steps>
-
-  </Tab>
-</Tabs>
-
-## Configuration
-
-Comfy supports shared top-level connection settings plus per-capability workflow sections (`image`, `video`, `music`):
+Comfy supports shared top-level connection settings plus per-capability workflow
+sections:
 
 ```json5
 {
@@ -191,164 +63,139 @@ Comfy supports shared top-level connection settings plus per-capability workflow
 }
 ```
 
-### Shared keys
+Shared keys:
 
-| Key                   | Type                   | Description                                                                           |
-| --------------------- | ---------------------- | ------------------------------------------------------------------------------------- |
-| `mode`                | `"local"` or `"cloud"` | Connection mode.                                                                      |
-| `baseUrl`             | string                 | Defaults to `http://127.0.0.1:8188` for local or `https://cloud.comfy.org` for cloud. |
-| `apiKey`              | string                 | Optional inline key, alternative to `COMFY_API_KEY` / `COMFY_CLOUD_API_KEY` env vars. |
-| `allowPrivateNetwork` | boolean                | Allow a private/LAN `baseUrl` in cloud mode.                                          |
+- `mode`: `local` or `cloud`
+- `baseUrl`: defaults to `http://127.0.0.1:8188` for local or `https://cloud.comfy.org` for cloud
+- `apiKey`: optional inline key alternative to env vars
+- `allowPrivateNetwork`: allow a private/LAN `baseUrl` in cloud mode
 
-### Per-capability keys
+Per-capability keys under `image`, `video`, or `music`:
 
-These keys apply inside the `image`, `video`, or `music` sections:
+- `workflow` or `workflowPath`: required
+- `promptNodeId`: required
+- `promptInputName`: defaults to `text`
+- `outputNodeId`: optional
+- `pollIntervalMs`: optional
+- `timeoutMs`: optional
 
-| Key                          | Required | Default  | Description                                                                  |
-| ---------------------------- | -------- | -------- | ---------------------------------------------------------------------------- |
-| `workflow` or `workflowPath` | Yes      | --       | Path to the ComfyUI workflow JSON file.                                      |
-| `promptNodeId`               | Yes      | --       | Node ID that receives the text prompt.                                       |
-| `promptInputName`            | No       | `"text"` | Input name on the prompt node.                                               |
-| `outputNodeId`               | No       | --       | Node ID to read output from. If omitted, all matching output nodes are used. |
-| `pollIntervalMs`             | No       | --       | Polling interval in milliseconds for job completion.                         |
-| `timeoutMs`                  | No       | --       | Timeout in milliseconds for the workflow run.                                |
+Image and video sections also support:
 
-The `image` and `video` sections also support:
+- `inputImageNodeId`: required when you pass a reference image
+- `inputImageInputName`: defaults to `image`
 
-| Key                   | Required                             | Default   | Description                                         |
-| --------------------- | ------------------------------------ | --------- | --------------------------------------------------- |
-| `inputImageNodeId`    | Yes (when passing a reference image) | --        | Node ID that receives the uploaded reference image. |
-| `inputImageInputName` | No                                   | `"image"` | Input name on the image node.                       |
+## Backward compatibility
 
-## Workflow details
+Existing top-level image config still works:
 
-<AccordionGroup>
-  <Accordion title="Image workflows">
-    Set the default image model to `comfy/workflow`:
+```json5
+{
+  models: {
+    providers: {
+      comfy: {
+        workflowPath: "./workflows/flux-api.json",
+        promptNodeId: "6",
+        outputNodeId: "9",
+      },
+    },
+  },
+}
+```
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          imageGenerationModel: {
-            primary: "comfy/workflow",
-          },
+OpenClaw treats that legacy shape as the image workflow config.
+
+## Image workflows
+
+Set the default image model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      imageGenerationModel: {
+        primary: "comfy/workflow",
+      },
+    },
+  },
+}
+```
+
+Reference-image editing example:
+
+```json5
+{
+  models: {
+    providers: {
+      comfy: {
+        image: {
+          workflowPath: "./workflows/edit-api.json",
+          promptNodeId: "6",
+          inputImageNodeId: "7",
+          inputImageInputName: "image",
+          outputNodeId: "9",
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    **Reference-image editing example:**
+## Video workflows
 
-    To enable image editing with an uploaded reference image, add `inputImageNodeId` to your image config:
+Set the default video model:
 
-    ```json5
-    {
-      models: {
-        providers: {
-          comfy: {
-            image: {
-              workflowPath: "./workflows/edit-api.json",
-              promptNodeId: "6",
-              inputImageNodeId: "7",
-              inputImageInputName: "image",
-              outputNodeId: "9",
-            },
-          },
-        },
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "comfy/workflow",
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-  </Accordion>
+Comfy video workflows currently support text-to-video and image-to-video through
+the configured graph. OpenClaw does not pass input videos into Comfy workflows.
 
-  <Accordion title="Video workflows">
-    Set the default video model to `comfy/workflow`:
+## Music workflows
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "comfy/workflow",
-          },
-        },
-      },
-    }
-    ```
+The bundled plugin registers a music-generation provider for workflow-defined
+audio or music outputs, surfaced through the shared `music_generate` tool:
 
-    Comfy video workflows support text-to-video and image-to-video through the configured graph.
+```text
+/tool music_generate prompt="Warm ambient synth loop with soft tape texture"
+```
 
-    <Note>
-    OpenClaw does not pass input videos into Comfy workflows. Only text prompts and single reference images are supported as inputs.
-    </Note>
+Use the `music` config section to point at your audio workflow JSON and output
+node.
 
-  </Accordion>
+## Comfy Cloud
 
-  <Accordion title="Music workflows">
-    The bundled plugin registers a music-generation provider for workflow-defined audio or music outputs, surfaced through the shared `music_generate` tool:
+Use `mode: "cloud"` plus one of:
 
-    ```text
-    /tool music_generate prompt="Warm ambient synth loop with soft tape texture"
-    ```
+- `COMFY_API_KEY`
+- `COMFY_CLOUD_API_KEY`
+- `models.providers.comfy.apiKey`
 
-    Use the `music` config section to point at your audio workflow JSON and output node.
+Cloud mode still uses the same `image`, `video`, and `music` workflow sections.
 
-  </Accordion>
+## Live tests
 
-  <Accordion title="Backward compatibility">
-    Existing top-level image config (without the nested `image` section) still works:
+Opt-in live coverage exists for the bundled plugin:
 
-    ```json5
-    {
-      models: {
-        providers: {
-          comfy: {
-            workflowPath: "./workflows/flux-api.json",
-            promptNodeId: "6",
-            outputNodeId: "9",
-          },
-        },
-      },
-    }
-    ```
+```bash
+OPENCLAW_LIVE_TEST=1 COMFY_LIVE_TEST=1 pnpm test:live -- extensions/comfy/comfy.live.test.ts
+```
 
-    OpenClaw treats that legacy shape as the image workflow config. You do not need to migrate immediately, but the nested `image` / `video` / `music` sections are recommended for new setups.
-
-    <Tip>
-    If you only use image generation, the legacy flat config and the new nested `image` section are functionally equivalent.
-    </Tip>
-
-  </Accordion>
-
-  <Accordion title="Live tests">
-    Opt-in live coverage exists for the bundled plugin:
-
-    ```bash
-    OPENCLAW_LIVE_TEST=1 COMFY_LIVE_TEST=1 pnpm test:live -- extensions/comfy/comfy.live.test.ts
-    ```
-
-    The live test skips individual image, video, or music cases unless the matching Comfy workflow section is configured.
-
-  </Accordion>
-</AccordionGroup>
+The live test skips individual image, video, or music cases unless the matching
+Comfy workflow section is configured.
 
 ## Related
 
-<CardGroup cols={2}>
-  <Card title="Image Generation" href="/tools/image-generation" icon="image">
-    Image generation tool configuration and usage.
-  </Card>
-  <Card title="Video Generation" href="/tools/video-generation" icon="video">
-    Video generation tool configuration and usage.
-  </Card>
-  <Card title="Music Generation" href="/tools/music-generation" icon="music">
-    Music and audio generation tool setup.
-  </Card>
-  <Card title="Provider Directory" href="/providers/index" icon="layers">
-    Overview of all providers and model refs.
-  </Card>
-  <Card title="Configuration Reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">
-    Full config reference including agent defaults.
-  </Card>
-</CardGroup>
+- [Image Generation](/tools/image-generation)
+- [Video Generation](/tools/video-generation)
+- [Music Generation](/tools/music-generation)
+- [Provider Directory](/providers/index)
+- [Configuration Reference](/gateway/configuration-reference#agent-defaults)

docs/providers/deepgram.md

@@ -15,128 +15,79 @@ When enabled, OpenClaw uploads the audio file to Deepgram and injects the transc
 into the reply pipeline (`{{Transcript}}` + `[Audio]` block). This is **not streaming**;
 it uses the pre-recorded transcription endpoint.
 
-| Detail        | Value                                                      |
-| ------------- | ---------------------------------------------------------- |
-| Website       | [deepgram.com](https://deepgram.com)                       |
-| Docs          | [developers.deepgram.com](https://developers.deepgram.com) |
-| Auth          | `DEEPGRAM_API_KEY`                                         |
-| Default model | `nova-3`                                                   |
+Website: [https://deepgram.com](https://deepgram.com)  
+Docs: [https://developers.deepgram.com](https://developers.deepgram.com)
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set your API key">
-    Add your Deepgram API key to the environment:
+1. Set your API key:
 
-    ```
-    DEEPGRAM_API_KEY=dg_...
-    ```
+```
+DEEPGRAM_API_KEY=dg_...
+```
 
-  </Step>
-  <Step title="Enable the audio provider">
-    ```json5
-    {
-      tools: {
-        media: {
-          audio: {
-            enabled: true,
-            models: [{ provider: "deepgram", model: "nova-3" }],
+2. Enable the provider:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        models: [{ provider: "deepgram", model: "nova-3" }],
+      },
+    },
+  },
+}
+```
+
+## Options
+
+- `model`: Deepgram model id (default: `nova-3`)
+- `language`: language hint (optional)
+- `tools.media.audio.providerOptions.deepgram.detect_language`: enable language detection (optional)
+- `tools.media.audio.providerOptions.deepgram.punctuate`: enable punctuation (optional)
+- `tools.media.audio.providerOptions.deepgram.smart_format`: enable smart formatting (optional)
+
+Example with language:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        models: [{ provider: "deepgram", model: "nova-3", language: "en" }],
+      },
+    },
+  },
+}
+```
+
+Example with Deepgram options:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        providerOptions: {
+          deepgram: {
+            detect_language: true,
+            punctuate: true,
+            smart_format: true,
           },
         },
+        models: [{ provider: "deepgram", model: "nova-3" }],
       },
-    }
-    ```
-  </Step>
-  <Step title="Send a voice note">
-    Send an audio message through any connected channel. OpenClaw transcribes it
-    via Deepgram and injects the transcript into the reply pipeline.
-  </Step>
-</Steps>
-
-## Configuration options
-
-| Option            | Path                                                         | Description                           |
-| ----------------- | ------------------------------------------------------------ | ------------------------------------- |
-| `model`           | `tools.media.audio.models[].model`                           | Deepgram model id (default: `nova-3`) |
-| `language`        | `tools.media.audio.models[].language`                        | Language hint (optional)              |
-| `detect_language` | `tools.media.audio.providerOptions.deepgram.detect_language` | Enable language detection (optional)  |
-| `punctuate`       | `tools.media.audio.providerOptions.deepgram.punctuate`       | Enable punctuation (optional)         |
-| `smart_format`    | `tools.media.audio.providerOptions.deepgram.smart_format`    | Enable smart formatting (optional)    |
-
-<Tabs>
-  <Tab title="With language hint">
-    ```json5
-    {
-      tools: {
-        media: {
-          audio: {
-            enabled: true,
-            models: [{ provider: "deepgram", model: "nova-3", language: "en" }],
-          },
-        },
-      },
-    }
-    ```
-  </Tab>
-  <Tab title="With Deepgram options">
-    ```json5
-    {
-      tools: {
-        media: {
-          audio: {
-            enabled: true,
-            providerOptions: {
-              deepgram: {
-                detect_language: true,
-                punctuate: true,
-                smart_format: true,
-              },
-            },
-            models: [{ provider: "deepgram", model: "nova-3" }],
-          },
-        },
-      },
-    }
-    ```
-  </Tab>
-</Tabs>
+    },
+  },
+}
+```
 
 ## Notes
 
-<AccordionGroup>
-  <Accordion title="Authentication">
-    Authentication follows the standard provider auth order. `DEEPGRAM_API_KEY` is
-    the simplest path.
-  </Accordion>
-  <Accordion title="Proxy and custom endpoints">
-    Override endpoints or headers with `tools.media.audio.baseUrl` and
-    `tools.media.audio.headers` when using a proxy.
-  </Accordion>
-  <Accordion title="Output behavior">
-    Output follows the same audio rules as other providers (size caps, timeouts,
-    transcript injection).
-  </Accordion>
-</AccordionGroup>
-
-<Note>
-Deepgram transcription is **pre-recorded only** (not real-time streaming). OpenClaw
-uploads the complete audio file and waits for the full transcript before injecting
-it into the conversation.
-</Note>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Media tools" href="/tools/media" icon="photo-film">
-    Audio, image, and video processing pipeline overview.
-  </Card>
-  <Card title="Configuration" href="/configuration" icon="gear">
-    Full config reference including media tool settings.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    Common issues and debugging steps.
-  </Card>
-  <Card title="FAQ" href="/help/faq" icon="circle-question">
-    Frequently asked questions about OpenClaw setup.
-  </Card>
-</CardGroup>
+- Authentication follows the standard provider auth order; `DEEPGRAM_API_KEY` is the simplest path.
+- Override endpoints or headers with `tools.media.audio.baseUrl` and `tools.media.audio.headers` when using a proxy.
+- Output follows the same audio rules as other providers (size caps, timeouts, transcript injection).

docs/providers/deepseek.md

@@ -1,5 +1,4 @@
 ---
-title: "DeepSeek"
 summary: "DeepSeek setup (auth + model selection)"
 read_when:
   - You want to use DeepSeek with OpenClaw
@@ -10,55 +9,37 @@ read_when:
 
 [DeepSeek](https://www.deepseek.com) provides powerful AI models with an OpenAI-compatible API.
 
-| Property | Value                      |
-| -------- | -------------------------- |
-| Provider | `deepseek`                 |
-| Auth     | `DEEPSEEK_API_KEY`         |
-| API      | OpenAI-compatible          |
-| Base URL | `https://api.deepseek.com` |
+- Provider: `deepseek`
+- Auth: `DEEPSEEK_API_KEY`
+- API: OpenAI-compatible
+- Base URL: `https://api.deepseek.com`
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Get your API key">
-    Create an API key at [platform.deepseek.com](https://platform.deepseek.com/api_keys).
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice deepseek-api-key
-    ```
+Set the API key (recommended: store it for the Gateway):
 
-    This will prompt for your API key and set `deepseek/deepseek-chat` as the default model.
+```bash
+openclaw onboard --auth-choice deepseek-api-key
+```
 
-  </Step>
-  <Step title="Verify models are available">
-    ```bash
-    openclaw models list --provider deepseek
-    ```
-  </Step>
-</Steps>
+This will prompt for your API key and set `deepseek/deepseek-chat` as the default model.
 
-<AccordionGroup>
-  <Accordion title="Non-interactive setup">
-    For scripted or headless installations, pass all flags directly:
+## Non-interactive example
 
-    ```bash
-    openclaw onboard --non-interactive \
-      --mode local \
-      --auth-choice deepseek-api-key \
-      --deepseek-api-key "$DEEPSEEK_API_KEY" \
-      --skip-health \
-      --accept-risk
-    ```
+```bash
+openclaw onboard --non-interactive \
+  --mode local \
+  --auth-choice deepseek-api-key \
+  --deepseek-api-key "$DEEPSEEK_API_KEY" \
+  --skip-health \
+  --accept-risk
+```
 
-  </Accordion>
-</AccordionGroup>
+## Environment note
 
-<Warning>
 If the Gateway runs as a daemon (launchd/systemd), make sure `DEEPSEEK_API_KEY`
 is available to that process (for example, in `~/.openclaw/.env` or via
 `env.shellEnv`).
-</Warning>
 
 ## Built-in catalog
 
@@ -67,30 +48,6 @@ is available to that process (for example, in `~/.openclaw/.env` or via
 | `deepseek/deepseek-chat`     | DeepSeek Chat     | text  | 131,072 | 8,192      | Default model; DeepSeek V3.2 non-thinking surface |
 | `deepseek/deepseek-reasoner` | DeepSeek Reasoner | text  | 131,072 | 65,536     | Reasoning-enabled V3.2 surface                    |
 
-<Tip>
 Both bundled models currently advertise streaming usage compatibility in source.
-</Tip>
 
-## Config example
-
-```json5
-{
-  env: { DEEPSEEK_API_KEY: "sk-..." },
-  agents: {
-    defaults: {
-      model: { primary: "deepseek/deepseek-chat" },
-    },
-  },
-}
-```
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config reference for agents, models, and providers.
-  </Card>
-</CardGroup>
+Get your API key at [platform.deepseek.com](https://platform.deepseek.com/api_keys).

docs/providers/fal.md

@@ -11,51 +11,42 @@ read_when:
 
 OpenClaw ships a bundled `fal` provider for hosted image and video generation.
 
-| Property | Value                                                         |
-| -------- | ------------------------------------------------------------- |
-| Provider | `fal`                                                         |
-| Auth     | `FAL_KEY` (canonical; `FAL_API_KEY` also works as a fallback) |
-| API      | fal model endpoints                                           |
+- Provider: `fal`
+- Auth: `FAL_KEY` (canonical; `FAL_API_KEY` also works as a fallback)
+- API: fal model endpoints
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set the API key">
-    ```bash
-    openclaw onboard --auth-choice fal-api-key
-    ```
-  </Step>
-  <Step title="Set a default image model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          imageGenerationModel: {
-            primary: "fal/fal-ai/flux/dev",
-          },
-        },
+1. Set the API key:
+
+```bash
+openclaw onboard --auth-choice fal-api-key
+```
+
+2. Set a default image model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      imageGenerationModel: {
+        primary: "fal/fal-ai/flux/dev",
       },
-    }
-    ```
-  </Step>
-</Steps>
+    },
+  },
+}
+```
 
 ## Image generation
 
 The bundled `fal` image-generation provider defaults to
 `fal/fal-ai/flux/dev`.
 
-| Capability     | Value                      |
-| -------------- | -------------------------- |
-| Max images     | 4 per request              |
-| Edit mode      | Enabled, 1 reference image |
-| Size overrides | Supported                  |
-| Aspect ratio   | Supported                  |
-| Resolution     | Supported                  |
-
-<Warning>
-The fal image edit endpoint does **not** support `aspectRatio` overrides.
-</Warning>
+- Generate: up to 4 images per request
+- Edit mode: enabled, 1 reference image
+- Supports `size`, `aspectRatio`, and `resolution`
+- Current edit caveat: the fal image edit endpoint does **not** support
+  `aspectRatio` overrides
 
 To use fal as the default image provider:
 
@@ -76,70 +67,46 @@ To use fal as the default image provider:
 The bundled `fal` video-generation provider defaults to
 `fal/fal-ai/minimax/video-01-live`.
 
-| Capability | Value                                                        |
-| ---------- | ------------------------------------------------------------ |
-| Modes      | Text-to-video, single-image reference                        |
-| Runtime    | Queue-backed submit/status/result flow for long-running jobs |
+- Modes: text-to-video and single-image reference flows
+- Runtime: queue-backed submit/status/result flow for long-running jobs
+- HeyGen video-agent model ref:
+  - `fal/fal-ai/heygen/v2/video-agent`
+- Seedance 2.0 model refs:
+  - `fal/bytedance/seedance-2.0/fast/text-to-video`
+  - `fal/bytedance/seedance-2.0/fast/image-to-video`
+  - `fal/bytedance/seedance-2.0/text-to-video`
+  - `fal/bytedance/seedance-2.0/image-to-video`
 
-<AccordionGroup>
-  <Accordion title="Available video models">
-    **HeyGen video-agent:**
+To use Seedance 2.0 as the default video model:
 
-    - `fal/fal-ai/heygen/v2/video-agent`
-
-    **Seedance 2.0:**
-
-    - `fal/bytedance/seedance-2.0/fast/text-to-video`
-    - `fal/bytedance/seedance-2.0/fast/image-to-video`
-    - `fal/bytedance/seedance-2.0/text-to-video`
-    - `fal/bytedance/seedance-2.0/image-to-video`
-
-  </Accordion>
-
-  <Accordion title="Seedance 2.0 config example">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "fal/bytedance/seedance-2.0/fast/text-to-video",
-          },
-        },
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "fal/bytedance/seedance-2.0/fast/text-to-video",
       },
-    }
-    ```
-  </Accordion>
+    },
+  },
+}
+```
 
-  <Accordion title="HeyGen video-agent config example">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "fal/fal-ai/heygen/v2/video-agent",
-          },
-        },
+To use HeyGen video-agent as the default video model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "fal/fal-ai/heygen/v2/video-agent",
       },
-    }
-    ```
-  </Accordion>
-</AccordionGroup>
-
-<Tip>
-Use `openclaw models list --provider fal` to see the full list of available fal
-models, including any recently added entries.
-</Tip>
+    },
+  },
+}
+```
 
 ## Related
 
-<CardGroup cols={2}>
-  <Card title="Image generation" href="/tools/image-generation" icon="image">
-    Shared image tool parameters and provider selection.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">
-    Agent defaults including image and video model selection.
-  </Card>
-</CardGroup>
+- [Image Generation](/tools/image-generation)
+- [Video Generation](/tools/video-generation)
+- [Configuration Reference](/gateway/configuration-reference#agent-defaults)

docs/providers/fireworks.md

@@ -1,5 +1,4 @@
 ---
-title: "Fireworks"
 summary: "Fireworks setup (auth + model selection)"
 read_when:
   - You want to use Fireworks with OpenClaw
@@ -8,38 +7,26 @@ read_when:
 
 # Fireworks
 
-[Fireworks](https://fireworks.ai) exposes open-weight and routed models through an OpenAI-compatible API. OpenClaw includes a bundled Fireworks provider plugin.
+[Fireworks](https://fireworks.ai) exposes open-weight and routed models through an OpenAI-compatible API. OpenClaw now includes a bundled Fireworks provider plugin.
 
-| Property      | Value                                                  |
-| ------------- | ------------------------------------------------------ |
-| Provider      | `fireworks`                                            |
-| Auth          | `FIREWORKS_API_KEY`                                    |
-| API           | OpenAI-compatible chat/completions                     |
-| Base URL      | `https://api.fireworks.ai/inference/v1`                |
-| Default model | `fireworks/accounts/fireworks/routers/kimi-k2p5-turbo` |
+- Provider: `fireworks`
+- Auth: `FIREWORKS_API_KEY`
+- API: OpenAI-compatible chat/completions
+- Base URL: `https://api.fireworks.ai/inference/v1`
+- Default model: `fireworks/accounts/fireworks/routers/kimi-k2p5-turbo`
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set up Fireworks auth through onboarding">
-    ```bash
-    openclaw onboard --auth-choice fireworks-api-key
-    ```
+Set up Fireworks auth through onboarding:
 
-    This stores your Fireworks key in OpenClaw config and sets the Fire Pass starter model as the default.
+```bash
+openclaw onboard --auth-choice fireworks-api-key
+```
 
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider fireworks
-    ```
-  </Step>
-</Steps>
+This stores your Fireworks key in OpenClaw config and sets the Fire Pass starter model as the default.
 
 ## Non-interactive example
 
-For scripted or CI setups, pass all values on the command line:
-
 ```bash
 openclaw onboard --non-interactive \
   --mode local \
@@ -49,20 +36,24 @@ openclaw onboard --non-interactive \
   --accept-risk
 ```
 
+## Environment note
+
+If the Gateway runs outside your interactive shell, make sure `FIREWORKS_API_KEY`
+is available to that process too. A key sitting only in `~/.profile` will not
+help a launchd/systemd daemon unless that environment is imported there as well.
+
 ## Built-in catalog
 
 | Model ref                                              | Name                        | Input      | Context | Max output | Notes                                      |
 | ------------------------------------------------------ | --------------------------- | ---------- | ------- | ---------- | ------------------------------------------ |
 | `fireworks/accounts/fireworks/routers/kimi-k2p5-turbo` | Kimi K2.5 Turbo (Fire Pass) | text,image | 256,000 | 256,000    | Default bundled starter model on Fireworks |
 
-<Tip>
-If Fireworks publishes a newer model such as a fresh Qwen or Gemma release, you can switch to it directly by using its Fireworks model id without waiting for a bundled catalog update.
-</Tip>
-
 ## Custom Fireworks model ids
 
 OpenClaw accepts dynamic Fireworks model ids too. Use the exact model or router id shown by Fireworks and prefix it with `fireworks/`.
 
+Example:
+
 ```json5
 {
   agents: {
@@ -75,34 +66,4 @@ OpenClaw accepts dynamic Fireworks model ids too. Use the exact model or router
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="How model id prefixing works">
-    Every Fireworks model ref in OpenClaw starts with `fireworks/` followed by the exact id or router path from the Fireworks platform. For example:
-
-    - Router model: `fireworks/accounts/fireworks/routers/kimi-k2p5-turbo`
-    - Direct model: `fireworks/accounts/fireworks/models/<model-name>`
-
-    OpenClaw strips the `fireworks/` prefix when building the API request and sends the remaining path to the Fireworks endpoint.
-
-  </Accordion>
-
-  <Accordion title="Environment note">
-    If the Gateway runs outside your interactive shell, make sure `FIREWORKS_API_KEY` is available to that process too.
-
-    <Warning>
-    A key sitting only in `~/.profile` will not help a launchd/systemd daemon unless that environment is imported there as well. Set the key in `~/.openclaw/.env` or via `env.shellEnv` to ensure the gateway process can read it.
-    </Warning>
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+If Fireworks publishes a newer model such as a fresh Qwen or Gemma release, you can switch to it directly by using its Fireworks model id without waiting for a bundled catalog update.

docs/providers/github-copilot.md

@@ -8,124 +8,73 @@ title: "GitHub Copilot"
 
 # GitHub Copilot
 
+## What is GitHub Copilot?
+
 GitHub Copilot is GitHub's AI coding assistant. It provides access to Copilot
 models for your GitHub account and plan. OpenClaw can use Copilot as a model
 provider in two different ways.
 
 ## Two ways to use Copilot in OpenClaw
 
-<Tabs>
-  <Tab title="Built-in provider (github-copilot)">
-    Use the native device-login flow to obtain a GitHub token, then exchange it for
-    Copilot API tokens when OpenClaw runs. This is the **default** and simplest path
-    because it does not require VS Code.
+### 1) Built-in GitHub Copilot provider (`github-copilot`)
 
-    <Steps>
-      <Step title="Run the login command">
-        ```bash
-        openclaw models auth login-github-copilot
-        ```
+Use the native device-login flow to obtain a GitHub token, then exchange it for
+Copilot API tokens when OpenClaw runs. This is the **default** and simplest path
+because it does not require VS Code.
 
-        You will be prompted to visit a URL and enter a one-time code. Keep the
-        terminal open until it completes.
-      </Step>
-      <Step title="Set a default model">
-        ```bash
-        openclaw models set github-copilot/gpt-4o
-        ```
+### 2) Copilot Proxy plugin (`copilot-proxy`)
 
-        Or in config:
+Use the **Copilot Proxy** VS Code extension as a local bridge. OpenClaw talks to
+the proxy’s `/v1` endpoint and uses the model list you configure there. Choose
+this when you already run Copilot Proxy in VS Code or need to route through it.
+You must enable the plugin and keep the VS Code extension running.
 
-        ```json5
-        {
-          agents: { defaults: { model: { primary: "github-copilot/gpt-4o" } } },
-        }
-        ```
-      </Step>
-    </Steps>
+Use GitHub Copilot as a model provider (`github-copilot`). The login command runs
+the GitHub device flow, saves an auth profile, and updates your config to use that
+profile.
 
-  </Tab>
-
-  <Tab title="Copilot Proxy plugin (copilot-proxy)">
-    Use the **Copilot Proxy** VS Code extension as a local bridge. OpenClaw talks to
-    the proxy's `/v1` endpoint and uses the model list you configure there.
-
-    <Note>
-    Choose this when you already run Copilot Proxy in VS Code or need to route
-    through it. You must enable the plugin and keep the VS Code extension running.
-    </Note>
-
-  </Tab>
-</Tabs>
-
-## Optional flags
-
-| Flag            | Description                                         |
-| --------------- | --------------------------------------------------- |
-| `--yes`         | Skip the confirmation prompt                        |
-| `--set-default` | Also apply the provider's recommended default model |
+## CLI setup
 
 ```bash
-# Skip confirmation
-openclaw models auth login-github-copilot --yes
+openclaw models auth login-github-copilot
+```
 
-# Login and set the default model in one step
+You'll be prompted to visit a URL and enter a one-time code. Keep the terminal
+open until it completes.
+
+### Optional flags
+
+```bash
+openclaw models auth login-github-copilot --yes
+```
+
+To also apply the provider's recommended default model in one step, use the
+generic auth command instead:
+
+```bash
 openclaw models auth login --provider github-copilot --method device --set-default
 ```
 
-<AccordionGroup>
-  <Accordion title="Interactive TTY required">
-    The device-login flow requires an interactive TTY. Run it directly in a
-    terminal, not in a non-interactive script or CI pipeline.
-  </Accordion>
+## Set a default model
 
-  <Accordion title="Model availability depends on your plan">
-    Copilot model availability depends on your GitHub plan. If a model is
-    rejected, try another ID (for example `github-copilot/gpt-4.1`).
-  </Accordion>
+```bash
+openclaw models set github-copilot/gpt-4o
+```
 
-  <Accordion title="Transport selection">
-    Claude model IDs use the Anthropic Messages transport automatically. GPT,
-    o-series, and Gemini models keep the OpenAI Responses transport. OpenClaw
-    selects the correct transport based on the model ref.
-  </Accordion>
+### Config snippet
 
-  <Accordion title="Environment variable resolution order">
-    OpenClaw resolves Copilot auth from environment variables in the following
-    priority order:
+```json5
+{
+  agents: { defaults: { model: { primary: "github-copilot/gpt-4o" } } },
+}
+```
 
-    | Priority | Variable              | Notes                            |
-    | -------- | --------------------- | -------------------------------- |
-    | 1        | `COPILOT_GITHUB_TOKEN` | Highest priority, Copilot-specific |
-    | 2        | `GH_TOKEN`            | GitHub CLI token (fallback)      |
-    | 3        | `GITHUB_TOKEN`        | Standard GitHub token (lowest)   |
+## Notes
 
-    When multiple variables are set, OpenClaw uses the highest-priority one.
-    The device-login flow (`openclaw models auth login-github-copilot`) stores
-    its token in the auth profile store and takes precedence over all environment
-    variables.
-
-  </Accordion>
-
-  <Accordion title="Token storage">
-    The login stores a GitHub token in the auth profile store and exchanges it
-    for a Copilot API token when OpenClaw runs. You do not need to manage the
-    token manually.
-  </Accordion>
-</AccordionGroup>
-
-<Warning>
-Requires an interactive TTY. Run the login command directly in a terminal, not
-inside a headless script or CI job.
-</Warning>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-</CardGroup>
+- Requires an interactive TTY; run it directly in a terminal.
+- Copilot model availability depends on your plan; if a model is rejected, try
+  another ID (for example `github-copilot/gpt-4.1`).
+- Claude model IDs use the Anthropic Messages transport automatically; GPT, o-series,
+  and Gemini models keep the OpenAI Responses transport.
+- The login stores a GitHub token in the auth profile store and exchanges it for a
+  Copilot API token when OpenClaw runs.

docs/providers/glm.md

@@ -3,7 +3,7 @@ summary: "GLM model family overview + how to use it in OpenClaw"
 read_when:
   - You want GLM models in OpenClaw
   - You need the model naming convention and setup
-title: "GLM (Zhipu)"
+title: "GLM Models"
 ---
 
 # GLM models
@@ -11,42 +11,26 @@ title: "GLM (Zhipu)"
 GLM is a **model family** (not a company) available through the Z.AI platform. In OpenClaw, GLM
 models are accessed via the `zai` provider and model IDs like `zai/glm-5`.
 
-## Getting started
+## CLI setup
 
-<Steps>
-  <Step title="Choose an auth route and run onboarding">
-    Pick the onboarding choice that matches your Z.AI plan and region:
+```bash
+# Generic API-key setup with endpoint auto-detection
+openclaw onboard --auth-choice zai-api-key
 
-    | Auth choice | Best for |
-    | ----------- | -------- |
-    | `zai-api-key` | Generic API-key setup with endpoint auto-detection |
-    | `zai-coding-global` | Coding Plan users (global) |
-    | `zai-coding-cn` | Coding Plan users (China region) |
-    | `zai-global` | General API (global) |
-    | `zai-cn` | General API (China region) |
+# Coding Plan Global, recommended for Coding Plan users
+openclaw onboard --auth-choice zai-coding-global
 
-    ```bash
-    # Example: generic auto-detect
-    openclaw onboard --auth-choice zai-api-key
+# Coding Plan CN (China region), recommended for Coding Plan users
+openclaw onboard --auth-choice zai-coding-cn
 
-    # Example: Coding Plan global
-    openclaw onboard --auth-choice zai-coding-global
-    ```
+# General API
+openclaw onboard --auth-choice zai-global
 
-  </Step>
-  <Step title="Set GLM as the default model">
-    ```bash
-    openclaw config set agents.defaults.model.primary "zai/glm-5.1"
-    ```
-  </Step>
-  <Step title="Verify models are available">
-    ```bash
-    openclaw models list --provider zai
-    ```
-  </Step>
-</Steps>
+# General API CN (China region)
+openclaw onboard --auth-choice zai-cn
+```
 
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -55,56 +39,30 @@ models are accessed via the `zai` provider and model IDs like `zai/glm-5`.
 }
 ```
 
-<Tip>
 `zai-api-key` lets OpenClaw detect the matching Z.AI endpoint from the key and
 apply the correct base URL automatically. Use the explicit regional choices when
 you want to force a specific Coding Plan or general API surface.
-</Tip>
 
-## Bundled GLM models
+## Current bundled GLM models
 
 OpenClaw currently seeds the bundled `zai` provider with these GLM refs:
 
-| Model           | Model            |
-| --------------- | ---------------- |
-| `glm-5.1`       | `glm-4.7`        |
-| `glm-5`         | `glm-4.7-flash`  |
-| `glm-5-turbo`   | `glm-4.7-flashx` |
-| `glm-5v-turbo`  | `glm-4.6`        |
-| `glm-4.5`       | `glm-4.6v`       |
-| `glm-4.5-air`   |                  |
-| `glm-4.5-flash` |                  |
-| `glm-4.5v`      |                  |
+- `glm-5.1`
+- `glm-5`
+- `glm-5-turbo`
+- `glm-5v-turbo`
+- `glm-4.7`
+- `glm-4.7-flash`
+- `glm-4.7-flashx`
+- `glm-4.6`
+- `glm-4.6v`
+- `glm-4.5`
+- `glm-4.5-air`
+- `glm-4.5-flash`
+- `glm-4.5v`
 
-<Note>
-The default bundled model ref is `zai/glm-5.1`. GLM versions and availability
-can change; check Z.AI's docs for the latest.
-</Note>
+## Notes
 
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Endpoint auto-detection">
-    When you use the `zai-api-key` auth choice, OpenClaw inspects the key format
-    to determine the correct Z.AI base URL. Explicit regional choices
-    (`zai-coding-global`, `zai-coding-cn`, `zai-global`, `zai-cn`) override
-    auto-detection and pin the endpoint directly.
-  </Accordion>
-
-  <Accordion title="Provider details">
-    GLM models are served by the `zai` runtime provider. For full provider
-    configuration, regional endpoints, and additional capabilities, see
-    [Z.AI provider docs](/providers/zai).
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Z.AI provider" href="/providers/zai" icon="server">
-    Full Z.AI provider configuration and regional endpoints.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>
+- GLM versions and availability can change; check Z.AI's docs for the latest.
+- Default bundled model ref is `zai/glm-5.1`.
+- For provider details, see [/providers/zai](/providers/zai).

docs/providers/google.md

@@ -17,114 +17,74 @@ Gemini Grounding.
 - API: Google Gemini API
 - Alternative provider: `google-gemini-cli` (OAuth)
 
-## Getting started
+## Quick start
 
-Choose your preferred auth method and follow the setup steps.
+1. Set the API key:
 
-<Tabs>
-  <Tab title="API key">
-    **Best for:** standard Gemini API access through Google AI Studio.
+```bash
+openclaw onboard --auth-choice gemini-api-key
+```
 
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice gemini-api-key
-        ```
+2. Set a default model:
 
-        Or pass the key directly:
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "google/gemini-3.1-pro-preview" },
+    },
+  },
+}
+```
 
-        ```bash
-        openclaw onboard --non-interactive \
-          --mode local \
-          --auth-choice gemini-api-key \
-          --gemini-api-key "$GEMINI_API_KEY"
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "google/gemini-3.1-pro-preview" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider google
-        ```
-      </Step>
-    </Steps>
+## Non-interactive example
 
-    <Tip>
-    The environment variables `GEMINI_API_KEY` and `GOOGLE_API_KEY` are both accepted. Use whichever you already have configured.
-    </Tip>
+```bash
+openclaw onboard --non-interactive \
+  --mode local \
+  --auth-choice gemini-api-key \
+  --gemini-api-key "$GEMINI_API_KEY"
+```
 
-  </Tab>
+## OAuth (Gemini CLI)
 
-  <Tab title="Gemini CLI (OAuth)">
-    **Best for:** reusing an existing Gemini CLI login via PKCE OAuth instead of a separate API key.
+An alternative provider `google-gemini-cli` uses PKCE OAuth instead of an API
+key. This is an unofficial integration; some users report account
+restrictions. Use at your own risk.
 
-    <Warning>
-    The `google-gemini-cli` provider is an unofficial integration. Some users
-    report account restrictions when using OAuth this way. Use at your own risk.
-    </Warning>
+- Default model: `google-gemini-cli/gemini-3-flash-preview`
+- Alias: `gemini-cli`
+- Install prerequisite: local Gemini CLI available as `gemini`
+  - Homebrew: `brew install gemini-cli`
+  - npm: `npm install -g @google/gemini-cli`
+- Login:
 
-    <Steps>
-      <Step title="Install the Gemini CLI">
-        The local `gemini` command must be available on `PATH`.
+```bash
+openclaw models auth login --provider google-gemini-cli --set-default
+```
 
-        ```bash
-        # Homebrew
-        brew install gemini-cli
+Environment variables:
 
-        # or npm
-        npm install -g @google/gemini-cli
-        ```
+- `OPENCLAW_GEMINI_OAUTH_CLIENT_ID`
+- `OPENCLAW_GEMINI_OAUTH_CLIENT_SECRET`
 
-        OpenClaw supports both Homebrew installs and global npm installs, including
-        common Windows/npm layouts.
-      </Step>
-      <Step title="Log in via OAuth">
-        ```bash
-        openclaw models auth login --provider google-gemini-cli --set-default
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider google-gemini-cli
-        ```
-      </Step>
-    </Steps>
+(Or the `GEMINI_CLI_*` variants.)
 
-    - Default model: `google-gemini-cli/gemini-3-flash-preview`
-    - Alias: `gemini-cli`
+If Gemini CLI OAuth requests fail after login, set
+`GOOGLE_CLOUD_PROJECT` or `GOOGLE_CLOUD_PROJECT_ID` on the gateway host and
+retry.
 
-    **Environment variables:**
+If login fails before the browser flow starts, make sure the local `gemini`
+command is installed and on `PATH`. OpenClaw supports both Homebrew installs
+and global npm installs, including common Windows/npm layouts.
 
-    - `OPENCLAW_GEMINI_OAUTH_CLIENT_ID`
-    - `OPENCLAW_GEMINI_OAUTH_CLIENT_SECRET`
+Gemini CLI JSON usage notes:
 
-    (Or the `GEMINI_CLI_*` variants.)
-
-    <Note>
-    If Gemini CLI OAuth requests fail after login, set `GOOGLE_CLOUD_PROJECT` or
-    `GOOGLE_CLOUD_PROJECT_ID` on the gateway host and retry.
-    </Note>
-
-    <Note>
-    If login fails before the browser flow starts, make sure the local `gemini`
-    command is installed and on `PATH`.
-    </Note>
-
-    The OAuth-only `google-gemini-cli` provider is a separate text-inference
-    surface. Image generation, media understanding, and Gemini Grounding stay on
-    the `google` provider id.
-
-  </Tab>
-</Tabs>
+- Reply text comes from the CLI JSON `response` field.
+- Usage falls back to `stats` when the CLI leaves `usage` empty.
+- `stats.cached` is normalized into OpenClaw `cacheRead`.
+- If `stats.input` is missing, OpenClaw derives input tokens from
+  `stats.input_tokens - stats.cached`.
 
 ## Capabilities
 
@@ -140,12 +100,37 @@ Choose your preferred auth method and follow the setup steps.
 | Thinking/reasoning     | Yes (Gemini 3.1+) |
 | Gemma 4 models         | Yes               |
 
-<Tip>
-Gemma 4 models (for example `gemma-4-26b-a4b-it`) support thinking mode. OpenClaw
-rewrites `thinkingBudget` to a supported Google `thinkingLevel` for Gemma 4.
-Setting thinking to `off` preserves thinking disabled instead of mapping to
-`MINIMAL`.
-</Tip>
+Gemma 4 models (for example `gemma-4-26b-a4b-it`) support thinking mode. OpenClaw rewrites `thinkingBudget` to a supported Google `thinkingLevel` for Gemma 4. Setting thinking to `off` preserves thinking disabled instead of mapping to `MINIMAL`.
+
+## Direct Gemini cache reuse
+
+For direct Gemini API runs (`api: "google-generative-ai"`), OpenClaw now
+passes a configured `cachedContent` handle through to Gemini requests.
+
+- Configure per-model or global params with either
+  `cachedContent` or legacy `cached_content`
+- If both are present, `cachedContent` wins
+- Example value: `cachedContents/prebuilt-context`
+- Gemini cache-hit usage is normalized into OpenClaw `cacheRead` from
+  upstream `cachedContentTokenCount`
+
+Example:
+
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "google/gemini-2.5-pro": {
+          params: {
+            cachedContent: "cachedContents/prebuilt-context",
+          },
+        },
+      },
+    },
+  },
+}
+```
 
 ## Image generation
 
@@ -157,6 +142,10 @@ The bundled `google` image-generation provider defaults to
 - Edit mode: enabled, up to 5 input images
 - Geometry controls: `size`, `aspectRatio`, and `resolution`
 
+The OAuth-only `google-gemini-cli` provider is a separate text-inference
+surface. Image generation, media understanding, and Gemini Grounding stay on
+the `google` provider id.
+
 To use Google as the default image provider:
 
 ```json5
@@ -171,9 +160,8 @@ To use Google as the default image provider:
 }
 ```
 
-<Note>
-See [Image Generation](/tools/image-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Image Generation](/tools/image-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
 ## Video generation
 
@@ -199,9 +187,8 @@ To use Google as the default video provider:
 }
 ```
 
-<Note>
-See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
 ## Music generation
 
@@ -229,74 +216,11 @@ To use Google as the default music provider:
 }
 ```
 
-<Note>
-See [Music Generation](/tools/music-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Music Generation](/tools/music-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-## Advanced configuration
+## Environment note
 
-<AccordionGroup>
-  <Accordion title="Direct Gemini cache reuse">
-    For direct Gemini API runs (`api: "google-generative-ai"`), OpenClaw
-    passes a configured `cachedContent` handle through to Gemini requests.
-
-    - Configure per-model or global params with either
-      `cachedContent` or legacy `cached_content`
-    - If both are present, `cachedContent` wins
-    - Example value: `cachedContents/prebuilt-context`
-    - Gemini cache-hit usage is normalized into OpenClaw `cacheRead` from
-      upstream `cachedContentTokenCount`
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "google/gemini-2.5-pro": {
-              params: {
-                cachedContent: "cachedContents/prebuilt-context",
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Gemini CLI JSON usage notes">
-    When using the `google-gemini-cli` OAuth provider, OpenClaw normalizes
-    the CLI JSON output as follows:
-
-    - Reply text comes from the CLI JSON `response` field.
-    - Usage falls back to `stats` when the CLI leaves `usage` empty.
-    - `stats.cached` is normalized into OpenClaw `cacheRead`.
-    - If `stats.input` is missing, OpenClaw derives input tokens from
-      `stats.input_tokens - stats.cached`.
-
-  </Accordion>
-
-  <Accordion title="Environment and daemon setup">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `GEMINI_API_KEY`
-    is available to that process (for example, in `~/.openclaw/.env` or via
-    `env.shellEnv`).
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Image generation" href="/tools/image-generation" icon="image">
-    Shared image tool parameters and provider selection.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Music generation" href="/tools/music-generation" icon="music">
-    Shared music tool parameters and provider selection.
-  </Card>
-</CardGroup>
+If the Gateway runs as a daemon (launchd/systemd), make sure `GEMINI_API_KEY`
+is available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).

docs/providers/groq.md

@@ -12,37 +12,33 @@ read_when:
 (Llama, Gemma, Mistral, and more) using custom LPU hardware. OpenClaw connects
 to Groq through its OpenAI-compatible API.
 
-| Property | Value             |
-| -------- | ----------------- |
-| Provider | `groq`            |
-| Auth     | `GROQ_API_KEY`    |
-| API      | OpenAI-compatible |
+- Provider: `groq`
+- Auth: `GROQ_API_KEY`
+- API: OpenAI-compatible
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Get an API key">
-    Create an API key at [console.groq.com/keys](https://console.groq.com/keys).
-  </Step>
-  <Step title="Set the API key">
-    ```bash
-    export GROQ_API_KEY="gsk_..."
-    ```
-  </Step>
-  <Step title="Set a default model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "groq/llama-3.3-70b-versatile" },
-        },
-      },
-    }
-    ```
-  </Step>
-</Steps>
+1. Get an API key from [console.groq.com/keys](https://console.groq.com/keys).
 
-### Config file example
+2. Set the API key:
+
+```bash
+export GROQ_API_KEY="gsk_..."
+```
+
+3. Set a default model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "groq/llama-3.3-70b-versatile" },
+    },
+  },
+}
+```
+
+## Config file example
 
 ```json5
 {
@@ -55,24 +51,6 @@ to Groq through its OpenAI-compatible API.
 }
 ```
 
-## Available models
-
-Groq's model catalog changes frequently. Run `openclaw models list | grep groq`
-to see currently available models, or check
-[console.groq.com/docs/models](https://console.groq.com/docs/models).
-
-| Model                       | Notes                              |
-| --------------------------- | ---------------------------------- |
-| **Llama 3.3 70B Versatile** | General-purpose, large context     |
-| **Llama 3.1 8B Instant**    | Fast, lightweight                  |
-| **Gemma 2 9B**              | Compact, efficient                 |
-| **Mixtral 8x7B**            | MoE architecture, strong reasoning |
-
-<Tip>
-Use `openclaw models list --provider groq` for the most up-to-date list of
-models available on your account.
-</Tip>
-
 ## Audio transcription
 
 Groq also provides fast Whisper-based audio transcription. When configured as a
@@ -92,43 +70,36 @@ surface.
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="Audio transcription details">
-    | Property | Value |
-    |----------|-------|
-    | Shared config path | `tools.media.audio` |
-    | Default base URL   | `https://api.groq.com/openai/v1` |
-    | Default model      | `whisper-large-v3-turbo` |
-    | API endpoint       | OpenAI-compatible `/audio/transcriptions` |
-  </Accordion>
+## Environment note
 
-  <Accordion title="Environment note">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `GROQ_API_KEY` is
-    available to that process (for example, in `~/.openclaw/.env` or via
-    `env.shellEnv`).
+If the Gateway runs as a daemon (launchd/systemd), make sure `GROQ_API_KEY` is
+available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).
 
-    <Warning>
-    Keys set only in your interactive shell are not visible to daemon-managed
-    gateway processes. Use `~/.openclaw/.env` or `env.shellEnv` config for
-    persistent availability.
-    </Warning>
+## Audio notes
 
-  </Accordion>
-</AccordionGroup>
+- Shared config path: `tools.media.audio`
+- Default Groq audio base URL: `https://api.groq.com/openai/v1`
+- Default Groq audio model: `whisper-large-v3-turbo`
+- Groq audio transcription uses the OpenAI-compatible `/audio/transcriptions`
+  path
 
-## Related
+## Available models
 
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider and audio settings.
-  </Card>
-  <Card title="Groq Console" href="https://console.groq.com" icon="arrow-up-right-from-square">
-    Groq dashboard, API docs, and pricing.
-  </Card>
-  <Card title="Groq model list" href="https://console.groq.com/docs/models" icon="list">
-    Official Groq model catalog.
-  </Card>
-</CardGroup>
+Groq's model catalog changes frequently. Run `openclaw models list | grep groq`
+to see currently available models, or check
+[console.groq.com/docs/models](https://console.groq.com/docs/models).
+
+Popular choices include:
+
+- **Llama 3.3 70B Versatile** - general-purpose, large context
+- **Llama 3.1 8B Instant** - fast, lightweight
+- **Gemma 2 9B** - compact, efficient
+- **Mixtral 8x7B** - MoE architecture, strong reasoning
+
+## Links
+
+- [Groq Console](https://console.groq.com)
+- [API Documentation](https://console.groq.com/docs)
+- [Model List](https://console.groq.com/docs/models)
+- [Pricing](https://groq.com/pricing)

docs/providers/huggingface.md

@@ -15,49 +15,29 @@ title: "Hugging Face (Inference)"
 - API: OpenAI-compatible (`https://router.huggingface.co/v1`)
 - Billing: Single HF token; [pricing](https://huggingface.co/docs/inference-providers/pricing) follows provider rates with a free tier.
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Create a fine-grained token">
-    Go to [Hugging Face Settings Tokens](https://huggingface.co/settings/tokens/new?ownUserPermissions=inference.serverless.write&tokenType=fineGrained) and create a new fine-grained token.
+1. Create a fine-grained token at [Hugging Face → Settings → Tokens](https://huggingface.co/settings/tokens/new?ownUserPermissions=inference.serverless.write&tokenType=fineGrained) with the **Make calls to Inference Providers** permission.
+2. Run onboarding and choose **Hugging Face** in the provider dropdown, then enter your API key when prompted:
 
-    <Warning>
-    The token must have the **Make calls to Inference Providers** permission enabled or API requests will be rejected.
-    </Warning>
+```bash
+openclaw onboard --auth-choice huggingface-api-key
+```
 
-  </Step>
-  <Step title="Run onboarding">
-    Choose **Hugging Face** in the provider dropdown, then enter your API key when prompted:
+3. In the **Default Hugging Face model** dropdown, pick the model you want (the list is loaded from the Inference API when you have a valid token; otherwise a built-in list is shown). Your choice is saved as the default model.
+4. You can also set or change the default model later in config:
 
-    ```bash
-    openclaw onboard --auth-choice huggingface-api-key
-    ```
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "huggingface/deepseek-ai/DeepSeek-R1" },
+    },
+  },
+}
+```
 
-  </Step>
-  <Step title="Select a default model">
-    In the **Default Hugging Face model** dropdown, pick the model you want. The list is loaded from the Inference API when you have a valid token; otherwise a built-in list is shown. Your choice is saved as the default model.
-
-    You can also set or change the default model later in config:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "huggingface/deepseek-ai/DeepSeek-R1" },
-        },
-      },
-    }
-    ```
-
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider huggingface
-    ```
-  </Step>
-</Steps>
-
-### Non-interactive setup
+## Non-interactive example
 
 ```bash
 openclaw onboard --non-interactive \
@@ -68,10 +48,56 @@ openclaw onboard --non-interactive \
 
 This will set `huggingface/deepseek-ai/DeepSeek-R1` as the default model.
 
-## Model IDs
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure `HUGGINGFACE_HUB_TOKEN` or `HF_TOKEN`
+is available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).
+
+## Model discovery and onboarding dropdown
+
+OpenClaw discovers models by calling the **Inference endpoint directly**:
+
+```bash
+GET https://router.huggingface.co/v1/models
+```
+
+(Optional: send `Authorization: Bearer $HUGGINGFACE_HUB_TOKEN` or `$HF_TOKEN` for the full list; some endpoints return a subset without auth.) The response is OpenAI-style `{ "object": "list", "data": [ { "id": "Qwen/Qwen3-8B", "owned_by": "Qwen", ... }, ... ] }`.
+
+When you configure a Hugging Face API key (via onboarding, `HUGGINGFACE_HUB_TOKEN`, or `HF_TOKEN`), OpenClaw uses this GET to discover available chat-completion models. During **interactive setup**, after you enter your token you see a **Default Hugging Face model** dropdown populated from that list (or the built-in catalog if the request fails). At runtime (e.g. Gateway startup), when a key is present, OpenClaw again calls **GET** `https://router.huggingface.co/v1/models` to refresh the catalog. The list is merged with a built-in catalog (for metadata like context window and cost). If the request fails or no key is set, only the built-in catalog is used.
+
+## Model names and editable options
+
+- **Name from API:** The model display name is **hydrated from GET /v1/models** when the API returns `name`, `title`, or `display_name`; otherwise it is derived from the model id (e.g. `deepseek-ai/DeepSeek-R1` → “DeepSeek R1”).
+- **Override display name:** You can set a custom label per model in config so it appears the way you want in the CLI and UI:
+
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "huggingface/deepseek-ai/DeepSeek-R1": { alias: "DeepSeek R1 (fast)" },
+        "huggingface/deepseek-ai/DeepSeek-R1:cheapest": { alias: "DeepSeek R1 (cheap)" },
+      },
+    },
+  },
+}
+```
+
+- **Policy suffixes:** OpenClaw's bundled Hugging Face docs and helpers currently treat these two suffixes as the built-in policy variants:
+  - **`:fastest`** — highest throughput.
+  - **`:cheapest`** — lowest cost per output token.
+
+  You can add these as separate entries in `models.providers.huggingface.models` or set `model.primary` with the suffix. You can also set your default provider order in [Inference Provider settings](https://hf.co/settings/inference-providers) (no suffix = use that order).
+
+- **Config merge:** Existing entries in `models.providers.huggingface.models` (e.g. in `models.json`) are kept when config is merged. So any custom `name`, `alias`, or model options you set there are preserved.
+
+## Model IDs and configuration examples
 
 Model refs use the form `huggingface/<org>/<model>` (Hub-style IDs). The list below is from **GET** `https://router.huggingface.co/v1/models`; your catalog may include more.
 
+**Example IDs (from the inference endpoint):**
+
 | Model                  | Ref (prefix with `huggingface/`)    |
 | ---------------------- | ----------------------------------- |
 | DeepSeek R1            | `deepseek-ai/DeepSeek-R1`           |
@@ -85,153 +111,83 @@ Model refs use the form `huggingface/<org>/<model>` (Hub-style IDs). The list be
 | GLM 4.7                | `zai-org/GLM-4.7`                   |
 | Kimi K2.5              | `moonshotai/Kimi-K2.5`              |
 
-<Tip>
-You can append `:fastest` or `:cheapest` to any model id. Set your default order in [Inference Provider settings](https://hf.co/settings/inference-providers); see [Inference Providers](https://huggingface.co/docs/inference-providers) and **GET** `https://router.huggingface.co/v1/models` for the full list.
-</Tip>
+You can append `:fastest` or `:cheapest` to the model id. Set your default order in [Inference Provider settings](https://hf.co/settings/inference-providers); see [Inference Providers](https://huggingface.co/docs/inference-providers) and **GET** `https://router.huggingface.co/v1/models` for the full list.
 
-## Advanced details
+### Complete configuration examples
 
-<AccordionGroup>
-  <Accordion title="Model discovery and onboarding dropdown">
-    OpenClaw discovers models by calling the **Inference endpoint directly**:
+**Primary DeepSeek R1 with Qwen fallback:**
 
-    ```bash
-    GET https://router.huggingface.co/v1/models
-    ```
-
-    (Optional: send `Authorization: Bearer $HUGGINGFACE_HUB_TOKEN` or `$HF_TOKEN` for the full list; some endpoints return a subset without auth.) The response is OpenAI-style `{ "object": "list", "data": [ { "id": "Qwen/Qwen3-8B", "owned_by": "Qwen", ... }, ... ] }`.
-
-    When you configure a Hugging Face API key (via onboarding, `HUGGINGFACE_HUB_TOKEN`, or `HF_TOKEN`), OpenClaw uses this GET to discover available chat-completion models. During **interactive setup**, after you enter your token you see a **Default Hugging Face model** dropdown populated from that list (or the built-in catalog if the request fails). At runtime (e.g. Gateway startup), when a key is present, OpenClaw again calls **GET** `https://router.huggingface.co/v1/models` to refresh the catalog. The list is merged with a built-in catalog (for metadata like context window and cost). If the request fails or no key is set, only the built-in catalog is used.
-
-  </Accordion>
-
-  <Accordion title="Model names, aliases, and policy suffixes">
-    - **Name from API:** The model display name is **hydrated from GET /v1/models** when the API returns `name`, `title`, or `display_name`; otherwise it is derived from the model id (e.g. `deepseek-ai/DeepSeek-R1` becomes "DeepSeek R1").
-    - **Override display name:** You can set a custom label per model in config so it appears the way you want in the CLI and UI:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "huggingface/deepseek-ai/DeepSeek-R1": { alias: "DeepSeek R1 (fast)" },
-            "huggingface/deepseek-ai/DeepSeek-R1:cheapest": { alias: "DeepSeek R1 (cheap)" },
-          },
-        },
+```json5
+{
+  agents: {
+    defaults: {
+      model: {
+        primary: "huggingface/deepseek-ai/DeepSeek-R1",
+        fallbacks: ["huggingface/Qwen/Qwen3-8B"],
       },
-    }
-    ```
-
-    - **Policy suffixes:** OpenClaw's bundled Hugging Face docs and helpers currently treat these two suffixes as the built-in policy variants:
-      - **`:fastest`** — highest throughput.
-      - **`:cheapest`** — lowest cost per output token.
-
-      You can add these as separate entries in `models.providers.huggingface.models` or set `model.primary` with the suffix. You can also set your default provider order in [Inference Provider settings](https://hf.co/settings/inference-providers) (no suffix = use that order).
-
-    - **Config merge:** Existing entries in `models.providers.huggingface.models` (e.g. in `models.json`) are kept when config is merged. So any custom `name`, `alias`, or model options you set there are preserved.
-
-  </Accordion>
-
-  <Accordion title="Environment and daemon setup">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `HUGGINGFACE_HUB_TOKEN` or `HF_TOKEN` is available to that process (for example, in `~/.openclaw/.env` or via `env.shellEnv`).
-
-    <Note>
-    OpenClaw accepts both `HUGGINGFACE_HUB_TOKEN` and `HF_TOKEN` as env var aliases. Either one works; if both are set, `HUGGINGFACE_HUB_TOKEN` takes precedence.
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Config: DeepSeek R1 with Qwen fallback">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: {
-            primary: "huggingface/deepseek-ai/DeepSeek-R1",
-            fallbacks: ["huggingface/Qwen/Qwen3-8B"],
-          },
-          models: {
-            "huggingface/deepseek-ai/DeepSeek-R1": { alias: "DeepSeek R1" },
-            "huggingface/Qwen/Qwen3-8B": { alias: "Qwen3 8B" },
-          },
-        },
+      models: {
+        "huggingface/deepseek-ai/DeepSeek-R1": { alias: "DeepSeek R1" },
+        "huggingface/Qwen/Qwen3-8B": { alias: "Qwen3 8B" },
       },
-    }
-    ```
-  </Accordion>
+    },
+  },
+}
+```
 
-  <Accordion title="Config: Qwen with cheapest and fastest variants">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "huggingface/Qwen/Qwen3-8B" },
-          models: {
-            "huggingface/Qwen/Qwen3-8B": { alias: "Qwen3 8B" },
-            "huggingface/Qwen/Qwen3-8B:cheapest": { alias: "Qwen3 8B (cheapest)" },
-            "huggingface/Qwen/Qwen3-8B:fastest": { alias: "Qwen3 8B (fastest)" },
-          },
-        },
+**Qwen as default, with :cheapest and :fastest variants:**
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "huggingface/Qwen/Qwen3-8B" },
+      models: {
+        "huggingface/Qwen/Qwen3-8B": { alias: "Qwen3 8B" },
+        "huggingface/Qwen/Qwen3-8B:cheapest": { alias: "Qwen3 8B (cheapest)" },
+        "huggingface/Qwen/Qwen3-8B:fastest": { alias: "Qwen3 8B (fastest)" },
       },
-    }
-    ```
-  </Accordion>
+    },
+  },
+}
+```
 
-  <Accordion title="Config: DeepSeek + Llama + GPT-OSS with aliases">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: {
-            primary: "huggingface/deepseek-ai/DeepSeek-V3.2",
-            fallbacks: [
-              "huggingface/meta-llama/Llama-3.3-70B-Instruct",
-              "huggingface/openai/gpt-oss-120b",
-            ],
-          },
-          models: {
-            "huggingface/deepseek-ai/DeepSeek-V3.2": { alias: "DeepSeek V3.2" },
-            "huggingface/meta-llama/Llama-3.3-70B-Instruct": { alias: "Llama 3.3 70B" },
-            "huggingface/openai/gpt-oss-120b": { alias: "GPT-OSS 120B" },
-          },
-        },
+**DeepSeek + Llama + GPT-OSS with aliases:**
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: {
+        primary: "huggingface/deepseek-ai/DeepSeek-V3.2",
+        fallbacks: [
+          "huggingface/meta-llama/Llama-3.3-70B-Instruct",
+          "huggingface/openai/gpt-oss-120b",
+        ],
       },
-    }
-    ```
-  </Accordion>
-
-  <Accordion title="Config: Multiple Qwen and DeepSeek with policy suffixes">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "huggingface/Qwen/Qwen2.5-7B-Instruct:cheapest" },
-          models: {
-            "huggingface/Qwen/Qwen2.5-7B-Instruct": { alias: "Qwen2.5 7B" },
-            "huggingface/Qwen/Qwen2.5-7B-Instruct:cheapest": { alias: "Qwen2.5 7B (cheap)" },
-            "huggingface/deepseek-ai/DeepSeek-R1:fastest": { alias: "DeepSeek R1 (fast)" },
-            "huggingface/meta-llama/Llama-3.1-8B-Instruct": { alias: "Llama 3.1 8B" },
-          },
-        },
+      models: {
+        "huggingface/deepseek-ai/DeepSeek-V3.2": { alias: "DeepSeek V3.2" },
+        "huggingface/meta-llama/Llama-3.3-70B-Instruct": { alias: "Llama 3.3 70B" },
+        "huggingface/openai/gpt-oss-120b": { alias: "GPT-OSS 120B" },
       },
-    }
-    ```
-  </Accordion>
-</AccordionGroup>
+    },
+  },
+}
+```
 
-## Related
+**Multiple Qwen and DeepSeek models with policy suffixes:**
 
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Model selection" href="/concepts/models" icon="brain">
-    How to choose and configure models.
-  </Card>
-  <Card title="Inference Providers docs" href="https://huggingface.co/docs/inference-providers" icon="book">
-    Official Hugging Face Inference Providers documentation.
-  </Card>
-  <Card title="Configuration" href="/gateway/configuration" icon="gear">
-    Full config reference.
-  </Card>
-</CardGroup>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "huggingface/Qwen/Qwen2.5-7B-Instruct:cheapest" },
+      models: {
+        "huggingface/Qwen/Qwen2.5-7B-Instruct": { alias: "Qwen2.5 7B" },
+        "huggingface/Qwen/Qwen2.5-7B-Instruct:cheapest": { alias: "Qwen2.5 7B (cheap)" },
+        "huggingface/deepseek-ai/DeepSeek-R1:fastest": { alias: "DeepSeek R1 (fast)" },
+        "huggingface/meta-llama/Llama-3.1-8B-Instruct": { alias: "Llama 3.1 8B" },
+      },
+    },
+  },
+}
+```

docs/providers/inferrs.md

@@ -16,27 +16,27 @@ OpenAI-compatible `/v1` API. OpenClaw works with `inferrs` through the generic
 `inferrs` is currently best treated as a custom self-hosted OpenAI-compatible
 backend, not a dedicated OpenClaw provider plugin.
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Start inferrs with a model">
-    ```bash
-    inferrs serve google/gemma-4-E2B-it \
-      --host 127.0.0.1 \
-      --port 8080 \
-      --device metal
-    ```
-  </Step>
-  <Step title="Verify the server is reachable">
-    ```bash
-    curl http://127.0.0.1:8080/health
-    curl http://127.0.0.1:8080/v1/models
-    ```
-  </Step>
-  <Step title="Add an OpenClaw provider entry">
-    Add an explicit provider entry and point your default model at it. See the full config example below.
-  </Step>
-</Steps>
+1. Start `inferrs` with a model.
+
+Example:
+
+```bash
+inferrs serve google/gemma-4-E2B-it \
+  --host 127.0.0.1 \
+  --port 8080 \
+  --device metal
+```
+
+2. Verify the server is reachable.
+
+```bash
+curl http://127.0.0.1:8080/health
+curl http://127.0.0.1:8080/v1/models
+```
+
+3. Add an explicit OpenClaw provider entry and point your default model at it.
 
 ## Full config example
 
@@ -81,130 +81,93 @@ This example uses Gemma 4 on a local `inferrs` server.
 }
 ```
 
-## Advanced
+## Why `requiresStringContent` matters
 
-<AccordionGroup>
-  <Accordion title="Why requiresStringContent matters">
-    Some `inferrs` Chat Completions routes accept only string
-    `messages[].content`, not structured content-part arrays.
+Some `inferrs` Chat Completions routes accept only string
+`messages[].content`, not structured content-part arrays.
 
-    <Warning>
-    If OpenClaw runs fail with an error like:
+If OpenClaw runs fail with an error like:
 
-    ```text
-    messages[1].content: invalid type: sequence, expected a string
-    ```
+```text
+messages[1].content: invalid type: sequence, expected a string
+```
 
-    set `compat.requiresStringContent: true` in your model entry.
-    </Warning>
+set:
 
-    ```json5
-    compat: {
-      requiresStringContent: true
-    }
-    ```
+```json5
+compat: {
+  requiresStringContent: true
+}
+```
 
-    OpenClaw will flatten pure text content parts into plain strings before sending
-    the request.
+OpenClaw will flatten pure text content parts into plain strings before sending
+the request.
 
-  </Accordion>
+## Gemma and tool-schema caveat
 
-  <Accordion title="Gemma and tool-schema caveat">
-    Some current `inferrs` + Gemma combinations accept small direct
-    `/v1/chat/completions` requests but still fail on full OpenClaw agent-runtime
-    turns.
+Some current `inferrs` + Gemma combinations accept small direct
+`/v1/chat/completions` requests but still fail on full OpenClaw agent-runtime
+turns.
 
-    If that happens, try this first:
+If that happens, try this first:
 
-    ```json5
-    compat: {
-      requiresStringContent: true,
-      supportsTools: false
-    }
-    ```
+```json5
+compat: {
+  requiresStringContent: true,
+  supportsTools: false
+}
+```
 
-    That disables OpenClaw's tool schema surface for the model and can reduce prompt
-    pressure on stricter local backends.
+That disables OpenClaw's tool schema surface for the model and can reduce prompt
+pressure on stricter local backends.
 
-    If tiny direct requests still work but normal OpenClaw agent turns continue to
-    crash inside `inferrs`, the remaining issue is usually upstream model/server
-    behavior rather than OpenClaw's transport layer.
+If tiny direct requests still work but normal OpenClaw agent turns continue to
+crash inside `inferrs`, the remaining issue is usually upstream model/server
+behavior rather than OpenClaw's transport layer.
 
-  </Accordion>
+## Manual smoke test
 
-  <Accordion title="Manual smoke test">
-    Once configured, test both layers:
+Once configured, test both layers:
 
-    ```bash
-    curl http://127.0.0.1:8080/v1/chat/completions \
-      -H 'content-type: application/json' \
-      -d '{"model":"google/gemma-4-E2B-it","messages":[{"role":"user","content":"What is 2 + 2?"}],"stream":false}'
-    ```
+```bash
+curl http://127.0.0.1:8080/v1/chat/completions \
+  -H 'content-type: application/json' \
+  -d '{"model":"google/gemma-4-E2B-it","messages":[{"role":"user","content":"What is 2 + 2?"}],"stream":false}'
 
-    ```bash
-    openclaw infer model run \
-      --model inferrs/google/gemma-4-E2B-it \
-      --prompt "What is 2 + 2? Reply with one short sentence." \
-      --json
-    ```
+openclaw infer model run \
+  --model inferrs/google/gemma-4-E2B-it \
+  --prompt "What is 2 + 2? Reply with one short sentence." \
+  --json
+```
 
-    If the first command works but the second fails, check the troubleshooting section below.
-
-  </Accordion>
-
-  <Accordion title="Proxy-style behavior">
-    `inferrs` is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
-    native OpenAI endpoint.
-
-    - Native OpenAI-only request shaping does not apply here
-    - No `service_tier`, no Responses `store`, no prompt-cache hints, and no
-      OpenAI reasoning-compat payload shaping
-    - Hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
-      are not injected on custom `inferrs` base URLs
-
-  </Accordion>
-</AccordionGroup>
+If the first command works but the second fails, use the troubleshooting notes
+below.
 
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="curl /v1/models fails">
-    `inferrs` is not running, not reachable, or not bound to the expected
-    host/port. Make sure the server is started and listening on the address you
-    configured.
-  </Accordion>
+- `curl /v1/models` fails: `inferrs` is not running, not reachable, or not
+  bound to the expected host/port.
+- `messages[].content ... expected a string`: set
+  `compat.requiresStringContent: true`.
+- Direct tiny `/v1/chat/completions` calls pass, but `openclaw infer model run`
+  fails: try `compat.supportsTools: false`.
+- OpenClaw no longer gets schema errors, but `inferrs` still crashes on larger
+  agent turns: treat it as an upstream `inferrs` or model limitation and reduce
+  prompt pressure or switch local backend/model.
 
-  <Accordion title="messages[].content expected a string">
-    Set `compat.requiresStringContent: true` in the model entry. See the
-    `requiresStringContent` section above for details.
-  </Accordion>
+## Proxy-style behavior
 
-  <Accordion title="Direct /v1/chat/completions calls pass but openclaw infer model run fails">
-    Try setting `compat.supportsTools: false` to disable the tool schema surface.
-    See the Gemma tool-schema caveat above.
-  </Accordion>
+`inferrs` is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
+native OpenAI endpoint.
 
-  <Accordion title="inferrs still crashes on larger agent turns">
-    If OpenClaw no longer gets schema errors but `inferrs` still crashes on larger
-    agent turns, treat it as an upstream `inferrs` or model limitation. Reduce
-    prompt pressure or switch to a different local backend or model.
-  </Accordion>
-</AccordionGroup>
-
-<Tip>
-For general help, see [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Tip>
+- native OpenAI-only request shaping does not apply here
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on custom `inferrs` base URLs
 
 ## See also
 
-<CardGroup cols={2}>
-  <Card title="Local models" href="/gateway/local-models" icon="server">
-    Running OpenClaw against local model servers.
-  </Card>
-  <Card title="Gateway troubleshooting" href="/gateway/troubleshooting#local-openai-compatible-backend-passes-direct-probes-but-agent-runs-fail" icon="wrench">
-    Debugging local OpenAI-compatible backends that pass probes but fail agent runs.
-  </Card>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>
+- [Local models](/gateway/local-models)
+- [Gateway troubleshooting](/gateway/troubleshooting#local-openai-compatible-backend-passes-direct-probes-but-agent-runs-fail)
+- [Model providers](/concepts/model-providers)

docs/providers/kilocode.md

@@ -1,5 +1,5 @@
 ---
-title: "Kilocode"
+title: "Kilo Gateway"
 summary: "Use Kilo Gateway's unified API to access many models in OpenClaw"
 read_when:
   - You want a single API key for many LLMs
@@ -11,73 +11,25 @@ read_when:
 Kilo Gateway provides a **unified API** that routes requests to many models behind a single
 endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switching the base URL.
 
-| Property | Value                              |
-| -------- | ---------------------------------- |
-| Provider | `kilocode`                         |
-| Auth     | `KILOCODE_API_KEY`                 |
-| API      | OpenAI-compatible                  |
-| Base URL | `https://api.kilo.ai/api/gateway/` |
+## Getting an API key
 
-## Getting started
+1. Go to [app.kilo.ai](https://app.kilo.ai)
+2. Sign in or create an account
+3. Navigate to API Keys and generate a new key
 
-<Steps>
-  <Step title="Create an account">
-    Go to [app.kilo.ai](https://app.kilo.ai), sign in or create an account, then navigate to API Keys and generate a new key.
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice kilocode-api-key
-    ```
+## CLI setup
 
-    Or set the environment variable directly:
+```bash
+openclaw onboard --auth-choice kilocode-api-key
+```
 
-    ```bash
-    export KILOCODE_API_KEY="<your-kilocode-api-key>" # pragma: allowlist secret
-    ```
+Or set the environment variable:
 
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider kilocode
-    ```
-  </Step>
-</Steps>
+```bash
+export KILOCODE_API_KEY="<your-kilocode-api-key>" # pragma: allowlist secret
+```
 
-## Default model
-
-The default model is `kilocode/kilo/auto`, a provider-owned smart-routing
-model managed by Kilo Gateway.
-
-<Note>
-OpenClaw treats `kilocode/kilo/auto` as the stable default ref, but does not
-publish a source-backed task-to-upstream-model mapping for that route. Exact
-upstream routing behind `kilocode/kilo/auto` is owned by Kilo Gateway, not
-hard-coded in OpenClaw.
-</Note>
-
-## Available models
-
-OpenClaw dynamically discovers available models from the Kilo Gateway at startup. Use
-`/models kilocode` to see the full list of models available with your account.
-
-Any model available on the gateway can be used with the `kilocode/` prefix:
-
-| Model ref                              | Notes                              |
-| -------------------------------------- | ---------------------------------- |
-| `kilocode/kilo/auto`                   | Default — smart routing            |
-| `kilocode/anthropic/claude-sonnet-4`   | Anthropic via Kilo                 |
-| `kilocode/openai/gpt-5.4`              | OpenAI via Kilo                    |
-| `kilocode/google/gemini-3-pro-preview` | Google via Kilo                    |
-| ...and many more                       | Use `/models kilocode` to list all |
-
-<Tip>
-At startup, OpenClaw queries `GET https://api.kilo.ai/api/gateway/models` and merges
-discovered models ahead of the static fallback catalog. The bundled fallback always
-includes `kilocode/kilo/auto` (`Kilo Auto`) with `input: ["text", "image"]`,
-`reasoning: true`, `contextWindow: 1000000`, and `maxTokens: 128000`.
-</Tip>
-
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -90,47 +42,48 @@ includes `kilocode/kilo/auto` (`Kilo Auto`) with `input: ["text", "image"]`,
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="Transport and compatibility">
-    Kilo Gateway is documented in source as OpenRouter-compatible, so it stays on
-    the proxy-style OpenAI-compatible path rather than native OpenAI request shaping.
+## Default model
 
-    - Gemini-backed Kilo refs stay on the proxy-Gemini path, so OpenClaw keeps
-      Gemini thought-signature sanitation there without enabling native Gemini
-      replay validation or bootstrap rewrites.
-    - Kilo Gateway uses a Bearer token with your API key under the hood.
+The default model is `kilocode/kilo/auto`, a provider-owned smart-routing
+model managed by Kilo Gateway.
 
-  </Accordion>
+OpenClaw treats `kilocode/kilo/auto` as the stable default ref, but does not
+publish a source-backed task-to-upstream-model mapping for that route.
 
-  <Accordion title="Stream wrapper and reasoning">
-    Kilo's shared stream wrapper adds the provider app header and normalizes
-    proxy reasoning payloads for supported concrete model refs.
+## Available models
 
-    <Warning>
-    `kilocode/kilo/auto` and other proxy-reasoning-unsupported hints skip reasoning
-    injection. If you need reasoning support, use a concrete model ref such as
-    `kilocode/anthropic/claude-sonnet-4`.
-    </Warning>
+OpenClaw dynamically discovers available models from the Kilo Gateway at startup. Use
+`/models kilocode` to see the full list of models available with your account.
 
-  </Accordion>
+Any model available on the gateway can be used with the `kilocode/` prefix:
 
-  <Accordion title="Troubleshooting">
-    - If model discovery fails at startup, OpenClaw falls back to the bundled static catalog containing `kilocode/kilo/auto`.
-    - Confirm your API key is valid and that your Kilo account has the desired models enabled.
-    - When the Gateway runs as a daemon, ensure `KILOCODE_API_KEY` is available to that process (for example in `~/.openclaw/.env` or via `env.shellEnv`).
-  </Accordion>
-</AccordionGroup>
+```
+kilocode/kilo/auto              (default - smart routing)
+kilocode/anthropic/claude-sonnet-4
+kilocode/openai/gpt-5.4
+kilocode/google/gemini-3-pro-preview
+...and many more
+```
 
-## Related
+## Notes
 
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration" icon="gear">
-    Full OpenClaw configuration reference.
-  </Card>
-  <Card title="Kilo Gateway" href="https://app.kilo.ai" icon="arrow-up-right-from-square">
-    Kilo Gateway dashboard, API keys, and account management.
-  </Card>
-</CardGroup>
+- Model refs are `kilocode/<model-id>` (e.g., `kilocode/anthropic/claude-sonnet-4`).
+- Default model: `kilocode/kilo/auto`
+- Base URL: `https://api.kilo.ai/api/gateway/`
+- Bundled fallback catalog always includes `kilocode/kilo/auto` (`Kilo Auto`) with
+  `input: ["text", "image"]`, `reasoning: true`, `contextWindow: 1000000`,
+  and `maxTokens: 128000`
+- At startup, OpenClaw tries `GET https://api.kilo.ai/api/gateway/models` and
+  merges discovered models ahead of the static fallback catalog
+- Exact upstream routing behind `kilocode/kilo/auto` is owned by Kilo Gateway,
+  not hard-coded in OpenClaw
+- Kilo Gateway is documented in source as OpenRouter-compatible, so it stays on
+  the proxy-style OpenAI-compatible path rather than native OpenAI request shaping
+- Gemini-backed Kilo refs stay on the proxy-Gemini path, so OpenClaw keeps
+  Gemini thought-signature sanitation there without enabling native Gemini
+  replay validation or bootstrap rewrites.
+- Kilo's shared stream wrapper adds the provider app header and normalizes
+  proxy reasoning payloads for supported concrete model refs. `kilocode/kilo/auto`
+  and other proxy-reasoning-unsupported hints skip that reasoning injection.
+- For more model/provider options, see [/concepts/model-providers](/concepts/model-providers).
+- Kilo Gateway uses a Bearer token with your API key under the hood.

docs/providers/litellm.md

@@ -10,55 +10,40 @@ read_when:
 
 [LiteLLM](https://litellm.ai) is an open-source LLM gateway that provides a unified API to 100+ model providers. Route OpenClaw through LiteLLM to get centralized cost tracking, logging, and the flexibility to switch backends without changing your OpenClaw config.
 
-<Tip>
-**Why use LiteLLM with OpenClaw?**
+## Why use LiteLLM with OpenClaw?
 
 - **Cost tracking** — See exactly what OpenClaw spends across all models
 - **Model routing** — Switch between Claude, GPT-4, Gemini, Bedrock without config changes
 - **Virtual keys** — Create keys with spend limits for OpenClaw
 - **Logging** — Full request/response logs for debugging
 - **Fallbacks** — Automatic failover if your primary provider is down
-  </Tip>
 
 ## Quick start
 
-<Tabs>
-  <Tab title="Onboarding (recommended)">
-    **Best for:** fastest path to a working LiteLLM setup.
+### Via onboarding
 
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice litellm-api-key
-        ```
-      </Step>
-    </Steps>
+```bash
+openclaw onboard --auth-choice litellm-api-key
+```
 
-  </Tab>
+### Manual setup
 
-  <Tab title="Manual setup">
-    **Best for:** full control over installation and config.
+1. Start LiteLLM Proxy:
 
-    <Steps>
-      <Step title="Start LiteLLM Proxy">
-        ```bash
-        pip install 'litellm[proxy]'
-        litellm --model claude-opus-4-6
-        ```
-      </Step>
-      <Step title="Point OpenClaw to LiteLLM">
-        ```bash
-        export LITELLM_API_KEY="your-litellm-key"
+```bash
+pip install 'litellm[proxy]'
+litellm --model claude-opus-4-6
+```
 
-        openclaw
-        ```
+2. Point OpenClaw to LiteLLM:
 
-        That's it. OpenClaw now routes through LiteLLM.
-      </Step>
-    </Steps>
+```bash
+export LITELLM_API_KEY="your-litellm-key"
 
-  </Tab>
-</Tabs>
+openclaw
+```
+
+That's it. OpenClaw now routes through LiteLLM.
 
 ## Configuration
 
@@ -107,91 +92,68 @@ export LITELLM_API_KEY="sk-litellm-key"
 }
 ```
 
-## Advanced topics
+## Virtual keys
 
-<AccordionGroup>
-  <Accordion title="Virtual keys">
-    Create a dedicated key for OpenClaw with spend limits:
+Create a dedicated key for OpenClaw with spend limits:
 
-    ```bash
-    curl -X POST "http://localhost:4000/key/generate" \
-      -H "Authorization: Bearer $LITELLM_MASTER_KEY" \
-      -H "Content-Type: application/json" \
-      -d '{
-        "key_alias": "openclaw",
-        "max_budget": 50.00,
-        "budget_duration": "monthly"
-      }'
-    ```
+```bash
+curl -X POST "http://localhost:4000/key/generate" \
+  -H "Authorization: Bearer $LITELLM_MASTER_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "key_alias": "openclaw",
+    "max_budget": 50.00,
+    "budget_duration": "monthly"
+  }'
+```
 
-    Use the generated key as `LITELLM_API_KEY`.
+Use the generated key as `LITELLM_API_KEY`.
 
-  </Accordion>
+## Model routing
 
-  <Accordion title="Model routing">
-    LiteLLM can route model requests to different backends. Configure in your LiteLLM `config.yaml`:
+LiteLLM can route model requests to different backends. Configure in your LiteLLM `config.yaml`:
 
-    ```yaml
-    model_list:
-      - model_name: claude-opus-4-6
-        litellm_params:
-          model: claude-opus-4-6
-          api_key: os.environ/ANTHROPIC_API_KEY
+```yaml
+model_list:
+  - model_name: claude-opus-4-6
+    litellm_params:
+      model: claude-opus-4-6
+      api_key: os.environ/ANTHROPIC_API_KEY
 
-      - model_name: gpt-4o
-        litellm_params:
-          model: gpt-4o
-          api_key: os.environ/OPENAI_API_KEY
-    ```
+  - model_name: gpt-4o
+    litellm_params:
+      model: gpt-4o
+      api_key: os.environ/OPENAI_API_KEY
+```
 
-    OpenClaw keeps requesting `claude-opus-4-6` — LiteLLM handles the routing.
+OpenClaw keeps requesting `claude-opus-4-6` — LiteLLM handles the routing.
 
-  </Accordion>
+## Viewing usage
 
-  <Accordion title="Viewing usage">
-    Check LiteLLM's dashboard or API:
+Check LiteLLM's dashboard or API:
 
-    ```bash
-    # Key info
-    curl "http://localhost:4000/key/info" \
-      -H "Authorization: Bearer sk-litellm-key"
+```bash
+# Key info
+curl "http://localhost:4000/key/info" \
+  -H "Authorization: Bearer sk-litellm-key"
 
-    # Spend logs
-    curl "http://localhost:4000/spend/logs" \
-      -H "Authorization: Bearer $LITELLM_MASTER_KEY"
-    ```
+# Spend logs
+curl "http://localhost:4000/spend/logs" \
+  -H "Authorization: Bearer $LITELLM_MASTER_KEY"
+```
 
-  </Accordion>
+## Notes
 
-  <Accordion title="Proxy behavior notes">
-    - LiteLLM runs on `http://localhost:4000` by default
-    - OpenClaw connects through LiteLLM's proxy-style OpenAI-compatible `/v1`
-      endpoint
-    - Native OpenAI-only request shaping does not apply through LiteLLM:
-      no `service_tier`, no Responses `store`, no prompt-cache hints, and no
-      OpenAI reasoning-compat payload shaping
-    - Hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
-      are not injected on custom LiteLLM base URLs
-  </Accordion>
-</AccordionGroup>
+- LiteLLM runs on `http://localhost:4000` by default
+- OpenClaw connects through LiteLLM's proxy-style OpenAI-compatible `/v1`
+  endpoint
+- Native OpenAI-only request shaping does not apply through LiteLLM:
+  no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- Hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on custom LiteLLM base URLs
 
-<Note>
-For general provider configuration and failover behavior, see [Model Providers](/concepts/model-providers).
-</Note>
+## See also
 
-## Related
-
-<CardGroup cols={2}>
-  <Card title="LiteLLM Docs" href="https://docs.litellm.ai" icon="book">
-    Official LiteLLM documentation and API reference.
-  </Card>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration" href="/gateway/configuration" icon="gear">
-    Full config reference.
-  </Card>
-  <Card title="Model selection" href="/concepts/models" icon="brain">
-    How to choose and configure models.
-  </Card>
-</CardGroup>
+- [LiteLLM Docs](https://docs.litellm.ai)
+- [Model Providers](/concepts/model-providers)

docs/providers/minimax.md

@@ -12,212 +12,31 @@ OpenClaw's MiniMax provider defaults to **MiniMax M2.7**.
 
 MiniMax also provides:
 
-- Bundled speech synthesis via T2A v2
-- Bundled image understanding via `MiniMax-VL-01`
-- Bundled music generation via `music-2.5+`
-- Bundled `web_search` through the MiniMax Coding Plan search API
+- bundled speech synthesis via T2A v2
+- bundled image understanding via `MiniMax-VL-01`
+- bundled music generation via `music-2.5+`
+- bundled `web_search` through the MiniMax Coding Plan search API
 
 Provider split:
 
-| Provider ID      | Auth    | Capabilities                                                    |
-| ---------------- | ------- | --------------------------------------------------------------- |
-| `minimax`        | API key | Text, image generation, image understanding, speech, web search |
-| `minimax-portal` | OAuth   | Text, image generation, image understanding                     |
+- `minimax`: API-key text provider, plus bundled image generation, image understanding, speech, and web search
+- `minimax-portal`: OAuth text provider, plus bundled image generation and image understanding
 
 ## Model lineup
 
-| Model                    | Type             | Description                              |
-| ------------------------ | ---------------- | ---------------------------------------- |
-| `MiniMax-M2.7`           | Chat (reasoning) | Default hosted reasoning model           |
-| `MiniMax-M2.7-highspeed` | Chat (reasoning) | Faster M2.7 reasoning tier               |
-| `MiniMax-VL-01`          | Vision           | Image understanding model                |
-| `image-01`               | Image generation | Text-to-image and image-to-image editing |
-| `music-2.5+`             | Music generation | Default music model                      |
-| `music-2.5`              | Music generation | Previous music generation tier           |
-| `music-2.0`              | Music generation | Legacy music generation tier             |
-| `MiniMax-Hailuo-2.3`     | Video generation | Text-to-video and image reference flows  |
+- `MiniMax-M2.7`: default hosted reasoning model.
+- `MiniMax-M2.7-highspeed`: faster M2.7 reasoning tier.
+- `image-01`: image generation model (generate and image-to-image editing).
 
-## Getting started
-
-Choose your preferred auth method and follow the setup steps.
-
-<Tabs>
-  <Tab title="OAuth (Coding Plan)">
-    **Best for:** quick setup with MiniMax Coding Plan via OAuth, no API key required.
-
-    <Tabs>
-      <Tab title="International">
-        <Steps>
-          <Step title="Run onboarding">
-            ```bash
-            openclaw onboard --auth-choice minimax-global-oauth
-            ```
-
-            This authenticates against `api.minimax.io`.
-          </Step>
-          <Step title="Verify the model is available">
-            ```bash
-            openclaw models list --provider minimax-portal
-            ```
-          </Step>
-        </Steps>
-      </Tab>
-      <Tab title="China">
-        <Steps>
-          <Step title="Run onboarding">
-            ```bash
-            openclaw onboard --auth-choice minimax-cn-oauth
-            ```
-
-            This authenticates against `api.minimaxi.com`.
-          </Step>
-          <Step title="Verify the model is available">
-            ```bash
-            openclaw models list --provider minimax-portal
-            ```
-          </Step>
-        </Steps>
-      </Tab>
-    </Tabs>
-
-    <Note>
-    OAuth setups use the `minimax-portal` provider id. Model refs follow the form `minimax-portal/MiniMax-M2.7`.
-    </Note>
-
-    <Tip>
-    Referral link for MiniMax Coding Plan (10% off): [MiniMax Coding Plan](https://platform.minimax.io/subscribe/coding-plan?code=DbXJTRClnb&source=link)
-    </Tip>
-
-  </Tab>
-
-  <Tab title="API key">
-    **Best for:** hosted MiniMax with Anthropic-compatible API.
-
-    <Tabs>
-      <Tab title="International">
-        <Steps>
-          <Step title="Run onboarding">
-            ```bash
-            openclaw onboard --auth-choice minimax-global-api
-            ```
-
-            This configures `api.minimax.io` as the base URL.
-          </Step>
-          <Step title="Verify the model is available">
-            ```bash
-            openclaw models list --provider minimax
-            ```
-          </Step>
-        </Steps>
-      </Tab>
-      <Tab title="China">
-        <Steps>
-          <Step title="Run onboarding">
-            ```bash
-            openclaw onboard --auth-choice minimax-cn-api
-            ```
-
-            This configures `api.minimaxi.com` as the base URL.
-          </Step>
-          <Step title="Verify the model is available">
-            ```bash
-            openclaw models list --provider minimax
-            ```
-          </Step>
-        </Steps>
-      </Tab>
-    </Tabs>
-
-    ### Config example
-
-    ```json5
-    {
-      env: { MINIMAX_API_KEY: "sk-..." },
-      agents: { defaults: { model: { primary: "minimax/MiniMax-M2.7" } } },
-      models: {
-        mode: "merge",
-        providers: {
-          minimax: {
-            baseUrl: "https://api.minimax.io/anthropic",
-            apiKey: "${MINIMAX_API_KEY}",
-            api: "anthropic-messages",
-            models: [
-              {
-                id: "MiniMax-M2.7",
-                name: "MiniMax M2.7",
-                reasoning: true,
-                input: ["text", "image"],
-                cost: { input: 0.3, output: 1.2, cacheRead: 0.06, cacheWrite: 0.375 },
-                contextWindow: 204800,
-                maxTokens: 131072,
-              },
-              {
-                id: "MiniMax-M2.7-highspeed",
-                name: "MiniMax M2.7 Highspeed",
-                reasoning: true,
-                input: ["text", "image"],
-                cost: { input: 0.6, output: 2.4, cacheRead: 0.06, cacheWrite: 0.375 },
-                contextWindow: 204800,
-                maxTokens: 131072,
-              },
-            ],
-          },
-        },
-      },
-    }
-    ```
-
-    <Warning>
-    On the Anthropic-compatible streaming path, OpenClaw disables MiniMax thinking by default unless you explicitly set `thinking` yourself. MiniMax's streaming endpoint emits `reasoning_content` in OpenAI-style delta chunks instead of native Anthropic thinking blocks, which can leak internal reasoning into visible output if left enabled implicitly.
-    </Warning>
-
-    <Note>
-    API-key setups use the `minimax` provider id. Model refs follow the form `minimax/MiniMax-M2.7`.
-    </Note>
-
-  </Tab>
-</Tabs>
-
-## Configure via `openclaw configure`
-
-Use the interactive config wizard to set MiniMax without editing JSON:
-
-<Steps>
-  <Step title="Launch the wizard">
-    ```bash
-    openclaw configure
-    ```
-  </Step>
-  <Step title="Select Model/auth">
-    Choose **Model/auth** from the menu.
-  </Step>
-  <Step title="Choose a MiniMax auth option">
-    Pick one of the available MiniMax options:
-
-    | Auth choice | Description |
-    | --- | --- |
-    | `minimax-global-oauth` | International OAuth (Coding Plan) |
-    | `minimax-cn-oauth` | China OAuth (Coding Plan) |
-    | `minimax-global-api` | International API key |
-    | `minimax-cn-api` | China API key |
-
-  </Step>
-  <Step title="Pick your default model">
-    Select your default model when prompted.
-  </Step>
-</Steps>
-
-## Capabilities
-
-### Image generation
+## Image generation
 
 The MiniMax plugin registers the `image-01` model for the `image_generate` tool. It supports:
 
-- **Text-to-image generation** with aspect ratio control
-- **Image-to-image editing** (subject reference) with aspect ratio control
-- Up to **9 output images** per request
-- Up to **1 reference image** per edit request
-- Supported aspect ratios: `1:1`, `16:9`, `4:3`, `3:2`, `2:3`, `3:4`, `9:16`, `21:9`
+- **Text-to-image generation** with aspect ratio control.
+- **Image-to-image editing** (subject reference) with aspect ratio control.
+- Up to **9 output images** per request.
+- Up to **1 reference image** per edit request.
+- Supported aspect ratios: `1:1`, `16:9`, `4:3`, `3:2`, `2:3`, `3:4`, `9:16`, `21:9`.
 
 To use MiniMax for image generation, set it as the image generation provider:
 
@@ -245,11 +64,10 @@ The built-in bundled MiniMax text catalog itself stays text-only metadata until
 that explicit provider config exists. Image understanding is exposed separately
 through the plugin-owned `MiniMax-VL-01` media provider.
 
-<Note>
-See [Image Generation](/tools/image-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Image Generation](/tools/image-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-### Music generation
+## Music generation
 
 The bundled `minimax` plugin also registers music generation through the shared
 `music_generate` tool.
@@ -274,11 +92,10 @@ To use MiniMax as the default music provider:
 }
 ```
 
-<Note>
-See [Music Generation](/tools/music-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Music Generation](/tools/music-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-### Video generation
+## Video generation
 
 The bundled `minimax` plugin also registers video generation through the shared
 `video_generate` tool.
@@ -301,24 +118,21 @@ To use MiniMax as the default video provider:
 }
 ```
 
-<Note>
-See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-### Image understanding
+## Image understanding
 
 The MiniMax plugin registers image understanding separately from the text
 catalog:
 
-| Provider ID      | Default image model |
-| ---------------- | ------------------- |
-| `minimax`        | `MiniMax-VL-01`     |
-| `minimax-portal` | `MiniMax-VL-01`     |
+- `minimax`: default image model `MiniMax-VL-01`
+- `minimax-portal`: default image model `MiniMax-VL-01`
 
 That is why automatic media routing can use MiniMax image understanding even
 when the bundled text-provider catalog still shows text-only M2.7 chat refs.
 
-### Web search
+## Web search
 
 The MiniMax plugin also registers `web_search` through the MiniMax Coding Plan
 search API.
@@ -332,66 +146,136 @@ search API.
 - Search stays on provider id `minimax`; OAuth CN/global setup can still steer region indirectly through `models.providers.minimax-portal.baseUrl`
 
 Config lives under `plugins.entries.minimax.config.webSearch.*`.
+See [MiniMax Search](/tools/minimax-search).
 
-<Note>
-See [MiniMax Search](/tools/minimax-search) for full web search configuration and usage.
-</Note>
+## Choose a setup
 
-## Advanced configuration
+### MiniMax OAuth (Coding Plan) - recommended
 
-<AccordionGroup>
-  <Accordion title="Configuration options">
-    | Option | Description |
-    | --- | --- |
-    | `models.providers.minimax.baseUrl` | Prefer `https://api.minimax.io/anthropic` (Anthropic-compatible); `https://api.minimax.io/v1` is optional for OpenAI-compatible payloads |
-    | `models.providers.minimax.api` | Prefer `anthropic-messages`; `openai-completions` is optional for OpenAI-compatible payloads |
-    | `models.providers.minimax.apiKey` | MiniMax API key (`MINIMAX_API_KEY`) |
-    | `models.providers.minimax.models` | Define `id`, `name`, `reasoning`, `contextWindow`, `maxTokens`, `cost` |
-    | `agents.defaults.models` | Alias models you want in the allowlist |
-    | `models.mode` | Keep `merge` if you want to add MiniMax alongside built-ins |
-  </Accordion>
+**Best for:** quick setup with MiniMax Coding Plan via OAuth, no API key required.
 
-  <Accordion title="Thinking defaults">
-    On `api: "anthropic-messages"`, OpenClaw injects `thinking: { type: "disabled" }` unless thinking is already explicitly set in params/config.
+Authenticate with the explicit regional OAuth choice:
 
-    This prevents MiniMax's streaming endpoint from emitting `reasoning_content` in OpenAI-style delta chunks, which would leak internal reasoning into visible output.
+```bash
+openclaw onboard --auth-choice minimax-global-oauth
+# or
+openclaw onboard --auth-choice minimax-cn-oauth
+```
 
-  </Accordion>
+Choice mapping:
 
-  <Accordion title="Fast mode">
-    `/fast on` or `params.fastMode: true` rewrites `MiniMax-M2.7` to `MiniMax-M2.7-highspeed` on the Anthropic-compatible stream path.
-  </Accordion>
+- `minimax-global-oauth`: International users (`api.minimax.io`)
+- `minimax-cn-oauth`: Users in China (`api.minimaxi.com`)
 
-  <Accordion title="Fallback example">
-    **Best for:** keep your strongest latest-generation model as primary, fail over to MiniMax M2.7. Example below uses Opus as a concrete primary; swap to your preferred latest-gen primary model.
+See the MiniMax plugin package README in the OpenClaw repo for details.
 
-    ```json5
-    {
-      env: { MINIMAX_API_KEY: "sk-..." },
-      agents: {
-        defaults: {
-          models: {
-            "anthropic/claude-opus-4-6": { alias: "primary" },
-            "minimax/MiniMax-M2.7": { alias: "minimax" },
+### MiniMax M2.7 (API key)
+
+**Best for:** hosted MiniMax with Anthropic-compatible API.
+
+Configure via CLI:
+
+- Interactive onboarding:
+
+```bash
+openclaw onboard --auth-choice minimax-global-api
+# or
+openclaw onboard --auth-choice minimax-cn-api
+```
+
+- `minimax-global-api`: International users (`api.minimax.io`)
+- `minimax-cn-api`: Users in China (`api.minimaxi.com`)
+
+```json5
+{
+  env: { MINIMAX_API_KEY: "sk-..." },
+  agents: { defaults: { model: { primary: "minimax/MiniMax-M2.7" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      minimax: {
+        baseUrl: "https://api.minimax.io/anthropic",
+        apiKey: "${MINIMAX_API_KEY}",
+        api: "anthropic-messages",
+        models: [
+          {
+            id: "MiniMax-M2.7",
+            name: "MiniMax M2.7",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0.3, output: 1.2, cacheRead: 0.06, cacheWrite: 0.375 },
+            contextWindow: 204800,
+            maxTokens: 131072,
           },
-          model: {
-            primary: "anthropic/claude-opus-4-6",
-            fallbacks: ["minimax/MiniMax-M2.7"],
+          {
+            id: "MiniMax-M2.7-highspeed",
+            name: "MiniMax M2.7 Highspeed",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0.6, output: 2.4, cacheRead: 0.06, cacheWrite: 0.375 },
+            contextWindow: 204800,
+            maxTokens: 131072,
           },
-        },
+        ],
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-  </Accordion>
+On the Anthropic-compatible streaming path, OpenClaw now disables MiniMax
+thinking by default unless you explicitly set `thinking` yourself. MiniMax's
+streaming endpoint emits `reasoning_content` in OpenAI-style delta chunks
+instead of native Anthropic thinking blocks, which can leak internal reasoning
+into visible output if left enabled implicitly.
 
-  <Accordion title="Coding Plan usage details">
-    - Coding Plan usage API: `https://api.minimaxi.com/v1/api/openplatform/coding_plan/remains` (requires a coding plan key).
-    - OpenClaw normalizes MiniMax coding-plan usage to the same `% left` display used by other providers. MiniMax's raw `usage_percent` / `usagePercent` fields are remaining quota, not consumed quota, so OpenClaw inverts them. Count-based fields win when present.
-    - When the API returns `model_remains`, OpenClaw prefers the chat-model entry, derives the window label from `start_time` / `end_time` when needed, and includes the selected model name in the plan label so coding-plan windows are easier to distinguish.
-    - Usage snapshots treat `minimax`, `minimax-cn`, and `minimax-portal` as the same MiniMax quota surface, and prefer stored MiniMax OAuth before falling back to Coding Plan key env vars.
-  </Accordion>
-</AccordionGroup>
+### MiniMax M2.7 as fallback (example)
+
+**Best for:** keep your strongest latest-generation model as primary, fail over to MiniMax M2.7.
+Example below uses Opus as a concrete primary; swap to your preferred latest-gen primary model.
+
+```json5
+{
+  env: { MINIMAX_API_KEY: "sk-..." },
+  agents: {
+    defaults: {
+      models: {
+        "anthropic/claude-opus-4-6": { alias: "primary" },
+        "minimax/MiniMax-M2.7": { alias: "minimax" },
+      },
+      model: {
+        primary: "anthropic/claude-opus-4-6",
+        fallbacks: ["minimax/MiniMax-M2.7"],
+      },
+    },
+  },
+}
+```
+
+## Configure via `openclaw configure`
+
+Use the interactive config wizard to set MiniMax without editing JSON:
+
+1. Run `openclaw configure`.
+2. Select **Model/auth**.
+3. Choose a **MiniMax** auth option.
+4. Pick your default model when prompted.
+
+Current MiniMax auth choices in the wizard/CLI:
+
+- `minimax-global-oauth`
+- `minimax-cn-oauth`
+- `minimax-global-api`
+- `minimax-cn-api`
+
+## Configuration options
+
+- `models.providers.minimax.baseUrl`: prefer `https://api.minimax.io/anthropic` (Anthropic-compatible); `https://api.minimax.io/v1` is optional for OpenAI-compatible payloads.
+- `models.providers.minimax.api`: prefer `anthropic-messages`; `openai-completions` is optional for OpenAI-compatible payloads.
+- `models.providers.minimax.apiKey`: MiniMax API key (`MINIMAX_API_KEY`).
+- `models.providers.minimax.models`: define `id`, `name`, `reasoning`, `contextWindow`, `maxTokens`, `cost`.
+- `agents.defaults.models`: alias models you want in the allowlist.
+- `models.mode`: keep `merge` if you want to add MiniMax alongside built-ins.
 
 ## Notes
 
@@ -400,67 +284,56 @@ See [MiniMax Search](/tools/minimax-search) for full web search configuration an
   - OAuth setup: `minimax-portal/<model>`
 - Default chat model: `MiniMax-M2.7`
 - Alternate chat model: `MiniMax-M2.7-highspeed`
-- Onboarding and direct API-key setup write explicit model definitions with `input: ["text", "image"]` for both M2.7 variants
-- The bundled provider catalog currently exposes the chat refs as text-only metadata until explicit MiniMax provider config exists
-- Update pricing values in `models.json` if you need exact cost tracking
-- Use `openclaw models list` to confirm the current provider id, then switch with `openclaw models set minimax/MiniMax-M2.7` or `openclaw models set minimax-portal/MiniMax-M2.7`
-
-<Tip>
-Referral link for MiniMax Coding Plan (10% off): [MiniMax Coding Plan](https://platform.minimax.io/subscribe/coding-plan?code=DbXJTRClnb&source=link)
-</Tip>
-
-<Note>
-See [Model providers](/concepts/model-providers) for provider rules.
-</Note>
+- On `api: "anthropic-messages"`, OpenClaw injects
+  `thinking: { type: "disabled" }` unless thinking is already explicitly set in
+  params/config.
+- `/fast on` or `params.fastMode: true` rewrites `MiniMax-M2.7` to
+  `MiniMax-M2.7-highspeed` on the Anthropic-compatible stream path.
+- Onboarding and direct API-key setup write explicit model definitions with
+  `input: ["text", "image"]` for both M2.7 variants
+- The bundled provider catalog currently exposes the chat refs as text-only
+  metadata until explicit MiniMax provider config exists
+- Coding Plan usage API: `https://api.minimaxi.com/v1/api/openplatform/coding_plan/remains` (requires a coding plan key).
+- OpenClaw normalizes MiniMax coding-plan usage to the same `% left` display
+  used by other providers. MiniMax's raw `usage_percent` / `usagePercent`
+  fields are remaining quota, not consumed quota, so OpenClaw inverts them.
+  Count-based fields win when present. When the API returns `model_remains`,
+  OpenClaw prefers the chat-model entry, derives the window label from
+  `start_time` / `end_time` when needed, and includes the selected model name
+  in the plan label so coding-plan windows are easier to distinguish.
+- Usage snapshots treat `minimax`, `minimax-cn`, and `minimax-portal` as the
+  same MiniMax quota surface, and prefer stored MiniMax OAuth before falling
+  back to Coding Plan key env vars.
+- Update pricing values in `models.json` if you need exact cost tracking.
+- Referral link for MiniMax Coding Plan (10% off): [https://platform.minimax.io/subscribe/coding-plan?code=DbXJTRClnb&source=link](https://platform.minimax.io/subscribe/coding-plan?code=DbXJTRClnb&source=link)
+- See [/concepts/model-providers](/concepts/model-providers) for provider rules.
+- Use `openclaw models list` to confirm the current provider id, then switch with
+  `openclaw models set minimax/MiniMax-M2.7` or
+  `openclaw models set minimax-portal/MiniMax-M2.7`.
 
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title='"Unknown model: minimax/MiniMax-M2.7"'>
-    This usually means the **MiniMax provider is not configured** (no matching provider entry and no MiniMax auth profile/env key found). A fix for this detection is in **2026.1.12**. Fix by:
+### "Unknown model: minimax/MiniMax-M2.7"
 
-    - Upgrading to **2026.1.12** (or run from source `main`), then restarting the gateway.
-    - Running `openclaw configure` and selecting a **MiniMax** auth option, or
-    - Adding the matching `models.providers.minimax` or `models.providers.minimax-portal` block manually, or
-    - Setting `MINIMAX_API_KEY`, `MINIMAX_OAUTH_TOKEN`, or a MiniMax auth profile so the matching provider can be injected.
+This usually means the **MiniMax provider isn’t configured** (no matching
+provider entry and no MiniMax auth profile/env key found). A fix for this
+detection is in **2026.1.12**. Fix by:
 
-    Make sure the model id is **case-sensitive**:
+- Upgrading to **2026.1.12** (or run from source `main`), then restarting the gateway.
+- Running `openclaw configure` and selecting a **MiniMax** auth option, or
+- Adding the matching `models.providers.minimax` or
+  `models.providers.minimax-portal` block manually, or
+- Setting `MINIMAX_API_KEY`, `MINIMAX_OAUTH_TOKEN`, or a MiniMax auth profile
+  so the matching provider can be injected.
 
-    - API-key path: `minimax/MiniMax-M2.7` or `minimax/MiniMax-M2.7-highspeed`
-    - OAuth path: `minimax-portal/MiniMax-M2.7` or `minimax-portal/MiniMax-M2.7-highspeed`
+Make sure the model id is **case‑sensitive**:
 
-    Then recheck with:
+- API-key path: `minimax/MiniMax-M2.7` or `minimax/MiniMax-M2.7-highspeed`
+- OAuth path: `minimax-portal/MiniMax-M2.7` or
+  `minimax-portal/MiniMax-M2.7-highspeed`
 
-    ```bash
-    openclaw models list
-    ```
+Then recheck with:
 
-  </Accordion>
-</AccordionGroup>
-
-<Note>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Note>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Image generation" href="/tools/image-generation" icon="image">
-    Shared image tool parameters and provider selection.
-  </Card>
-  <Card title="Music generation" href="/tools/music-generation" icon="music">
-    Shared music tool parameters and provider selection.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="MiniMax Search" href="/tools/minimax-search" icon="magnifying-glass">
-    Web search configuration via MiniMax Coding Plan.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+```bash
+openclaw models list
+```

docs/providers/mistral.md

@@ -12,42 +12,22 @@ OpenClaw supports Mistral for both text/image model routing (`mistral/...`) and
 audio transcription via Voxtral in media understanding.
 Mistral can also be used for memory embeddings (`memorySearch.provider = "mistral"`).
 
-- Provider: `mistral`
-- Auth: `MISTRAL_API_KEY`
-- API: Mistral Chat Completions (`https://api.mistral.ai/v1`)
+## CLI setup
 
-## Getting started
+```bash
+openclaw onboard --auth-choice mistral-api-key
+# or non-interactive
+openclaw onboard --mistral-api-key "$MISTRAL_API_KEY"
+```
 
-<Steps>
-  <Step title="Get your API key">
-    Create an API key in the [Mistral Console](https://console.mistral.ai/).
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice mistral-api-key
-    ```
+## Config snippet (LLM provider)
 
-    Or pass the key directly:
-
-    ```bash
-    openclaw onboard --mistral-api-key "$MISTRAL_API_KEY"
-    ```
-
-  </Step>
-  <Step title="Set a default model">
-    ```json5
-    {
-      env: { MISTRAL_API_KEY: "sk-..." },
-      agents: { defaults: { model: { primary: "mistral/mistral-large-latest" } } },
-    }
-    ```
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider mistral
-    ```
-  </Step>
-</Steps>
+```json5
+{
+  env: { MISTRAL_API_KEY: "sk-..." },
+  agents: { defaults: { model: { primary: "mistral/mistral-large-latest" } } },
+}
+```
 
 ## Built-in LLM catalog
 
@@ -63,9 +43,7 @@ OpenClaw currently ships this bundled Mistral catalog:
 | `mistral/devstral-medium-latest` | text        | 262,144 | 32,768     | Devstral 2                                                       |
 | `mistral/magistral-small`        | text        | 128,000 | 40,000     | Reasoning-enabled                                                |
 
-## Audio transcription (Voxtral)
-
-Use Voxtral for audio transcription through the media understanding pipeline.
+## Config snippet (audio transcription with Voxtral)
 
 ```json5
 {
@@ -80,55 +58,22 @@ Use Voxtral for audio transcription through the media understanding pipeline.
 }
 ```
 
-<Tip>
-The media transcription path uses `/v1/audio/transcriptions`. The default audio model for Mistral is `voxtral-mini-latest`.
-</Tip>
+## Adjustable reasoning (`mistral-small-latest`)
 
-## Advanced configuration
+`mistral/mistral-small-latest` maps to Mistral Small 4 and supports [adjustable reasoning](https://docs.mistral.ai/capabilities/reasoning/adjustable) on the Chat Completions API via `reasoning_effort` (`none` minimizes extra thinking in the output; `high` surfaces full thinking traces before the final answer).
 
-<AccordionGroup>
-  <Accordion title="Adjustable reasoning (mistral-small-latest)">
-    `mistral/mistral-small-latest` maps to Mistral Small 4 and supports [adjustable reasoning](https://docs.mistral.ai/capabilities/reasoning/adjustable) on the Chat Completions API via `reasoning_effort` (`none` minimizes extra thinking in the output; `high` surfaces full thinking traces before the final answer).
+OpenClaw maps the session **thinking** level to Mistral’s API:
 
-    OpenClaw maps the session **thinking** level to Mistral's API:
+- **off** / **minimal** → `none`
+- **low** / **medium** / **high** / **xhigh** / **adaptive** → `high`
 
-    | OpenClaw thinking level                          | Mistral `reasoning_effort` |
-    | ------------------------------------------------ | -------------------------- |
-    | **off** / **minimal**                            | `none`                     |
-    | **low** / **medium** / **high** / **xhigh** / **adaptive** | `high`             |
+Other bundled Mistral catalog models do not use this parameter; keep using `magistral-*` models when you want Mistral’s native reasoning-first behavior.
 
-    <Note>
-    Other bundled Mistral catalog models do not use this parameter. Keep using `magistral-*` models when you want Mistral's native reasoning-first behavior.
-    </Note>
+## Notes
 
-  </Accordion>
-
-  <Accordion title="Memory embeddings">
-    Mistral can serve memory embeddings via `/v1/embeddings` (default model: `mistral-embed`).
-
-    ```json5
-    {
-      memorySearch: { provider: "mistral" },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Auth and base URL">
-    - Mistral auth uses `MISTRAL_API_KEY`.
-    - Provider base URL defaults to `https://api.mistral.ai/v1`.
-    - Onboarding default model is `mistral/mistral-large-latest`.
-    - Z.AI uses Bearer auth with your API key.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Media understanding" href="/tools/media-understanding" icon="microphone">
-    Audio transcription setup and provider selection.
-  </Card>
-</CardGroup>
+- Mistral auth uses `MISTRAL_API_KEY`.
+- Provider base URL defaults to `https://api.mistral.ai/v1`.
+- Onboarding default model is `mistral/mistral-large-latest`.
+- Media-understanding default audio model for Mistral is `voxtral-mini-latest`.
+- Media transcription path uses `/v1/audio/transcriptions`.
+- Memory embeddings path uses `/v1/embeddings` (default model: `mistral-embed`).

docs/providers/moonshot.md

@@ -13,215 +13,138 @@ Moonshot provides the Kimi API with OpenAI-compatible endpoints. Configure the
 provider and set the default model to `moonshot/kimi-k2.5`, or use
 Kimi Coding with `kimi/kimi-code`.
 
-<Warning>
-Moonshot and Kimi Coding are **separate providers**. Keys are not interchangeable, endpoints differ, and model refs differ (`moonshot/...` vs `kimi/...`).
-</Warning>
-
-## Built-in model catalog
+Current Kimi K2 model IDs:
 
 [//]: # "moonshot-kimi-k2-ids:start"
 
-| Model ref                         | Name                   | Reasoning | Input       | Context | Max output |
-| --------------------------------- | ---------------------- | --------- | ----------- | ------- | ---------- |
-| `moonshot/kimi-k2.5`              | Kimi K2.5              | No        | text, image | 262,144 | 262,144    |
-| `moonshot/kimi-k2-thinking`       | Kimi K2 Thinking       | Yes       | text        | 262,144 | 262,144    |
-| `moonshot/kimi-k2-thinking-turbo` | Kimi K2 Thinking Turbo | Yes       | text        | 262,144 | 262,144    |
-| `moonshot/kimi-k2-turbo`          | Kimi K2 Turbo          | No        | text        | 256,000 | 16,384     |
+- `kimi-k2.5`
+- `kimi-k2-thinking`
+- `kimi-k2-thinking-turbo`
+- `kimi-k2-turbo`
 
 [//]: # "moonshot-kimi-k2-ids:end"
 
-## Getting started
+```bash
+openclaw onboard --auth-choice moonshot-api-key
+# or
+openclaw onboard --auth-choice moonshot-api-key-cn
+```
 
-Choose your provider and follow the setup steps.
+Kimi Coding:
 
-<Tabs>
-  <Tab title="Moonshot API">
-    **Best for:** Kimi K2 models via the Moonshot Open Platform.
+```bash
+openclaw onboard --auth-choice kimi-code-api-key
+```
 
-    <Steps>
-      <Step title="Choose your endpoint region">
-        | Auth choice            | Endpoint                       | Region        |
-        | ---------------------- | ------------------------------ | ------------- |
-        | `moonshot-api-key`     | `https://api.moonshot.ai/v1`   | International |
-        | `moonshot-api-key-cn`  | `https://api.moonshot.cn/v1`   | China         |
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice moonshot-api-key
-        ```
+Note: Moonshot and Kimi Coding are separate providers. Keys are not interchangeable, endpoints differ, and model refs differ (Moonshot uses `moonshot/...`, Kimi Coding uses `kimi/...`).
 
-        Or for the China endpoint:
+Kimi web search uses the Moonshot plugin too:
 
-        ```bash
-        openclaw onboard --auth-choice moonshot-api-key-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "moonshot/kimi-k2.5" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider moonshot
-        ```
-      </Step>
-    </Steps>
+```bash
+openclaw configure --section web
+```
 
-    ### Config example
+Choose **Kimi** in the web-search section to store
+`plugins.entries.moonshot.config.webSearch.*`.
 
-    ```json5
-    {
-      env: { MOONSHOT_API_KEY: "sk-..." },
-      agents: {
-        defaults: {
-          model: { primary: "moonshot/kimi-k2.5" },
-          models: {
-            // moonshot-kimi-k2-aliases:start
-            "moonshot/kimi-k2.5": { alias: "Kimi K2.5" },
-            "moonshot/kimi-k2-thinking": { alias: "Kimi K2 Thinking" },
-            "moonshot/kimi-k2-thinking-turbo": { alias: "Kimi K2 Thinking Turbo" },
-            "moonshot/kimi-k2-turbo": { alias: "Kimi K2 Turbo" },
-            // moonshot-kimi-k2-aliases:end
-          },
-        },
-      },
+## Config snippet (Moonshot API)
+
+```json5
+{
+  env: { MOONSHOT_API_KEY: "sk-..." },
+  agents: {
+    defaults: {
+      model: { primary: "moonshot/kimi-k2.5" },
       models: {
-        mode: "merge",
-        providers: {
-          moonshot: {
-            baseUrl: "https://api.moonshot.ai/v1",
-            apiKey: "${MOONSHOT_API_KEY}",
-            api: "openai-completions",
-            models: [
-              // moonshot-kimi-k2-models:start
-              {
-                id: "kimi-k2.5",
-                name: "Kimi K2.5",
-                reasoning: false,
-                input: ["text", "image"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 262144,
-              },
-              {
-                id: "kimi-k2-thinking",
-                name: "Kimi K2 Thinking",
-                reasoning: true,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 262144,
-              },
-              {
-                id: "kimi-k2-thinking-turbo",
-                name: "Kimi K2 Thinking Turbo",
-                reasoning: true,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 262144,
-              },
-              {
-                id: "kimi-k2-turbo",
-                name: "Kimi K2 Turbo",
-                reasoning: false,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 256000,
-                maxTokens: 16384,
-              },
-              // moonshot-kimi-k2-models:end
-            ],
-          },
-        },
+        // moonshot-kimi-k2-aliases:start
+        "moonshot/kimi-k2.5": { alias: "Kimi K2.5" },
+        "moonshot/kimi-k2-thinking": { alias: "Kimi K2 Thinking" },
+        "moonshot/kimi-k2-thinking-turbo": { alias: "Kimi K2 Thinking Turbo" },
+        "moonshot/kimi-k2-turbo": { alias: "Kimi K2 Turbo" },
+        // moonshot-kimi-k2-aliases:end
       },
-    }
-    ```
-
-  </Tab>
-
-  <Tab title="Kimi Coding">
-    **Best for:** code-focused tasks via the Kimi Coding endpoint.
-
-    <Note>
-    Kimi Coding uses a different API key and provider prefix (`kimi/...`) than Moonshot (`moonshot/...`). Legacy model ref `kimi/k2p5` remains accepted as a compatibility id.
-    </Note>
-
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice kimi-code-api-key
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "kimi/kimi-code" },
-            },
+    },
+  },
+  models: {
+    mode: "merge",
+    providers: {
+      moonshot: {
+        baseUrl: "https://api.moonshot.ai/v1",
+        apiKey: "${MOONSHOT_API_KEY}",
+        api: "openai-completions",
+        models: [
+          // moonshot-kimi-k2-models:start
+          {
+            id: "kimi-k2.5",
+            name: "Kimi K2.5",
+            reasoning: false,
+            input: ["text", "image"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 262144,
           },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider kimi
-        ```
-      </Step>
-    </Steps>
-
-    ### Config example
-
-    ```json5
-    {
-      env: { KIMI_API_KEY: "sk-..." },
-      agents: {
-        defaults: {
-          model: { primary: "kimi/kimi-code" },
-          models: {
-            "kimi/kimi-code": { alias: "Kimi" },
+          {
+            id: "kimi-k2-thinking",
+            name: "Kimi K2 Thinking",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 262144,
           },
-        },
+          {
+            id: "kimi-k2-thinking-turbo",
+            name: "Kimi K2 Thinking Turbo",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 262144,
+          },
+          {
+            id: "kimi-k2-turbo",
+            name: "Kimi K2 Turbo",
+            reasoning: false,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 256000,
+            maxTokens: 16384,
+          },
+          // moonshot-kimi-k2-models:end
+        ],
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-  </Tab>
-</Tabs>
+## Kimi Coding
+
+```json5
+{
+  env: { KIMI_API_KEY: "sk-..." },
+  agents: {
+    defaults: {
+      model: { primary: "kimi/kimi-code" },
+      models: {
+        "kimi/kimi-code": { alias: "Kimi" },
+      },
+    },
+  },
+}
+```
 
 ## Kimi web search
 
 OpenClaw also ships **Kimi** as a `web_search` provider, backed by Moonshot web
 search.
 
-<Steps>
-  <Step title="Run interactive web search setup">
-    ```bash
-    openclaw configure --section web
-    ```
+Interactive setup can prompt for:
 
-    Choose **Kimi** in the web-search section to store
-    `plugins.entries.moonshot.config.webSearch.*`.
-
-  </Step>
-  <Step title="Configure the web search region and model">
-    Interactive setup prompts for:
-
-    | Setting             | Options                                                              |
-    | ------------------- | -------------------------------------------------------------------- |
-    | API region          | `https://api.moonshot.ai/v1` (international) or `https://api.moonshot.cn/v1` (China) |
-    | Web search model    | Defaults to `kimi-k2.5`                                             |
-
-  </Step>
-</Steps>
+- the Moonshot API region:
+  - `https://api.moonshot.ai/v1`
+  - `https://api.moonshot.cn/v1`
+- the default Kimi web-search model (defaults to `kimi-k2.5`)
 
 Config lives under `plugins.entries.moonshot.config.webSearch`:
 
@@ -250,82 +173,52 @@ Config lives under `plugins.entries.moonshot.config.webSearch`:
 }
 ```
 
-## Advanced
+## Notes
 
-<AccordionGroup>
-  <Accordion title="Native thinking mode">
-    Moonshot Kimi supports binary native thinking:
+- Moonshot model refs use `moonshot/<modelId>`. Kimi Coding model refs use `kimi/<modelId>`.
+- Current Kimi Coding default model ref is `kimi/kimi-code`. Legacy `kimi/k2p5` remains accepted as a compatibility model id.
+- Kimi web search uses `KIMI_API_KEY` or `MOONSHOT_API_KEY`, and defaults to `https://api.moonshot.ai/v1` with model `kimi-k2.5`.
+- Native Moonshot endpoints (`https://api.moonshot.ai/v1` and
+  `https://api.moonshot.cn/v1`) advertise streaming usage compatibility on the
+  shared `openai-completions` transport. OpenClaw now keys that off endpoint
+  capabilities, so compatible custom provider ids targeting the same native
+  Moonshot hosts inherit the same streaming-usage behavior.
+- Override pricing and context metadata in `models.providers` if needed.
+- If Moonshot publishes different context limits for a model, adjust
+  `contextWindow` accordingly.
+- Use `https://api.moonshot.ai/v1` for the international endpoint, and `https://api.moonshot.cn/v1` for the China endpoint.
+- Onboarding choices:
+  - `moonshot-api-key` for `https://api.moonshot.ai/v1`
+  - `moonshot-api-key-cn` for `https://api.moonshot.cn/v1`
 
-    - `thinking: { type: "enabled" }`
-    - `thinking: { type: "disabled" }`
+## Native thinking mode (Moonshot)
 
-    Configure it per model via `agents.defaults.models.<provider/model>.params`:
+Moonshot Kimi supports binary native thinking:
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "moonshot/kimi-k2.5": {
-              params: {
-                thinking: { type: "disabled" },
-              },
-            },
+- `thinking: { type: "enabled" }`
+- `thinking: { type: "disabled" }`
+
+Configure it per model via `agents.defaults.models.<provider/model>.params`:
+
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "moonshot/kimi-k2.5": {
+          params: {
+            thinking: { type: "disabled" },
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    OpenClaw also maps runtime `/think` levels for Moonshot:
+OpenClaw also maps runtime `/think` levels for Moonshot:
 
-    | `/think` level       | Moonshot behavior          |
-    | -------------------- | -------------------------- |
-    | `/think off`         | `thinking.type=disabled`   |
-    | Any non-off level    | `thinking.type=enabled`    |
+- `/think off` -> `thinking.type=disabled`
+- any non-off thinking level -> `thinking.type=enabled`
 
-    <Warning>
-    When Moonshot thinking is enabled, `tool_choice` must be `auto` or `none`. OpenClaw normalizes incompatible `tool_choice` values to `auto` for compatibility.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="Streaming usage compatibility">
-    Native Moonshot endpoints (`https://api.moonshot.ai/v1` and
-    `https://api.moonshot.cn/v1`) advertise streaming usage compatibility on the
-    shared `openai-completions` transport. OpenClaw keys that off endpoint
-    capabilities, so compatible custom provider ids targeting the same native
-    Moonshot hosts inherit the same streaming-usage behavior.
-  </Accordion>
-
-  <Accordion title="Endpoint and model ref reference">
-    | Provider   | Model ref prefix | Endpoint                      | Auth env var        |
-    | ---------- | ---------------- | ----------------------------- | ------------------- |
-    | Moonshot   | `moonshot/`      | `https://api.moonshot.ai/v1`  | `MOONSHOT_API_KEY`  |
-    | Moonshot CN| `moonshot/`      | `https://api.moonshot.cn/v1`  | `MOONSHOT_API_KEY`  |
-    | Kimi Coding| `kimi/`          | Kimi Coding endpoint          | `KIMI_API_KEY`      |
-    | Web search | N/A              | Same as Moonshot API region   | `KIMI_API_KEY` or `MOONSHOT_API_KEY` |
-
-    - Kimi web search uses `KIMI_API_KEY` or `MOONSHOT_API_KEY`, and defaults to `https://api.moonshot.ai/v1` with model `kimi-k2.5`.
-    - Override pricing and context metadata in `models.providers` if needed.
-    - If Moonshot publishes different context limits for a model, adjust `contextWindow` accordingly.
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Web search" href="/tools/web-search" icon="magnifying-glass">
-    Configuring web search providers including Kimi.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema for providers, models, and plugins.
-  </Card>
-  <Card title="Moonshot Open Platform" href="https://platform.moonshot.ai" icon="globe">
-    Moonshot API key management and documentation.
-  </Card>
-</CardGroup>
+When Moonshot thinking is enabled, `tool_choice` must be `auto` or `none`. OpenClaw normalizes incompatible `tool_choice` values to `auto` for compatibility.

docs/providers/nvidia.md

@@ -8,35 +8,21 @@ title: "NVIDIA"
 
 # NVIDIA
 
-NVIDIA provides an OpenAI-compatible API at `https://integrate.api.nvidia.com/v1` for
-open models for free. Authenticate with an API key from
-[build.nvidia.com](https://build.nvidia.com/settings/api-keys).
+NVIDIA provides an OpenAI-compatible API at `https://integrate.api.nvidia.com/v1` for open models for free. Authenticate with an API key from [build.nvidia.com](https://build.nvidia.com/settings/api-keys).
 
-## Getting started
+## CLI setup
 
-<Steps>
-  <Step title="Get your API key">
-    Create an API key at [build.nvidia.com](https://build.nvidia.com/settings/api-keys).
-  </Step>
-  <Step title="Export the key and run onboarding">
-    ```bash
-    export NVIDIA_API_KEY="nvapi-..."
-    openclaw onboard --auth-choice skip
-    ```
-  </Step>
-  <Step title="Set an NVIDIA model">
-    ```bash
-    openclaw models set nvidia/nvidia/nemotron-3-super-120b-a12b
-    ```
-  </Step>
-</Steps>
+Export the key once, then run onboarding and set an NVIDIA model:
 
-<Warning>
-If you pass `--token` instead of the env var, the value lands in shell history and
-`ps` output. Prefer the `NVIDIA_API_KEY` environment variable when possible.
-</Warning>
+```bash
+export NVIDIA_API_KEY="nvapi-..."
+openclaw onboard --auth-choice skip
+openclaw models set nvidia/nvidia/nemotron-3-super-120b-a12b
+```
 
-## Config example
+If you still pass `--token`, remember it lands in shell history and `ps` output; prefer the env var when possible.
+
+## Config snippet
 
 ```json5
 {
@@ -57,7 +43,7 @@ If you pass `--token` instead of the env var, the value lands in shell history a
 }
 ```
 
-## Built-in catalog
+## Model IDs
 
 | Model ref                                  | Name                         | Context | Max output |
 | ------------------------------------------ | ---------------------------- | ------- | ---------- |
@@ -66,38 +52,8 @@ If you pass `--token` instead of the env var, the value lands in shell history a
 | `nvidia/minimaxai/minimax-m2.5`            | Minimax M2.5                 | 196,608 | 8,192      |
 | `nvidia/z-ai/glm5`                         | GLM 5                        | 202,752 | 8,192      |
 
-## Advanced notes
+## Notes
 
-<AccordionGroup>
-  <Accordion title="Auto-enable behavior">
-    The provider auto-enables when the `NVIDIA_API_KEY` environment variable is set.
-    No explicit provider config is required beyond the key.
-  </Accordion>
-
-  <Accordion title="Catalog and pricing">
-    The bundled catalog is static. Costs default to `0` in source since NVIDIA
-    currently offers free API access for the listed models.
-  </Accordion>
-
-  <Accordion title="OpenAI-compatible endpoint">
-    NVIDIA uses the standard `/v1` completions endpoint. Any OpenAI-compatible
-    tooling should work out of the box with the NVIDIA base URL.
-  </Accordion>
-</AccordionGroup>
-
-<Tip>
-NVIDIA models are currently free to use. Check
-[build.nvidia.com](https://build.nvidia.com/) for the latest availability and
-rate-limit details.
-</Tip>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config reference for agents, models, and providers.
-  </Card>
-</CardGroup>
+- OpenAI-compatible `/v1` endpoint; use an API key from [build.nvidia.com](https://build.nvidia.com/).
+- Provider auto-enables when `NVIDIA_API_KEY` is set.
+- The bundled catalog is static; costs default to `0` in source.

docs/providers/ollama.md

@@ -14,154 +14,122 @@ Ollama is a local LLM runtime that makes it easy to run open-source models on yo
 **Remote Ollama users**: Do not use the `/v1` OpenAI-compatible URL (`http://host:11434/v1`) with OpenClaw. This breaks tool calling and models may output raw tool JSON as plain text. Use the native Ollama API URL instead: `baseUrl: "http://host:11434"` (no `/v1`).
 </Warning>
 
-## Getting started
+## Quick start
 
-Choose your preferred setup method and mode.
+### Onboarding (recommended)
 
-<Tabs>
-  <Tab title="Onboarding (recommended)">
-    **Best for:** fastest path to a working Ollama setup with automatic model discovery.
+The fastest way to set up Ollama is through onboarding:
 
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard
-        ```
+```bash
+openclaw onboard
+```
 
-        Select **Ollama** from the provider list.
-      </Step>
-      <Step title="Choose your mode">
-        - **Cloud + Local** — cloud-hosted models and local models together
-        - **Local** — local models only
+Select **Ollama** from the provider list. Onboarding will:
 
-        If you choose **Cloud + Local** and are not signed in to ollama.com, onboarding opens a browser sign-in flow.
-      </Step>
-      <Step title="Select a model">
-        Onboarding discovers available models and suggests defaults. It auto-pulls the selected model if it is not available locally.
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider ollama
-        ```
-      </Step>
-    </Steps>
+1. Ask for the Ollama base URL where your instance can be reached (default `http://127.0.0.1:11434`).
+2. Let you choose **Cloud + Local** (cloud models and local models) or **Local** (local models only).
+3. Open a browser sign-in flow if you choose **Cloud + Local** and are not signed in to ollama.com.
+4. Discover available models and suggest defaults.
+5. Auto-pull the selected model if it is not available locally.
 
-    ### Non-interactive mode
+Non-interactive mode is also supported:
 
-    ```bash
-    openclaw onboard --non-interactive \
-      --auth-choice ollama \
-      --accept-risk
-    ```
+```bash
+openclaw onboard --non-interactive \
+  --auth-choice ollama \
+  --accept-risk
+```
 
-    Optionally specify a custom base URL or model:
+Optionally specify a custom base URL or model:
 
-    ```bash
-    openclaw onboard --non-interactive \
-      --auth-choice ollama \
-      --custom-base-url "http://ollama-host:11434" \
-      --custom-model-id "qwen3.5:27b" \
-      --accept-risk
-    ```
+```bash
+openclaw onboard --non-interactive \
+  --auth-choice ollama \
+  --custom-base-url "http://ollama-host:11434" \
+  --custom-model-id "qwen3.5:27b" \
+  --accept-risk
+```
 
-  </Tab>
+### Manual setup
 
-  <Tab title="Manual setup">
-    **Best for:** full control over installation, model pulls, and config.
+1. Install Ollama: [https://ollama.com/download](https://ollama.com/download)
 
-    <Steps>
-      <Step title="Install Ollama">
-        Download from [ollama.com/download](https://ollama.com/download).
-      </Step>
-      <Step title="Pull a local model">
-        ```bash
-        ollama pull gemma4
-        # or
-        ollama pull gpt-oss:20b
-        # or
-        ollama pull llama3.3
-        ```
-      </Step>
-      <Step title="Sign in for cloud models (optional)">
-        If you want cloud models too:
+2. Pull a local model if you want local inference:
 
-        ```bash
-        ollama signin
-        ```
-      </Step>
-      <Step title="Enable Ollama for OpenClaw">
-        Set any value for the API key (Ollama does not require a real key):
+```bash
+ollama pull gemma4
+# or
+ollama pull gpt-oss:20b
+# or
+ollama pull llama3.3
+```
 
-        ```bash
-        # Set environment variable
-        export OLLAMA_API_KEY="ollama-local"
+3. If you want cloud models too, sign in:
 
-        # Or configure in your config file
-        openclaw config set models.providers.ollama.apiKey "ollama-local"
-        ```
-      </Step>
-      <Step title="Inspect and set your model">
-        ```bash
-        openclaw models list
-        openclaw models set ollama/gemma4
-        ```
+```bash
+ollama signin
+```
 
-        Or set the default in config:
+4. Run onboarding and choose `Ollama`:
 
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "ollama/gemma4" },
-            },
-          },
-        }
-        ```
-      </Step>
-    </Steps>
+```bash
+openclaw onboard
+```
 
-  </Tab>
-</Tabs>
+- `Local`: local models only
+- `Cloud + Local`: local models plus cloud models
+- Cloud models such as `kimi-k2.5:cloud`, `minimax-m2.7:cloud`, and `glm-5.1:cloud` do **not** require a local `ollama pull`
 
-## Cloud models
+OpenClaw currently suggests:
 
-<Tabs>
-  <Tab title="Cloud + Local">
-    Cloud models let you run cloud-hosted models alongside your local models. Examples include `kimi-k2.5:cloud`, `minimax-m2.7:cloud`, and `glm-5.1:cloud` -- these do **not** require a local `ollama pull`.
+- local default: `gemma4`
+- cloud defaults: `kimi-k2.5:cloud`, `minimax-m2.7:cloud`, `glm-5.1:cloud`
 
-    Select **Cloud + Local** mode during setup. The wizard checks whether you are signed in and opens a browser sign-in flow when needed. If authentication cannot be verified, the wizard falls back to local model defaults.
+5. If you prefer manual setup, enable Ollama for OpenClaw directly (any value works; Ollama doesn't require a real key):
 
-    You can also sign in directly at [ollama.com/signin](https://ollama.com/signin).
+```bash
+# Set environment variable
+export OLLAMA_API_KEY="ollama-local"
 
-    OpenClaw currently suggests these cloud defaults: `kimi-k2.5:cloud`, `minimax-m2.7:cloud`, `glm-5.1:cloud`.
+# Or configure in your config file
+openclaw config set models.providers.ollama.apiKey "ollama-local"
+```
 
-  </Tab>
+6. Inspect or switch models:
 
-  <Tab title="Local only">
-    In local-only mode, OpenClaw discovers models from the local Ollama instance. No cloud sign-in is needed.
+```bash
+openclaw models list
+openclaw models set ollama/gemma4
+```
 
-    OpenClaw currently suggests `gemma4` as the local default.
+7. Or set the default in config:
 
-  </Tab>
-</Tabs>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "ollama/gemma4" },
+    },
+  },
+}
+```
 
 ## Model discovery (implicit provider)
 
-When you set `OLLAMA_API_KEY` (or an auth profile) and **do not** define `models.providers.ollama`, OpenClaw discovers models from the local Ollama instance at `http://127.0.0.1:11434`.
+When you set `OLLAMA_API_KEY` (or an auth profile) and **do not** define `models.providers.ollama`, OpenClaw discovers models from the local Ollama instance at `http://127.0.0.1:11434`:
 
-| Behavior             | Detail                                                                                                                                                              |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Catalog query        | Queries `/api/tags`                                                                                                                                                 |
-| Capability detection | Uses best-effort `/api/show` lookups to read `contextWindow` and detect capabilities (including vision)                                                             |
-| Vision models        | Models with a `vision` capability reported by `/api/show` are marked as image-capable (`input: ["text", "image"]`), so OpenClaw auto-injects images into the prompt |
-| Reasoning detection  | Marks `reasoning` with a model-name heuristic (`r1`, `reasoning`, `think`)                                                                                          |
-| Token limits         | Sets `maxTokens` to the default Ollama max-token cap used by OpenClaw                                                                                               |
-| Costs                | Sets all costs to `0`                                                                                                                                               |
+- Queries `/api/tags`
+- Uses best-effort `/api/show` lookups to read `contextWindow` and detect capabilities (including vision) when available
+- Models with a `vision` capability reported by `/api/show` are marked as image-capable (`input: ["text", "image"]`), so OpenClaw auto-injects images into the prompt for those models
+- Marks `reasoning` with a model-name heuristic (`r1`, `reasoning`, `think`)
+- Sets `maxTokens` to the default Ollama max-token cap used by OpenClaw
+- Sets all costs to `0`
 
 This avoids manual model entries while keeping the catalog aligned with the local Ollama instance.
 
+To see what models are available:
+
 ```bash
-# See what models are available
 ollama list
 openclaw models list
 ```
@@ -174,79 +142,74 @@ ollama pull mistral
 
 The new model will be automatically discovered and available to use.
 
-<Note>
-If you set `models.providers.ollama` explicitly, auto-discovery is skipped and you must define models manually. See the explicit config section below.
-</Note>
+If you set `models.providers.ollama` explicitly, auto-discovery is skipped and you must define models manually (see below).
 
 ## Configuration
 
-<Tabs>
-  <Tab title="Basic (implicit discovery)">
-    The simplest way to enable Ollama is via environment variable:
+### Basic setup (implicit discovery)
 
-    ```bash
-    export OLLAMA_API_KEY="ollama-local"
-    ```
+The simplest way to enable Ollama is via environment variable:
 
-    <Tip>
-    If `OLLAMA_API_KEY` is set, you can omit `apiKey` in the provider entry and OpenClaw will fill it for availability checks.
-    </Tip>
+```bash
+export OLLAMA_API_KEY="ollama-local"
+```
 
-  </Tab>
+### Explicit setup (manual models)
 
-  <Tab title="Explicit (manual models)">
-    Use explicit config when Ollama runs on another host/port, you want to force specific context windows or model lists, or you want fully manual model definitions.
+Use explicit config when:
 
-    ```json5
-    {
-      models: {
-        providers: {
-          ollama: {
-            baseUrl: "http://ollama-host:11434",
-            apiKey: "ollama-local",
-            api: "ollama",
-            models: [
-              {
-                id: "gpt-oss:20b",
-                name: "GPT-OSS 20B",
-                reasoning: false,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 8192,
-                maxTokens: 8192 * 10
-              }
-            ]
+- Ollama runs on another host/port.
+- You want to force specific context windows or model lists.
+- You want fully manual model definitions.
+
+```json5
+{
+  models: {
+    providers: {
+      ollama: {
+        baseUrl: "http://ollama-host:11434",
+        apiKey: "ollama-local",
+        api: "ollama",
+        models: [
+          {
+            id: "gpt-oss:20b",
+            name: "GPT-OSS 20B",
+            reasoning: false,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 8192,
+            maxTokens: 8192 * 10
           }
-        }
+        ]
       }
     }
-    ```
+  }
+}
+```
 
-  </Tab>
+If `OLLAMA_API_KEY` is set, you can omit `apiKey` in the provider entry and OpenClaw will fill it for availability checks.
 
-  <Tab title="Custom base URL">
-    If Ollama is running on a different host or port (explicit config disables auto-discovery, so define models manually):
+### Custom base URL (explicit config)
 
-    ```json5
-    {
-      models: {
-        providers: {
-          ollama: {
-            apiKey: "ollama-local",
-            baseUrl: "http://ollama-host:11434", // No /v1 - use native Ollama API URL
-            api: "ollama", // Set explicitly to guarantee native tool-calling behavior
-          },
-        },
+If Ollama is running on a different host or port (explicit config disables auto-discovery, so define models manually):
+
+```json5
+{
+  models: {
+    providers: {
+      ollama: {
+        apiKey: "ollama-local",
+        baseUrl: "http://ollama-host:11434", // No /v1 - use native Ollama API URL
+        api: "ollama", // Set explicitly to guarantee native tool-calling behavior
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Warning>
-    Do not add `/v1` to the URL. The `/v1` path uses OpenAI-compatible mode, where tool calling is not reliable. Use the base Ollama URL without a path suffix.
-    </Warning>
-
-  </Tab>
-</Tabs>
+<Warning>
+Do not add `/v1` to the URL. The `/v1` path uses OpenAI-compatible mode, where tool calling is not reliable. Use the base Ollama URL without a path suffix.
+</Warning>
 
 ### Model selection
 
@@ -265,17 +228,26 @@ Once configured, all your Ollama models are available:
 }
 ```
 
+## Cloud models
+
+Cloud models let you run cloud-hosted models (for example `kimi-k2.5:cloud`, `minimax-m2.7:cloud`, `glm-5.1:cloud`) alongside your local models.
+
+To use cloud models, select **Cloud + Local** mode during setup. The wizard checks whether you are signed in and opens a browser sign-in flow when needed. If authentication cannot be verified, the wizard falls back to local model defaults.
+
+You can also sign in directly at [ollama.com/signin](https://ollama.com/signin).
+
 ## Ollama Web Search
 
-OpenClaw supports **Ollama Web Search** as a bundled `web_search` provider.
+OpenClaw also supports **Ollama Web Search** as a bundled `web_search`
+provider.
 
-| Property    | Detail                                                                                                            |
-| ----------- | ----------------------------------------------------------------------------------------------------------------- |
-| Host        | Uses your configured Ollama host (`models.providers.ollama.baseUrl` when set, otherwise `http://127.0.0.1:11434`) |
-| Auth        | Key-free                                                                                                          |
-| Requirement | Ollama must be running and signed in with `ollama signin`                                                         |
+- It uses your configured Ollama host (`models.providers.ollama.baseUrl` when
+  set, otherwise `http://127.0.0.1:11434`).
+- It is key-free.
+- It requires Ollama to be running and signed in with `ollama signin`.
 
-Choose **Ollama Web Search** during `openclaw onboard` or `openclaw configure --section web`, or set:
+Choose **Ollama Web Search** during `openclaw onboard` or
+`openclaw configure --section web`, or set:
 
 ```json5
 {
@@ -289,193 +261,120 @@ Choose **Ollama Web Search** during `openclaw onboard` or `openclaw configure --
 }
 ```
 
-<Note>
 For the full setup and behavior details, see [Ollama Web Search](/tools/ollama-search).
-</Note>
 
-## Advanced configuration
+## Advanced
 
-<AccordionGroup>
-  <Accordion title="Legacy OpenAI-compatible mode">
-    <Warning>
-    **Tool calling is not reliable in OpenAI-compatible mode.** Use this mode only if you need OpenAI format for a proxy and do not depend on native tool calling behavior.
-    </Warning>
+### Reasoning models
 
-    If you need to use the OpenAI-compatible endpoint instead (for example, behind a proxy that only supports OpenAI format), set `api: "openai-completions"` explicitly:
+OpenClaw treats models with names such as `deepseek-r1`, `reasoning`, or `think` as reasoning-capable by default:
 
-    ```json5
-    {
-      models: {
-        providers: {
-          ollama: {
-            baseUrl: "http://ollama-host:11434/v1",
-            api: "openai-completions",
-            injectNumCtxForOpenAICompat: true, // default: true
-            apiKey: "ollama-local",
-            models: [...]
-          }
-        }
+```bash
+ollama pull deepseek-r1:32b
+```
+
+### Model Costs
+
+Ollama is free and runs locally, so all model costs are set to $0.
+
+### Streaming Configuration
+
+OpenClaw's Ollama integration uses the **native Ollama API** (`/api/chat`) by default, which fully supports streaming and tool calling simultaneously. No special configuration is needed.
+
+#### Legacy OpenAI-Compatible Mode
+
+<Warning>
+**Tool calling is not reliable in OpenAI-compatible mode.** Use this mode only if you need OpenAI format for a proxy and do not depend on native tool calling behavior.
+</Warning>
+
+If you need to use the OpenAI-compatible endpoint instead (e.g., behind a proxy that only supports OpenAI format), set `api: "openai-completions"` explicitly:
+
+```json5
+{
+  models: {
+    providers: {
+      ollama: {
+        baseUrl: "http://ollama-host:11434/v1",
+        api: "openai-completions",
+        injectNumCtxForOpenAICompat: true, // default: true
+        apiKey: "ollama-local",
+        models: [...]
       }
     }
-    ```
+  }
+}
+```
 
-    This mode may not support streaming and tool calling simultaneously. You may need to disable streaming with `params: { streaming: false }` in model config.
+This mode may not support streaming + tool calling simultaneously. You may need to disable streaming with `params: { streaming: false }` in model config.
 
-    When `api: "openai-completions"` is used with Ollama, OpenClaw injects `options.num_ctx` by default so Ollama does not silently fall back to a 4096 context window. If your proxy/upstream rejects unknown `options` fields, disable this behavior:
+When `api: "openai-completions"` is used with Ollama, OpenClaw injects `options.num_ctx` by default so Ollama does not silently fall back to a 4096 context window. If your proxy/upstream rejects unknown `options` fields, disable this behavior:
 
-    ```json5
-    {
-      models: {
-        providers: {
-          ollama: {
-            baseUrl: "http://ollama-host:11434/v1",
-            api: "openai-completions",
-            injectNumCtxForOpenAICompat: false,
-            apiKey: "ollama-local",
-            models: [...]
-          }
-        }
+```json5
+{
+  models: {
+    providers: {
+      ollama: {
+        baseUrl: "http://ollama-host:11434/v1",
+        api: "openai-completions",
+        injectNumCtxForOpenAICompat: false,
+        apiKey: "ollama-local",
+        models: [...]
       }
     }
-    ```
+  }
+}
+```
 
-  </Accordion>
+### Context windows
 
-  <Accordion title="Context windows">
-    For auto-discovered models, OpenClaw uses the context window reported by Ollama when available, otherwise it falls back to the default Ollama context window used by OpenClaw.
-
-    You can override `contextWindow` and `maxTokens` in explicit provider config:
-
-    ```json5
-    {
-      models: {
-        providers: {
-          ollama: {
-            models: [
-              {
-                id: "llama3.3",
-                contextWindow: 131072,
-                maxTokens: 65536,
-              }
-            ]
-          }
-        }
-      }
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Reasoning models">
-    OpenClaw treats models with names such as `deepseek-r1`, `reasoning`, or `think` as reasoning-capable by default.
-
-    ```bash
-    ollama pull deepseek-r1:32b
-    ```
-
-    No additional configuration is needed -- OpenClaw marks them automatically.
-
-  </Accordion>
-
-  <Accordion title="Model costs">
-    Ollama is free and runs locally, so all model costs are set to $0. This applies to both auto-discovered and manually defined models.
-  </Accordion>
-
-  <Accordion title="Memory embeddings">
-    The bundled Ollama plugin registers a memory embedding provider for
-    [memory search](/concepts/memory). It uses the configured Ollama base URL
-    and API key.
-
-    | Property      | Value               |
-    | ------------- | ------------------- |
-    | Default model | `nomic-embed-text`  |
-    | Auto-pull     | Yes — the embedding model is pulled automatically if not present locally |
-
-    To select Ollama as the memory search embedding provider:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          memorySearch: { provider: "ollama" },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Streaming configuration">
-    OpenClaw's Ollama integration uses the **native Ollama API** (`/api/chat`) by default, which fully supports streaming and tool calling simultaneously. No special configuration is needed.
-
-    <Tip>
-    If you need to use the OpenAI-compatible endpoint, see the "Legacy OpenAI-compatible mode" section above. Streaming and tool calling may not work simultaneously in that mode.
-    </Tip>
-
-  </Accordion>
-</AccordionGroup>
+For auto-discovered models, OpenClaw uses the context window reported by Ollama when available, otherwise it falls back to the default Ollama context window used by OpenClaw. You can override `contextWindow` and `maxTokens` in explicit provider config.
 
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="Ollama not detected">
-    Make sure Ollama is running and that you set `OLLAMA_API_KEY` (or an auth profile), and that you did **not** define an explicit `models.providers.ollama` entry:
+### Ollama not detected
 
-    ```bash
-    ollama serve
-    ```
+Make sure Ollama is running and that you set `OLLAMA_API_KEY` (or an auth profile), and that you did **not** define an explicit `models.providers.ollama` entry:
 
-    Verify that the API is accessible:
+```bash
+ollama serve
+```
 
-    ```bash
-    curl http://localhost:11434/api/tags
-    ```
+And that the API is accessible:
 
-  </Accordion>
+```bash
+curl http://localhost:11434/api/tags
+```
 
-  <Accordion title="No models available">
-    If your model is not listed, either pull the model locally or define it explicitly in `models.providers.ollama`.
+### No models available
 
-    ```bash
-    ollama list  # See what's installed
-    ollama pull gemma4
-    ollama pull gpt-oss:20b
-    ollama pull llama3.3     # Or another model
-    ```
+If your model is not listed, either:
 
-  </Accordion>
+- Pull the model locally, or
+- Define the model explicitly in `models.providers.ollama`.
 
-  <Accordion title="Connection refused">
-    Check that Ollama is running on the correct port:
+To add models:
 
-    ```bash
-    # Check if Ollama is running
-    ps aux | grep ollama
+```bash
+ollama list  # See what's installed
+ollama pull gemma4
+ollama pull gpt-oss:20b
+ollama pull llama3.3     # Or another model
+```
 
-    # Or restart Ollama
-    ollama serve
-    ```
+### Connection refused
 
-  </Accordion>
-</AccordionGroup>
+Check that Ollama is running on the correct port:
 
-<Note>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Note>
+```bash
+# Check if Ollama is running
+ps aux | grep ollama
 
-## Related
+# Or restart Ollama
+ollama serve
+```
 
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Model selection" href="/concepts/models" icon="brain">
-    How to choose and configure models.
-  </Card>
-  <Card title="Ollama Web Search" href="/tools/ollama-search" icon="magnifying-glass">
-    Full setup and behavior details for Ollama-powered web search.
-  </Card>
-  <Card title="Configuration" href="/gateway/configuration" icon="gear">
-    Full config reference.
-  </Card>
-</CardGroup>
+## See Also
+
+- [Model Providers](/concepts/model-providers) - Overview of all providers
+- [Model Selection](/concepts/models) - How to choose models
+- [Configuration](/gateway/configuration) - Full config reference

docs/providers/openai.md

@@ -3,542 +3,555 @@ summary: "Use OpenAI via API keys or Codex subscription in OpenClaw"
 read_when:
   - You want to use OpenAI models in OpenClaw
   - You want Codex subscription auth instead of API keys
-  - You need stricter GPT-5 agent execution behavior
 title: "OpenAI"
 ---
 
 # OpenAI
 
-OpenAI provides developer APIs for GPT models. OpenClaw supports two auth routes:
+OpenAI provides developer APIs for GPT models. Codex supports **ChatGPT sign-in** for subscription
+access or **API key** sign-in for usage-based access. Codex cloud requires ChatGPT sign-in.
+OpenAI explicitly supports subscription OAuth usage in external tools/workflows like OpenClaw.
 
-- **API key** — direct OpenAI Platform access with usage-based billing (`openai/*` models)
-- **Codex subscription** — ChatGPT/Codex sign-in with subscription access (`openai-codex/*` models)
+## Default interaction style
 
-OpenAI explicitly supports subscription OAuth usage in external tools and workflows like OpenClaw.
+OpenClaw can add a small OpenAI-specific prompt overlay for both `openai/*` and
+`openai-codex/*` runs. By default, the overlay keeps the assistant warm,
+collaborative, concise, direct, and a little more emotionally expressive
+without replacing the base OpenClaw system prompt. The friendly overlay also
+permits the occasional emoji when it fits naturally, while keeping overall
+output concise.
 
-## Getting started
+Config key:
 
-Choose your preferred auth method and follow the setup steps.
+`plugins.entries.openai.config.personality`
 
-<Tabs>
-  <Tab title="API key (OpenAI Platform)">
-    **Best for:** direct API access and usage-based billing.
+Allowed values:
 
-    <Steps>
-      <Step title="Get your API key">
-        Create or copy an API key from the [OpenAI Platform dashboard](https://platform.openai.com/api-keys).
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice openai-api-key
-        ```
+- `"friendly"`: default; enable the OpenAI-specific overlay.
+- `"on"`: alias for `"friendly"`.
+- `"off"`: disable the overlay and use the base OpenClaw prompt only.
 
-        Or pass the key directly:
+Scope:
 
-        ```bash
-        openclaw onboard --openai-api-key "$OPENAI_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider openai
-        ```
-      </Step>
-    </Steps>
+- Applies to `openai/*` models.
+- Applies to `openai-codex/*` models.
+- Does not affect other providers.
 
-    ### Route summary
+This behavior is on by default. Keep `"friendly"` explicitly if you want that
+to survive future local config churn:
 
-    | Model ref | Route | Auth |
-    |-----------|-------|------|
-    | `openai/gpt-5.4` | Direct OpenAI Platform API | `OPENAI_API_KEY` |
-    | `openai/gpt-5.4-pro` | Direct OpenAI Platform API | `OPENAI_API_KEY` |
-
-    <Note>
-    ChatGPT/Codex sign-in is routed through `openai-codex/*`, not `openai/*`.
-    </Note>
-
-    ### Config example
-
-    ```json5
-    {
-      env: { OPENAI_API_KEY: "sk-..." },
-      agents: { defaults: { model: { primary: "openai/gpt-5.4" } } },
-    }
-    ```
-
-    <Warning>
-    OpenClaw does **not** expose `openai/gpt-5.3-codex-spark` on the direct API path. Live OpenAI API requests reject that model. Spark is Codex-only.
-    </Warning>
-
-  </Tab>
-
-  <Tab title="Codex subscription">
-    **Best for:** using your ChatGPT/Codex subscription instead of a separate API key. Codex cloud requires ChatGPT sign-in.
-
-    <Steps>
-      <Step title="Run Codex OAuth">
-        ```bash
-        openclaw onboard --auth-choice openai-codex
-        ```
-
-        Or run OAuth directly:
-
-        ```bash
-        openclaw models auth login --provider openai-codex
-        ```
-      </Step>
-      <Step title="Set the default model">
-        ```bash
-        openclaw config set agents.defaults.model.primary openai-codex/gpt-5.4
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider openai-codex
-        ```
-      </Step>
-    </Steps>
-
-    ### Route summary
-
-    | Model ref | Route | Auth |
-    |-----------|-------|------|
-    | `openai-codex/gpt-5.4` | ChatGPT/Codex OAuth | Codex sign-in |
-    | `openai-codex/gpt-5.3-codex-spark` | ChatGPT/Codex OAuth | Codex sign-in (entitlement-dependent) |
-
-    <Note>
-    This route is intentionally separate from `openai/gpt-5.4`. Use `openai/*` with an API key for direct Platform access, and `openai-codex/*` for Codex subscription access.
-    </Note>
-
-    ### Config example
-
-    ```json5
-    {
-      agents: { defaults: { model: { primary: "openai-codex/gpt-5.4" } } },
-    }
-    ```
-
-    <Tip>
-    If onboarding reuses an existing Codex CLI login, those credentials stay managed by Codex CLI. On expiry, OpenClaw re-reads the external Codex source first and writes the refreshed credential back to Codex storage.
-    </Tip>
-
-    ### Context window cap
-
-    OpenClaw treats model metadata and the runtime context cap as separate values.
-
-    For `openai-codex/gpt-5.4`:
-
-    - Native `contextWindow`: `1050000`
-    - Default runtime `contextTokens` cap: `272000`
-
-    The smaller default cap has better latency and quality characteristics in practice. Override it with `contextTokens`:
-
-    ```json5
-    {
-      models: {
-        providers: {
-          "openai-codex": {
-            models: [{ id: "gpt-5.4", contextTokens: 160000 }],
-          },
+```json5
+{
+  plugins: {
+    entries: {
+      openai: {
+        config: {
+          personality: "friendly",
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Note>
-    Use `contextWindow` to declare native model metadata. Use `contextTokens` to limit the runtime context budget.
-    </Note>
+### Disable the OpenAI prompt overlay
 
-  </Tab>
-</Tabs>
+If you want the unmodified base OpenClaw prompt, set the overlay to `"off"`:
+
+```json5
+{
+  plugins: {
+    entries: {
+      openai: {
+        config: {
+          personality: "off",
+        },
+      },
+    },
+  },
+}
+```
+
+You can also set it directly with the config CLI:
+
+```bash
+openclaw config set plugins.entries.openai.config.personality off
+```
+
+OpenClaw normalizes this setting case-insensitively at runtime, so values like
+`"Off"` still disable the friendly overlay.
+
+## Option A: OpenAI API key (OpenAI Platform)
+
+**Best for:** direct API access and usage-based billing.
+Get your API key from the OpenAI dashboard.
+
+Route summary:
+
+- `openai/gpt-5.4` = direct OpenAI Platform API route
+- Requires `OPENAI_API_KEY` (or equivalent OpenAI provider config)
+- In OpenClaw, ChatGPT/Codex sign-in is routed through `openai-codex/*`, not `openai/*`
+
+### CLI setup
+
+```bash
+openclaw onboard --auth-choice openai-api-key
+# or non-interactive
+openclaw onboard --openai-api-key "$OPENAI_API_KEY"
+```
+
+### Config snippet
+
+```json5
+{
+  env: { OPENAI_API_KEY: "sk-..." },
+  agents: { defaults: { model: { primary: "openai/gpt-5.4" } } },
+}
+```
+
+OpenAI's current API model docs list `gpt-5.4` and `gpt-5.4-pro` for direct
+OpenAI API usage. OpenClaw forwards both through the `openai/*` Responses path.
+OpenClaw intentionally suppresses the stale `openai/gpt-5.3-codex-spark` row,
+because direct OpenAI API calls reject it in live traffic.
+
+OpenClaw does **not** expose `openai/gpt-5.3-codex-spark` on the direct OpenAI
+API path. `pi-ai` still ships a built-in row for that model, but live OpenAI API
+requests currently reject it. Spark is treated as Codex-only in OpenClaw.
 
 ## Image generation
 
-The bundled `openai` plugin registers image generation through the `image_generate` tool.
+The bundled `openai` plugin also registers image generation through the shared
+`image_generate` tool.
 
-| Capability                | Value                              |
-| ------------------------- | ---------------------------------- |
-| Default model             | `openai/gpt-image-1`               |
-| Max images per request    | 4                                  |
-| Edit mode                 | Enabled (up to 5 reference images) |
-| Size overrides            | Supported                          |
-| Aspect ratio / resolution | Not forwarded to OpenAI Images API |
+- Default image model: `openai/gpt-image-1`
+- Generate: up to 4 images per request
+- Edit mode: enabled, up to 5 reference images
+- Supports `size`
+- Current OpenAI-specific caveat: OpenClaw does not forward `aspectRatio` or
+  `resolution` overrides to the OpenAI Images API today
+
+To use OpenAI as the default image provider:
 
 ```json5
 {
   agents: {
     defaults: {
-      imageGenerationModel: { primary: "openai/gpt-image-1" },
+      imageGenerationModel: {
+        primary: "openai/gpt-image-1",
+      },
     },
   },
 }
 ```
 
-<Note>
-See [Image Generation](/tools/image-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Image Generation](/tools/image-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
 ## Video generation
 
-The bundled `openai` plugin registers video generation through the `video_generate` tool.
+The bundled `openai` plugin also registers video generation through the shared
+`video_generate` tool.
 
-| Capability       | Value                                                                             |
-| ---------------- | --------------------------------------------------------------------------------- |
-| Default model    | `openai/sora-2`                                                                   |
-| Modes            | Text-to-video, image-to-video, single-video edit                                  |
-| Reference inputs | 1 image or 1 video                                                                |
-| Size overrides   | Supported                                                                         |
-| Other overrides  | `aspectRatio`, `resolution`, `audio`, `watermark` are ignored with a tool warning |
+- Default video model: `openai/sora-2`
+- Modes: text-to-video, image-to-video, and single-video reference/edit flows
+- Current limits: 1 image or 1 video reference input
+- Current OpenAI-specific caveat: OpenClaw currently only forwards `size`
+  overrides for native OpenAI video generation. Unsupported optional overrides
+  such as `aspectRatio`, `resolution`, `audio`, and `watermark` are ignored
+  and reported back as a tool warning.
+
+To use OpenAI as the default video provider:
 
 ```json5
 {
   agents: {
     defaults: {
-      videoGenerationModel: { primary: "openai/sora-2" },
+      videoGenerationModel: {
+        primary: "openai/sora-2",
+      },
     },
   },
 }
 ```
 
-<Note>
-See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-## Personality overlay
+## Option B: OpenAI Code (Codex) subscription
 
-OpenClaw adds a small OpenAI-specific prompt overlay for `openai/*` and `openai-codex/*` runs. The overlay keeps the assistant warm, collaborative, concise, and a little more emotionally expressive without replacing the base system prompt.
+**Best for:** using ChatGPT/Codex subscription access instead of an API key.
+Codex cloud requires ChatGPT sign-in, while the Codex CLI supports ChatGPT or API key sign-in.
 
-| Value                  | Effect                             |
-| ---------------------- | ---------------------------------- |
-| `"friendly"` (default) | Enable the OpenAI-specific overlay |
-| `"on"`                 | Alias for `"friendly"`             |
-| `"off"`                | Use base OpenClaw prompt only      |
+Route summary:
 
-<Tabs>
-  <Tab title="Config">
-    ```json5
-    {
-      plugins: {
-        entries: {
-          openai: { config: { personality: "friendly" } },
-        },
+- `openai-codex/gpt-5.4` = ChatGPT/Codex OAuth route
+- Uses ChatGPT/Codex sign-in, not a direct OpenAI Platform API key
+- Provider-side limits for `openai-codex/*` can differ from the ChatGPT web/app experience
+
+### CLI setup (Codex OAuth)
+
+```bash
+# Run Codex OAuth in the wizard
+openclaw onboard --auth-choice openai-codex
+
+# Or run OAuth directly
+openclaw models auth login --provider openai-codex
+```
+
+### Config snippet (Codex subscription)
+
+```json5
+{
+  agents: { defaults: { model: { primary: "openai-codex/gpt-5.4" } } },
+}
+```
+
+OpenAI's current Codex docs list `gpt-5.4` as the current Codex model. OpenClaw
+maps that to `openai-codex/gpt-5.4` for ChatGPT/Codex OAuth usage.
+
+This route is intentionally separate from `openai/gpt-5.4`. If you want the
+direct OpenAI Platform API path, use `openai/*` with an API key. If you want
+ChatGPT/Codex sign-in, use `openai-codex/*`.
+
+If onboarding reuses an existing Codex CLI login, those credentials stay
+managed by Codex CLI. On expiry, OpenClaw re-reads the external Codex source
+first and, when the provider can refresh it, writes the refreshed credential
+back to Codex storage instead of taking ownership in a separate OpenClaw-only
+copy.
+
+If your Codex account is entitled to Codex Spark, OpenClaw also supports:
+
+- `openai-codex/gpt-5.3-codex-spark`
+
+OpenClaw treats Codex Spark as Codex-only. It does not expose a direct
+`openai/gpt-5.3-codex-spark` API-key path.
+
+OpenClaw also preserves `openai-codex/gpt-5.3-codex-spark` when `pi-ai`
+discovers it. Treat it as entitlement-dependent and experimental: Codex Spark is
+separate from GPT-5.4 `/fast`, and availability depends on the signed-in Codex /
+ChatGPT account.
+
+### Codex context window cap
+
+OpenClaw treats the Codex model metadata and the runtime context cap as separate
+values.
+
+For `openai-codex/gpt-5.4`:
+
+- native `contextWindow`: `1050000`
+- default runtime `contextTokens` cap: `272000`
+
+That keeps model metadata truthful while preserving the smaller default runtime
+window that has better latency and quality characteristics in practice.
+
+If you want a different effective cap, set `models.providers.<provider>.models[].contextTokens`:
+
+```json5
+{
+  models: {
+    providers: {
+      "openai-codex": {
+        models: [
+          {
+            id: "gpt-5.4",
+            contextTokens: 160000,
+          },
+        ],
       },
-    }
-    ```
-  </Tab>
-  <Tab title="CLI">
-    ```bash
-    openclaw config set plugins.entries.openai.config.personality off
-    ```
-  </Tab>
-</Tabs>
+    },
+  },
+}
+```
 
-<Tip>
-Values are case-insensitive at runtime, so `"Off"` and `"off"` both disable the overlay.
-</Tip>
+Use `contextWindow` only when you are declaring or overriding native model
+metadata. Use `contextTokens` when you want to limit the runtime context budget.
 
-## Voice and speech
+### Transport default
 
-<AccordionGroup>
-  <Accordion title="Speech synthesis (TTS)">
-    The bundled `openai` plugin registers speech synthesis for the `messages.tts` surface.
+OpenClaw uses `pi-ai` for model streaming. For both `openai/*` and
+`openai-codex/*`, default transport is `"auto"` (WebSocket-first, then SSE
+fallback).
 
-    | Setting | Config path | Default |
-    |---------|------------|---------|
-    | Model | `messages.tts.providers.openai.model` | `gpt-4o-mini-tts` |
-    | Voice | `messages.tts.providers.openai.voice` | `coral` |
-    | Speed | `messages.tts.providers.openai.speed` | (unset) |
-    | Instructions | `messages.tts.providers.openai.instructions` | (unset, `gpt-4o-mini-tts` only) |
-    | Format | `messages.tts.providers.openai.responseFormat` | `opus` for voice notes, `mp3` for files |
-    | API key | `messages.tts.providers.openai.apiKey` | Falls back to `OPENAI_API_KEY` |
-    | Base URL | `messages.tts.providers.openai.baseUrl` | `https://api.openai.com/v1` |
+In `"auto"` mode, OpenClaw also retries one early, retryable WebSocket failure
+before it falls back to SSE. Forced `"websocket"` mode still surfaces transport
+errors directly instead of hiding them behind fallback.
 
-    Available models: `gpt-4o-mini-tts`, `tts-1`, `tts-1-hd`. Available voices: `alloy`, `ash`, `ballad`, `cedar`, `coral`, `echo`, `fable`, `juniper`, `marin`, `onyx`, `nova`, `sage`, `shimmer`, `verse`.
+After a connect or early-turn WebSocket failure in `"auto"` mode, OpenClaw marks
+that session's WebSocket path as degraded for about 60 seconds and sends
+subsequent turns over SSE during the cool-down instead of thrashing between
+transports.
 
-    ```json5
-    {
-      messages: {
-        tts: {
-          providers: {
-            openai: { model: "gpt-4o-mini-tts", voice: "coral" },
+For native OpenAI-family endpoints (`openai/*`, `openai-codex/*`, and Azure
+OpenAI Responses), OpenClaw also attaches stable session and turn identity state
+to requests so retries, reconnects, and SSE fallback stay aligned to the same
+conversation identity. On native OpenAI-family routes this includes stable
+session/turn request identity headers plus matching transport metadata.
+
+OpenClaw also normalizes OpenAI usage counters across transport variants before
+they reach session/status surfaces. Native OpenAI/Codex Responses traffic may
+report usage as either `input_tokens` / `output_tokens` or
+`prompt_tokens` / `completion_tokens`; OpenClaw treats those as the same input
+and output counters for `/status`, `/usage`, and session logs. When native
+WebSocket traffic omits `total_tokens` (or reports `0`), OpenClaw falls back to
+the normalized input + output total so session/status displays stay populated.
+
+You can set `agents.defaults.models.<provider/model>.params.transport`:
+
+- `"sse"`: force SSE
+- `"websocket"`: force WebSocket
+- `"auto"`: try WebSocket, then fall back to SSE
+
+For `openai/*` (Responses API), OpenClaw also enables WebSocket warm-up by
+default (`openaiWsWarmup: true`) when WebSocket transport is used.
+
+Related OpenAI docs:
+
+- [Realtime API with WebSocket](https://platform.openai.com/docs/guides/realtime-websocket)
+- [Streaming API responses (SSE)](https://platform.openai.com/docs/guides/streaming-responses)
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "openai-codex/gpt-5.4" },
+      models: {
+        "openai-codex/gpt-5.4": {
+          params: {
+            transport: "auto",
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Note>
-    Set `OPENAI_TTS_BASE_URL` to override the TTS base URL without affecting the chat API endpoint.
-    </Note>
+### OpenAI WebSocket warm-up
 
-  </Accordion>
+OpenAI docs describe warm-up as optional. OpenClaw enables it by default for
+`openai/*` to reduce first-turn latency when using WebSocket transport.
 
-  <Accordion title="Realtime transcription">
-    The bundled `openai` plugin registers realtime transcription for the Voice Call plugin.
+### Disable warm-up
 
-    | Setting | Config path | Default |
-    |---------|------------|---------|
-    | Model | `plugins.entries.voice-call.config.streaming.providers.openai.model` | `gpt-4o-transcribe` |
-    | Silence duration | `...openai.silenceDurationMs` | `800` |
-    | VAD threshold | `...openai.vadThreshold` | `0.5` |
-    | API key | `...openai.apiKey` | Falls back to `OPENAI_API_KEY` |
-
-    <Note>
-    Uses a WebSocket connection to `wss://api.openai.com/v1/realtime` with G.711 u-law audio.
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Realtime voice">
-    The bundled `openai` plugin registers realtime voice for the Voice Call plugin.
-
-    | Setting | Config path | Default |
-    |---------|------------|---------|
-    | Model | `plugins.entries.voice-call.config.realtime.providers.openai.model` | `gpt-realtime` |
-    | Voice | `...openai.voice` | `alloy` |
-    | Temperature | `...openai.temperature` | `0.8` |
-    | VAD threshold | `...openai.vadThreshold` | `0.5` |
-    | Silence duration | `...openai.silenceDurationMs` | `500` |
-    | API key | `...openai.apiKey` | Falls back to `OPENAI_API_KEY` |
-
-    <Note>
-    Supports Azure OpenAI via `azureEndpoint` and `azureDeployment` config keys. Supports bidirectional tool calling. Uses G.711 u-law audio format.
-    </Note>
-
-  </Accordion>
-</AccordionGroup>
-
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Transport (WebSocket vs SSE)">
-    OpenClaw uses WebSocket-first with SSE fallback (`"auto"`) for both `openai/*` and `openai-codex/*`.
-
-    In `"auto"` mode, OpenClaw:
-    - Retries one early WebSocket failure before falling back to SSE
-    - After a failure, marks WebSocket as degraded for ~60 seconds and uses SSE during cool-down
-    - Attaches stable session and turn identity headers for retries and reconnects
-    - Normalizes usage counters (`input_tokens` / `prompt_tokens`) across transport variants
-
-    | Value | Behavior |
-    |-------|----------|
-    | `"auto"` (default) | WebSocket first, SSE fallback |
-    | `"sse"` | Force SSE only |
-    | `"websocket"` | Force WebSocket only |
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "openai-codex/gpt-5.4": {
-              params: { transport: "auto" },
-            },
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            openaiWsWarmup: false,
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    Related OpenAI docs:
-    - [Realtime API with WebSocket](https://platform.openai.com/docs/guides/realtime-websocket)
-    - [Streaming API responses (SSE)](https://platform.openai.com/docs/guides/streaming-responses)
+### Enable warm-up explicitly
 
-  </Accordion>
-
-  <Accordion title="WebSocket warm-up">
-    OpenClaw enables WebSocket warm-up by default for `openai/*` to reduce first-turn latency.
-
-    ```json5
-    // Disable warm-up
-    {
-      agents: {
-        defaults: {
-          models: {
-            "openai/gpt-5.4": {
-              params: { openaiWsWarmup: false },
-            },
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            openaiWsWarmup: true,
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-  </Accordion>
+### OpenAI and Codex priority processing
 
-  <Accordion title="Fast mode">
-    OpenClaw exposes a shared fast-mode toggle for both `openai/*` and `openai-codex/*`:
+OpenAI's API exposes priority processing via `service_tier=priority`. In
+OpenClaw, set `agents.defaults.models["<provider>/<model>"].params.serviceTier`
+to pass that field through on native OpenAI/Codex Responses endpoints.
 
-    - **Chat/UI:** `/fast status|on|off`
-    - **Config:** `agents.defaults.models["<provider>/<model>"].params.fastMode`
-
-    When enabled, OpenClaw maps fast mode to OpenAI priority processing (`service_tier = "priority"`). Existing `service_tier` values are preserved, and fast mode does not rewrite `reasoning` or `text.verbosity`.
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "openai/gpt-5.4": { params: { fastMode: true } },
-            "openai-codex/gpt-5.4": { params: { fastMode: true } },
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            serviceTier: "priority",
+          },
+        },
+        "openai-codex/gpt-5.4": {
+          params: {
+            serviceTier: "priority",
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Note>
-    Session overrides win over config. Clearing the session override in the Sessions UI returns the session to the configured default.
-    </Note>
+Supported values are `auto`, `default`, `flex`, and `priority`.
 
-  </Accordion>
+OpenClaw forwards `params.serviceTier` to both direct `openai/*` Responses
+requests and `openai-codex/*` Codex Responses requests when those models point
+at the native OpenAI/Codex endpoints.
 
-  <Accordion title="Priority processing (service_tier)">
-    OpenAI's API exposes priority processing via `service_tier`. Set it per model in OpenClaw:
+Important behavior:
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "openai/gpt-5.4": { params: { serviceTier: "priority" } },
-            "openai-codex/gpt-5.4": { params: { serviceTier: "priority" } },
+- direct `openai/*` must target `api.openai.com`
+- `openai-codex/*` must target `chatgpt.com/backend-api`
+- if you route either provider through another base URL or proxy, OpenClaw leaves `service_tier` untouched
+
+### OpenAI fast mode
+
+OpenClaw exposes a shared fast-mode toggle for both `openai/*` and
+`openai-codex/*` sessions:
+
+- Chat/UI: `/fast status|on|off`
+- Config: `agents.defaults.models["<provider>/<model>"].params.fastMode`
+
+When fast mode is enabled, OpenClaw maps it to OpenAI priority processing:
+
+- direct `openai/*` Responses calls to `api.openai.com` send `service_tier = "priority"`
+- `openai-codex/*` Responses calls to `chatgpt.com/backend-api` also send `service_tier = "priority"`
+- existing payload `service_tier` values are preserved
+- fast mode does not rewrite `reasoning` or `text.verbosity`
+
+For GPT 5.4 specifically, the most common setup is:
+
+- send `/fast on` in a session using `openai/gpt-5.4` or `openai-codex/gpt-5.4`
+- or set `agents.defaults.models["openai/gpt-5.4"].params.fastMode = true`
+- if you also use Codex OAuth, set `agents.defaults.models["openai-codex/gpt-5.4"].params.fastMode = true` too
+
+Example:
+
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            fastMode: true,
+          },
+        },
+        "openai-codex/gpt-5.4": {
+          params: {
+            fastMode: true,
           },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    Supported values: `auto`, `default`, `flex`, `priority`.
+Session overrides win over config. Clearing the session override in the Sessions UI
+returns the session to the configured default.
 
-    <Warning>
-    `serviceTier` is only forwarded to native OpenAI endpoints (`api.openai.com`) and native Codex endpoints (`chatgpt.com/backend-api`). If you route either provider through a proxy, OpenClaw leaves `service_tier` untouched.
-    </Warning>
+### Native OpenAI versus OpenAI-compatible routes
 
-  </Accordion>
+OpenClaw treats direct OpenAI, Codex, and Azure OpenAI endpoints differently
+from generic OpenAI-compatible `/v1` proxies:
 
-  <Accordion title="Server-side compaction (Responses API)">
-    For direct OpenAI Responses models (`openai/*` on `api.openai.com`), OpenClaw auto-enables server-side compaction:
+- native `openai/*`, `openai-codex/*`, and Azure OpenAI routes keep
+  `reasoning: { effort: "none" }` intact when you explicitly disable reasoning
+- native OpenAI-family routes default tool schemas to strict mode
+- hidden OpenClaw attribution headers (`originator`, `version`, and
+  `User-Agent`) are only attached on verified native OpenAI hosts
+  (`api.openai.com`) and native Codex hosts (`chatgpt.com/backend-api`)
+- native OpenAI/Codex routes keep OpenAI-only request shaping such as
+  `service_tier`, Responses `store`, OpenAI reasoning-compat payloads, and
+  prompt-cache hints
+- proxy-style OpenAI-compatible routes keep the looser compat behavior and do
+  not force strict tool schemas, native-only request shaping, or hidden
+  OpenAI/Codex attribution headers
 
-    - Forces `store: true` (unless model compat sets `supportsStore: false`)
-    - Injects `context_management: [{ type: "compaction", compact_threshold: ... }]`
-    - Default `compact_threshold`: 70% of `contextWindow` (or `80000` when unavailable)
+Azure OpenAI stays in the native-routing bucket for transport and compat
+behavior, but it does not receive the hidden OpenAI/Codex attribution headers.
 
-    <Tabs>
-      <Tab title="Enable explicitly">
-        Useful for compatible endpoints like Azure OpenAI Responses:
+This preserves current native OpenAI Responses behavior without forcing older
+OpenAI-compatible shims onto third-party `/v1` backends.
 
-        ```json5
-        {
-          agents: {
-            defaults: {
-              models: {
-                "azure-openai-responses/gpt-5.4": {
-                  params: { responsesServerCompaction: true },
-                },
-              },
-            },
+### OpenAI Responses server-side compaction
+
+For direct OpenAI Responses models (`openai/*` using `api: "openai-responses"` with
+`baseUrl` on `api.openai.com`), OpenClaw now auto-enables OpenAI server-side
+compaction payload hints:
+
+- Forces `store: true` (unless model compat sets `supportsStore: false`)
+- Injects `context_management: [{ type: "compaction", compact_threshold: ... }]`
+
+By default, `compact_threshold` is `70%` of model `contextWindow` (or `80000`
+when unavailable).
+
+### Enable server-side compaction explicitly
+
+Use this when you want to force `context_management` injection on compatible
+Responses models (for example Azure OpenAI Responses):
+
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "azure-openai-responses/gpt-5.4": {
+          params: {
+            responsesServerCompaction: true,
           },
-        }
-        ```
-      </Tab>
-      <Tab title="Custom threshold">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              models: {
-                "openai/gpt-5.4": {
-                  params: {
-                    responsesServerCompaction: true,
-                    responsesCompactThreshold: 120000,
-                  },
-                },
-              },
-            },
-          },
-        }
-        ```
-      </Tab>
-      <Tab title="Disable">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              models: {
-                "openai/gpt-5.4": {
-                  params: { responsesServerCompaction: false },
-                },
-              },
-            },
-          },
-        }
-        ```
-      </Tab>
-    </Tabs>
-
-    <Note>
-    `responsesServerCompaction` only controls `context_management` injection. Direct OpenAI Responses models still force `store: true` unless compat sets `supportsStore: false`.
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Strict-agentic GPT mode">
-    For GPT-5-family runs on `openai/*` and `openai-codex/*`, OpenClaw can use a stricter embedded execution contract:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          embeddedPi: { executionContract: "strict-agentic" },
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    With `strict-agentic`, OpenClaw:
-    - No longer treats a plan-only turn as successful progress when a tool action is available
-    - Retries the turn with an act-now steer
-    - Auto-enables `update_plan` for substantial work
-    - Surfaces an explicit blocked state if the model keeps planning without acting
+### Enable with a custom threshold
 
-    <Note>
-    Scoped to OpenAI and Codex GPT-5-family runs only. Other providers and older model families keep default behavior.
-    </Note>
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            responsesServerCompaction: true,
+            responsesCompactThreshold: 120000,
+          },
+        },
+      },
+    },
+  },
+}
+```
 
-  </Accordion>
+### Disable server-side compaction
 
-  <Accordion title="Native vs OpenAI-compatible routes">
-    OpenClaw treats direct OpenAI, Codex, and Azure OpenAI endpoints differently from generic OpenAI-compatible `/v1` proxies:
+```json5
+{
+  agents: {
+    defaults: {
+      models: {
+        "openai/gpt-5.4": {
+          params: {
+            responsesServerCompaction: false,
+          },
+        },
+      },
+    },
+  },
+}
+```
 
-    **Native routes** (`openai/*`, `openai-codex/*`, Azure OpenAI):
-    - Keep `reasoning: { effort: "none" }` intact when reasoning is explicitly disabled
-    - Default tool schemas to strict mode
-    - Attach hidden attribution headers on verified native hosts only
-    - Keep OpenAI-only request shaping (`service_tier`, `store`, reasoning-compat, prompt-cache hints)
+`responsesServerCompaction` only controls `context_management` injection.
+Direct OpenAI Responses models still force `store: true` unless compat sets
+`supportsStore: false`.
 
-    **Proxy/compatible routes:**
-    - Use looser compat behavior
-    - Do not force strict tool schemas or native-only headers
+## Notes
 
-    Azure OpenAI uses native transport and compat behavior but does not receive the hidden attribution headers.
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Image generation" href="/tools/image-generation" icon="image">
-    Shared image tool parameters and provider selection.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-</CardGroup>
+- Model refs always use `provider/model` (see [/concepts/models](/concepts/models)).
+- Auth details + reuse rules are in [/concepts/oauth](/concepts/oauth).

docs/providers/opencode-go.md

@@ -12,60 +12,21 @@ OpenCode Go is the Go catalog within [OpenCode](/providers/opencode).
 It uses the same `OPENCODE_API_KEY` as the Zen catalog, but keeps the runtime
 provider id `opencode-go` so upstream per-model routing stays correct.
 
-| Property         | Value                           |
-| ---------------- | ------------------------------- |
-| Runtime provider | `opencode-go`                   |
-| Auth             | `OPENCODE_API_KEY`              |
-| Parent setup     | [OpenCode](/providers/opencode) |
-
 ## Supported models
 
-| Model ref                  | Name         |
-| -------------------------- | ------------ |
-| `opencode-go/kimi-k2.5`    | Kimi K2.5    |
-| `opencode-go/glm-5`        | GLM 5        |
-| `opencode-go/minimax-m2.5` | MiniMax M2.5 |
+- `opencode-go/kimi-k2.5`
+- `opencode-go/glm-5`
+- `opencode-go/minimax-m2.5`
 
-## Getting started
+## CLI setup
 
-<Tabs>
-  <Tab title="Interactive">
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice opencode-go
-        ```
-      </Step>
-      <Step title="Set a Go model as default">
-        ```bash
-        openclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.5"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider opencode-go
-        ```
-      </Step>
-    </Steps>
-  </Tab>
+```bash
+openclaw onboard --auth-choice opencode-go
+# or non-interactive
+openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
+```
 
-  <Tab title="Non-interactive">
-    <Steps>
-      <Step title="Pass the key directly">
-        ```bash
-        openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider opencode-go
-        ```
-      </Step>
-    </Steps>
-  </Tab>
-</Tabs>
-
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -74,37 +35,11 @@ provider id `opencode-go` so upstream per-model routing stays correct.
 }
 ```
 
-## Advanced notes
+## Routing behavior
 
-<AccordionGroup>
-  <Accordion title="Routing behavior">
-    OpenClaw handles per-model routing automatically when the model ref uses
-    `opencode-go/...`. No additional provider config is required.
-  </Accordion>
+OpenClaw handles per-model routing automatically when the model ref uses `opencode-go/...`.
 
-  <Accordion title="Runtime ref convention">
-    Runtime refs stay explicit: `opencode/...` for Zen, `opencode-go/...` for Go.
-    This keeps upstream per-model routing correct across both catalogs.
-  </Accordion>
+## Notes
 
-  <Accordion title="Shared credentials">
-    The same `OPENCODE_API_KEY` is used by both the Zen and Go catalogs. Entering
-    the key during setup stores credentials for both runtime providers.
-  </Accordion>
-</AccordionGroup>
-
-<Tip>
-See [OpenCode](/providers/opencode) for the shared onboarding overview and the full
-Zen + Go catalog reference.
-</Tip>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="OpenCode (parent)" href="/providers/opencode" icon="server">
-    Shared onboarding, catalog overview, and advanced notes.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>
+- Use [OpenCode](/providers/opencode) for the shared onboarding and catalog overview.
+- Runtime refs stay explicit: `opencode/...` for Zen, `opencode-go/...` for Go.

docs/providers/opencode.md

@@ -10,78 +10,30 @@ title: "OpenCode"
 
 OpenCode exposes two hosted catalogs in OpenClaw:
 
-| Catalog | Prefix            | Runtime provider |
-| ------- | ----------------- | ---------------- |
-| **Zen** | `opencode/...`    | `opencode`       |
-| **Go**  | `opencode-go/...` | `opencode-go`    |
+- `opencode/...` for the **Zen** catalog
+- `opencode-go/...` for the **Go** catalog
 
 Both catalogs use the same OpenCode API key. OpenClaw keeps the runtime provider ids
 split so upstream per-model routing stays correct, but onboarding and docs treat them
 as one OpenCode setup.
 
-## Getting started
+## CLI setup
 
-<Tabs>
-  <Tab title="Zen catalog">
-    **Best for:** the curated OpenCode multi-model proxy (Claude, GPT, Gemini).
+### Zen catalog
 
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice opencode-zen
-        ```
+```bash
+openclaw onboard --auth-choice opencode-zen
+openclaw onboard --opencode-zen-api-key "$OPENCODE_API_KEY"
+```
 
-        Or pass the key directly:
+### Go catalog
 
-        ```bash
-        openclaw onboard --opencode-zen-api-key "$OPENCODE_API_KEY"
-        ```
-      </Step>
-      <Step title="Set a Zen model as the default">
-        ```bash
-        openclaw config set agents.defaults.model.primary "opencode/claude-opus-4-6"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider opencode
-        ```
-      </Step>
-    </Steps>
+```bash
+openclaw onboard --auth-choice opencode-go
+openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
+```
 
-  </Tab>
-
-  <Tab title="Go catalog">
-    **Best for:** the OpenCode-hosted Kimi, GLM, and MiniMax lineup.
-
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice opencode-go
-        ```
-
-        Or pass the key directly:
-
-        ```bash
-        openclaw onboard --opencode-go-api-key "$OPENCODE_API_KEY"
-        ```
-      </Step>
-      <Step title="Set a Go model as the default">
-        ```bash
-        openclaw config set agents.defaults.model.primary "opencode-go/kimi-k2.5"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider opencode-go
-        ```
-      </Step>
-    </Steps>
-
-  </Tab>
-</Tabs>
-
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -94,58 +46,23 @@ as one OpenCode setup.
 
 ### Zen
 
-| Property         | Value                                                                   |
-| ---------------- | ----------------------------------------------------------------------- |
-| Runtime provider | `opencode`                                                              |
-| Example models   | `opencode/claude-opus-4-6`, `opencode/gpt-5.4`, `opencode/gemini-3-pro` |
+- Runtime provider: `opencode`
+- Example models: `opencode/claude-opus-4-6`, `opencode/gpt-5.4`, `opencode/gemini-3-pro`
+- Best when you want the curated OpenCode multi-model proxy
 
 ### Go
 
-| Property         | Value                                                                    |
-| ---------------- | ------------------------------------------------------------------------ |
-| Runtime provider | `opencode-go`                                                            |
-| Example models   | `opencode-go/kimi-k2.5`, `opencode-go/glm-5`, `opencode-go/minimax-m2.5` |
+- Runtime provider: `opencode-go`
+- Example models: `opencode-go/kimi-k2.5`, `opencode-go/glm-5`, `opencode-go/minimax-m2.5`
+- Best when you want the OpenCode-hosted Kimi/GLM/MiniMax lineup
 
-## Advanced notes
+## Notes
 
-<AccordionGroup>
-  <Accordion title="API key aliases">
-    `OPENCODE_ZEN_API_KEY` is also supported as an alias for `OPENCODE_API_KEY`.
-  </Accordion>
-
-  <Accordion title="Shared credentials">
-    Entering one OpenCode key during setup stores credentials for both runtime
-    providers. You do not need to onboard each catalog separately.
-  </Accordion>
-
-  <Accordion title="Billing and dashboard">
-    You sign in to OpenCode, add billing details, and copy your API key. Billing
-    and catalog availability are managed from the OpenCode dashboard.
-  </Accordion>
-
-  <Accordion title="Gemini replay behavior">
-    Gemini-backed OpenCode refs stay on the proxy-Gemini path, so OpenClaw keeps
-    Gemini thought-signature sanitation there without enabling native Gemini
-    replay validation or bootstrap rewrites.
-  </Accordion>
-
-  <Accordion title="Non-Gemini replay behavior">
-    Non-Gemini OpenCode refs keep the minimal OpenAI-compatible replay policy.
-  </Accordion>
-</AccordionGroup>
-
-<Tip>
-Entering one OpenCode key during setup stores credentials for both the Zen and
-Go runtime providers, so you only need to onboard once.
-</Tip>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config reference for agents, models, and providers.
-  </Card>
-</CardGroup>
+- `OPENCODE_ZEN_API_KEY` is also supported.
+- Entering one OpenCode key during setup stores credentials for both runtime providers.
+- You sign in to OpenCode, add billing details, and copy your API key.
+- Billing and catalog availability are managed from the OpenCode dashboard.
+- Gemini-backed OpenCode refs stay on the proxy-Gemini path, so OpenClaw keeps
+  Gemini thought-signature sanitation there without enabling native Gemini
+  replay validation or bootstrap rewrites.
+- Non-Gemini OpenCode refs keep the minimal OpenAI-compatible replay policy.

docs/providers/openrouter.md

@@ -11,28 +11,13 @@ title: "OpenRouter"
 OpenRouter provides a **unified API** that routes requests to many models behind a single
 endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switching the base URL.
 
-## Getting started
+## CLI setup
 
-<Steps>
-  <Step title="Get your API key">
-    Create an API key at [openrouter.ai/keys](https://openrouter.ai/keys).
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice openrouter-api-key
-    ```
-  </Step>
-  <Step title="(Optional) Switch to a specific model">
-    Onboarding defaults to `openrouter/auto`. Pick a concrete model later:
+```bash
+openclaw onboard --auth-choice openrouter-api-key
+```
 
-    ```bash
-    openclaw models set openrouter/<provider>/<model>
-    ```
-
-  </Step>
-</Steps>
-
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -45,71 +30,30 @@ endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switc
 }
 ```
 
-## Model references
+## Notes
 
-<Note>
-Model refs follow the pattern `openrouter/<provider>/<model>`. For the full list of
-available providers and models, see [/concepts/model-providers](/concepts/model-providers).
-</Note>
-
-## Authentication and headers
-
-OpenRouter uses a Bearer token with your API key under the hood.
-
-On real OpenRouter requests (`https://openrouter.ai/api/v1`), OpenClaw also adds
-OpenRouter's documented app-attribution headers:
-
-| Header                    | Value                 |
-| ------------------------- | --------------------- |
-| `HTTP-Referer`            | `https://openclaw.ai` |
-| `X-OpenRouter-Title`      | `OpenClaw`            |
-| `X-OpenRouter-Categories` | `cli-agent`           |
-
-<Warning>
-If you repoint the OpenRouter provider at some other proxy or base URL, OpenClaw
-does **not** inject those OpenRouter-specific headers or Anthropic cache markers.
-</Warning>
-
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Anthropic cache markers">
-    On verified OpenRouter routes, Anthropic model refs keep the
-    OpenRouter-specific Anthropic `cache_control` markers that OpenClaw uses for
-    better prompt-cache reuse on system/developer prompt blocks.
-  </Accordion>
-
-  <Accordion title="Thinking / reasoning injection">
-    On supported non-`auto` routes, OpenClaw maps the selected thinking level to
-    OpenRouter proxy reasoning payloads. Unsupported model hints and
-    `openrouter/auto` skip that reasoning injection.
-  </Accordion>
-
-  <Accordion title="OpenAI-only request shaping">
-    OpenRouter still runs through the proxy-style OpenAI-compatible path, so
-    native OpenAI-only request shaping such as `serviceTier`, Responses `store`,
-    OpenAI reasoning-compat payloads, and prompt-cache hints is not forwarded.
-  </Accordion>
-
-  <Accordion title="Gemini-backed routes">
-    Gemini-backed OpenRouter refs stay on the proxy-Gemini path: OpenClaw keeps
-    Gemini thought-signature sanitation there, but does not enable native Gemini
-    replay validation or bootstrap rewrites.
-  </Accordion>
-
-  <Accordion title="Provider routing metadata">
-    If you pass OpenRouter provider routing under model params, OpenClaw forwards
-    it as OpenRouter routing metadata before the shared stream wrappers run.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config reference for agents, models, and providers.
-  </Card>
-</CardGroup>
+- Model refs are `openrouter/<provider>/<model>`.
+- Onboarding defaults to `openrouter/auto`. Switch to a concrete model later with
+  `openclaw models set openrouter/<provider>/<model>`.
+- For more model/provider options, see [/concepts/model-providers](/concepts/model-providers).
+- OpenRouter uses a Bearer token with your API key under the hood.
+- On real OpenRouter requests (`https://openrouter.ai/api/v1`), OpenClaw also
+  adds OpenRouter's documented app-attribution headers:
+  `HTTP-Referer: https://openclaw.ai`, `X-OpenRouter-Title: OpenClaw`, and
+  `X-OpenRouter-Categories: cli-agent`.
+- On verified OpenRouter routes, Anthropic model refs also keep the
+  OpenRouter-specific Anthropic `cache_control` markers that OpenClaw uses for
+  better prompt-cache reuse on system/developer prompt blocks.
+- If you repoint the OpenRouter provider at some other proxy/base URL, OpenClaw
+  does not inject those OpenRouter-specific headers or Anthropic cache markers.
+- OpenRouter still runs through the proxy-style OpenAI-compatible path, so
+  native OpenAI-only request shaping such as `serviceTier`, Responses `store`,
+  OpenAI reasoning-compat payloads, and prompt-cache hints is not forwarded.
+- Gemini-backed OpenRouter refs stay on the proxy-Gemini path: OpenClaw keeps
+  Gemini thought-signature sanitation there, but does not enable native Gemini
+  replay validation or bootstrap rewrites.
+- On supported non-`auto` routes, OpenClaw maps the selected thinking level to
+  OpenRouter proxy reasoning payloads. Unsupported model hints and
+  `openrouter/auto` skip that reasoning injection.
+- If you pass OpenRouter provider routing under model params, OpenClaw forwards
+  it as OpenRouter routing metadata before the shared stream wrappers run.

docs/providers/perplexity-provider.md

@@ -1,5 +1,5 @@
 ---
-title: "Perplexity"
+title: "Perplexity (Provider)"
 summary: "Perplexity web search provider setup (API key, search modes, filtering)"
 read_when:
   - You want to configure Perplexity as a web search provider
@@ -16,52 +16,30 @@ This page covers the Perplexity **provider** setup. For the Perplexity
 **tool** (how the agent uses it), see [Perplexity tool](/tools/perplexity-search).
 </Note>
 
-| Property    | Value                                                                  |
-| ----------- | ---------------------------------------------------------------------- |
-| Type        | Web search provider (not a model provider)                             |
-| Auth        | `PERPLEXITY_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter) |
-| Config path | `plugins.entries.perplexity.config.webSearch.apiKey`                   |
+- Type: web search provider (not a model provider)
+- Auth: `PERPLEXITY_API_KEY` (direct) or `OPENROUTER_API_KEY` (via OpenRouter)
+- Config path: `plugins.entries.perplexity.config.webSearch.apiKey`
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set the API key">
-    Run the interactive web-search configuration flow:
+1. Set the API key:
 
-    ```bash
-    openclaw configure --section web
-    ```
+```bash
+openclaw configure --section web
+```
 
-    Or set the key directly:
+Or set it directly:
 
-    ```bash
-    openclaw config set plugins.entries.perplexity.config.webSearch.apiKey "pplx-xxxxxxxxxxxx"
-    ```
+```bash
+openclaw config set plugins.entries.perplexity.config.webSearch.apiKey "pplx-xxxxxxxxxxxx"
+```
 
-  </Step>
-  <Step title="Start searching">
-    The agent will automatically use Perplexity for web searches once the key is
-    configured. No additional steps are required.
-  </Step>
-</Steps>
+2. The agent will automatically use Perplexity for web searches when configured.
 
 ## Search modes
 
 The plugin auto-selects the transport based on API key prefix:
 
-<Tabs>
-  <Tab title="Native Perplexity API (pplx-)">
-    When your key starts with `pplx-`, OpenClaw uses the native Perplexity Search
-    API. This transport returns structured results and supports domain, language,
-    and date filters (see filtering options below).
-  </Tab>
-  <Tab title="OpenRouter / Sonar (sk-or-)">
-    When your key starts with `sk-or-`, OpenClaw routes through OpenRouter using
-    the Perplexity Sonar model. This transport returns AI-synthesized answers with
-    citations.
-  </Tab>
-</Tabs>
-
 | Key prefix | Transport                    | Features                                         |
 | ---------- | ---------------------------- | ------------------------------------------------ |
 | `pplx-`    | Native Perplexity Search API | Structured results, domain/language/date filters |
@@ -69,58 +47,16 @@ The plugin auto-selects the transport based on API key prefix:
 
 ## Native API filtering
 
-<Note>
-Filtering options are only available when using the native Perplexity API
-(`pplx-` key). OpenRouter/Sonar searches do not support these parameters.
-</Note>
+When using the native Perplexity API (`pplx-` key), searches support:
 
-When using the native Perplexity API, searches support the following filters:
+- **Country**: 2-letter country code
+- **Language**: ISO 639-1 language code
+- **Date range**: day, week, month, year
+- **Domain filters**: allowlist/denylist (max 20 domains)
+- **Content budget**: `max_tokens`, `max_tokens_per_page`
 
-| Filter         | Description                            | Example                             |
-| -------------- | -------------------------------------- | ----------------------------------- |
-| Country        | 2-letter country code                  | `us`, `de`, `jp`                    |
-| Language       | ISO 639-1 language code                | `en`, `fr`, `zh`                    |
-| Date range     | Recency window                         | `day`, `week`, `month`, `year`      |
-| Domain filters | Allowlist or denylist (max 20 domains) | `example.com`                       |
-| Content budget | Token limits per response / per page   | `max_tokens`, `max_tokens_per_page` |
+## Environment note
 
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Environment variable for daemon processes">
-    If the OpenClaw Gateway runs as a daemon (launchd/systemd), make sure
-    `PERPLEXITY_API_KEY` is available to that process.
-
-    <Warning>
-    A key set only in `~/.profile` will not be visible to a launchd/systemd
-    daemon unless that environment is explicitly imported. Set the key in
-    `~/.openclaw/.env` or via `env.shellEnv` to ensure the gateway process can
-    read it.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="OpenRouter proxy setup">
-    If you prefer to route Perplexity searches through OpenRouter, set an
-    `OPENROUTER_API_KEY` (prefix `sk-or-`) instead of a native Perplexity key.
-    OpenClaw will detect the prefix and switch to the Sonar transport
-    automatically.
-
-    <Tip>
-    The OpenRouter transport is useful if you already have an OpenRouter account
-    and want consolidated billing across multiple providers.
-    </Tip>
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Perplexity search tool" href="/tools/perplexity-search" icon="magnifying-glass">
-    How the agent invokes Perplexity searches and interprets results.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full configuration reference including plugin entries.
-  </Card>
-</CardGroup>
+If the Gateway runs as a daemon (launchd/systemd), make sure
+`PERPLEXITY_API_KEY` is available to that process (for example, in
+`~/.openclaw/.env` or via `env.shellEnv`).

docs/providers/qianfan.md

@@ -6,51 +6,31 @@ read_when:
 title: "Qianfan"
 ---
 
-# Qianfan
+# Qianfan Provider Guide
 
-Qianfan is Baidu's MaaS platform, providing a **unified API** that routes requests to many models behind a single
+Qianfan is Baidu's MaaS platform, provides a **unified API** that routes requests to many models behind a single
 endpoint and API key. It is OpenAI-compatible, so most OpenAI SDKs work by switching the base URL.
 
-| Property | Value                             |
-| -------- | --------------------------------- |
-| Provider | `qianfan`                         |
-| Auth     | `QIANFAN_API_KEY`                 |
-| API      | OpenAI-compatible                 |
-| Base URL | `https://qianfan.baidubce.com/v2` |
+## Prerequisites
 
-## Getting started
+1. A Baidu Cloud account with Qianfan API access
+2. An API key from the Qianfan console
+3. OpenClaw installed on your system
 
-<Steps>
-  <Step title="Create a Baidu Cloud account">
-    Sign up or log in at the [Qianfan Console](https://console.bce.baidu.com/qianfan/ais/console/apiKey) and ensure you have Qianfan API access enabled.
-  </Step>
-  <Step title="Generate an API key">
-    Create a new application or select an existing one, then generate an API key. The key format is `bce-v3/ALTAK-...`.
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice qianfan-api-key
-    ```
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider qianfan
-    ```
-  </Step>
-</Steps>
+## Getting Your API Key
 
-## Available models
+1. Visit the [Qianfan Console](https://console.bce.baidu.com/qianfan/ais/console/apiKey)
+2. Create a new application or select an existing one
+3. Generate an API key (format: `bce-v3/ALTAK-...`)
+4. Copy the API key for use with OpenClaw
 
-| Model ref                            | Input       | Context | Max output | Reasoning | Notes         |
-| ------------------------------------ | ----------- | ------- | ---------- | --------- | ------------- |
-| `qianfan/deepseek-v3.2`              | text        | 98,304  | 32,768     | Yes       | Default model |
-| `qianfan/ernie-5.0-thinking-preview` | text, image | 119,000 | 64,000     | Yes       | Multimodal    |
+## CLI setup
 
-<Tip>
-The default bundled model ref is `qianfan/deepseek-v3.2`. You only need to override `models.providers.qianfan` when you need a custom base URL or model metadata.
-</Tip>
+```bash
+openclaw onboard --auth-choice qianfan-api-key
+```
 
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -94,40 +74,17 @@ The default bundled model ref is `qianfan/deepseek-v3.2`. You only need to overr
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="Transport and compatibility">
-    Qianfan runs through the OpenAI-compatible transport path, not native OpenAI request shaping. This means standard OpenAI SDK features work, but provider-specific parameters may not be forwarded.
-  </Accordion>
+## Notes
 
-  <Accordion title="Catalog and overrides">
-    The bundled catalog currently includes `deepseek-v3.2` and `ernie-5.0-thinking-preview`. Add or override `models.providers.qianfan` only when you need a custom base URL or model metadata.
+- Default bundled model ref: `qianfan/deepseek-v3.2`
+- Default base URL: `https://qianfan.baidubce.com/v2`
+- Bundled catalog currently includes `deepseek-v3.2` and `ernie-5.0-thinking-preview`
+- Add or override `models.providers.qianfan` only when you need custom base URL or model metadata
+- Qianfan runs through the OpenAI-compatible transport path, not native OpenAI request shaping
 
-    <Note>
-    Model refs use the `qianfan/` prefix (for example `qianfan/deepseek-v3.2`).
-    </Note>
+## Related Documentation
 
-  </Accordion>
-
-  <Accordion title="Troubleshooting">
-    - Ensure your API key starts with `bce-v3/ALTAK-` and has Qianfan API access enabled in the Baidu Cloud console.
-    - If models are not listed, confirm your account has the Qianfan service activated.
-    - The default base URL is `https://qianfan.baidubce.com/v2`. Only change it if you use a custom endpoint or proxy.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration" icon="gear">
-    Full OpenClaw configuration reference.
-  </Card>
-  <Card title="Agent setup" href="/concepts/agent" icon="robot">
-    Configuring agent defaults and model assignments.
-  </Card>
-  <Card title="Qianfan API docs" href="https://cloud.baidu.com/doc/qianfan-api/s/3m7of64lb" icon="arrow-up-right-from-square">
-    Official Qianfan API documentation.
-  </Card>
-</CardGroup>
+- [OpenClaw Configuration](/gateway/configuration)
+- [Model Providers](/concepts/model-providers)
+- [Agent Setup](/concepts/agent)
+- [Qianfan API Documentation](https://cloud.baidu.com/doc/qianfan-api/s/3m7of64lb)

docs/providers/qwen.md

@@ -17,6 +17,8 @@ background.
 
 </Warning>
 
+## Recommended: Qwen Cloud
+
 OpenClaw now treats Qwen as a first-class bundled provider with canonical id
 `qwen`. The bundled provider targets the Qwen Cloud / Alibaba DashScope and
 Coding Plan endpoints and keeps legacy `modelstudio` ids working as a
@@ -27,108 +29,38 @@ compatibility alias.
 - Also accepted for compatibility: `MODELSTUDIO_API_KEY`, `DASHSCOPE_API_KEY`
 - API style: OpenAI-compatible
 
-<Tip>
 If you want `qwen3.6-plus`, prefer the **Standard (pay-as-you-go)** endpoint.
 Coding Plan support can lag behind the public catalog.
-</Tip>
 
-## Getting started
+```bash
+# Global Coding Plan endpoint
+openclaw onboard --auth-choice qwen-api-key
 
-Choose your plan type and follow the setup steps.
+# China Coding Plan endpoint
+openclaw onboard --auth-choice qwen-api-key-cn
 
-<Tabs>
-  <Tab title="Coding Plan (subscription)">
-    **Best for:** subscription-based access through the Qwen Coding Plan.
+# Global Standard (pay-as-you-go) endpoint
+openclaw onboard --auth-choice qwen-standard-api-key
 
-    <Steps>
-      <Step title="Get your API key">
-        Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
-      </Step>
-      <Step title="Run onboarding">
-        For the **Global** endpoint:
+# China Standard (pay-as-you-go) endpoint
+openclaw onboard --auth-choice qwen-standard-api-key-cn
+```
 
-        ```bash
-        openclaw onboard --auth-choice qwen-api-key
-        ```
+Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
+work as compatibility aliases, but new setup flows should prefer the canonical
+`qwen-*` auth-choice ids and `qwen/...` model refs.
 
-        For the **China** endpoint:
+After onboarding, set a default model:
 
-        ```bash
-        openclaw onboard --auth-choice qwen-api-key-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "qwen/qwen3.5-plus" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider qwen
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
-    work as compatibility aliases, but new setup flows should prefer the canonical
-    `qwen-*` auth-choice ids and `qwen/...` model refs.
-    </Note>
-
-  </Tab>
-
-  <Tab title="Standard (pay-as-you-go)">
-    **Best for:** pay-as-you-go access through the Standard Model Studio endpoint, including models like `qwen3.6-plus` that may not be available on the Coding Plan.
-
-    <Steps>
-      <Step title="Get your API key">
-        Create or copy an API key from [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys).
-      </Step>
-      <Step title="Run onboarding">
-        For the **Global** endpoint:
-
-        ```bash
-        openclaw onboard --auth-choice qwen-standard-api-key
-        ```
-
-        For the **China** endpoint:
-
-        ```bash
-        openclaw onboard --auth-choice qwen-standard-api-key-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          agents: {
-            defaults: {
-              model: { primary: "qwen/qwen3.5-plus" },
-            },
-          },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider qwen
-        ```
-      </Step>
-    </Steps>
-
-    <Note>
-    Legacy `modelstudio-*` auth-choice ids and `modelstudio/...` model refs still
-    work as compatibility aliases, but new setup flows should prefer the canonical
-    `qwen-*` auth-choice ids and `qwen/...` model refs.
-    </Note>
-
-  </Tab>
-</Tabs>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "qwen/qwen3.5-plus" },
+    },
+  },
+}
+```
 
 ## Plan types and endpoints
 
@@ -143,10 +75,16 @@ The provider auto-selects the endpoint based on your auth choice. Canonical
 choices use the `qwen-*` family; `modelstudio-*` remains compatibility-only.
 You can override with a custom `baseUrl` in config.
 
-<Tip>
-**Manage keys:** [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys) |
-**Docs:** [docs.qwencloud.com](https://docs.qwencloud.com/developer-guides/getting-started/introduction)
-</Tip>
+Native Model Studio endpoints advertise streaming usage compatibility on the
+shared `openai-completions` transport. OpenClaw keys that off endpoint
+capabilities now, so DashScope-compatible custom provider ids targeting the
+same native hosts inherit the same streaming-usage behavior instead of
+requiring the built-in `qwen` provider id specifically.
+
+## Get your API key
+
+- **Manage keys**: [home.qwencloud.com/api-keys](https://home.qwencloud.com/api-keys)
+- **Docs**: [docs.qwencloud.com](https://docs.qwencloud.com/developer-guides/getting-started/introduction)
 
 ## Built-in catalog
 
@@ -166,20 +104,71 @@ the Standard endpoint.
 | `qwen/glm-4.7`              | text        | 202,752   | GLM                                                |
 | `qwen/kimi-k2.5`            | text, image | 262,144   | Moonshot AI via Alibaba                            |
 
-<Note>
 Availability can still vary by endpoint and billing plan even when a model is
 present in the bundled catalog.
-</Note>
+
+Native-streaming usage compatibility applies to both the Coding Plan hosts and
+the Standard DashScope-compatible hosts:
+
+- `https://coding.dashscope.aliyuncs.com/v1`
+- `https://coding-intl.dashscope.aliyuncs.com/v1`
+- `https://dashscope.aliyuncs.com/compatible-mode/v1`
+- `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
+
+## Qwen 3.6 Plus availability
+
+`qwen3.6-plus` is available on the Standard (pay-as-you-go) Model Studio
+endpoints:
+
+- China: `dashscope.aliyuncs.com/compatible-mode/v1`
+- Global: `dashscope-intl.aliyuncs.com/compatible-mode/v1`
+
+If the Coding Plan endpoints return an "unsupported model" error for
+`qwen3.6-plus`, switch to Standard (pay-as-you-go) instead of the Coding Plan
+endpoint/key pair.
+
+## Capability plan
+
+The `qwen` extension is being positioned as the vendor home for the full Qwen
+Cloud surface, not just coding/text models.
+
+- Text/chat models: bundled now
+- Tool calling, structured output, thinking: inherited from the OpenAI-compatible transport
+- Image generation: planned at the provider-plugin layer
+- Image/video understanding: bundled now on the Standard endpoint
+- Speech/audio: planned at the provider-plugin layer
+- Memory embeddings/reranking: planned through the embedding adapter surface
+- Video generation: bundled now through the shared video-generation capability
 
 ## Multimodal add-ons
 
-The `qwen` extension also exposes multimodal capabilities on the **Standard**
-DashScope endpoints (not the Coding Plan endpoints):
+The `qwen` extension now also exposes:
 
-- **Video understanding** via `qwen-vl-max-latest`
-- **Wan video generation** via `wan2.6-t2v` (default), `wan2.6-i2v`, `wan2.6-r2v`, `wan2.6-r2v-flash`, `wan2.7-r2v`
+- Video understanding via `qwen-vl-max-latest`
+- Wan video generation via:
+  - `wan2.6-t2v` (default)
+  - `wan2.6-i2v`
+  - `wan2.6-r2v`
+  - `wan2.6-r2v-flash`
+  - `wan2.7-r2v`
 
-To use Qwen as the default video provider:
+These multimodal surfaces use the **Standard** DashScope endpoints, not the
+Coding Plan endpoints.
+
+- Global/Intl Standard base URL: `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
+- China Standard base URL: `https://dashscope.aliyuncs.com/compatible-mode/v1`
+
+For video generation, OpenClaw maps the configured Qwen region to the matching
+DashScope AIGC host before submitting the job:
+
+- Global/Intl: `https://dashscope-intl.aliyuncs.com`
+- China: `https://dashscope.aliyuncs.com`
+
+That means a normal `models.providers.qwen.baseUrl` pointing at either the
+Coding Plan or Standard Qwen hosts still keeps video generation on the correct
+regional DashScope video endpoint.
+
+For video generation, set a default model explicitly:
 
 ```json5
 {
@@ -191,125 +180,22 @@ To use Qwen as the default video provider:
 }
 ```
 
-<Note>
-See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-</Note>
+Current bundled Qwen video-generation limits:
 
-## Advanced
+- Up to **1** output video per request
+- Up to **1** input image
+- Up to **4** input videos
+- Up to **10 seconds** duration
+- Supports `size`, `aspectRatio`, `resolution`, `audio`, and `watermark`
+- Reference image/video mode currently requires **remote http(s) URLs**. Local
+  file paths are rejected up front because the DashScope video endpoint does not
+  accept uploaded local buffers for those references.
 
-<AccordionGroup>
-  <Accordion title="Image and video understanding">
-    The bundled Qwen plugin registers media understanding for images and video
-    on the **Standard** DashScope endpoints (not the Coding Plan endpoints).
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-    | Property      | Value                 |
-    | ------------- | --------------------- |
-    | Model         | `qwen-vl-max-latest`  |
-    | Supported input | Images, video       |
+## Environment note
 
-    Media understanding is auto-resolved from the configured Qwen auth — no
-    additional config is needed. Ensure you are using a Standard (pay-as-you-go)
-    endpoint for media understanding support.
-
-  </Accordion>
-
-  <Accordion title="Qwen 3.6 Plus availability">
-    `qwen3.6-plus` is available on the Standard (pay-as-you-go) Model Studio
-    endpoints:
-
-    - China: `dashscope.aliyuncs.com/compatible-mode/v1`
-    - Global: `dashscope-intl.aliyuncs.com/compatible-mode/v1`
-
-    If the Coding Plan endpoints return an "unsupported model" error for
-    `qwen3.6-plus`, switch to Standard (pay-as-you-go) instead of the Coding Plan
-    endpoint/key pair.
-
-  </Accordion>
-
-  <Accordion title="Capability plan">
-    The `qwen` extension is being positioned as the vendor home for the full Qwen
-    Cloud surface, not just coding/text models.
-
-    - **Text/chat models:** bundled now
-    - **Tool calling, structured output, thinking:** inherited from the OpenAI-compatible transport
-    - **Image generation:** planned at the provider-plugin layer
-    - **Image/video understanding:** bundled now on the Standard endpoint
-    - **Speech/audio:** planned at the provider-plugin layer
-    - **Memory embeddings/reranking:** planned through the embedding adapter surface
-    - **Video generation:** bundled now through the shared video-generation capability
-
-  </Accordion>
-
-  <Accordion title="Video generation details">
-    For video generation, OpenClaw maps the configured Qwen region to the matching
-    DashScope AIGC host before submitting the job:
-
-    - Global/Intl: `https://dashscope-intl.aliyuncs.com`
-    - China: `https://dashscope.aliyuncs.com`
-
-    That means a normal `models.providers.qwen.baseUrl` pointing at either the
-    Coding Plan or Standard Qwen hosts still keeps video generation on the correct
-    regional DashScope video endpoint.
-
-    Current bundled Qwen video-generation limits:
-
-    - Up to **1** output video per request
-    - Up to **1** input image
-    - Up to **4** input videos
-    - Up to **10 seconds** duration
-    - Supports `size`, `aspectRatio`, `resolution`, `audio`, and `watermark`
-    - Reference image/video mode currently requires **remote http(s) URLs**. Local
-      file paths are rejected up front because the DashScope video endpoint does not
-      accept uploaded local buffers for those references.
-
-  </Accordion>
-
-  <Accordion title="Streaming usage compatibility">
-    Native Model Studio endpoints advertise streaming usage compatibility on the
-    shared `openai-completions` transport. OpenClaw keys that off endpoint
-    capabilities now, so DashScope-compatible custom provider ids targeting the
-    same native hosts inherit the same streaming-usage behavior instead of
-    requiring the built-in `qwen` provider id specifically.
-
-    Native-streaming usage compatibility applies to both the Coding Plan hosts and
-    the Standard DashScope-compatible hosts:
-
-    - `https://coding.dashscope.aliyuncs.com/v1`
-    - `https://coding-intl.dashscope.aliyuncs.com/v1`
-    - `https://dashscope.aliyuncs.com/compatible-mode/v1`
-    - `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
-
-  </Accordion>
-
-  <Accordion title="Multimodal endpoint regions">
-    Multimodal surfaces (video understanding and Wan video generation) use the
-    **Standard** DashScope endpoints, not the Coding Plan endpoints:
-
-    - Global/Intl Standard base URL: `https://dashscope-intl.aliyuncs.com/compatible-mode/v1`
-    - China Standard base URL: `https://dashscope.aliyuncs.com/compatible-mode/v1`
-
-  </Accordion>
-
-  <Accordion title="Environment and daemon setup">
-    If the Gateway runs as a daemon (launchd/systemd), make sure `QWEN_API_KEY` is
-    available to that process (for example, in `~/.openclaw/.env` or via
-    `env.shellEnv`).
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Alibaba (ModelStudio)" href="/providers/alibaba" icon="cloud">
-    Legacy ModelStudio provider and migration notes.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+If the Gateway runs as a daemon (launchd/systemd), make sure `QWEN_API_KEY` is
+available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).

docs/providers/runway.md

@@ -11,29 +11,25 @@ read_when:
 
 OpenClaw ships a bundled `runway` provider for hosted video generation.
 
-| Property    | Value                                                             |
-| ----------- | ----------------------------------------------------------------- |
-| Provider id | `runway`                                                          |
-| Auth        | `RUNWAYML_API_SECRET` (canonical) or `RUNWAY_API_KEY`             |
-| API         | Runway task-based video generation (`GET /v1/tasks/{id}` polling) |
+- Provider id: `runway`
+- Auth: `RUNWAYML_API_SECRET` (canonical) or `RUNWAY_API_KEY`
+- API: Runway task-based video generation (`GET /v1/tasks/{id}` polling)
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set the API key">
-    ```bash
-    openclaw onboard --auth-choice runway-api-key
-    ```
-  </Step>
-  <Step title="Set Runway as the default video provider">
-    ```bash
-    openclaw config set agents.defaults.videoGenerationModel.primary "runway/gen4.5"
-    ```
-  </Step>
-  <Step title="Generate a video">
-    Ask the agent to generate a video. Runway will be used automatically.
-  </Step>
-</Steps>
+1. Set the API key:
+
+```bash
+openclaw onboard --auth-choice runway-api-key
+```
+
+2. Set Runway as the default video provider:
+
+```bash
+openclaw config set agents.defaults.videoGenerationModel.primary "runway/gen4.5"
+```
+
+3. Ask the agent to generate a video. Runway will be used automatically.
 
 ## Supported modes
 
@@ -43,14 +39,9 @@ OpenClaw ships a bundled `runway` provider for hosted video generation.
 | Image-to-video | `gen4.5`           | 1 local or remote image |
 | Video-to-video | `gen4_aleph`       | 1 local or remote video |
 
-<Note>
-Local image and video references are supported via data URIs. Text-only runs
-currently expose `16:9` and `9:16` aspect ratios.
-</Note>
-
-<Warning>
-Video-to-video currently requires `runway/gen4_aleph` specifically.
-</Warning>
+- Local image and video references are supported via data URIs.
+- Video-to-video currently requires `runway/gen4_aleph` specifically.
+- Text-only runs currently expose `16:9` and `9:16` aspect ratios.
 
 ## Configuration
 
@@ -66,28 +57,7 @@ Video-to-video currently requires `runway/gen4_aleph` specifically.
 }
 ```
 
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Environment variable aliases">
-    OpenClaw recognizes both `RUNWAYML_API_SECRET` (canonical) and `RUNWAY_API_KEY`.
-    Either variable will authenticate the Runway provider.
-  </Accordion>
-
-  <Accordion title="Task polling">
-    Runway uses a task-based API. After submitting a generation request, OpenClaw
-    polls `GET /v1/tasks/{id}` until the video is ready. No additional
-    configuration is needed for the polling behavior.
-  </Accordion>
-</AccordionGroup>
-
 ## Related
 
-<CardGroup cols={2}>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared tool parameters, provider selection, and async behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">
-    Agent default settings including video generation model.
-  </Card>
-</CardGroup>
+- [Video Generation](/tools/video-generation) -- shared tool parameters, provider selection, and async behavior
+- [Configuration Reference](/gateway/configuration-reference#agent-defaults)

docs/providers/sglang.md

@@ -15,44 +15,36 @@ OpenClaw can also **auto-discover** available models from SGLang when you opt
 in with `SGLANG_API_KEY` (any value works if your server does not enforce auth)
 and you do not define an explicit `models.providers.sglang` entry.
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Start SGLang">
-    Launch SGLang with an OpenAI-compatible server. Your base URL should expose
-    `/v1` endpoints (for example `/v1/models`, `/v1/chat/completions`). SGLang
-    commonly runs on:
+1. Start SGLang with an OpenAI-compatible server.
 
-    - `http://127.0.0.1:30000/v1`
+Your base URL should expose `/v1` endpoints (for example `/v1/models`,
+`/v1/chat/completions`). SGLang commonly runs on:
 
-  </Step>
-  <Step title="Set an API key">
-    Any value works if no auth is configured on your server:
+- `http://127.0.0.1:30000/v1`
 
-    ```bash
-    export SGLANG_API_KEY="sglang-local"
-    ```
+2. Opt in (any value works if no auth is configured):
 
-  </Step>
-  <Step title="Run onboarding or set a model directly">
-    ```bash
-    openclaw onboard
-    ```
+```bash
+export SGLANG_API_KEY="sglang-local"
+```
 
-    Or configure the model manually:
+3. Run onboarding and choose `SGLang`, or set a model directly:
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "sglang/your-model-id" },
-        },
-      },
-    }
-    ```
+```bash
+openclaw onboard
+```
 
-  </Step>
-</Steps>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "sglang/your-model-id" },
+    },
+  },
+}
+```
 
 ## Model discovery (implicit provider)
 
@@ -63,10 +55,8 @@ define `models.providers.sglang`, OpenClaw will query:
 
 and convert the returned IDs into model entries.
 
-<Note>
 If you set `models.providers.sglang` explicitly, auto-discovery is skipped and
 you must define models manually.
-</Note>
 
 ## Explicit configuration (manual models)
 
@@ -101,52 +91,25 @@ Use explicit config when:
 }
 ```
 
-## Advanced configuration
+## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="Proxy-style behavior">
-    SGLang is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
-    native OpenAI endpoint.
+- Check the server is reachable:
 
-    | Behavior | SGLang |
-    |----------|--------|
-    | OpenAI-only request shaping | Not applied |
-    | `service_tier`, Responses `store`, prompt-cache hints | Not sent |
-    | Reasoning-compat payload shaping | Not applied |
-    | Hidden attribution headers (`originator`, `version`, `User-Agent`) | Not injected on custom SGLang base URLs |
+```bash
+curl http://127.0.0.1:30000/v1/models
+```
 
-  </Accordion>
+- If requests fail with auth errors, set a real `SGLANG_API_KEY` that matches
+  your server configuration, or configure the provider explicitly under
+  `models.providers.sglang`.
 
-  <Accordion title="Troubleshooting">
-    **Server not reachable**
+## Proxy-style behavior
 
-    Verify the server is running and responding:
+SGLang is treated as a proxy-style OpenAI-compatible `/v1` backend, not a
+native OpenAI endpoint.
 
-    ```bash
-    curl http://127.0.0.1:30000/v1/models
-    ```
-
-    **Auth errors**
-
-    If requests fail with auth errors, set a real `SGLANG_API_KEY` that matches
-    your server configuration, or configure the provider explicitly under
-    `models.providers.sglang`.
-
-    <Tip>
-    If you run SGLang without authentication, any non-empty value for
-    `SGLANG_API_KEY` is sufficient to opt in to model discovery.
-    </Tip>
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider entries.
-  </Card>
-</CardGroup>
+- native OpenAI-only request shaping does not apply here
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on custom SGLang base URLs

docs/providers/stepfun.md

@@ -13,18 +13,49 @@ OpenClaw includes a bundled StepFun provider plugin with two provider ids:
 - `stepfun` for the standard endpoint
 - `stepfun-plan` for the Step Plan endpoint
 
-<Warning>
-Standard and Step Plan are **separate providers** with different endpoints and model ref prefixes (`stepfun/...` vs `stepfun-plan/...`). Use a China key with the `.com` endpoints and a global key with the `.ai` endpoints.
-</Warning>
+The built-in catalogs currently differ by surface:
+
+- Standard: `step-3.5-flash`
+- Step Plan: `step-3.5-flash`, `step-3.5-flash-2603`
 
 ## Region and endpoint overview
 
-| Endpoint  | China (`.com`)                         | Global (`.ai`)                        |
-| --------- | -------------------------------------- | ------------------------------------- |
-| Standard  | `https://api.stepfun.com/v1`           | `https://api.stepfun.ai/v1`           |
-| Step Plan | `https://api.stepfun.com/step_plan/v1` | `https://api.stepfun.ai/step_plan/v1` |
+- China standard endpoint: `https://api.stepfun.com/v1`
+- Global standard endpoint: `https://api.stepfun.ai/v1`
+- China Step Plan endpoint: `https://api.stepfun.com/step_plan/v1`
+- Global Step Plan endpoint: `https://api.stepfun.ai/step_plan/v1`
+- Auth env var: `STEPFUN_API_KEY`
 
-Auth env var: `STEPFUN_API_KEY`
+Use a China key with the `.com` endpoints and a global key with the `.ai`
+endpoints.
+
+## CLI setup
+
+Interactive setup:
+
+```bash
+openclaw onboard
+```
+
+Choose one of these auth choices:
+
+- `stepfun-standard-api-key-cn`
+- `stepfun-standard-api-key-intl`
+- `stepfun-plan-api-key-cn`
+- `stepfun-plan-api-key-intl`
+
+Non-interactive examples:
+
+```bash
+openclaw onboard --auth-choice stepfun-standard-api-key-intl --stepfun-api-key "$STEPFUN_API_KEY"
+openclaw onboard --auth-choice stepfun-plan-api-key-intl --stepfun-api-key "$STEPFUN_API_KEY"
+```
+
+## Model refs
+
+- Standard default model: `stepfun/step-3.5-flash`
+- Step Plan default model: `stepfun-plan/step-3.5-flash`
+- Step Plan alternate model: `stepfun-plan/step-3.5-flash-2603`
 
 ## Built-in catalogs
 
@@ -41,190 +72,81 @@ Step Plan (`stepfun-plan`):
 | `stepfun-plan/step-3.5-flash`      | 262,144 | 65,536     | Default Step Plan model    |
 | `stepfun-plan/step-3.5-flash-2603` | 262,144 | 65,536     | Additional Step Plan model |
 
-## Getting started
+## Config snippets
 
-Choose your provider surface and follow the setup steps.
+Standard provider:
 
-<Tabs>
-  <Tab title="Standard">
-    **Best for:** general-purpose use via the standard StepFun endpoint.
-
-    <Steps>
-      <Step title="Choose your endpoint region">
-        | Auth choice                      | Endpoint                         | Region        |
-        | -------------------------------- | -------------------------------- | ------------- |
-        | `stepfun-standard-api-key-intl`  | `https://api.stepfun.ai/v1`     | International |
-        | `stepfun-standard-api-key-cn`    | `https://api.stepfun.com/v1`    | China         |
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice stepfun-standard-api-key-intl
-        ```
-
-        Or for the China endpoint:
-
-        ```bash
-        openclaw onboard --auth-choice stepfun-standard-api-key-cn
-        ```
-      </Step>
-      <Step title="Non-interactive alternative">
-        ```bash
-        openclaw onboard --auth-choice stepfun-standard-api-key-intl \
-          --stepfun-api-key "$STEPFUN_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider stepfun
-        ```
-      </Step>
-    </Steps>
-
-    ### Model refs
-
-    - Default model: `stepfun/step-3.5-flash`
-
-  </Tab>
-
-  <Tab title="Step Plan">
-    **Best for:** Step Plan reasoning endpoint.
-
-    <Steps>
-      <Step title="Choose your endpoint region">
-        | Auth choice                  | Endpoint                                | Region        |
-        | ---------------------------- | --------------------------------------- | ------------- |
-        | `stepfun-plan-api-key-intl`  | `https://api.stepfun.ai/step_plan/v1`  | International |
-        | `stepfun-plan-api-key-cn`    | `https://api.stepfun.com/step_plan/v1` | China         |
-      </Step>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice stepfun-plan-api-key-intl
-        ```
-
-        Or for the China endpoint:
-
-        ```bash
-        openclaw onboard --auth-choice stepfun-plan-api-key-cn
-        ```
-      </Step>
-      <Step title="Non-interactive alternative">
-        ```bash
-        openclaw onboard --auth-choice stepfun-plan-api-key-intl \
-          --stepfun-api-key "$STEPFUN_API_KEY"
-        ```
-      </Step>
-      <Step title="Verify models are available">
-        ```bash
-        openclaw models list --provider stepfun-plan
-        ```
-      </Step>
-    </Steps>
-
-    ### Model refs
-
-    - Default model: `stepfun-plan/step-3.5-flash`
-    - Alternate model: `stepfun-plan/step-3.5-flash-2603`
-
-  </Tab>
-</Tabs>
-
-## Advanced
-
-<AccordionGroup>
-  <Accordion title="Full config: Standard provider">
-    ```json5
-    {
-      env: { STEPFUN_API_KEY: "your-key" },
-      agents: { defaults: { model: { primary: "stepfun/step-3.5-flash" } } },
-      models: {
-        mode: "merge",
-        providers: {
-          stepfun: {
-            baseUrl: "https://api.stepfun.ai/v1",
-            api: "openai-completions",
-            apiKey: "${STEPFUN_API_KEY}",
-            models: [
-              {
-                id: "step-3.5-flash",
-                name: "Step 3.5 Flash",
-                reasoning: true,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 65536,
-              },
-            ],
+```json5
+{
+  env: { STEPFUN_API_KEY: "your-key" },
+  agents: { defaults: { model: { primary: "stepfun/step-3.5-flash" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      stepfun: {
+        baseUrl: "https://api.stepfun.ai/v1",
+        api: "openai-completions",
+        apiKey: "${STEPFUN_API_KEY}",
+        models: [
+          {
+            id: "step-3.5-flash",
+            name: "Step 3.5 Flash",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
           },
-        },
+        ],
       },
-    }
-    ```
-  </Accordion>
+    },
+  },
+}
+```
 
-  <Accordion title="Full config: Step Plan provider">
-    ```json5
-    {
-      env: { STEPFUN_API_KEY: "your-key" },
-      agents: { defaults: { model: { primary: "stepfun-plan/step-3.5-flash" } } },
-      models: {
-        mode: "merge",
-        providers: {
-          "stepfun-plan": {
-            baseUrl: "https://api.stepfun.ai/step_plan/v1",
-            api: "openai-completions",
-            apiKey: "${STEPFUN_API_KEY}",
-            models: [
-              {
-                id: "step-3.5-flash",
-                name: "Step 3.5 Flash",
-                reasoning: true,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 65536,
-              },
-              {
-                id: "step-3.5-flash-2603",
-                name: "Step 3.5 Flash 2603",
-                reasoning: true,
-                input: ["text"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 262144,
-                maxTokens: 65536,
-              },
-            ],
+Step Plan provider:
+
+```json5
+{
+  env: { STEPFUN_API_KEY: "your-key" },
+  agents: { defaults: { model: { primary: "stepfun-plan/step-3.5-flash" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      "stepfun-plan": {
+        baseUrl: "https://api.stepfun.ai/step_plan/v1",
+        api: "openai-completions",
+        apiKey: "${STEPFUN_API_KEY}",
+        models: [
+          {
+            id: "step-3.5-flash",
+            name: "Step 3.5 Flash",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
           },
-        },
+          {
+            id: "step-3.5-flash-2603",
+            name: "Step 3.5 Flash 2603",
+            reasoning: true,
+            input: ["text"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 262144,
+            maxTokens: 65536,
+          },
+        ],
       },
-    }
-    ```
-  </Accordion>
+    },
+  },
+}
+```
 
-  <Accordion title="Notes">
-    - The provider is bundled with OpenClaw, so there is no separate plugin install step.
-    - `step-3.5-flash-2603` is currently exposed only on `stepfun-plan`.
-    - A single auth flow writes region-matched profiles for both `stepfun` and `stepfun-plan`, so both surfaces can be discovered together.
-    - Use `openclaw models list` and `openclaw models set <provider/model>` to inspect or switch models.
-  </Accordion>
-</AccordionGroup>
+## Notes
 
-<Note>
-For the broader provider overview, see [Model providers](/concepts/model-providers).
-</Note>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Overview of all providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema for providers, models, and plugins.
-  </Card>
-  <Card title="Model selection" href="/concepts/models" icon="brain">
-    How to choose and configure models.
-  </Card>
-  <Card title="StepFun Platform" href="https://platform.stepfun.com" icon="globe">
-    StepFun API key management and documentation.
-  </Card>
-</CardGroup>
+- The provider is bundled with OpenClaw, so there is no separate plugin install step.
+- `step-3.5-flash-2603` is currently exposed only on `stepfun-plan`.
+- A single auth flow writes region-matched profiles for both `stepfun` and `stepfun-plan`, so both surfaces can be discovered together.
+- Use `openclaw models list` and `openclaw models set <provider/model>` to inspect or switch models.
+- For the broader provider overview, see [Model providers](/concepts/model-providers).

docs/providers/synthetic.md

@@ -8,42 +8,23 @@ title: "Synthetic"
 
 # Synthetic
 
-[Synthetic](https://synthetic.new) exposes Anthropic-compatible endpoints.
-OpenClaw registers it as the `synthetic` provider and uses the Anthropic
-Messages API.
+Synthetic exposes Anthropic-compatible endpoints. OpenClaw registers it as the
+`synthetic` provider and uses the Anthropic Messages API.
 
-| Property | Value                                 |
-| -------- | ------------------------------------- |
-| Provider | `synthetic`                           |
-| Auth     | `SYNTHETIC_API_KEY`                   |
-| API      | Anthropic Messages                    |
-| Base URL | `https://api.synthetic.new/anthropic` |
+## Quick setup
 
-## Getting started
+1. Set `SYNTHETIC_API_KEY` (or run the wizard below).
+2. Run onboarding:
 
-<Steps>
-  <Step title="Get an API key">
-    Obtain a `SYNTHETIC_API_KEY` from your Synthetic account, or let the
-    onboarding wizard prompt you for one.
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice synthetic-api-key
-    ```
-  </Step>
-  <Step title="Verify the default model">
-    After onboarding the default model is set to:
-    ```
-    synthetic/hf:MiniMaxAI/MiniMax-M2.5
-    ```
-  </Step>
-</Steps>
+```bash
+openclaw onboard --auth-choice synthetic-api-key
+```
 
-<Warning>
-OpenClaw's Anthropic client appends `/v1` to the base URL automatically, so use
-`https://api.synthetic.new/anthropic` (not `/anthropic/v1`). If Synthetic
-changes its base URL, override `models.providers.synthetic.baseUrl`.
-</Warning>
+The default model is set to:
+
+```
+synthetic/hf:MiniMaxAI/MiniMax-M2.5
+```
 
 ## Config example
 
@@ -80,77 +61,41 @@ changes its base URL, override `models.providers.synthetic.baseUrl`.
 }
 ```
 
+Note: OpenClaw's Anthropic client appends `/v1` to the base URL, so use
+`https://api.synthetic.new/anthropic` (not `/anthropic/v1`). If Synthetic changes
+its base URL, override `models.providers.synthetic.baseUrl`.
+
 ## Model catalog
 
-All Synthetic models use cost `0` (input/output/cache).
+All models below use cost `0` (input/output/cache).
 
 | Model ID                                               | Context window | Max tokens | Reasoning | Input        |
 | ------------------------------------------------------ | -------------- | ---------- | --------- | ------------ |
-| `hf:MiniMaxAI/MiniMax-M2.5`                            | 192,000        | 65,536     | no        | text         |
-| `hf:moonshotai/Kimi-K2-Thinking`                       | 256,000        | 8,192      | yes       | text         |
-| `hf:zai-org/GLM-4.7`                                   | 198,000        | 128,000    | no        | text         |
-| `hf:deepseek-ai/DeepSeek-R1-0528`                      | 128,000        | 8,192      | no        | text         |
-| `hf:deepseek-ai/DeepSeek-V3-0324`                      | 128,000        | 8,192      | no        | text         |
-| `hf:deepseek-ai/DeepSeek-V3.1`                         | 128,000        | 8,192      | no        | text         |
-| `hf:deepseek-ai/DeepSeek-V3.1-Terminus`                | 128,000        | 8,192      | no        | text         |
-| `hf:deepseek-ai/DeepSeek-V3.2`                         | 159,000        | 8,192      | no        | text         |
-| `hf:meta-llama/Llama-3.3-70B-Instruct`                 | 128,000        | 8,192      | no        | text         |
-| `hf:meta-llama/Llama-4-Maverick-17B-128E-Instruct-FP8` | 524,000        | 8,192      | no        | text         |
-| `hf:moonshotai/Kimi-K2-Instruct-0905`                  | 256,000        | 8,192      | no        | text         |
-| `hf:moonshotai/Kimi-K2.5`                              | 256,000        | 8,192      | yes       | text + image |
-| `hf:openai/gpt-oss-120b`                               | 128,000        | 8,192      | no        | text         |
-| `hf:Qwen/Qwen3-235B-A22B-Instruct-2507`                | 256,000        | 8,192      | no        | text         |
-| `hf:Qwen/Qwen3-Coder-480B-A35B-Instruct`               | 256,000        | 8,192      | no        | text         |
-| `hf:Qwen/Qwen3-VL-235B-A22B-Instruct`                  | 250,000        | 8,192      | no        | text + image |
-| `hf:zai-org/GLM-4.5`                                   | 128,000        | 128,000    | no        | text         |
-| `hf:zai-org/GLM-4.6`                                   | 198,000        | 128,000    | no        | text         |
-| `hf:zai-org/GLM-5`                                     | 256,000        | 128,000    | yes       | text + image |
-| `hf:deepseek-ai/DeepSeek-V3`                           | 128,000        | 8,192      | no        | text         |
-| `hf:Qwen/Qwen3-235B-A22B-Thinking-2507`                | 256,000        | 8,192      | yes       | text         |
+| `hf:MiniMaxAI/MiniMax-M2.5`                            | 192000         | 65536      | false     | text         |
+| `hf:moonshotai/Kimi-K2-Thinking`                       | 256000         | 8192       | true      | text         |
+| `hf:zai-org/GLM-4.7`                                   | 198000         | 128000     | false     | text         |
+| `hf:deepseek-ai/DeepSeek-R1-0528`                      | 128000         | 8192       | false     | text         |
+| `hf:deepseek-ai/DeepSeek-V3-0324`                      | 128000         | 8192       | false     | text         |
+| `hf:deepseek-ai/DeepSeek-V3.1`                         | 128000         | 8192       | false     | text         |
+| `hf:deepseek-ai/DeepSeek-V3.1-Terminus`                | 128000         | 8192       | false     | text         |
+| `hf:deepseek-ai/DeepSeek-V3.2`                         | 159000         | 8192       | false     | text         |
+| `hf:meta-llama/Llama-3.3-70B-Instruct`                 | 128000         | 8192       | false     | text         |
+| `hf:meta-llama/Llama-4-Maverick-17B-128E-Instruct-FP8` | 524000         | 8192       | false     | text         |
+| `hf:moonshotai/Kimi-K2-Instruct-0905`                  | 256000         | 8192       | false     | text         |
+| `hf:moonshotai/Kimi-K2.5`                              | 256000         | 8192       | true      | text + image |
+| `hf:openai/gpt-oss-120b`                               | 128000         | 8192       | false     | text         |
+| `hf:Qwen/Qwen3-235B-A22B-Instruct-2507`                | 256000         | 8192       | false     | text         |
+| `hf:Qwen/Qwen3-Coder-480B-A35B-Instruct`               | 256000         | 8192       | false     | text         |
+| `hf:Qwen/Qwen3-VL-235B-A22B-Instruct`                  | 250000         | 8192       | false     | text + image |
+| `hf:zai-org/GLM-4.5`                                   | 128000         | 128000     | false     | text         |
+| `hf:zai-org/GLM-4.6`                                   | 198000         | 128000     | false     | text         |
+| `hf:zai-org/GLM-5`                                     | 256000         | 128000     | true      | text + image |
+| `hf:deepseek-ai/DeepSeek-V3`                           | 128000         | 8192       | false     | text         |
+| `hf:Qwen/Qwen3-235B-A22B-Thinking-2507`                | 256000         | 8192       | true      | text         |
 
-<Tip>
-Model refs use the form `synthetic/<modelId>`. Use
-`openclaw models list --provider synthetic` to see all models available on your
-account.
-</Tip>
+## Notes
 
-<AccordionGroup>
-  <Accordion title="Model allowlist">
-    If you enable a model allowlist (`agents.defaults.models`), add every
-    Synthetic model you plan to use. Models not in the allowlist will be hidden
-    from the agent.
-  </Accordion>
-
-  <Accordion title="Base URL override">
-    If Synthetic changes its API endpoint, override the base URL in your config:
-
-    ```json5
-    {
-      models: {
-        providers: {
-          synthetic: {
-            baseUrl: "https://new-api.synthetic.new/anthropic",
-          },
-        },
-      },
-    }
-    ```
-
-    Remember that OpenClaw appends `/v1` automatically.
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Provider rules, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider settings.
-  </Card>
-  <Card title="Synthetic" href="https://synthetic.new" icon="arrow-up-right-from-square">
-    Synthetic dashboard and API docs.
-  </Card>
-</CardGroup>
+- Model refs use `synthetic/<modelId>`.
+- If you enable a model allowlist (`agents.defaults.models`), add every model you
+  plan to use.
+- See [Model providers](/concepts/model-providers) for provider rules.

docs/providers/together.md

@@ -8,42 +8,34 @@ read_when:
 
 # Together AI
 
-[Together AI](https://together.ai) provides access to leading open-source
-models including Llama, DeepSeek, Kimi, and more through a unified API.
+The [Together AI](https://together.ai) provides access to leading open-source models including Llama, DeepSeek, Kimi, and more through a unified API.
 
-| Property | Value                         |
-| -------- | ----------------------------- |
-| Provider | `together`                    |
-| Auth     | `TOGETHER_API_KEY`            |
-| API      | OpenAI-compatible             |
-| Base URL | `https://api.together.xyz/v1` |
+- Provider: `together`
+- Auth: `TOGETHER_API_KEY`
+- API: OpenAI-compatible
+- Base URL: `https://api.together.xyz/v1`
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Get an API key">
-    Create an API key at
-    [api.together.ai/settings/api-keys](https://api.together.ai/settings/api-keys).
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice together-api-key
-    ```
-  </Step>
-  <Step title="Set a default model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "together/moonshotai/Kimi-K2.5" },
-        },
-      },
-    }
-    ```
-  </Step>
-</Steps>
+1. Set the API key (recommended: store it for the Gateway):
 
-### Non-interactive example
+```bash
+openclaw onboard --auth-choice together-api-key
+```
+
+2. Set a default model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "together/moonshotai/Kimi-K2.5" },
+    },
+  },
+}
+```
+
+## Non-interactive example
 
 ```bash
 openclaw onboard --non-interactive \
@@ -52,14 +44,17 @@ openclaw onboard --non-interactive \
   --together-api-key "$TOGETHER_API_KEY"
 ```
 
-<Note>
-The onboarding preset sets `together/moonshotai/Kimi-K2.5` as the default
-model.
-</Note>
+This will set `together/moonshotai/Kimi-K2.5` as the default model.
+
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure `TOGETHER_API_KEY`
+is available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).
 
 ## Built-in catalog
 
-OpenClaw ships this bundled Together catalog:
+OpenClaw currently ships this bundled Together catalog:
 
 | Model ref                                                    | Name                                   | Input       | Context    | Notes                            |
 | ------------------------------------------------------------ | -------------------------------------- | ----------- | ---------- | -------------------------------- |
@@ -72,16 +67,16 @@ OpenClaw ships this bundled Together catalog:
 | `together/deepseek-ai/DeepSeek-R1`                           | DeepSeek R1                            | text        | 131,072    | Reasoning model                  |
 | `together/moonshotai/Kimi-K2-Instruct-0905`                  | Kimi K2-Instruct 0905                  | text        | 262,144    | Secondary Kimi text model        |
 
+The onboarding preset sets `together/moonshotai/Kimi-K2.5` as the default model.
+
 ## Video generation
 
 The bundled `together` plugin also registers video generation through the
 shared `video_generate` tool.
 
-| Property             | Value                                 |
-| -------------------- | ------------------------------------- |
-| Default video model  | `together/Wan-AI/Wan2.2-T2V-A14B`     |
-| Modes                | text-to-video, single-image reference |
-| Supported parameters | `aspectRatio`, `resolution`           |
+- Default video model: `together/Wan-AI/Wan2.2-T2V-A14B`
+- Modes: text-to-video and single-image reference flows
+- Supports `aspectRatio` and `resolution`
 
 To use Together as the default video provider:
 
@@ -97,46 +92,5 @@ To use Together as the default video provider:
 }
 ```
 
-<Tip>
-See [Video Generation](/tools/video-generation) for the shared tool parameters,
-provider selection, and failover behavior.
-</Tip>
-
-<AccordionGroup>
-  <Accordion title="Environment note">
-    If the Gateway runs as a daemon (launchd/systemd), make sure
-    `TOGETHER_API_KEY` is available to that process (for example, in
-    `~/.openclaw/.env` or via `env.shellEnv`).
-
-    <Warning>
-    Keys set only in your interactive shell are not visible to daemon-managed
-    gateway processes. Use `~/.openclaw/.env` or `env.shellEnv` config for
-    persistent availability.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="Troubleshooting">
-    - Verify your key works: `openclaw models list --provider together`
-    - If models are not appearing, confirm the API key is set in the correct
-      environment for your Gateway process.
-    - Model refs use the form `together/<model-id>`.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model providers" href="/concepts/model-providers" icon="layers">
-    Provider rules, model refs, and failover behavior.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video generation tool parameters and provider selection.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference" icon="gear">
-    Full config schema including provider settings.
-  </Card>
-  <Card title="Together AI" href="https://together.ai" icon="arrow-up-right-from-square">
-    Together AI dashboard, API docs, and pricing.
-  </Card>
-</CardGroup>
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.

docs/providers/venice.md

@@ -6,9 +6,11 @@ read_when:
 title: "Venice AI"
 ---
 
-# Venice AI
+# Venice AI (Venice highlight)
 
-Venice AI provides **privacy-focused AI inference** with support for uncensored models and access to major proprietary models through their anonymized proxy. All inference is private by default — no training on your data, no logging.
+**Venice** is our highlight Venice setup for privacy-first inference with optional anonymized access to proprietary models.
+
+Venice AI provides privacy-focused AI inference with support for uncensored models and access to major proprietary models through their anonymized proxy. All inference is private by default—no training on your data, no logging.
 
 ## Why Venice in OpenClaw
 
@@ -17,7 +19,7 @@ Venice AI provides **privacy-focused AI inference** with support for uncensored
 - **Anonymized access** to proprietary models (Opus/GPT/Gemini) when quality matters.
 - OpenAI-compatible `/v1` endpoints.
 
-## Privacy modes
+## Privacy Modes
 
 Venice offers two privacy levels — understanding this is key to choosing your model:
 
@@ -26,67 +28,61 @@ Venice offers two privacy levels — understanding this is key to choosing your
 | **Private**    | Fully private. Prompts/responses are **never stored or logged**. Ephemeral.                                                       | Llama, Qwen, DeepSeek, Kimi, MiniMax, Venice Uncensored, etc. |
 | **Anonymized** | Proxied through Venice with metadata stripped. The underlying provider (OpenAI, Anthropic, Google, xAI) sees anonymized requests. | Claude, GPT, Gemini, Grok                                     |
 
-<Warning>
-Anonymized models are **not** fully private. Venice strips metadata before forwarding, but the underlying provider (OpenAI, Anthropic, Google, xAI) still processes the request. Choose **Private** models when full privacy is required.
-</Warning>
-
 ## Features
 
 - **Privacy-focused**: Choose between "private" (fully private) and "anonymized" (proxied) modes
 - **Uncensored models**: Access to models without content restrictions
 - **Major model access**: Use Claude, GPT, Gemini, and Grok via Venice's anonymized proxy
 - **OpenAI-compatible API**: Standard `/v1` endpoints for easy integration
-- **Streaming**: Supported on all models
-- **Function calling**: Supported on select models (check model capabilities)
-- **Vision**: Supported on models with vision capability
+- **Streaming**: ✅ Supported on all models
+- **Function calling**: ✅ Supported on select models (check model capabilities)
+- **Vision**: ✅ Supported on models with vision capability
 - **No hard rate limits**: Fair-use throttling may apply for extreme usage
 
-## Getting started
+## Setup
 
-<Steps>
-  <Step title="Get your API key">
-    1. Sign up at [venice.ai](https://venice.ai)
-    2. Go to **Settings > API Keys > Create new key**
-    3. Copy your API key (format: `vapi_xxxxxxxxxxxx`)
-  </Step>
-  <Step title="Configure OpenClaw">
-    Choose your preferred setup method:
+### 1. Get API Key
 
-    <Tabs>
-      <Tab title="Interactive (recommended)">
-        ```bash
-        openclaw onboard --auth-choice venice-api-key
-        ```
+1. Sign up at [venice.ai](https://venice.ai)
+2. Go to **Settings → API Keys → Create new key**
+3. Copy your API key (format: `vapi_xxxxxxxxxxxx`)
 
-        This will:
-        1. Prompt for your API key (or use existing `VENICE_API_KEY`)
-        2. Show all available Venice models
-        3. Let you pick your default model
-        4. Configure the provider automatically
-      </Tab>
-      <Tab title="Environment variable">
-        ```bash
-        export VENICE_API_KEY="vapi_xxxxxxxxxxxx"
-        ```
-      </Tab>
-      <Tab title="Non-interactive">
-        ```bash
-        openclaw onboard --non-interactive \
-          --auth-choice venice-api-key \
-          --venice-api-key "vapi_xxxxxxxxxxxx"
-        ```
-      </Tab>
-    </Tabs>
+### 2. Configure OpenClaw
 
-  </Step>
-  <Step title="Verify setup">
-    ```bash
-    openclaw agent --model venice/kimi-k2-5 --message "Hello, are you working?"
-    ```
-  </Step>
-</Steps>
+**Option A: Environment Variable**
 
-## Model selection
+```bash
+export VENICE_API_KEY="vapi_xxxxxxxxxxxx"
+```
+
+**Option B: Interactive Setup (Recommended)**
+
+```bash
+openclaw onboard --auth-choice venice-api-key
+```
+
+This will:
+
+1. Prompt for your API key (or use existing `VENICE_API_KEY`)
+2. Show all available Venice models
+3. Let you pick your default model
+4. Configure the provider automatically
+
+**Option C: Non-interactive**
+
+```bash
+openclaw onboard --non-interactive \
+  --auth-choice venice-api-key \
+  --venice-api-key "vapi_xxxxxxxxxxxx"
+```
+
+### 3. Verify Setup
+
+```bash
+openclaw agent --model venice/kimi-k2-5 --message "Hello, are you working?"
+```
+
+## Model Selection
 
 After setup, OpenClaw shows all available Venice models. Pick based on your needs:
 
@@ -108,10 +104,13 @@ List all available models:
 openclaw models list | grep venice
 ```
 
-You can also run `openclaw configure`, select **Model/auth**, and choose **Venice AI**.
+## Configure via `openclaw configure`
 
-<Tip>
-Use the table below to pick the right model for your use case.
+1. Run `openclaw configure`
+2. Select **Model/auth**
+3. Choose **Venice AI**
+
+## Which Model Should I Use?
 
 | Use Case                   | Recommended Model                | Why                                          |
 | -------------------------- | -------------------------------- | -------------------------------------------- |
@@ -123,77 +122,73 @@ Use the table below to pick the right model for your use case.
 | **Complex private tasks**  | `deepseek-v3.2`                  | Strong reasoning, but no Venice tool support |
 | **Uncensored**             | `venice-uncensored`              | No content restrictions                      |
 
-</Tip>
+## Available Models (41 Total)
 
-## Available models (41 total)
+### Private Models (26) - Fully Private, No Logging
 
-<AccordionGroup>
-  <Accordion title="Private models (26) — fully private, no logging">
-    | Model ID                               | Name                                | Context | Features                   |
-    | -------------------------------------- | ----------------------------------- | ------- | -------------------------- |
-    | `kimi-k2-5`                            | Kimi K2.5                           | 256k    | Default, reasoning, vision |
-    | `kimi-k2-thinking`                     | Kimi K2 Thinking                    | 256k    | Reasoning                  |
-    | `llama-3.3-70b`                        | Llama 3.3 70B                       | 128k    | General                    |
-    | `llama-3.2-3b`                         | Llama 3.2 3B                        | 128k    | General                    |
-    | `hermes-3-llama-3.1-405b`              | Hermes 3 Llama 3.1 405B            | 128k    | General, tools disabled    |
-    | `qwen3-235b-a22b-thinking-2507`        | Qwen3 235B Thinking                | 128k    | Reasoning                  |
-    | `qwen3-235b-a22b-instruct-2507`        | Qwen3 235B Instruct                | 128k    | General                    |
-    | `qwen3-coder-480b-a35b-instruct`       | Qwen3 Coder 480B                   | 256k    | Coding                     |
-    | `qwen3-coder-480b-a35b-instruct-turbo` | Qwen3 Coder 480B Turbo             | 256k    | Coding                     |
-    | `qwen3-5-35b-a3b`                      | Qwen3.5 35B A3B                    | 256k    | Reasoning, vision          |
-    | `qwen3-next-80b`                       | Qwen3 Next 80B                     | 256k    | General                    |
-    | `qwen3-vl-235b-a22b`                   | Qwen3 VL 235B (Vision)             | 256k    | Vision                     |
-    | `qwen3-4b`                             | Venice Small (Qwen3 4B)            | 32k     | Fast, reasoning            |
-    | `deepseek-v3.2`                        | DeepSeek V3.2                      | 160k    | Reasoning, tools disabled  |
-    | `venice-uncensored`                    | Venice Uncensored (Dolphin-Mistral) | 32k     | Uncensored, tools disabled |
-    | `mistral-31-24b`                       | Venice Medium (Mistral)            | 128k    | Vision                     |
-    | `google-gemma-3-27b-it`                | Google Gemma 3 27B Instruct        | 198k    | Vision                     |
-    | `openai-gpt-oss-120b`                  | OpenAI GPT OSS 120B               | 128k    | General                    |
-    | `nvidia-nemotron-3-nano-30b-a3b`       | NVIDIA Nemotron 3 Nano 30B         | 128k    | General                    |
-    | `olafangensan-glm-4.7-flash-heretic`   | GLM 4.7 Flash Heretic              | 128k    | Reasoning                  |
-    | `zai-org-glm-4.6`                      | GLM 4.6                            | 198k    | General                    |
-    | `zai-org-glm-4.7`                      | GLM 4.7                            | 198k    | Reasoning                  |
-    | `zai-org-glm-4.7-flash`                | GLM 4.7 Flash                      | 128k    | Reasoning                  |
-    | `zai-org-glm-5`                        | GLM 5                              | 198k    | Reasoning                  |
-    | `minimax-m21`                          | MiniMax M2.1                       | 198k    | Reasoning                  |
-    | `minimax-m25`                          | MiniMax M2.5                       | 198k    | Reasoning                  |
-  </Accordion>
+| Model ID                               | Name                                | Context | Features                   |
+| -------------------------------------- | ----------------------------------- | ------- | -------------------------- |
+| `kimi-k2-5`                            | Kimi K2.5                           | 256k    | Default, reasoning, vision |
+| `kimi-k2-thinking`                     | Kimi K2 Thinking                    | 256k    | Reasoning                  |
+| `llama-3.3-70b`                        | Llama 3.3 70B                       | 128k    | General                    |
+| `llama-3.2-3b`                         | Llama 3.2 3B                        | 128k    | General                    |
+| `hermes-3-llama-3.1-405b`              | Hermes 3 Llama 3.1 405B             | 128k    | General, tools disabled    |
+| `qwen3-235b-a22b-thinking-2507`        | Qwen3 235B Thinking                 | 128k    | Reasoning                  |
+| `qwen3-235b-a22b-instruct-2507`        | Qwen3 235B Instruct                 | 128k    | General                    |
+| `qwen3-coder-480b-a35b-instruct`       | Qwen3 Coder 480B                    | 256k    | Coding                     |
+| `qwen3-coder-480b-a35b-instruct-turbo` | Qwen3 Coder 480B Turbo              | 256k    | Coding                     |
+| `qwen3-5-35b-a3b`                      | Qwen3.5 35B A3B                     | 256k    | Reasoning, vision          |
+| `qwen3-next-80b`                       | Qwen3 Next 80B                      | 256k    | General                    |
+| `qwen3-vl-235b-a22b`                   | Qwen3 VL 235B (Vision)              | 256k    | Vision                     |
+| `qwen3-4b`                             | Venice Small (Qwen3 4B)             | 32k     | Fast, reasoning            |
+| `deepseek-v3.2`                        | DeepSeek V3.2                       | 160k    | Reasoning, tools disabled  |
+| `venice-uncensored`                    | Venice Uncensored (Dolphin-Mistral) | 32k     | Uncensored, tools disabled |
+| `mistral-31-24b`                       | Venice Medium (Mistral)             | 128k    | Vision                     |
+| `google-gemma-3-27b-it`                | Google Gemma 3 27B Instruct         | 198k    | Vision                     |
+| `openai-gpt-oss-120b`                  | OpenAI GPT OSS 120B                 | 128k    | General                    |
+| `nvidia-nemotron-3-nano-30b-a3b`       | NVIDIA Nemotron 3 Nano 30B          | 128k    | General                    |
+| `olafangensan-glm-4.7-flash-heretic`   | GLM 4.7 Flash Heretic               | 128k    | Reasoning                  |
+| `zai-org-glm-4.6`                      | GLM 4.6                             | 198k    | General                    |
+| `zai-org-glm-4.7`                      | GLM 4.7                             | 198k    | Reasoning                  |
+| `zai-org-glm-4.7-flash`                | GLM 4.7 Flash                       | 128k    | Reasoning                  |
+| `zai-org-glm-5`                        | GLM 5                               | 198k    | Reasoning                  |
+| `minimax-m21`                          | MiniMax M2.1                        | 198k    | Reasoning                  |
+| `minimax-m25`                          | MiniMax M2.5                        | 198k    | Reasoning                  |
 
-  <Accordion title="Anonymized models (15) — via Venice proxy">
-    | Model ID                        | Name                           | Context | Features                  |
-    | ------------------------------- | ------------------------------ | ------- | ------------------------- |
-    | `claude-opus-4-6`               | Claude Opus 4.6 (via Venice)   | 1M      | Reasoning, vision         |
-    | `claude-opus-4-5`               | Claude Opus 4.5 (via Venice)   | 198k    | Reasoning, vision         |
-    | `claude-sonnet-4-6`             | Claude Sonnet 4.6 (via Venice) | 1M      | Reasoning, vision         |
-    | `claude-sonnet-4-5`             | Claude Sonnet 4.5 (via Venice) | 198k    | Reasoning, vision         |
-    | `openai-gpt-54`                 | GPT-5.4 (via Venice)           | 1M      | Reasoning, vision         |
-    | `openai-gpt-53-codex`           | GPT-5.3 Codex (via Venice)     | 400k    | Reasoning, vision, coding |
-    | `openai-gpt-52`                 | GPT-5.2 (via Venice)           | 256k    | Reasoning                 |
-    | `openai-gpt-52-codex`           | GPT-5.2 Codex (via Venice)     | 256k    | Reasoning, vision, coding |
-    | `openai-gpt-4o-2024-11-20`      | GPT-4o (via Venice)            | 128k    | Vision                    |
-    | `openai-gpt-4o-mini-2024-07-18` | GPT-4o Mini (via Venice)       | 128k    | Vision                    |
-    | `gemini-3-1-pro-preview`        | Gemini 3.1 Pro (via Venice)    | 1M      | Reasoning, vision         |
-    | `gemini-3-pro-preview`          | Gemini 3 Pro (via Venice)      | 198k    | Reasoning, vision         |
-    | `gemini-3-flash-preview`        | Gemini 3 Flash (via Venice)    | 256k    | Reasoning, vision         |
-    | `grok-41-fast`                  | Grok 4.1 Fast (via Venice)     | 1M      | Reasoning, vision         |
-    | `grok-code-fast-1`              | Grok Code Fast 1 (via Venice)  | 256k    | Reasoning, coding         |
-  </Accordion>
-</AccordionGroup>
+### Anonymized Models (15) - Via Venice Proxy
 
-## Model discovery
+| Model ID                        | Name                           | Context | Features                  |
+| ------------------------------- | ------------------------------ | ------- | ------------------------- |
+| `claude-opus-4-6`               | Claude Opus 4.6 (via Venice)   | 1M      | Reasoning, vision         |
+| `claude-opus-4-5`               | Claude Opus 4.5 (via Venice)   | 198k    | Reasoning, vision         |
+| `claude-sonnet-4-6`             | Claude Sonnet 4.6 (via Venice) | 1M      | Reasoning, vision         |
+| `claude-sonnet-4-5`             | Claude Sonnet 4.5 (via Venice) | 198k    | Reasoning, vision         |
+| `openai-gpt-54`                 | GPT-5.4 (via Venice)           | 1M      | Reasoning, vision         |
+| `openai-gpt-53-codex`           | GPT-5.3 Codex (via Venice)     | 400k    | Reasoning, vision, coding |
+| `openai-gpt-52`                 | GPT-5.2 (via Venice)           | 256k    | Reasoning                 |
+| `openai-gpt-52-codex`           | GPT-5.2 Codex (via Venice)     | 256k    | Reasoning, vision, coding |
+| `openai-gpt-4o-2024-11-20`      | GPT-4o (via Venice)            | 128k    | Vision                    |
+| `openai-gpt-4o-mini-2024-07-18` | GPT-4o Mini (via Venice)       | 128k    | Vision                    |
+| `gemini-3-1-pro-preview`        | Gemini 3.1 Pro (via Venice)    | 1M      | Reasoning, vision         |
+| `gemini-3-pro-preview`          | Gemini 3 Pro (via Venice)      | 198k    | Reasoning, vision         |
+| `gemini-3-flash-preview`        | Gemini 3 Flash (via Venice)    | 256k    | Reasoning, vision         |
+| `grok-41-fast`                  | Grok 4.1 Fast (via Venice)     | 1M      | Reasoning, vision         |
+| `grok-code-fast-1`              | Grok Code Fast 1 (via Venice)  | 256k    | Reasoning, coding         |
+
+## Model Discovery
 
 OpenClaw automatically discovers models from the Venice API when `VENICE_API_KEY` is set. If the API is unreachable, it falls back to a static catalog.
 
 The `/models` endpoint is public (no auth needed for listing), but inference requires a valid API key.
 
-## Streaming and tool support
+## Streaming & Tool Support
 
-| Feature              | Support                                              |
-| -------------------- | ---------------------------------------------------- |
-| **Streaming**        | All models                                           |
-| **Function calling** | Most models (check `supportsFunctionCalling` in API) |
-| **Vision/Images**    | Models marked with "Vision" feature                  |
-| **JSON mode**        | Supported via `response_format`                      |
+| Feature              | Support                                                 |
+| -------------------- | ------------------------------------------------------- |
+| **Streaming**        | ✅ All models                                           |
+| **Function calling** | ✅ Most models (check `supportsFunctionCalling` in API) |
+| **Vision/Images**    | ✅ Models marked with "Vision" feature                  |
+| **JSON mode**        | ✅ Supported via `response_format`                      |
 
 ## Pricing
 
@@ -202,7 +197,7 @@ Venice uses a credit-based system. Check [venice.ai/pricing](https://venice.ai/p
 - **Private models**: Generally lower cost
 - **Anonymized models**: Similar to direct API pricing + small Venice fee
 
-### Venice (anonymized) vs direct API
+## Comparison: Venice vs Direct API
 
 | Aspect       | Venice (Anonymized)           | Direct API          |
 | ------------ | ----------------------------- | ------------------- |
@@ -211,7 +206,7 @@ Venice uses a credit-based system. Check [venice.ai/pricing](https://venice.ai/p
 | **Features** | Most features supported       | Full features       |
 | **Billing**  | Venice credits                | Provider billing    |
 
-## Usage examples
+## Usage Examples
 
 ```bash
 # Use the default private model
@@ -232,77 +227,56 @@ openclaw agent --model venice/qwen3-coder-480b-a35b-instruct --message "Refactor
 
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="API key not recognized">
-    ```bash
-    echo $VENICE_API_KEY
-    openclaw models list | grep venice
-    ```
+### API key not recognized
 
-    Ensure the key starts with `vapi_`.
+```bash
+echo $VENICE_API_KEY
+openclaw models list | grep venice
+```
 
-  </Accordion>
+Ensure the key starts with `vapi_`.
 
-  <Accordion title="Model not available">
-    The Venice model catalog updates dynamically. Run `openclaw models list` to see currently available models. Some models may be temporarily offline.
-  </Accordion>
+### Model not available
 
-  <Accordion title="Connection issues">
-    Venice API is at `https://api.venice.ai/api/v1`. Ensure your network allows HTTPS connections.
-  </Accordion>
-</AccordionGroup>
+The Venice model catalog updates dynamically. Run `openclaw models list` to see currently available models. Some models may be temporarily offline.
 
-<Note>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Note>
+### Connection issues
 
-## Advanced configuration
+Venice API is at `https://api.venice.ai/api/v1`. Ensure your network allows HTTPS connections.
 
-<AccordionGroup>
-  <Accordion title="Config file example">
-    ```json5
-    {
-      env: { VENICE_API_KEY: "vapi_..." },
-      agents: { defaults: { model: { primary: "venice/kimi-k2-5" } } },
-      models: {
-        mode: "merge",
-        providers: {
-          venice: {
-            baseUrl: "https://api.venice.ai/api/v1",
-            apiKey: "${VENICE_API_KEY}",
-            api: "openai-completions",
-            models: [
-              {
-                id: "kimi-k2-5",
-                name: "Kimi K2.5",
-                reasoning: true,
-                input: ["text", "image"],
-                cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
-                contextWindow: 256000,
-                maxTokens: 65536,
-              },
-            ],
+## Config file example
+
+```json5
+{
+  env: { VENICE_API_KEY: "vapi_..." },
+  agents: { defaults: { model: { primary: "venice/kimi-k2-5" } } },
+  models: {
+    mode: "merge",
+    providers: {
+      venice: {
+        baseUrl: "https://api.venice.ai/api/v1",
+        apiKey: "${VENICE_API_KEY}",
+        api: "openai-completions",
+        models: [
+          {
+            id: "kimi-k2-5",
+            name: "Kimi K2.5",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 256000,
+            maxTokens: 65536,
           },
-        },
+        ],
       },
-    }
-    ```
-  </Accordion>
-</AccordionGroup>
+    },
+  },
+}
+```
 
-## Related
+## Links
 
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Venice AI" href="https://venice.ai" icon="globe">
-    Venice AI homepage and account signup.
-  </Card>
-  <Card title="API documentation" href="https://docs.venice.ai" icon="book">
-    Venice API reference and developer docs.
-  </Card>
-  <Card title="Pricing" href="https://venice.ai/pricing" icon="credit-card">
-    Current Venice credit rates and plans.
-  </Card>
-</CardGroup>
+- [Venice AI](https://venice.ai)
+- [API Documentation](https://docs.venice.ai)
+- [Pricing](https://venice.ai/pricing)
+- [Status](https://status.venice.ai)

docs/providers/vercel-ai-gateway.md

@@ -8,58 +8,36 @@ read_when:
 
 # Vercel AI Gateway
 
-The [Vercel AI Gateway](https://vercel.com/ai-gateway) provides a unified API to
-access hundreds of models through a single endpoint.
+The [Vercel AI Gateway](https://vercel.com/ai-gateway) provides a unified API to access hundreds of models through a single endpoint.
 
-| Property      | Value                            |
-| ------------- | -------------------------------- |
-| Provider      | `vercel-ai-gateway`              |
-| Auth          | `AI_GATEWAY_API_KEY`             |
-| API           | Anthropic Messages compatible    |
-| Model catalog | Auto-discovered via `/v1/models` |
+- Provider: `vercel-ai-gateway`
+- Auth: `AI_GATEWAY_API_KEY`
+- API: Anthropic Messages compatible
+- OpenClaw auto-discovers the Gateway `/v1/models` catalog, so `/models vercel-ai-gateway`
+  includes current model refs such as `vercel-ai-gateway/openai/gpt-5.4`.
 
-<Tip>
-OpenClaw auto-discovers the Gateway `/v1/models` catalog, so
-`/models vercel-ai-gateway` includes current model refs such as
-`vercel-ai-gateway/openai/gpt-5.4`.
-</Tip>
+## Quick start
 
-## Getting started
+1. Set the API key (recommended: store it for the Gateway):
 
-<Steps>
-  <Step title="Set the API key">
-    Run onboarding and choose the AI Gateway auth option:
+```bash
+openclaw onboard --auth-choice ai-gateway-api-key
+```
 
-    ```bash
-    openclaw onboard --auth-choice ai-gateway-api-key
-    ```
+2. Set a default model:
 
-  </Step>
-  <Step title="Set a default model">
-    Add the model to your OpenClaw config:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "vercel-ai-gateway/anthropic/claude-opus-4.6" },
-        },
-      },
-    }
-    ```
-
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider vercel-ai-gateway
-    ```
-  </Step>
-</Steps>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "vercel-ai-gateway/anthropic/claude-opus-4.6" },
+    },
+  },
+}
+```
 
 ## Non-interactive example
 
-For scripted or CI setups, pass all values on the command line:
-
 ```bash
 openclaw onboard --non-interactive \
   --mode local \
@@ -67,53 +45,16 @@ openclaw onboard --non-interactive \
   --ai-gateway-api-key "$AI_GATEWAY_API_KEY"
 ```
 
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure `AI_GATEWAY_API_KEY`
+is available to that process (for example, in `~/.openclaw/.env` or via
+`env.shellEnv`).
+
 ## Model ID shorthand
 
 OpenClaw accepts Vercel Claude shorthand model refs and normalizes them at
 runtime:
 
-| Shorthand input                     | Normalized model ref                          |
-| ----------------------------------- | --------------------------------------------- |
-| `vercel-ai-gateway/claude-opus-4.6` | `vercel-ai-gateway/anthropic/claude-opus-4.6` |
-| `vercel-ai-gateway/opus-4.6`        | `vercel-ai-gateway/anthropic/claude-opus-4-6` |
-
-<Tip>
-You can use either the shorthand or the fully qualified model ref in your
-configuration. OpenClaw resolves the canonical form automatically.
-</Tip>
-
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Environment variable for daemon processes">
-    If the OpenClaw Gateway runs as a daemon (launchd/systemd), make sure
-    `AI_GATEWAY_API_KEY` is available to that process.
-
-    <Warning>
-    A key set only in `~/.profile` will not be visible to a launchd/systemd
-    daemon unless that environment is explicitly imported. Set the key in
-    `~/.openclaw/.env` or via `env.shellEnv` to ensure the gateway process can
-    read it.
-    </Warning>
-
-  </Accordion>
-
-  <Accordion title="Provider routing">
-    Vercel AI Gateway routes requests to the upstream provider based on the model
-    ref prefix. For example, `vercel-ai-gateway/anthropic/claude-opus-4.6` routes
-    through Anthropic, while `vercel-ai-gateway/openai/gpt-5.4` routes through
-    OpenAI. Your single `AI_GATEWAY_API_KEY` handles authentication for all
-    upstream providers.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    General troubleshooting and FAQ.
-  </Card>
-</CardGroup>
+- `vercel-ai-gateway/claude-opus-4.6` -> `vercel-ai-gateway/anthropic/claude-opus-4.6`
+- `vercel-ai-gateway/opus-4.6` -> `vercel-ai-gateway/anthropic/claude-opus-4-6`

docs/providers/vllm.md

@@ -8,78 +8,53 @@ title: "vLLM"
 
 # vLLM
 
-vLLM can serve open-source (and some custom) models via an **OpenAI-compatible** HTTP API. OpenClaw connects to vLLM using the `openai-completions` API.
+vLLM can serve open-source (and some custom) models via an **OpenAI-compatible** HTTP API. OpenClaw can connect to vLLM using the `openai-completions` API.
 
-OpenClaw can also **auto-discover** available models from vLLM when you opt in with `VLLM_API_KEY` (any value works if your server does not enforce auth) and you do not define an explicit `models.providers.vllm` entry.
+OpenClaw can also **auto-discover** available models from vLLM when you opt in with `VLLM_API_KEY` (any value works if your server doesn’t enforce auth) and you do not define an explicit `models.providers.vllm` entry.
 
-| Property         | Value                                    |
-| ---------------- | ---------------------------------------- |
-| Provider ID      | `vllm`                                   |
-| API              | `openai-completions` (OpenAI-compatible) |
-| Auth             | `VLLM_API_KEY` environment variable      |
-| Default base URL | `http://127.0.0.1:8000/v1`               |
+## Quick start
 
-## Getting started
+1. Start vLLM with an OpenAI-compatible server.
 
-<Steps>
-  <Step title="Start vLLM with an OpenAI-compatible server">
-    Your base URL should expose `/v1` endpoints (e.g. `/v1/models`, `/v1/chat/completions`). vLLM commonly runs on:
+Your base URL should expose `/v1` endpoints (e.g. `/v1/models`, `/v1/chat/completions`). vLLM commonly runs on:
 
-    ```
-    http://127.0.0.1:8000/v1
-    ```
+- `http://127.0.0.1:8000/v1`
 
-  </Step>
-  <Step title="Set the API key environment variable">
-    Any value works if your server does not enforce auth:
+2. Opt in (any value works if no auth is configured):
 
-    ```bash
-    export VLLM_API_KEY="vllm-local"
-    ```
+```bash
+export VLLM_API_KEY="vllm-local"
+```
 
-  </Step>
-  <Step title="Select a model">
-    Replace with one of your vLLM model IDs:
+3. Select a model (replace with one of your vLLM model IDs):
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "vllm/your-model-id" },
-        },
-      },
-    }
-    ```
-
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider vllm
-    ```
-  </Step>
-</Steps>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "vllm/your-model-id" },
+    },
+  },
+}
+```
 
 ## Model discovery (implicit provider)
 
-When `VLLM_API_KEY` is set (or an auth profile exists) and you **do not** define `models.providers.vllm`, OpenClaw queries:
+When `VLLM_API_KEY` is set (or an auth profile exists) and you **do not** define `models.providers.vllm`, OpenClaw will query:
 
-```
-GET http://127.0.0.1:8000/v1/models
-```
+- `GET http://127.0.0.1:8000/v1/models`
 
-and converts the returned IDs into model entries.
+…and convert the returned IDs into model entries.
 
-<Note>
 If you set `models.providers.vllm` explicitly, auto-discovery is skipped and you must define models manually.
-</Note>
 
 ## Explicit configuration (manual models)
 
 Use explicit config when:
 
-- vLLM runs on a different host or port
-- You want to pin `contextWindow` or `maxTokens` values
-- Your server requires a real API key (or you want to control headers)
+- vLLM runs on a different host/port.
+- You want to pin `contextWindow`/`maxTokens` values.
+- Your server requires a real API key (or you want to control headers).
 
 ```json5
 {
@@ -106,99 +81,23 @@ Use explicit config when:
 }
 ```
 
-## Advanced notes
-
-<AccordionGroup>
-  <Accordion title="Proxy-style behavior">
-    vLLM is treated as a proxy-style OpenAI-compatible `/v1` backend, not a native
-    OpenAI endpoint. This means:
-
-    | Behavior | Applied? |
-    |----------|----------|
-    | Native OpenAI request shaping | No |
-    | `service_tier` | Not sent |
-    | Responses `store` | Not sent |
-    | Prompt-cache hints | Not sent |
-    | OpenAI reasoning-compat payload shaping | Not applied |
-    | Hidden OpenClaw attribution headers | Not injected on custom base URLs |
-
-  </Accordion>
-
-  <Accordion title="Custom base URL">
-    If your vLLM server runs on a non-default host or port, set `baseUrl` in the explicit provider config:
-
-    ```json5
-    {
-      models: {
-        providers: {
-          vllm: {
-            baseUrl: "http://192.168.1.50:9000/v1",
-            apiKey: "${VLLM_API_KEY}",
-            api: "openai-completions",
-            models: [
-              {
-                id: "my-custom-model",
-                name: "Remote vLLM Model",
-                reasoning: false,
-                input: ["text"],
-                contextWindow: 64000,
-                maxTokens: 4096,
-              },
-            ],
-          },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-</AccordionGroup>
-
 ## Troubleshooting
 
-<AccordionGroup>
-  <Accordion title="Server not reachable">
-    Check that the vLLM server is running and accessible:
+- Check the server is reachable:
 
-    ```bash
-    curl http://127.0.0.1:8000/v1/models
-    ```
+```bash
+curl http://127.0.0.1:8000/v1/models
+```
 
-    If you see a connection error, verify the host, port, and that vLLM started with the OpenAI-compatible server mode.
+- If requests fail with auth errors, set a real `VLLM_API_KEY` that matches your server configuration, or configure the provider explicitly under `models.providers.vllm`.
 
-  </Accordion>
+## Proxy-style behavior
 
-  <Accordion title="Auth errors on requests">
-    If requests fail with auth errors, set a real `VLLM_API_KEY` that matches your server configuration, or configure the provider explicitly under `models.providers.vllm`.
+vLLM is treated as a proxy-style OpenAI-compatible `/v1` backend, not a native
+OpenAI endpoint.
 
-    <Tip>
-    If your vLLM server does not enforce auth, any non-empty value for `VLLM_API_KEY` works as an opt-in signal for OpenClaw.
-    </Tip>
-
-  </Accordion>
-
-  <Accordion title="No models discovered">
-    Auto-discovery requires `VLLM_API_KEY` to be set **and** no explicit `models.providers.vllm` config entry. If you have defined the provider manually, OpenClaw skips discovery and uses only your declared models.
-  </Accordion>
-</AccordionGroup>
-
-<Warning>
-More help: [Troubleshooting](/help/troubleshooting) and [FAQ](/help/faq).
-</Warning>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="OpenAI" href="/providers/openai" icon="bolt">
-    Native OpenAI provider and OpenAI-compatible route behavior.
-  </Card>
-  <Card title="OAuth and auth" href="/gateway/authentication" icon="key">
-    Auth details and credential reuse rules.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    Common issues and how to resolve them.
-  </Card>
-</CardGroup>
+- native OpenAI-only request shaping does not apply here
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden OpenClaw attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on custom vLLM base URLs

docs/providers/volcengine.md

@@ -12,46 +12,31 @@ The Volcengine provider gives access to Doubao models and third-party models
 hosted on Volcano Engine, with separate endpoints for general and coding
 workloads.
 
-| Detail    | Value                                               |
-| --------- | --------------------------------------------------- |
-| Providers | `volcengine` (general) + `volcengine-plan` (coding) |
-| Auth      | `VOLCANO_ENGINE_API_KEY`                            |
-| API       | OpenAI-compatible                                   |
+- Providers: `volcengine` (general) + `volcengine-plan` (coding)
+- Auth: `VOLCANO_ENGINE_API_KEY`
+- API: OpenAI-compatible
 
-## Getting started
+## Quick start
 
-<Steps>
-  <Step title="Set the API key">
-    Run interactive onboarding:
+1. Set the API key:
 
-    ```bash
-    openclaw onboard --auth-choice volcengine-api-key
-    ```
+```bash
+openclaw onboard --auth-choice volcengine-api-key
+```
 
-    This registers both the general (`volcengine`) and coding (`volcengine-plan`) providers from a single API key.
+2. Set a default model:
 
-  </Step>
-  <Step title="Set a default model">
-    ```json5
-    {
-      agents: {
-        defaults: {
-          model: { primary: "volcengine-plan/ark-code-latest" },
-        },
-      },
-    }
-    ```
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider volcengine
-    openclaw models list --provider volcengine-plan
-    ```
-  </Step>
-</Steps>
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "volcengine-plan/ark-code-latest" },
+    },
+  },
+}
+```
 
-<Tip>
-For non-interactive setup (CI, scripting), pass the key directly:
+## Non-interactive example
 
 ```bash
 openclaw onboard --non-interactive \
@@ -60,8 +45,6 @@ openclaw onboard --non-interactive \
   --volcengine-api-key "$VOLCANO_ENGINE_API_KEY"
 ```
 
-</Tip>
-
 ## Providers and endpoints
 
 | Provider          | Endpoint                                  | Use case       |
@@ -69,75 +52,43 @@ openclaw onboard --non-interactive \
 | `volcengine`      | `ark.cn-beijing.volces.com/api/v3`        | General models |
 | `volcengine-plan` | `ark.cn-beijing.volces.com/api/coding/v3` | Coding models  |
 
-<Note>
-Both providers are configured from a single API key. Setup registers both automatically.
-</Note>
+Both providers are configured from a single API key. Setup registers both
+automatically.
 
 ## Available models
 
-<Tabs>
-  <Tab title="General (volcengine)">
-    | Model ref                                    | Name                            | Input       | Context |
-    | -------------------------------------------- | ------------------------------- | ----------- | ------- |
-    | `volcengine/doubao-seed-1-8-251228`          | Doubao Seed 1.8                 | text, image | 256,000 |
-    | `volcengine/doubao-seed-code-preview-251028` | doubao-seed-code-preview-251028 | text, image | 256,000 |
-    | `volcengine/kimi-k2-5-260127`                | Kimi K2.5                       | text, image | 256,000 |
-    | `volcengine/glm-4-7-251222`                  | GLM 4.7                         | text, image | 200,000 |
-    | `volcengine/deepseek-v3-2-251201`            | DeepSeek V3.2                   | text, image | 128,000 |
-  </Tab>
-  <Tab title="Coding (volcengine-plan)">
-    | Model ref                                         | Name                     | Input | Context |
-    | ------------------------------------------------- | ------------------------ | ----- | ------- |
-    | `volcengine-plan/ark-code-latest`                 | Ark Coding Plan          | text  | 256,000 |
-    | `volcengine-plan/doubao-seed-code`                | Doubao Seed Code         | text  | 256,000 |
-    | `volcengine-plan/glm-4.7`                         | GLM 4.7 Coding           | text  | 200,000 |
-    | `volcengine-plan/kimi-k2-thinking`                | Kimi K2 Thinking         | text  | 256,000 |
-    | `volcengine-plan/kimi-k2.5`                       | Kimi K2.5 Coding         | text  | 256,000 |
-    | `volcengine-plan/doubao-seed-code-preview-251028` | Doubao Seed Code Preview | text  | 256,000 |
-  </Tab>
-</Tabs>
+General provider (`volcengine`):
 
-## Advanced notes
+| Model ref                                    | Name                            | Input       | Context |
+| -------------------------------------------- | ------------------------------- | ----------- | ------- |
+| `volcengine/doubao-seed-1-8-251228`          | Doubao Seed 1.8                 | text, image | 256,000 |
+| `volcengine/doubao-seed-code-preview-251028` | doubao-seed-code-preview-251028 | text, image | 256,000 |
+| `volcengine/kimi-k2-5-260127`                | Kimi K2.5                       | text, image | 256,000 |
+| `volcengine/glm-4-7-251222`                  | GLM 4.7                         | text, image | 200,000 |
+| `volcengine/deepseek-v3-2-251201`            | DeepSeek V3.2                   | text, image | 128,000 |
 
-<AccordionGroup>
-  <Accordion title="Default model after onboarding">
-    `openclaw onboard --auth-choice volcengine-api-key` currently sets
-    `volcengine-plan/ark-code-latest` as the default model while also registering
-    the general `volcengine` catalog.
-  </Accordion>
+Coding provider (`volcengine-plan`):
 
-  <Accordion title="Model picker fallback behavior">
-    During onboarding/configure model selection, the Volcengine auth choice prefers
-    both `volcengine/*` and `volcengine-plan/*` rows. If those models are not
-    loaded yet, OpenClaw falls back to the unfiltered catalog instead of showing an
-    empty provider-scoped picker.
-  </Accordion>
+| Model ref                                         | Name                     | Input | Context |
+| ------------------------------------------------- | ------------------------ | ----- | ------- |
+| `volcengine-plan/ark-code-latest`                 | Ark Coding Plan          | text  | 256,000 |
+| `volcengine-plan/doubao-seed-code`                | Doubao Seed Code         | text  | 256,000 |
+| `volcengine-plan/glm-4.7`                         | GLM 4.7 Coding           | text  | 200,000 |
+| `volcengine-plan/kimi-k2-thinking`                | Kimi K2 Thinking         | text  | 256,000 |
+| `volcengine-plan/kimi-k2.5`                       | Kimi K2.5 Coding         | text  | 256,000 |
+| `volcengine-plan/doubao-seed-code-preview-251028` | Doubao Seed Code Preview | text  | 256,000 |
 
-  <Accordion title="Environment variables for daemon processes">
-    If the Gateway runs as a daemon (launchd/systemd), make sure
-    `VOLCANO_ENGINE_API_KEY` is available to that process (for example, in
-    `~/.openclaw/.env` or via `env.shellEnv`).
-  </Accordion>
-</AccordionGroup>
+`openclaw onboard --auth-choice volcengine-api-key` currently sets
+`volcengine-plan/ark-code-latest` as the default model while also registering
+the general `volcengine` catalog.
 
-<Warning>
-When running OpenClaw as a background service, environment variables set in your
-interactive shell are not automatically inherited. See the daemon note above.
-</Warning>
+During onboarding/configure model selection, the Volcengine auth choice prefers
+both `volcengine/*` and `volcengine-plan/*` rows. If those models are not
+loaded yet, OpenClaw falls back to the unfiltered catalog instead of showing an
+empty provider-scoped picker.
 
-## Related
+## Environment note
 
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration" href="/configuration" icon="gear">
-    Full config reference for agents, models, and providers.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    Common issues and debugging steps.
-  </Card>
-  <Card title="FAQ" href="/help/faq" icon="circle-question">
-    Frequently asked questions about OpenClaw setup.
-  </Card>
-</CardGroup>
+If the Gateway runs as a daemon (launchd/systemd), make sure
+`VOLCANO_ENGINE_API_KEY` is available to that process (for example, in
+`~/.openclaw/.env` or via `env.shellEnv`).

docs/providers/vydra.md

@@ -10,165 +10,134 @@ title: "Vydra"
 
 The bundled Vydra plugin adds:
 
-- Image generation via `vydra/grok-imagine`
-- Video generation via `vydra/veo3` and `vydra/kling`
-- Speech synthesis via Vydra's ElevenLabs-backed TTS route
+- image generation via `vydra/grok-imagine`
+- video generation via `vydra/veo3` and `vydra/kling`
+- speech synthesis via Vydra's ElevenLabs-backed TTS route
 
 OpenClaw uses the same `VYDRA_API_KEY` for all three capabilities.
 
-<Warning>
-Use `https://www.vydra.ai/api/v1` as the base URL.
+## Important base URL
+
+Use `https://www.vydra.ai/api/v1`.
 
 Vydra's apex host (`https://vydra.ai/api/v1`) currently redirects to `www`. Some HTTP clients drop `Authorization` on that cross-host redirect, which turns a valid API key into a misleading auth failure. The bundled plugin uses the `www` base URL directly to avoid that.
-</Warning>
 
 ## Setup
 
-<Steps>
-  <Step title="Run interactive onboarding">
-    ```bash
-    openclaw onboard --auth-choice vydra-api-key
-    ```
+Interactive onboarding:
 
-    Or set the env var directly:
+```bash
+openclaw onboard --auth-choice vydra-api-key
+```
 
-    ```bash
-    export VYDRA_API_KEY="vydra_live_..."
-    ```
+Or set the env var directly:
 
-  </Step>
-  <Step title="Choose a default capability">
-    Pick one or more of the capabilities below (image, video, or speech) and apply the matching configuration.
-  </Step>
-</Steps>
+```bash
+export VYDRA_API_KEY="vydra_live_..."
+```
 
-## Capabilities
+## Image generation
 
-<AccordionGroup>
-  <Accordion title="Image generation">
-    Default image model:
+Default image model:
 
-    - `vydra/grok-imagine`
+- `vydra/grok-imagine`
 
-    Set it as the default image provider:
+Set it as the default image provider:
 
-    ```json5
-    {
-      agents: {
-        defaults: {
-          imageGenerationModel: {
-            primary: "vydra/grok-imagine",
-          },
+```json5
+{
+  agents: {
+    defaults: {
+      imageGenerationModel: {
+        primary: "vydra/grok-imagine",
+      },
+    },
+  },
+}
+```
+
+Current bundled support is text-to-image only. Vydra's hosted edit routes expect remote image URLs, and OpenClaw does not add a Vydra-specific upload bridge in the bundled plugin yet.
+
+See [Image Generation](/tools/image-generation) for shared tool behavior.
+
+## Video generation
+
+Registered video models:
+
+- `vydra/veo3` for text-to-video
+- `vydra/kling` for image-to-video
+
+Set Vydra as the default video provider:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "vydra/veo3",
+      },
+    },
+  },
+}
+```
+
+Notes:
+
+- `vydra/veo3` is bundled as text-to-video only.
+- `vydra/kling` currently requires a remote image URL reference. Local file uploads are rejected up front.
+- Vydra's current `kling` HTTP route has been inconsistent about whether it requires `image_url` or `video_url`; the bundled provider maps the same remote image URL into both fields.
+- The bundled plugin stays conservative and does not forward undocumented style knobs such as aspect ratio, resolution, watermark, or generated audio.
+
+Provider-specific live coverage:
+
+```bash
+OPENCLAW_LIVE_TEST=1 \
+OPENCLAW_LIVE_VYDRA_VIDEO=1 \
+pnpm test:live -- extensions/vydra/vydra.live.test.ts
+```
+
+The bundled Vydra live file now covers:
+
+- `vydra/veo3` text-to-video
+- `vydra/kling` image-to-video using a remote image URL
+
+Override the remote image fixture when needed:
+
+```bash
+export OPENCLAW_LIVE_VYDRA_KLING_IMAGE_URL="https://example.com/reference.png"
+```
+
+See [Video Generation](/tools/video-generation) for shared tool behavior.
+
+## Speech synthesis
+
+Set Vydra as the speech provider:
+
+```json5
+{
+  messages: {
+    tts: {
+      provider: "vydra",
+      providers: {
+        vydra: {
+          apiKey: "${VYDRA_API_KEY}",
+          voiceId: "21m00Tcm4TlvDq8ikWAM",
         },
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    Current bundled support is text-to-image only. Vydra's hosted edit routes expect remote image URLs, and OpenClaw does not add a Vydra-specific upload bridge in the bundled plugin yet.
+Defaults:
 
-    <Note>
-    See [Image Generation](/tools/image-generation) for shared tool parameters, provider selection, and failover behavior.
-    </Note>
+- model: `elevenlabs/tts`
+- voice id: `21m00Tcm4TlvDq8ikWAM`
 
-  </Accordion>
-
-  <Accordion title="Video generation">
-    Registered video models:
-
-    - `vydra/veo3` for text-to-video
-    - `vydra/kling` for image-to-video
-
-    Set Vydra as the default video provider:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "vydra/veo3",
-          },
-        },
-      },
-    }
-    ```
-
-    Notes:
-
-    - `vydra/veo3` is bundled as text-to-video only.
-    - `vydra/kling` currently requires a remote image URL reference. Local file uploads are rejected up front.
-    - Vydra's current `kling` HTTP route has been inconsistent about whether it requires `image_url` or `video_url`; the bundled provider maps the same remote image URL into both fields.
-    - The bundled plugin stays conservative and does not forward undocumented style knobs such as aspect ratio, resolution, watermark, or generated audio.
-
-    <Note>
-    See [Video Generation](/tools/video-generation) for shared tool parameters, provider selection, and failover behavior.
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Video live tests">
-    Provider-specific live coverage:
-
-    ```bash
-    OPENCLAW_LIVE_TEST=1 \
-    OPENCLAW_LIVE_VYDRA_VIDEO=1 \
-    pnpm test:live -- extensions/vydra/vydra.live.test.ts
-    ```
-
-    The bundled Vydra live file now covers:
-
-    - `vydra/veo3` text-to-video
-    - `vydra/kling` image-to-video using a remote image URL
-
-    Override the remote image fixture when needed:
-
-    ```bash
-    export OPENCLAW_LIVE_VYDRA_KLING_IMAGE_URL="https://example.com/reference.png"
-    ```
-
-  </Accordion>
-
-  <Accordion title="Speech synthesis">
-    Set Vydra as the speech provider:
-
-    ```json5
-    {
-      messages: {
-        tts: {
-          provider: "vydra",
-          providers: {
-            vydra: {
-              apiKey: "${VYDRA_API_KEY}",
-              voiceId: "21m00Tcm4TlvDq8ikWAM",
-            },
-          },
-        },
-      },
-    }
-    ```
-
-    Defaults:
-
-    - Model: `elevenlabs/tts`
-    - Voice id: `21m00Tcm4TlvDq8ikWAM`
-
-    The bundled plugin currently exposes one known-good default voice and returns MP3 audio files.
-
-  </Accordion>
-</AccordionGroup>
+The bundled plugin currently exposes one known-good default voice and returns MP3 audio files.
 
 ## Related
 
-<CardGroup cols={2}>
-  <Card title="Provider directory" href="/providers/index" icon="list">
-    Browse all available providers.
-  </Card>
-  <Card title="Image generation" href="/tools/image-generation" icon="image">
-    Shared image tool parameters and provider selection.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration-reference#agent-defaults" icon="gear">
-    Agent defaults and model configuration.
-  </Card>
-</CardGroup>
+- [Provider Directory](/providers/index)
+- [Image Generation](/tools/image-generation)
+- [Video Generation](/tools/video-generation)

docs/providers/xai.md

@@ -10,238 +10,113 @@ title: "xAI"
 
 OpenClaw ships a bundled `xai` provider plugin for Grok models.
 
-## Getting started
+## Setup
 
-<Steps>
-  <Step title="Create an API key">
-    Create an API key in the [xAI console](https://console.x.ai/).
-  </Step>
-  <Step title="Set your API key">
-    Set `XAI_API_KEY`, or run:
+1. Create an API key in the xAI console.
+2. Set `XAI_API_KEY`, or run:
 
-    ```bash
-    openclaw onboard --auth-choice xai-api-key
-    ```
+```bash
+openclaw onboard --auth-choice xai-api-key
+```
 
-  </Step>
-  <Step title="Pick a model">
-    ```json5
-    {
-      agents: { defaults: { model: { primary: "xai/grok-4" } } },
-    }
-    ```
-  </Step>
-</Steps>
+3. Pick a model such as:
 
-<Note>
-OpenClaw uses the xAI Responses API as the bundled xAI transport. The same
+```json5
+{
+  agents: { defaults: { model: { primary: "xai/grok-4" } } },
+}
+```
+
+OpenClaw now uses the xAI Responses API as the bundled xAI transport. The same
 `XAI_API_KEY` can also power Grok-backed `web_search`, first-class `x_search`,
 and remote `code_execution`.
 If you store an xAI key under `plugins.entries.xai.config.webSearch.apiKey`,
-the bundled xAI model provider reuses that key as a fallback too.
+the bundled xAI model provider now reuses that key as a fallback too.
 `code_execution` tuning lives under `plugins.entries.xai.config.codeExecution`.
-</Note>
 
-## Bundled model catalog
+## Current bundled model catalog
 
-OpenClaw includes these xAI model families out of the box:
+OpenClaw now includes these xAI model families out of the box:
 
-| Family         | Model ids                                                                |
-| -------------- | ------------------------------------------------------------------------ |
-| Grok 3         | `grok-3`, `grok-3-fast`, `grok-3-mini`, `grok-3-mini-fast`               |
-| Grok 4         | `grok-4`, `grok-4-0709`                                                  |
-| Grok 4 Fast    | `grok-4-fast`, `grok-4-fast-non-reasoning`                               |
-| Grok 4.1 Fast  | `grok-4-1-fast`, `grok-4-1-fast-non-reasoning`                           |
-| Grok 4.20 Beta | `grok-4.20-beta-latest-reasoning`, `grok-4.20-beta-latest-non-reasoning` |
-| Grok Code      | `grok-code-fast-1`                                                       |
+- `grok-3`, `grok-3-fast`, `grok-3-mini`, `grok-3-mini-fast`
+- `grok-4`, `grok-4-0709`
+- `grok-4-fast`, `grok-4-fast-non-reasoning`
+- `grok-4-1-fast`, `grok-4-1-fast-non-reasoning`
+- `grok-4.20-beta-latest-reasoning`, `grok-4.20-beta-latest-non-reasoning`
+- `grok-code-fast-1`
 
 The plugin also forward-resolves newer `grok-4*` and `grok-code-fast*` ids when
 they follow the same API shape.
 
-<Tip>
-`grok-4-fast`, `grok-4-1-fast`, and the `grok-4.20-beta-*` variants are the
-current image-capable Grok refs in the bundled catalog.
-</Tip>
+Fast-model notes:
 
-### Fast-mode mappings
+- `grok-4-fast`, `grok-4-1-fast`, and the `grok-4.20-beta-*` variants are the
+  current image-capable Grok refs in the bundled catalog.
+- `/fast on` or `agents.defaults.models["xai/<model>"].params.fastMode: true`
+  rewrites native xAI requests as follows:
+  - `grok-3` -> `grok-3-fast`
+  - `grok-3-mini` -> `grok-3-mini-fast`
+  - `grok-4` -> `grok-4-fast`
+  - `grok-4-0709` -> `grok-4-fast`
 
-`/fast on` or `agents.defaults.models["xai/<model>"].params.fastMode: true`
-rewrites native xAI requests as follows:
+Legacy compatibility aliases still normalize to the canonical bundled ids. For
+example:
 
-| Source model  | Fast-mode target   |
-| ------------- | ------------------ |
-| `grok-3`      | `grok-3-fast`      |
-| `grok-3-mini` | `grok-3-mini-fast` |
-| `grok-4`      | `grok-4-fast`      |
-| `grok-4-0709` | `grok-4-fast`      |
+- `grok-4-fast-reasoning` -> `grok-4-fast`
+- `grok-4-1-fast-reasoning` -> `grok-4-1-fast`
+- `grok-4.20-reasoning` -> `grok-4.20-beta-latest-reasoning`
+- `grok-4.20-non-reasoning` -> `grok-4.20-beta-latest-non-reasoning`
 
-### Legacy compatibility aliases
+## Web search
 
-Legacy aliases still normalize to the canonical bundled ids:
+The bundled `grok` web-search provider uses `XAI_API_KEY` too:
 
-| Legacy alias              | Canonical id                          |
-| ------------------------- | ------------------------------------- |
-| `grok-4-fast-reasoning`   | `grok-4-fast`                         |
-| `grok-4-1-fast-reasoning` | `grok-4-1-fast`                       |
-| `grok-4.20-reasoning`     | `grok-4.20-beta-latest-reasoning`     |
-| `grok-4.20-non-reasoning` | `grok-4.20-beta-latest-non-reasoning` |
+```bash
+openclaw config set tools.web.search.provider grok
+```
 
-## Features
+## Video generation
 
-<AccordionGroup>
-  <Accordion title="Web search">
-    The bundled `grok` web-search provider uses `XAI_API_KEY` too:
+The bundled `xai` plugin also registers video generation through the shared
+`video_generate` tool.
 
-    ```bash
-    openclaw config set tools.web.search.provider grok
-    ```
+- Default video model: `xai/grok-imagine-video`
+- Modes: text-to-video, image-to-video, and remote video edit/extend flows
+- Supports `aspectRatio` and `resolution`
+- Current limit: local video buffers are not accepted; use remote `http(s)`
+  URLs for video-reference/edit inputs
 
-  </Accordion>
+To use xAI as the default video provider:
 
-  <Accordion title="Video generation">
-    The bundled `xai` plugin registers video generation through the shared
-    `video_generate` tool.
-
-    - Default video model: `xai/grok-imagine-video`
-    - Modes: text-to-video, image-to-video, and remote video edit/extend flows
-    - Supports `aspectRatio` and `resolution`
-
-    <Warning>
-    Local video buffers are not accepted. Use remote `http(s)` URLs for
-    video-reference and edit inputs.
-    </Warning>
-
-    To use xAI as the default video provider:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          videoGenerationModel: {
-            primary: "xai/grok-imagine-video",
-          },
-        },
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "xai/grok-imagine-video",
       },
-    }
-    ```
+    },
+  },
+}
+```
 
-    <Note>
-    See [Video Generation](/tools/video-generation) for shared tool parameters,
-    provider selection, and failover behavior.
-    </Note>
+See [Video Generation](/tools/video-generation) for the shared tool
+parameters, provider selection, and failover behavior.
 
-  </Accordion>
+## Known limits
 
-  <Accordion title="x_search configuration">
-    The bundled xAI plugin exposes `x_search` as an OpenClaw tool for searching
-    X (formerly Twitter) content via Grok.
+- Auth is API-key only today. There is no xAI OAuth/device-code flow in OpenClaw yet.
+- `grok-4.20-multi-agent-experimental-beta-0304` is not supported on the normal xAI provider path because it requires a different upstream API surface than the standard OpenClaw xAI transport.
 
-    Config path: `plugins.entries.xai.config.xSearch`
+## Notes
 
-    | Key                | Type    | Default            | Description                          |
-    | ------------------ | ------- | ------------------ | ------------------------------------ |
-    | `enabled`          | boolean | —                  | Enable or disable x_search           |
-    | `model`            | string  | `grok-4-1-fast`    | Model used for x_search requests     |
-    | `inlineCitations`  | boolean | —                  | Include inline citations in results  |
-    | `maxTurns`         | number  | —                  | Maximum conversation turns           |
-    | `timeoutSeconds`   | number  | —                  | Request timeout in seconds           |
-    | `cacheTtlMinutes`  | number  | —                  | Cache time-to-live in minutes        |
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          xai: {
-            config: {
-              xSearch: {
-                enabled: true,
-                model: "grok-4-1-fast",
-                inlineCitations: true,
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Code execution configuration">
-    The bundled xAI plugin exposes `code_execution` as an OpenClaw tool for
-    remote code execution in xAI's sandbox environment.
-
-    Config path: `plugins.entries.xai.config.codeExecution`
-
-    | Key               | Type    | Default            | Description                              |
-    | ----------------- | ------- | ------------------ | ---------------------------------------- |
-    | `enabled`         | boolean | `true` (if key available) | Enable or disable code execution  |
-    | `model`           | string  | `grok-4-1-fast`    | Model used for code execution requests   |
-    | `maxTurns`        | number  | —                  | Maximum conversation turns               |
-    | `timeoutSeconds`  | number  | —                  | Request timeout in seconds               |
-
-    <Note>
-    This is remote xAI sandbox execution, not local [`exec`](/tools/exec).
-    </Note>
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          xai: {
-            config: {
-              codeExecution: {
-                enabled: true,
-                model: "grok-4-1-fast",
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Known limits">
-    - Auth is API-key only today. There is no xAI OAuth or device-code flow in
-      OpenClaw yet.
-    - `grok-4.20-multi-agent-experimental-beta-0304` is not supported on the
-      normal xAI provider path because it requires a different upstream API
-      surface than the standard OpenClaw xAI transport.
-  </Accordion>
-
-  <Accordion title="Advanced notes">
-    - OpenClaw applies xAI-specific tool-schema and tool-call compatibility fixes
-      automatically on the shared runner path.
-    - Native xAI requests default `tool_stream: true`. Set
-      `agents.defaults.models["xai/<model>"].params.tool_stream` to `false` to
-      disable it.
-    - The bundled xAI wrapper strips unsupported strict tool-schema flags and
-      reasoning payload keys before sending native xAI requests.
-    - `web_search`, `x_search`, and `code_execution` are exposed as OpenClaw
-      tools. OpenClaw enables the specific xAI built-in it needs inside each tool
-      request instead of attaching all native tools to every chat turn.
-    - `x_search` and `code_execution` are owned by the bundled xAI plugin rather
-      than hardcoded into the core model runtime.
-    - `code_execution` is remote xAI sandbox execution, not local
-      [`exec`](/tools/exec).
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Video generation" href="/tools/video-generation" icon="video">
-    Shared video tool parameters and provider selection.
-  </Card>
-  <Card title="All providers" href="/providers/index" icon="grid-2">
-    The broader provider overview.
-  </Card>
-  <Card title="Troubleshooting" href="/help/troubleshooting" icon="wrench">
-    Common issues and fixes.
-  </Card>
-</CardGroup>
+- OpenClaw applies xAI-specific tool-schema and tool-call compatibility fixes automatically on the shared runner path.
+- Native xAI requests default `tool_stream: true`. Set
+  `agents.defaults.models["xai/<model>"].params.tool_stream` to `false` to
+  disable it.
+- The bundled xAI wrapper strips unsupported strict tool-schema flags and
+  reasoning payload keys before sending native xAI requests.
+- `web_search`, `x_search`, and `code_execution` are exposed as OpenClaw tools. OpenClaw enables the specific xAI built-in it needs inside each tool request instead of attaching all native tools to every chat turn.
+- `x_search` and `code_execution` are owned by the bundled xAI plugin rather than hardcoded into the core model runtime.
+- `code_execution` is remote xAI sandbox execution, not local [`exec`](/tools/exec).
+- For the broader provider overview, see [Model providers](/providers/index).

docs/providers/xiaomi.md

@@ -9,53 +9,31 @@ title: "Xiaomi MiMo"
 # Xiaomi MiMo
 
 Xiaomi MiMo is the API platform for **MiMo** models. OpenClaw uses the Xiaomi
-OpenAI-compatible endpoint with API-key authentication.
+OpenAI-compatible endpoint with API-key authentication. Create your API key in the
+[Xiaomi MiMo console](https://platform.xiaomimimo.com/#/console/api-keys), then configure the
+bundled `xiaomi` provider with that key.
 
-| Property | Value                           |
-| -------- | ------------------------------- |
-| Provider | `xiaomi`                        |
-| Auth     | `XIAOMI_API_KEY`                |
-| API      | OpenAI-compatible               |
-| Base URL | `https://api.xiaomimimo.com/v1` |
+## Built-in catalog
 
-## Getting started
+- Base URL: `https://api.xiaomimimo.com/v1`
+- API: `openai-completions`
+- Authorization: `Bearer $XIAOMI_API_KEY`
 
-<Steps>
-  <Step title="Get an API key">
-    Create an API key in the [Xiaomi MiMo console](https://platform.xiaomimimo.com/#/console/api-keys).
-  </Step>
-  <Step title="Run onboarding">
-    ```bash
-    openclaw onboard --auth-choice xiaomi-api-key
-    ```
+| Model ref              | Input       | Context   | Max output | Notes                        |
+| ---------------------- | ----------- | --------- | ---------- | ---------------------------- |
+| `xiaomi/mimo-v2-flash` | text        | 262,144   | 8,192      | Default model                |
+| `xiaomi/mimo-v2-pro`   | text        | 1,048,576 | 32,000     | Reasoning-enabled            |
+| `xiaomi/mimo-v2-omni`  | text, image | 262,144   | 32,000     | Reasoning-enabled multimodal |
 
-    Or pass the key directly:
+## CLI setup
 
-    ```bash
-    openclaw onboard --auth-choice xiaomi-api-key --xiaomi-api-key "$XIAOMI_API_KEY"
-    ```
+```bash
+openclaw onboard --auth-choice xiaomi-api-key
+# or non-interactive
+openclaw onboard --auth-choice xiaomi-api-key --xiaomi-api-key "$XIAOMI_API_KEY"
+```
 
-  </Step>
-  <Step title="Verify the model is available">
-    ```bash
-    openclaw models list --provider xiaomi
-    ```
-  </Step>
-</Steps>
-
-## Available models
-
-| Model ref              | Input       | Context   | Max output | Reasoning | Notes         |
-| ---------------------- | ----------- | --------- | ---------- | --------- | ------------- |
-| `xiaomi/mimo-v2-flash` | text        | 262,144   | 8,192      | No        | Default model |
-| `xiaomi/mimo-v2-pro`   | text        | 1,048,576 | 32,000     | Yes       | Large context |
-| `xiaomi/mimo-v2-omni`  | text, image | 262,144   | 32,000     | Yes       | Multimodal    |
-
-<Tip>
-The default model ref is `xiaomi/mimo-v2-flash`. The provider is injected automatically when `XIAOMI_API_KEY` is set or an auth profile exists.
-</Tip>
-
-## Config example
+## Config snippet
 
 ```json5
 {
@@ -103,43 +81,9 @@ The default model ref is `xiaomi/mimo-v2-flash`. The provider is injected automa
 }
 ```
 
-<AccordionGroup>
-  <Accordion title="Auto-injection behavior">
-    The `xiaomi` provider is injected automatically when `XIAOMI_API_KEY` is set in your environment or an auth profile exists. You do not need to manually configure the provider unless you want to override model metadata or the base URL.
-  </Accordion>
+## Notes
 
-  <Accordion title="Model details">
-    - **mimo-v2-flash** — lightweight and fast, ideal for general-purpose text tasks. No reasoning support.
-    - **mimo-v2-pro** — supports reasoning with a 1M token context window for long-document workloads.
-    - **mimo-v2-omni** — reasoning-enabled multimodal model that accepts both text and image inputs.
-
-    <Note>
-    All models use the `xiaomi/` prefix (for example `xiaomi/mimo-v2-pro`).
-    </Note>
-
-  </Accordion>
-
-  <Accordion title="Troubleshooting">
-    - If models do not appear, confirm `XIAOMI_API_KEY` is set and valid.
-    - When the Gateway runs as a daemon, ensure the key is available to that process (for example in `~/.openclaw/.env` or via `env.shellEnv`).
-
-    <Warning>
-    Keys set only in your interactive shell are not visible to daemon-managed gateway processes. Use `~/.openclaw/.env` or `env.shellEnv` config for persistent availability.
-    </Warning>
-
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-  <Card title="Configuration reference" href="/gateway/configuration" icon="gear">
-    Full OpenClaw configuration reference.
-  </Card>
-  <Card title="Xiaomi MiMo console" href="https://platform.xiaomimimo.com" icon="arrow-up-right-from-square">
-    Xiaomi MiMo dashboard and API key management.
-  </Card>
-</CardGroup>
+- Default model ref: `xiaomi/mimo-v2-flash`.
+- Additional built-in models: `xiaomi/mimo-v2-pro`, `xiaomi/mimo-v2-omni`.
+- The provider is injected automatically when `XIAOMI_API_KEY` is set (or an auth profile exists).
+- See [/concepts/model-providers](/concepts/model-providers) for provider rules.

docs/providers/zai.md

@@ -12,154 +12,64 @@ Z.AI is the API platform for **GLM** models. It provides REST APIs for GLM and u
 for authentication. Create your API key in the Z.AI console. OpenClaw uses the `zai` provider
 with a Z.AI API key.
 
-- Provider: `zai`
-- Auth: `ZAI_API_KEY`
-- API: Z.AI Chat Completions (Bearer auth)
+## CLI setup
 
-## Getting started
+```bash
+# Generic API-key setup with endpoint auto-detection
+openclaw onboard --auth-choice zai-api-key
 
-<Tabs>
-  <Tab title="Auto-detect endpoint">
-    **Best for:** most users. OpenClaw detects the matching Z.AI endpoint from the key and applies the correct base URL automatically.
+# Coding Plan Global, recommended for Coding Plan users
+openclaw onboard --auth-choice zai-coding-global
 
-    <Steps>
-      <Step title="Run onboarding">
-        ```bash
-        openclaw onboard --auth-choice zai-api-key
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          env: { ZAI_API_KEY: "sk-..." },
-          agents: { defaults: { model: { primary: "zai/glm-5.1" } } },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider zai
-        ```
-      </Step>
-    </Steps>
+# Coding Plan CN (China region), recommended for Coding Plan users
+openclaw onboard --auth-choice zai-coding-cn
 
-  </Tab>
+# General API
+openclaw onboard --auth-choice zai-global
 
-  <Tab title="Explicit regional endpoint">
-    **Best for:** users who want to force a specific Coding Plan or general API surface.
+# General API CN (China region)
+openclaw onboard --auth-choice zai-cn
+```
 
-    <Steps>
-      <Step title="Pick the right onboarding choice">
-        ```bash
-        # Coding Plan Global (recommended for Coding Plan users)
-        openclaw onboard --auth-choice zai-coding-global
+## Config snippet
 
-        # Coding Plan CN (China region)
-        openclaw onboard --auth-choice zai-coding-cn
+```json5
+{
+  env: { ZAI_API_KEY: "sk-..." },
+  agents: { defaults: { model: { primary: "zai/glm-5.1" } } },
+}
+```
 
-        # General API
-        openclaw onboard --auth-choice zai-global
-
-        # General API CN (China region)
-        openclaw onboard --auth-choice zai-cn
-        ```
-      </Step>
-      <Step title="Set a default model">
-        ```json5
-        {
-          env: { ZAI_API_KEY: "sk-..." },
-          agents: { defaults: { model: { primary: "zai/glm-5.1" } } },
-        }
-        ```
-      </Step>
-      <Step title="Verify the model is available">
-        ```bash
-        openclaw models list --provider zai
-        ```
-      </Step>
-    </Steps>
-
-  </Tab>
-</Tabs>
+`zai-api-key` lets OpenClaw detect the matching Z.AI endpoint from the key and
+apply the correct base URL automatically. Use the explicit regional choices when
+you want to force a specific Coding Plan or general API surface.
 
 ## Bundled GLM catalog
 
 OpenClaw currently seeds the bundled `zai` provider with:
 
-| Model ref            | Notes         |
-| -------------------- | ------------- |
-| `zai/glm-5.1`        | Default model |
-| `zai/glm-5`          |               |
-| `zai/glm-5-turbo`    |               |
-| `zai/glm-5v-turbo`   |               |
-| `zai/glm-4.7`        |               |
-| `zai/glm-4.7-flash`  |               |
-| `zai/glm-4.7-flashx` |               |
-| `zai/glm-4.6`        |               |
-| `zai/glm-4.6v`       |               |
-| `zai/glm-4.5`        |               |
-| `zai/glm-4.5-air`    |               |
-| `zai/glm-4.5-flash`  |               |
-| `zai/glm-4.5v`       |               |
+- `glm-5.1`
+- `glm-5`
+- `glm-5-turbo`
+- `glm-5v-turbo`
+- `glm-4.7`
+- `glm-4.7-flash`
+- `glm-4.7-flashx`
+- `glm-4.6`
+- `glm-4.6v`
+- `glm-4.5`
+- `glm-4.5-air`
+- `glm-4.5-flash`
+- `glm-4.5v`
 
-<Tip>
-GLM models are available as `zai/<model>` (example: `zai/glm-5`). The default bundled model ref is `zai/glm-5.1`.
-</Tip>
+## Notes
 
-## Advanced configuration
-
-<AccordionGroup>
-  <Accordion title="Forward-resolving unknown GLM-5 models">
-    Unknown `glm-5*` ids still forward-resolve on the bundled provider path by
-    synthesizing provider-owned metadata from the `glm-4.7` template when the id
-    matches the current GLM-5 family shape.
-  </Accordion>
-
-  <Accordion title="Tool-call streaming">
-    `tool_stream` is enabled by default for Z.AI tool-call streaming. To disable it:
-
-    ```json5
-    {
-      agents: {
-        defaults: {
-          models: {
-            "zai/<model>": {
-              params: { tool_stream: false },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-  </Accordion>
-
-  <Accordion title="Image understanding">
-    The bundled Z.AI plugin registers image understanding.
-
-    | Property      | Value       |
-    | ------------- | ----------- |
-    | Model         | `glm-4.6v`  |
-
-    Image understanding is auto-resolved from the configured Z.AI auth — no
-    additional config is needed.
-
-  </Accordion>
-
-  <Accordion title="Auth details">
-    - Z.AI uses Bearer auth with your API key.
-    - The `zai-api-key` onboarding choice auto-detects the matching Z.AI endpoint from the key prefix.
-    - Use the explicit regional choices (`zai-coding-global`, `zai-coding-cn`, `zai-global`, `zai-cn`) when you want to force a specific API surface.
-  </Accordion>
-</AccordionGroup>
-
-## Related
-
-<CardGroup cols={2}>
-  <Card title="GLM model family" href="/providers/glm" icon="microchip">
-    Model family overview for GLM.
-  </Card>
-  <Card title="Model selection" href="/concepts/model-providers" icon="layers">
-    Choosing providers, model refs, and failover behavior.
-  </Card>
-</CardGroup>
+- GLM models are available as `zai/<model>` (example: `zai/glm-5`).
+- Default bundled model ref: `zai/glm-5.1`
+- Unknown `glm-5*` ids still forward-resolve on the bundled provider path by
+  synthesizing provider-owned metadata from the `glm-4.7` template when the id
+  matches the current GLM-5 family shape.
+- `tool_stream` is enabled by default for Z.AI tool-call streaming. Set
+  `agents.defaults.models["zai/<model>"].params.tool_stream` to `false` to disable it.
+- See [/providers/glm](/providers/glm) for the model family overview.
+- Z.AI uses Bearer auth with your API key.

docs/reference/rich-output-protocol.md

@@ -1,50 +0,0 @@
-# Rich Output Protocol
-
-Assistant output can carry a small set of delivery/render directives:
-
-- `MEDIA:` for attachment delivery
-- `[[audio_as_voice]]` for audio presentation hints
-- `[[reply_to_current]]` / `[[reply_to:<id>]]` for reply metadata
-- `[embed ...]` for Control UI rich rendering
-
-These directives are separate. `MEDIA:` and reply/voice tags remain delivery metadata; `[embed ...]` is the web-only rich render path.
-
-## `[embed ...]`
-
-`[embed ...]` is the only agent-facing rich render syntax for the Control UI.
-
-Self-closing example:
-
-```text
-[embed ref="cv_123" title="Status" /]
-```
-
-Rules:
-
-- `[view ...]` is no longer valid for new output.
-- Embed shortcodes render in the assistant message surface only.
-- Only URL-backed embeds are rendered. Use `ref="..."` or `url="..."`.
-- Block-form inline HTML embed shortcodes are not rendered.
-- The web UI strips the shortcode from visible text and renders the embed inline.
-- `MEDIA:` is not an embed alias and should not be used for rich embed rendering.
-
-## Stored Rendering Shape
-
-The normalized/stored assistant content block is a structured `canvas` item:
-
-```json
-{
-  "type": "canvas",
-  "preview": {
-    "kind": "canvas",
-    "surface": "assistant_message",
-    "render": "url",
-    "viewId": "cv_123",
-    "url": "/__openclaw__/canvas/documents/cv_123/index.html",
-    "title": "Status",
-    "preferredHeight": 320
-  }
-}
-```
-
-Stored/rendered rich blocks use this `canvas` shape directly. `present_view` is not recognized.

docs/reference/templates/AGENTS.md

@@ -15,19 +15,14 @@ If `BOOTSTRAP.md` exists, that's your birth certificate. Follow it, figure out w
 
 ## Session Startup
 
-Use runtime-provided startup context first.
+Before doing anything else:
 
-That context may already include:
+1. Read `SOUL.md` — this is who you are
+2. Read `USER.md` — this is who you're helping
+3. Read `memory/YYYY-MM-DD.md` (today + yesterday) for recent context
+4. **If in MAIN SESSION** (direct chat with your human): Also read `MEMORY.md`
 
-- `AGENTS.md`, `SOUL.md`, and `USER.md`
-- recent daily memory such as `memory/YYYY-MM-DD.md`
-- `MEMORY.md` when this is the main session
-
-Do not manually reread startup files unless:
-
-1. The user explicitly asks
-2. The provided context is missing something you need
-3. You need a deeper follow-up read beyond the provided startup context
+Don't ask permission. Just do it.
 
 ## Memory
 

docs/reference/token-use.md

@@ -18,7 +18,7 @@ OpenClaw assembles its own system prompt on every run. It includes:
 - Tool list + short descriptions
 - Skills list (only metadata; instructions are loaded on demand with `read`)
 - Self-update instructions
-- Workspace + bootstrap files (`AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`, `BOOTSTRAP.md` when new, plus `MEMORY.md` when present or `memory.md` as a lowercase fallback). Large files are truncated by `agents.defaults.bootstrapMaxChars` (default: 20000), and total bootstrap injection is capped by `agents.defaults.bootstrapTotalMaxChars` (default: 150000). `memory/*.md` daily files are not part of the normal bootstrap prompt; they remain on-demand via memory tools on ordinary turns, but bare `/new` and `/reset` can prepend a one-shot startup-context block with recent daily memory for that first turn. That startup prelude is controlled by `agents.defaults.startupContext`.
+- Workspace + bootstrap files (`AGENTS.md`, `SOUL.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `HEARTBEAT.md`, `BOOTSTRAP.md` when new, plus `MEMORY.md` when present or `memory.md` as a lowercase fallback). Large files are truncated by `agents.defaults.bootstrapMaxChars` (default: 20000), and total bootstrap injection is capped by `agents.defaults.bootstrapTotalMaxChars` (default: 150000). `memory/*.md` files are on-demand via memory tools and are not auto-injected.
 - Time (UTC + user timezone)
 - Reply tags + heartbeat behavior
 - Runtime metadata (host/OS/model/thinking)

docs/tools/video-generation.md

@@ -1,5 +1,5 @@
 ---
-summary: "Generate videos from text, images, or existing videos using 14 provider backends"
+summary: "Generate videos from text, images, or existing videos using 12 provider backends"
 read_when:
   - Generating videos via the agent
   - Configuring video generation providers and models
@@ -9,7 +9,7 @@ title: "Video Generation"
 
 # Video Generation
 
-OpenClaw agents can generate videos from text prompts, reference images, or existing videos. Fourteen provider backends are supported, each with different model options, input modes, and feature sets. The agent picks the right provider automatically based on your configuration and available API keys.
+OpenClaw agents can generate videos from text prompts, reference images, or existing videos. Twelve provider backends are supported, each with different model options, input modes, and feature sets. The agent picks the right provider automatically based on your configuration and available API keys.
 
 <Note>
 The `video_generate` tool only appears when at least one video-generation provider is available. If you do not see it in your agent tools, set a provider API key or configure `agents.defaults.videoGenerationModel`.
@@ -78,22 +78,20 @@ Duplicate prevention: if a video task is already `queued` or `running` for the c
 
 ## Supported providers
 
-| Provider              | Default model                   | Text | Image ref                                            | Video ref        | API key                                  |
-| --------------------- | ------------------------------- | ---- | ---------------------------------------------------- | ---------------- | ---------------------------------------- |
-| Alibaba               | `wan2.6-t2v`                    | Yes  | Yes (remote URL)                                     | Yes (remote URL) | `MODELSTUDIO_API_KEY`                    |
-| BytePlus (1.0)        | `seedance-1-0-pro-250528`       | Yes  | Up to 2 images (I2V models only; first + last frame) | No               | `BYTEPLUS_API_KEY`                       |
-| BytePlus Seedance 1.5 | `seedance-1-5-pro-251215`       | Yes  | Up to 2 images (first + last frame via role)         | No               | `BYTEPLUS_API_KEY`                       |
-| BytePlus Seedance 2.0 | `dreamina-seedance-2-0-260128`  | Yes  | Up to 9 reference images                             | Up to 3 videos   | `BYTEPLUS_API_KEY`                       |
-| ComfyUI               | `workflow`                      | Yes  | 1 image                                              | No               | `COMFY_API_KEY` or `COMFY_CLOUD_API_KEY` |
-| fal                   | `fal-ai/minimax/video-01-live`  | Yes  | 1 image                                              | No               | `FAL_KEY`                                |
-| Google                | `veo-3.1-fast-generate-preview` | Yes  | 1 image                                              | 1 video          | `GEMINI_API_KEY`                         |
-| MiniMax               | `MiniMax-Hailuo-2.3`            | Yes  | 1 image                                              | No               | `MINIMAX_API_KEY`                        |
-| OpenAI                | `sora-2`                        | Yes  | 1 image                                              | 1 video          | `OPENAI_API_KEY`                         |
-| Qwen                  | `wan2.6-t2v`                    | Yes  | Yes (remote URL)                                     | Yes (remote URL) | `QWEN_API_KEY`                           |
-| Runway                | `gen4.5`                        | Yes  | 1 image                                              | 1 video          | `RUNWAYML_API_SECRET`                    |
-| Together              | `Wan-AI/Wan2.2-T2V-A14B`        | Yes  | 1 image                                              | No               | `TOGETHER_API_KEY`                       |
-| Vydra                 | `veo3`                          | Yes  | 1 image (`kling`)                                    | No               | `VYDRA_API_KEY`                          |
-| xAI                   | `grok-imagine-video`            | Yes  | 1 image                                              | 1 video          | `XAI_API_KEY`                            |
+| Provider | Default model                   | Text | Image ref         | Video ref        | API key                                  |
+| -------- | ------------------------------- | ---- | ----------------- | ---------------- | ---------------------------------------- |
+| Alibaba  | `wan2.6-t2v`                    | Yes  | Yes (remote URL)  | Yes (remote URL) | `MODELSTUDIO_API_KEY`                    |
+| BytePlus | `seedance-1-0-lite-t2v-250428`  | Yes  | 1 image           | No               | `BYTEPLUS_API_KEY`                       |
+| ComfyUI  | `workflow`                      | Yes  | 1 image           | No               | `COMFY_API_KEY` or `COMFY_CLOUD_API_KEY` |
+| fal      | `fal-ai/minimax/video-01-live`  | Yes  | 1 image           | No               | `FAL_KEY`                                |
+| Google   | `veo-3.1-fast-generate-preview` | Yes  | 1 image           | 1 video          | `GEMINI_API_KEY`                         |
+| MiniMax  | `MiniMax-Hailuo-2.3`            | Yes  | 1 image           | No               | `MINIMAX_API_KEY`                        |
+| OpenAI   | `sora-2`                        | Yes  | 1 image           | 1 video          | `OPENAI_API_KEY`                         |
+| Qwen     | `wan2.6-t2v`                    | Yes  | Yes (remote URL)  | Yes (remote URL) | `QWEN_API_KEY`                           |
+| Runway   | `gen4.5`                        | Yes  | 1 image           | 1 video          | `RUNWAYML_API_SECRET`                    |
+| Together | `Wan-AI/Wan2.2-T2V-A14B`        | Yes  | 1 image           | No               | `TOGETHER_API_KEY`                       |
+| Vydra    | `veo3`                          | Yes  | 1 image (`kling`) | No               | `VYDRA_API_KEY`                          |
+| xAI      | `grok-imagine-video`            | Yes  | 1 image           | 1 video          | `XAI_API_KEY`                            |
 
 Some providers accept additional or alternate API key env vars. See individual [provider pages](#related) for details.
 
@@ -130,49 +128,31 @@ and the shared live sweep.
 
 ### Content inputs
 
-| Parameter    | Type     | Description                                                                                                                            |
-| ------------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------- |
-| `image`      | string   | Single reference image (path or URL)                                                                                                   |
-| `images`     | string[] | Multiple reference images (up to 9)                                                                                                    |
-| `imageRoles` | string[] | Optional per-position role hints parallel to the combined image list. Canonical values: `first_frame`, `last_frame`, `reference_image` |
-| `video`      | string   | Single reference video (path or URL)                                                                                                   |
-| `videos`     | string[] | Multiple reference videos (up to 4)                                                                                                    |
-| `videoRoles` | string[] | Optional per-position role hints parallel to the combined video list. Canonical value: `reference_video`                               |
-| `audioRef`   | string   | Single reference audio (path or URL). Used for e.g. background music or voice reference when the provider supports audio inputs        |
-| `audioRefs`  | string[] | Multiple reference audios (up to 3)                                                                                                    |
-| `audioRoles` | string[] | Optional per-position role hints parallel to the combined audio list. Canonical value: `reference_audio`                               |
-
-Role hints are forwarded to the provider as-is. Canonical values come from
-the `VideoGenerationAssetRole` union but providers may accept additional
-role strings. `*Roles` arrays must not have more entries than the
-corresponding reference list; off-by-one mistakes fail with a clear error.
-Use an empty string to leave a slot unset.
+| Parameter | Type     | Description                          |
+| --------- | -------- | ------------------------------------ |
+| `image`   | string   | Single reference image (path or URL) |
+| `images`  | string[] | Multiple reference images (up to 5)  |
+| `video`   | string   | Single reference video (path or URL) |
+| `videos`  | string[] | Multiple reference videos (up to 4)  |
 
 ### Style controls
 
-| Parameter         | Type    | Description                                                                             |
-| ----------------- | ------- | --------------------------------------------------------------------------------------- |
-| `aspectRatio`     | string  | `1:1`, `2:3`, `3:2`, `3:4`, `4:3`, `4:5`, `5:4`, `9:16`, `16:9`, `21:9`, or `adaptive`  |
-| `resolution`      | string  | `480P`, `720P`, `768P`, or `1080P`                                                      |
-| `durationSeconds` | number  | Target duration in seconds (rounded to nearest provider-supported value)                |
-| `size`            | string  | Size hint when the provider supports it                                                 |
-| `audio`           | boolean | Enable generated audio in the output when supported. Distinct from `audioRef*` (inputs) |
-| `watermark`       | boolean | Toggle provider watermarking when supported                                             |
-
-`adaptive` is a provider-specific sentinel: it is forwarded as-is to
-providers that declare `adaptive` in their capabilities (e.g. BytePlus
-Seedance uses it to auto-detect the ratio from the input image
-dimensions). Providers that do not declare it surface the value via
-`details.ignoredOverrides` in the tool result so the drop is visible.
+| Parameter         | Type    | Description                                                              |
+| ----------------- | ------- | ------------------------------------------------------------------------ |
+| `aspectRatio`     | string  | `1:1`, `2:3`, `3:2`, `3:4`, `4:3`, `4:5`, `5:4`, `9:16`, `16:9`, `21:9`  |
+| `resolution`      | string  | `480P`, `720P`, `768P`, or `1080P`                                       |
+| `durationSeconds` | number  | Target duration in seconds (rounded to nearest provider-supported value) |
+| `size`            | string  | Size hint when the provider supports it                                  |
+| `audio`           | boolean | Enable generated audio when supported                                    |
+| `watermark`       | boolean | Toggle provider watermarking when supported                              |
 
 ### Advanced
 
-| Parameter         | Type   | Description                                                                                                                                                                                                                                                                                                                                          |
-| ----------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`          | string | `"generate"` (default), `"status"`, or `"list"`                                                                                                                                                                                                                                                                                                      |
-| `model`           | string | Provider/model override (e.g. `runway/gen4.5`)                                                                                                                                                                                                                                                                                                       |
-| `filename`        | string | Output filename hint                                                                                                                                                                                                                                                                                                                                 |
-| `providerOptions` | object | Provider-specific options as a JSON object (e.g. `{"seed": 42, "draft": true}`). Providers that declare a typed schema validate the keys and types; unknown keys or mismatches skip the candidate during fallback. Providers without a declared schema receive the options as-is. Run `video_generate action=list` to see what each provider accepts |
+| Parameter  | Type   | Description                                     |
+| ---------- | ------ | ----------------------------------------------- |
+| `action`   | string | `"generate"` (default), `"status"`, or `"list"` |
+| `model`    | string | Provider/model override (e.g. `runway/gen4.5`)  |
+| `filename` | string | Output filename hint                            |
 
 Not all providers support all parameters. OpenClaw already normalizes duration to the closest provider-supported value, and it also remaps translated geometry hints such as size-to-aspect-ratio when a fallback provider exposes a different control surface. Truly unsupported overrides are ignored on a best-effort basis and reported as warnings in the tool result. Hard capability limits (such as too many reference inputs) fail before submission.
 
@@ -183,37 +163,10 @@ Reference inputs also select the runtime mode:
 - No reference media: `generate`
 - Any image reference: `imageToVideo`
 - Any video reference: `videoToVideo`
-- Reference audio inputs do not change the resolved mode; they apply on top of whatever mode the image/video references select, and only work with providers that declare `maxInputAudios`
 
 Mixed image and video references are not a stable shared capability surface.
 Prefer one reference type per request.
 
-#### Fallback and typed options
-
-Some capability checks are applied at the fallback layer rather than the
-tool boundary so that a request that exceeds the primary provider's limits
-can still run on a capable fallback:
-
-- If the active candidate declares no `maxInputAudios` (or declares it as
-  `0`), it is skipped when the request contains audio references, and the
-  next candidate is tried.
-- If the active candidate's `maxDurationSeconds` is below the requested
-  `durationSeconds` and the candidate does not declare a
-  `supportedDurationSeconds` list, it is skipped.
-- If the request contains `providerOptions` and the active candidate
-  explicitly declares a typed `providerOptions` schema, the candidate is
-  skipped when the supplied keys are not in the schema or the value types do
-  not match. Providers that have not yet declared a schema receive the
-  options as-is (backward-compatible pass-through). A provider can
-  explicitly opt out of all provider options by declaring an empty schema
-  (`capabilities.providerOptions: {}`), which causes the same skip as a
-  type mismatch.
-
-The first skip reason in a request is logged at `warn` so operators see
-when their primary provider was passed over; subsequent skips log at
-`debug` to keep long fallback chains quiet. If every candidate is skipped,
-the aggregated error includes the skip reason for each.
-
 ## Actions
 
 - **generate** (default) -- create a video from the given prompt and optional reference inputs.
@@ -248,24 +201,50 @@ entries.
 }
 ```
 
+HeyGen video-agent on fal can be pinned with:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "fal/fal-ai/heygen/v2/video-agent",
+      },
+    },
+  },
+}
+```
+
+Seedance 2.0 on fal can be pinned with:
+
+```json5
+{
+  agents: {
+    defaults: {
+      videoGenerationModel: {
+        primary: "fal/bytedance/seedance-2.0/fast/text-to-video",
+      },
+    },
+  },
+}
+```
+
 ## Provider notes
 
-| Provider              | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Alibaba               | Uses DashScope/Model Studio async endpoint. Reference images and videos must be remote `http(s)` URLs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| BytePlus (1.0)        | Provider id `byteplus`. Models: `seedance-1-0-pro-250528` (default), `seedance-1-0-pro-t2v-250528`, `seedance-1-0-pro-fast-251015`, `seedance-1-0-lite-t2v-250428`, `seedance-1-0-lite-i2v-250428`. T2V models (`*-t2v-*`) do not accept image inputs; I2V models and general `*-pro-*` models support a single reference image (first frame). Pass the image positionally or set `role: "first_frame"`. T2V model IDs are automatically switched to the corresponding I2V variant when an image is provided. Supported `providerOptions` keys: `seed` (number), `draft` (boolean, forces 480p), `camera_fixed` (boolean).                                                                       |
-| BytePlus Seedance 1.5 | Requires the [`@openclaw/byteplus-modelark`](https://www.npmjs.com/package/@openclaw/byteplus-modelark) plugin. Provider id `byteplus-seedance15`. Model: `seedance-1-5-pro-251215`. Uses the unified `content[]` API. Supports at most 2 input images (first_frame + last_frame). All inputs must be remote `https://` URLs. Set `role: "first_frame"` / `"last_frame"` on each image, or pass images positionally. `aspectRatio: "adaptive"` auto-detects ratio from the input image. `audio: true` maps to `generate_audio`. `providerOptions.seed` (number) is forwarded.                                                                                                                    |
-| BytePlus Seedance 2.0 | Requires the [`@openclaw/byteplus-modelark`](https://www.npmjs.com/package/@openclaw/byteplus-modelark) plugin. Provider id `byteplus-seedance2`. Models: `dreamina-seedance-2-0-260128`, `dreamina-seedance-2-0-fast-260128`. Uses the unified `content[]` API. Supports up to 9 reference images, 3 reference videos, and 3 reference audios. All inputs must be remote `https://` URLs. Set `role` on each asset — supported values: `"first_frame"`, `"last_frame"`, `"reference_image"`, `"reference_video"`, `"reference_audio"`. `aspectRatio: "adaptive"` auto-detects ratio from the input image. `audio: true` maps to `generate_audio`. `providerOptions.seed` (number) is forwarded. |
-| ComfyUI               | Workflow-driven local or cloud execution. Supports text-to-video and image-to-video through the configured graph.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| fal                   | Uses queue-backed flow for long-running jobs. Single image reference only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| Google                | Uses Gemini/Veo. Supports one image or one video reference.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| MiniMax               | Single image reference only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| OpenAI                | Only `size` override is forwarded. Other style overrides (`aspectRatio`, `resolution`, `audio`, `watermark`) are ignored with a warning.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| Qwen                  | Same DashScope backend as Alibaba. Reference inputs must be remote `http(s)` URLs; local files are rejected upfront.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| Runway                | Supports local files via data URIs. Video-to-video requires `runway/gen4_aleph`. Text-only runs expose `16:9` and `9:16` aspect ratios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| Together              | Single image reference only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| Vydra                 | Uses `https://www.vydra.ai/api/v1` directly to avoid auth-dropping redirects. `veo3` is bundled as text-to-video only; `kling` requires a remote image URL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| xAI                   | Supports text-to-video, image-to-video, and remote video edit/extend flows.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Provider | Notes                                                                                                                                                                |
+| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Alibaba  | Uses DashScope/Model Studio async endpoint. Reference images and videos must be remote `http(s)` URLs.                                                               |
+| BytePlus | Single image reference only.                                                                                                                                         |
+| ComfyUI  | Workflow-driven local or cloud execution. Supports text-to-video and image-to-video through the configured graph.                                                    |
+| fal      | Uses queue-backed flow for long-running jobs. Single image reference only. Includes HeyGen video-agent and Seedance 2.0 text-to-video and image-to-video model refs. |
+| Google   | Uses Gemini/Veo. Supports one image or one video reference.                                                                                                          |
+| MiniMax  | Single image reference only.                                                                                                                                         |
+| OpenAI   | Only `size` override is forwarded. Other style overrides (`aspectRatio`, `resolution`, `audio`, `watermark`) are ignored with a warning.                             |
+| Qwen     | Same DashScope backend as Alibaba. Reference inputs must be remote `http(s)` URLs; local files are rejected upfront.                                                 |
+| Runway   | Supports local files via data URIs. Video-to-video requires `runway/gen4_aleph`. Text-only runs expose `16:9` and `9:16` aspect ratios.                              |
+| Together | Single image reference only.                                                                                                                                         |
+| Vydra    | Uses `https://www.vydra.ai/api/v1` directly to avoid auth-dropping redirects. `veo3` is bundled as text-to-video only; `kling` requires a remote image URL.          |
+| xAI      | Supports text-to-video, image-to-video, and remote video edit/extend flows.                                                                                          |
 
 ## Provider capability modes
 

docs/web/control-ui.md

@@ -138,38 +138,6 @@ Cron jobs panel notes:
   - Gateway persists aborted partial assistant text into transcript history when buffered output exists
   - Persisted entries include abort metadata so transcript consumers can tell abort partials from normal completion output
 
-## Hosted embeds
-
-Assistant messages can render hosted web content inline with the `[embed ...]`
-shortcode. The iframe sandbox policy is controlled by
-`gateway.controlUi.embedSandbox`:
-
-- `strict`: disables script execution inside hosted embeds
-- `scripts`: allows interactive embeds while keeping origin isolation; this is
-  the default and is usually enough for self-contained browser games/widgets
-- `trusted`: adds `allow-same-origin` on top of `allow-scripts` for same-site
-  documents that intentionally need stronger privileges
-
-Example:
-
-```json5
-{
-  gateway: {
-    controlUi: {
-      embedSandbox: "scripts",
-    },
-  },
-}
-```
-
-Use `trusted` only when the embedded document genuinely needs same-origin
-behavior. For most agent-generated games and interactive canvases, `scripts` is
-the safer choice.
-
-Absolute external `http(s)` embed URLs stay blocked by default. If you
-intentionally want `[embed url="https://..."]` to load third-party pages, set
-`gateway.controlUi.allowExternalEmbedUrls: true`.
-
 ## Tailnet access (recommended)
 
 ### Integrated Tailscale Serve (preferred)

extensions/AGENTS.md

@@ -51,15 +51,6 @@ third-party plugins see.
   provider needs OpenAI-style Anthropic tool payload compat, Gemini schema
   cleanup, or an XAI compat patch, use a named shared helper instead of
   inlining the policy knobs again.
-- Keep control-plane metadata separate from runtime logic. Discovery, config
-  validation, setup hints, onboarding hints, and activation planning should be
-  expressible from manifest/descriptors whenever possible.
-- If setup truly requires runtime execution, make that explicit in the plugin's
-  declared setup/runtime surface instead of letting metadata flows import
-  runtime code accidentally.
-- Do not rely on eager global registry seeding or import-time side effects to
-  make a plugin “available”. Plugin availability should come from manifest
-  ownership plus targeted activation.
 
 ## Expanding The Boundary