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.

.agents/skills/openclaw-release-maintainer/SKILL.md

@@ -120,10 +120,6 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
   `.github/workflows/openclaw-npm-release.yml`, but it still needs a valid
   `NPM_TOKEN` because `npm dist-tag` management is separate from trusted
   publishing.
-- Direct stable publishes can also run the same workflow with
-  `sync_stable_dist_tags=true` to point both `latest` and `beta` at the
-  already-published stable version. This also needs the `npm-release`
-  environment approval and `NPM_TOKEN`.
 - The publish run must be started manually with `workflow_dispatch`.
 - The npm workflow and the private mac publish workflow accept
   `preflight_only=true` to run validation/build/package steps without uploading
@@ -182,10 +178,7 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
   plan does not yet support required reviewers there, do not assume the
   environment alone is the approval boundary; rely on private repo access and
   CODEOWNERS until those settings can be enabled.
-- Do not use `NPM_TOKEN` or the plugin OTP flow for the OpenClaw package
-  publish path; package publishing uses trusted publishing.
-- Use `NPM_TOKEN` only for explicit npm dist-tag management modes, because npm
-  does not support trusted publishing for `npm dist-tag add`.
+- Do not use `NPM_TOKEN` or the plugin OTP flow for OpenClaw releases.
 - `@openclaw/*` plugin publishes use a separate maintainer-only flow.
 - Only publish plugins that already exist on npm; bundled disk-tree-only plugins stay unpublished.
 
@@ -255,25 +248,19 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
     passes with the same stable tag, `promote_beta_to_latest=true`,
     `preflight_only=false`, empty `preflight_run_id`, and `npm_dist_tag=beta`,
     then verify `latest` now points at that version.
-17. If the stable release was published directly to `latest` and `beta` should
-    follow it, start `.github/workflows/openclaw-npm-release.yml` again with
-    the same stable tag, `sync_stable_dist_tags=true`,
-    `promote_beta_to_latest=false`, `preflight_only=false`, empty
-    `preflight_run_id`, and `npm_dist_tag=latest`, then verify both `latest`
-    and `beta` point at that version.
-18. Start
+17. Start
     `openclaw/releases-private/.github/workflows/openclaw-macos-publish.yml`
     for the real publish with the successful private mac `preflight_run_id` and
     wait for success.
-19. Verify the successful real private mac run uploaded the `.zip`, `.dmg`,
+18. Verify the successful real private mac run uploaded the `.zip`, `.dmg`,
     and `.dSYM.zip` artifacts to the existing GitHub release in
     `openclaw/openclaw`.
-20. For stable releases, download `macos-appcast-<tag>` from the successful
+19. For stable releases, download `macos-appcast-<tag>` from the successful
     private mac run, update `appcast.xml` on `main`, and verify the feed.
-21. For beta releases, publish the mac assets but expect no shared production
+20. For beta releases, publish the mac assets but expect no shared production
     `appcast.xml` artifact and do not update the shared production feed unless a
     separate beta feed exists.
-22. After publish, verify npm and the attached release artifacts.
+21. After publish, verify npm and the attached release artifacts.
 
 ## GHSA advisory work
 

.agents/skills/openclaw-secret-scanning-maintainer/SKILL.md

@@ -1,201 +0,0 @@
----
-name: openclaw-secret-scanning-maintainer
-description: Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
----
-
-# OpenClaw Secret Scanning Maintainer
-
-**Maintainer-only.** This skill requires repo admin / maintainer permissions to edit or delete other users' comments and resolve secret scanning alerts.
-
-Use this skill when processing alerts from `https://github.com/openclaw/openclaw/security/secret-scanning`.
-
-**Language rule:** All notification comments and replacement comments MUST be written in English.
-
-## Script
-
-All mechanical operations (API calls, temp file management, security enforcements) are handled by:
-
-```
-$REPO_ROOT/.agents/skills/openclaw-secret-scanning-maintainer/scripts/secret-scanning.mjs
-```
-
-The script enforces:
-
-- `hide_secret=true` on all alert fetches (no plaintext secrets in stdout)
-- `mktemp` with random UUIDs for all temp files
-- `-F body=@file` for all body uploads (no inline shell quoting)
-- Notification templates branched by location type
-- Never prints `.secret` or `.body` to stdout
-
-## Overall Flow
-
-Supports single or multiple alerts. For multiple alerts, process in ascending order.
-
-For each alert:
-
-1. **Identify** — `fetch-alert` + `fetch-content` to get metadata and body
-2. **Decide** — Agent reads the body file, identifies all secrets, produces redacted version
-3. **Redact** — `redact-body` for issue/PR body; skip for comments (delete directly)
-4. **Purge** — `delete-comment` + `recreate-comment` for comments; cannot purge body history
-5. **Notify** — `notify` posts the right template per location type
-6. **Resolve** — `resolve` closes the alert
-7. **Summary** — `summary` prints formatted results
-
-## Step 1: Identify
-
-```bash
-# List all open alerts
-node secret-scanning.mjs list-open
-
-# Fetch specific alert metadata + locations
-node secret-scanning.mjs fetch-alert <NUMBER>
-
-# Fetch content for each location (saves body to temp file)
-node secret-scanning.mjs fetch-content '<location-json>'
-```
-
-The `fetch-content` output includes:
-
-- `body_file`: path to temp file with full body content
-- `author`: who posted it
-- `issue_number` / `pr_number`: where it is
-- `edit_history_count`: number of existing edits
-- `type`: location type for routing
-
-### Location type routing
-
-| type                          | Flow                     |
-| ----------------------------- | ------------------------ |
-| `issue_comment`               | Comment: delete+recreate |
-| `pull_request_comment`        | Comment: delete+recreate |
-| `pull_request_review_comment` | Comment: delete+recreate |
-| `issue_body`                  | Body: redact in place    |
-| `pull_request_body`           | Body: redact in place    |
-| `commit`                      | Notify only              |
-| _other_                       | Skip and report          |
-
-## Step 2: Decide (Agent)
-
-The agent reads the body file from `fetch-content` output and:
-
-1. Identifies ALL secrets in the content (there may be more than the alert flagged)
-2. Replaces each secret with `[REDACTED <secret_type>]` — **no partial values, no prefix/suffix**
-3. Saves the redacted content to a new temp file
-
-This is the only step that requires semantic understanding. Everything else is mechanical.
-
-## Step 3: Redact
-
-### For comments (issue_comment / PR comments)
-
-**Do NOT redact.** Skip directly to Step 4 (delete + recreate). PATCHing before DELETE creates an unnecessary edit history revision.
-
-### For issue_body / pull_request_body
-
-```bash
-node secret-scanning.mjs redact-body <issue|pr> <NUMBER> <redacted-body-file>
-```
-
-## Step 4: Purge Edit History
-
-### Comments — Delete and Recreate
-
-```bash
-# Delete original (all edit history gone)
-node secret-scanning.mjs delete-comment <COMMENT_ID>
-
-# Recreate with redacted content
-# Agent prepares the body file with maintainer header + redacted content
-node secret-scanning.mjs recreate-comment <ISSUE_NUMBER> <body-file>
-```
-
-The recreated comment should follow this format:
-
-```
-> **Note from maintainer (@<LOGIN>):** The original comment by @<AUTHOR> has been removed due to secret leakage. Below is the redacted version of the original content.
-
----
-
-<redacted original content>
-```
-
-### issue_body / pull_request_body — Cannot Purge
-
-Editing creates an edit history revision with the pre-edit plaintext. This cannot be cleared via API.
-
-**Output to maintainer terminal only (never in public comments):**
-
-```
-⚠️ Issue/PR body edit history still contains plaintext secrets.
-Contact GitHub Support to purge: https://support.github.com/contact
-Request purge of issue/PR #{NUMBER} userContentEdits.
-```
-
-> **CRITICAL:** Do NOT mention edit history or the "edited" button in any public comment or resolution_comment.
-
-### Commits
-
-Cannot clean. Notify author to delete branch or force-push (for unmerged PRs).
-
-## Step 5: Notify
-
-```bash
-node secret-scanning.mjs notify <ISSUE_NUMBER> <AUTHOR> <LOCATION_TYPE> <SECRET_TYPES>
-```
-
-Secret types are comma-separated: `"Discord Bot Token,Feishu App Secret"`
-
-The script picks the right template:
-
-- **comment types**: "your comment … removed and replaced"
-- **body types**: "your issue/PR description … redacted in place"
-- **commit**: "code you committed"
-
-## Step 6: Resolve
-
-```bash
-node secret-scanning.mjs resolve <ALERT_NUMBER>
-# or with custom resolution:
-node secret-scanning.mjs resolve <ALERT_NUMBER> revoked "Custom comment"
-```
-
-Resolution is `revoked` by default. As maintainers we cannot control whether users rotate — our responsibility is to redact + notify. The `revoked` means "this secret should be considered leaked", not "I confirmed it was revoked".
-
-## Step 7: Summary
-
-After processing, create a JSON results file and pass it to the summary command:
-
-```bash
-node secret-scanning.mjs summary /tmp/results.json
-```
-
-The script outputs a block delimited by `---BEGIN SUMMARY---` and `---END SUMMARY---`. **You MUST output the content between these markers verbatim to the user. Do NOT rephrase, reformat, abbreviate, or create your own summary.** The script already includes full URLs for every alert and location.
-
-The JSON format:
-
-```json
-[
-  {
-    "number": 72,
-    "secret_type": "Discord Bot Token",
-    "location_label": "Issue #63101 comment",
-    "location_url": "https://github.com/openclaw/openclaw/issues/63101#issuecomment-xxx",
-    "actions": "Deleted+Recreated+Notified",
-    "history_cleared": true
-  }
-]
-```
-
-For unsupported types, add `"skipped": true, "unsupported_type": "<type>"`.
-
-## Safety Rules
-
-- **Agent reads content, identifies secrets, produces redaction.** Script handles all API calls.
-- **Never include any portion of a secret** in public comments, redaction markers, or terminal output.
-- **Never include alert URLs or numbers** in public comments.
-- **For comments, skip PATCH — go directly to DELETE + recreate.**
-- **Never mention edit history, "edited" button, or commit SHAs** in any public content.
-- **Ask for confirmation** before deleting any comment.
-- **One alert at a time** unless user requests batch.
-- **All public comments in English.**
-- **Skip unsupported location types** and report in summary.

.agents/skills/openclaw-secret-scanning-maintainer/scripts/secret-scanning.mjs

@@ -1,538 +0,0 @@
-#!/usr/bin/env node
-// Secret scanning alert handler for OpenClaw maintainers.
-// Usage: node secret-scanning.mjs <command> [options]
-
-import { execFileSync, spawnSync } from "node:child_process";
-import crypto from "node:crypto";
-import fs from "node:fs";
-import os from "node:os";
-import path from "node:path";
-
-const REPO = "openclaw/openclaw";
-const REPO_URL = `https://github.com/${REPO}`;
-
-// ─── Helpers ────────────────────────────────────────────────────────────────
-
-function fail(message) {
-  console.error(`error: ${message}`);
-  process.exit(1);
-}
-
-function tmpFile(purpose) {
-  const filePath = path.join(os.tmpdir(), `secretscan-${purpose}-${crypto.randomUUID()}`);
-  // 预创建文件，限制权限为 owner-only
-  fs.writeFileSync(filePath, "", { mode: 0o600 });
-  return filePath;
-}
-
-function gh(args, { json = true, allowFailure = false } = {}) {
-  const proc = spawnSync("gh", args, { encoding: "utf8", maxBuffer: 10 * 1024 * 1024 });
-  if (proc.status !== 0 && !allowFailure) {
-    fail(`gh ${args.slice(0, 3).join(" ")} failed:\n${(proc.stderr || proc.stdout || "").trim()}`);
-  }
-  if (!json) return proc.stdout;
-  try {
-    return JSON.parse(proc.stdout);
-  } catch {
-    return proc.stdout;
-  }
-}
-
-function ghGraphQL(query) {
-  return gh(["api", "graphql", "-f", `query=${query}`]);
-}
-
-// ─── Commands ───────────────────────────────────────────────────────────────
-
-/**
- * fetch-alert <number>
- * Fetch alert metadata + locations. Never exposes .secret.
- */
-function cmdFetchAlert(alertNumber) {
-  if (!alertNumber) fail("Usage: fetch-alert <number>");
-
-  const alert = gh(["api", `repos/${REPO}/secret-scanning/alerts/${alertNumber}?hide_secret=true`]);
-
-  const locations = gh([
-    "api",
-    `repos/${REPO}/secret-scanning/alerts/${alertNumber}/locations`,
-    "--paginate",
-    "--slurp",
-  ]);
-  // --paginate + --slurp 确保多页结果合并为一个 JSON 数组
-  const flatLocations = Array.isArray(locations?.[0])
-    ? locations.flat()
-    : Array.isArray(locations)
-      ? locations
-      : [];
-
-  const result = {
-    number: alert.number,
-    state: alert.state,
-    secret_type: alert.secret_type,
-    secret_type_display_name: alert.secret_type_display_name,
-    validity: alert.validity,
-    html_url: alert.html_url,
-    locations: flatLocations.map((loc) => ({
-      type: loc.type,
-      details: loc.details,
-    })),
-  };
-
-  console.log(JSON.stringify(result, null, 2));
-}
-
-/**
- * fetch-content <location-json>
- * Fetch the content and metadata for a specific location.
- * Saves full body to a temp file. Prints metadata + file path to stdout.
- */
-function cmdFetchContent(locationJson) {
-  if (!locationJson) fail("Usage: fetch-content '<location-json>'");
-  const location = JSON.parse(locationJson);
-  const type = location.type;
-  const details = location.details;
-
-  if (
-    type === "issue_comment" ||
-    type === "pull_request_comment" ||
-    type === "pull_request_review_comment"
-  ) {
-    // 从 url 中提取 comment ID
-    const commentUrl =
-      details.issue_comment_url ||
-      details.pull_request_comment_url ||
-      details.pull_request_review_comment_url;
-    if (!commentUrl) fail(`No comment URL in location details`);
-
-    const comment = gh(["api", commentUrl]);
-    const bodyFile = tmpFile("body.md");
-    fs.writeFileSync(bodyFile, comment.body || "");
-
-    // 获取编辑历史
-    const nodeId = comment.node_id;
-    const typeName =
-      type === "pull_request_review_comment" ? "PullRequestReviewComment" : "IssueComment";
-    const gql = ghGraphQL(`{
-      node(id: "${nodeId}") {
-        ... on ${typeName} {
-          userContentEdits(first: 50) {
-            totalCount
-          }
-        }
-      }
-    }`);
-    const editCount = gql?.data?.node?.userContentEdits?.totalCount ?? 0;
-
-    // 提取 issue number（从 html_url）
-    const htmlUrl = comment.html_url || details.html_url || "";
-    const issueMatch = htmlUrl.match(/\/(issues|pull)\/(\d+)/);
-    const issueNumber = issueMatch ? issueMatch[2] : null;
-
-    console.log(
-      JSON.stringify(
-        {
-          type,
-          comment_id: comment.id,
-          node_id: nodeId,
-          author: comment.user?.login,
-          issue_number: issueNumber,
-          html_url: htmlUrl,
-          edit_history_count: editCount,
-          body_file: bodyFile,
-        },
-        null,
-        2,
-      ),
-    );
-  } else if (type === "issue_body") {
-    const issueUrl = details.issue_body_url || details.issue_url;
-    if (!issueUrl) fail("No issue URL in location details");
-
-    const issue = gh(["api", issueUrl]);
-    const bodyFile = tmpFile("body.md");
-    fs.writeFileSync(bodyFile, issue.body || "");
-
-    const nodeId = issue.node_id;
-    const number = issue.number;
-    const gql = ghGraphQL(`{
-      node(id: "${nodeId}") {
-        ... on Issue {
-          userContentEdits(first: 50) {
-            totalCount
-          }
-        }
-      }
-    }`);
-    const editCount = gql?.data?.node?.userContentEdits?.totalCount ?? 0;
-
-    console.log(
-      JSON.stringify(
-        {
-          type,
-          issue_number: number,
-          node_id: nodeId,
-          author: issue.user?.login,
-          html_url: issue.html_url,
-          edit_history_count: editCount,
-          body_file: bodyFile,
-        },
-        null,
-        2,
-      ),
-    );
-  } else if (type === "pull_request_body") {
-    const prUrl = details.pull_request_body_url || details.pull_request_url;
-    if (!prUrl) fail("No PR URL in location details");
-
-    const pr = gh(["api", prUrl]);
-    const bodyFile = tmpFile("body.md");
-    fs.writeFileSync(bodyFile, pr.body || "");
-
-    const nodeId = pr.node_id;
-    const number = pr.number;
-    const gql = ghGraphQL(`{
-      node(id: "${nodeId}") {
-        ... on PullRequest {
-          userContentEdits(first: 50) {
-            totalCount
-          }
-        }
-      }
-    }`);
-    const editCount = gql?.data?.node?.userContentEdits?.totalCount ?? 0;
-
-    console.log(
-      JSON.stringify(
-        {
-          type,
-          pr_number: number,
-          node_id: nodeId,
-          author: pr.user?.login,
-          merged: pr.merged,
-          state: pr.state,
-          html_url: pr.html_url,
-          edit_history_count: editCount,
-          body_file: bodyFile,
-        },
-        null,
-        2,
-      ),
-    );
-  } else if (type === "commit") {
-    console.log(
-      JSON.stringify(
-        {
-          type,
-          commit_sha: details.commit_sha,
-          path: details.path,
-          start_line: details.start_line,
-          end_line: details.end_line,
-          html_url: details.html_url || details.commit_url || details.blob_url || null,
-          // commit 没有 body 文件
-          body_file: null,
-        },
-        null,
-        2,
-      ),
-    );
-  } else {
-    console.log(
-      JSON.stringify(
-        {
-          type,
-          unsupported: true,
-          details,
-        },
-        null,
-        2,
-      ),
-    );
-  }
-}
-
-/**
- * redact-body <issue|pr> <number> <redacted-body-file>
- * PATCH the issue or PR body with redacted content from a file.
- */
-function cmdRedactBody(kind, number, bodyFile) {
-  if (!kind || !number || !bodyFile) {
-    fail("Usage: redact-body <issue|pr> <number> <redacted-body-file>");
-  }
-  if (!fs.existsSync(bodyFile)) fail(`File not found: ${bodyFile}`);
-
-  const endpoint =
-    kind === "pr" ? `repos/${REPO}/pulls/${number}` : `repos/${REPO}/issues/${number}`;
-
-  gh(["api", endpoint, "-X", "PATCH", "-F", `body=@${bodyFile}`]);
-  console.log(JSON.stringify({ ok: true, kind, number: Number(number) }));
-}
-
-/**
- * delete-comment <comment-id>
- * Delete a comment (and all its edit history).
- */
-function cmdDeleteComment(commentId) {
-  if (!commentId) fail("Usage: delete-comment <comment-id>");
-  gh(["api", `repos/${REPO}/issues/comments/${commentId}`, "-X", "DELETE"], { json: false });
-  console.log(JSON.stringify({ ok: true, deleted_comment_id: Number(commentId) }));
-}
-
-/**
- * recreate-comment <issue-number> <body-file>
- * Create a new comment from a file.
- */
-function cmdRecreateComment(issueNumber, bodyFile) {
-  if (!issueNumber || !bodyFile) fail("Usage: recreate-comment <issue-number> <body-file>");
-  if (!fs.existsSync(bodyFile)) fail(`File not found: ${bodyFile}`);
-
-  const result = gh([
-    "api",
-    `repos/${REPO}/issues/${issueNumber}/comments`,
-    "-X",
-    "POST",
-    "-F",
-    `body=@${bodyFile}`,
-  ]);
-
-  console.log(
-    JSON.stringify({
-      ok: true,
-      comment_id: result.id,
-      html_url: result.html_url,
-    }),
-  );
-}
-
-/**
- * notify <issue-or-pr-number> <author> <location-type> <secret-types>
- * Post a notification comment with the correct template for the location type.
- */
-function cmdNotify(issueNumber, author, locationType, secretTypes) {
-  if (!issueNumber || !author || !locationType || !secretTypes) {
-    fail("Usage: notify <issue-or-pr-number> <author> <location-type> <secret-types-comma-sep>");
-  }
-
-  const types = secretTypes.split(",").map((s) => s.trim());
-  const typeList = types.map((t, i) => `${i + 1}. **${t}**`).join("\n");
-
-  let locationDesc;
-  let actionDesc;
-  if (
-    locationType === "issue_comment" ||
-    locationType === "pull_request_comment" ||
-    locationType === "pull_request_review_comment"
-  ) {
-    locationDesc = "your comment";
-    actionDesc = "The affected comment has been removed and replaced with a redacted version.";
-  } else if (locationType === "issue_body") {
-    locationDesc = "your issue description";
-    actionDesc = "The affected content has been redacted in place.";
-  } else if (locationType === "pull_request_body") {
-    locationDesc = "your pull request description";
-    actionDesc = "The affected content has been redacted in place.";
-  } else if (locationType === "commit") {
-    locationDesc = "code you committed";
-    actionDesc = "";
-  } else {
-    locationDesc = "your content";
-    actionDesc = "";
-  }
-
-  const body = [
-    `@${author} :warning: **Security Notice: Secret Leakage Detected**`,
-    "",
-    `GitHub Secret Scanning detected the following exposed secret types in ${locationDesc}:`,
-    "",
-    typeList,
-    "",
-    actionDesc,
-    "",
-    "**Please rotate these credentials immediately.**",
-    "",
-    "These secrets were publicly exposed and should be considered compromised.",
-  ]
-    .filter((line) => line !== undefined)
-    .join("\n");
-
-  const bodyFile = tmpFile("notify.md");
-  fs.writeFileSync(bodyFile, body);
-
-  const result = gh([
-    "api",
-    `repos/${REPO}/issues/${issueNumber}/comments`,
-    "-X",
-    "POST",
-    "-F",
-    `body=@${bodyFile}`,
-  ]);
-
-  console.log(
-    JSON.stringify({
-      ok: true,
-      comment_id: result.id,
-      html_url: result.html_url,
-    }),
-  );
-}
-
-/**
- * resolve <alert-number> [resolution] [comment]
- * Close a secret scanning alert.
- */
-function cmdResolve(alertNumber, resolution, comment) {
-  if (!alertNumber) fail("Usage: resolve <alert-number> [resolution] [comment]");
-
-  const res = resolution || "revoked";
-  const resComment = comment || "Content redacted and author notified to rotate credentials.";
-
-  const result = gh([
-    "api",
-    `repos/${REPO}/secret-scanning/alerts/${alertNumber}`,
-    "-X",
-    "PATCH",
-    "-f",
-    `state=resolved`,
-    "-f",
-    `resolution=${res}`,
-    "-f",
-    `resolution_comment=${resComment}`,
-  ]);
-
-  console.log(
-    JSON.stringify({
-      ok: true,
-      number: result.number,
-      state: result.state,
-      resolution: result.resolution,
-      resolved_at: result.resolved_at,
-    }),
-  );
-}
-
-/**
- * list-open
- * List all open secret scanning alerts.
- */
-function cmdListOpen() {
-  const alerts = gh([
-    "api",
-    `repos/${REPO}/secret-scanning/alerts?hide_secret=true&state=open`,
-    "--paginate",
-    "--slurp",
-  ]);
-
-  // --slurp 将分页结果合并为 [[page1], [page2], ...] 需要 flat
-  const flat = Array.isArray(alerts?.[0]) ? alerts.flat() : Array.isArray(alerts) ? alerts : [];
-  const rows = flat.map((a) => ({
-    number: a.number,
-    secret_type_display_name: a.secret_type_display_name,
-    html_url: a.html_url,
-    first_location_html_url: a.first_location_detected?.html_url || null,
-  }));
-
-  console.log(JSON.stringify(rows, null, 2));
-}
-
-/**
- * summary <json-file>
- * Print a formatted summary table from a JSON results file.
- */
-function cmdSummary(jsonFile) {
-  if (!jsonFile) fail("Usage: summary <json-file>");
-  if (!fs.existsSync(jsonFile)) fail(`File not found: ${jsonFile}`);
-
-  const results = JSON.parse(fs.readFileSync(jsonFile, "utf8"));
-  const lines = [];
-
-  lines.push("---BEGIN SUMMARY---");
-  lines.push("");
-  lines.push("## Secret Scanning Results");
-  lines.push("");
-  lines.push("| Alert | Type | Location | Actions | Edit History |");
-  lines.push("|-------|------|----------|---------|--------------|");
-
-  const needsPurge = [];
-
-  for (const r of results) {
-    const alertLink = `#${r.number} ${REPO_URL}/security/secret-scanning/${r.number}`;
-    const locationLink = r.location_url
-      ? `${r.location_label} ${r.location_url}`
-      : r.location_label;
-    const history = r.history_cleared ? "Cleared" : "⚠️ History remains";
-
-    lines.push(`| ${alertLink} | ${r.secret_type} | ${locationLink} | ${r.actions} | ${history} |`);
-
-    if (!r.history_cleared && r.location_url) {
-      needsPurge.push(r);
-    }
-  }
-
-  if (needsPurge.length > 0) {
-    lines.push("");
-    lines.push("Issues requiring GitHub Support to purge edit history:");
-    for (const r of needsPurge) {
-      lines.push(`- ${r.location_label} ${r.location_url} — ${r.secret_type}`);
-    }
-    lines.push(
-      `Contact: https://support.github.com/contact — request purge of userContentEdits for the above issues.`,
-    );
-  }
-
-  const skipped = results.filter((r) => r.skipped);
-  if (skipped.length > 0) {
-    lines.push("");
-    lines.push(
-      "⚠️ The following alerts were skipped because their location type is not supported:",
-    );
-    for (const r of skipped) {
-      lines.push(
-        `- Alert #${r.number}: unsupported type "${r.unsupported_type}" — ${REPO_URL}/security/secret-scanning/${r.number}`,
-      );
-    }
-    lines.push("Please update the skill to define handling for these types.");
-  }
-
-  lines.push("");
-  lines.push("---END SUMMARY---");
-
-  console.log(lines.join("\n"));
-}
-
-// ─── Dispatch ───────────────────────────────────────────────────────────────
-
-const [command, ...args] = process.argv.slice(2);
-
-const commands = {
-  "fetch-alert": () => cmdFetchAlert(args[0]),
-  "fetch-content": () => cmdFetchContent(args[0]),
-  "redact-body": () => cmdRedactBody(args[0], args[1], args[2]),
-  "delete-comment": () => cmdDeleteComment(args[0]),
-  "recreate-comment": () => cmdRecreateComment(args[0], args[1]),
-  notify: () => cmdNotify(args[0], args[1], args[2], args[3]),
-  resolve: () => cmdResolve(args[0], args[1], args[2]),
-  "list-open": () => cmdListOpen(),
-  summary: () => cmdSummary(args[0]),
-};
-
-if (!command || !commands[command]) {
-  console.error(
-    [
-      "Usage: node secret-scanning.mjs <command> [args]",
-      "",
-      "Commands:",
-      "  fetch-alert <number>             Fetch alert metadata + locations",
-      "  fetch-content '<location-json>'   Fetch content for a location",
-      "  redact-body <issue|pr> <n> <file> PATCH body with redacted file",
-      "  delete-comment <comment-id>       Delete a comment",
-      "  recreate-comment <issue-n> <file> Create replacement comment",
-      "  notify <n> <author> <type> <types> Post notification",
-      "  resolve <n> [resolution] [comment] Close alert",
-      "  list-open                          List open alerts",
-      "  summary <json-file>               Print formatted summary",
-    ].join("\n"),
-  );
-  process.exit(1);
-}
-
-commands[command]();

.env.example

@@ -14,15 +14,12 @@
 # -----------------------------------------------------------------------------
 # Gateway auth + paths
 # -----------------------------------------------------------------------------
-# Required if the gateway binds beyond loopback. Leave blank to have OpenClaw
-# auto-generate a token on first start, or provide your own using
-# `openssl rand -hex 32`. The gateway will refuse to start if this is set to
-# the documented example placeholder, so never copy-paste an example value
-# from docs or tutorials into this file verbatim.
-OPENCLAW_GATEWAY_TOKEN=
+# Recommended if the gateway binds beyond loopback.
+OPENCLAW_GATEWAY_TOKEN=change-me-to-a-long-random-token
+# Example generator: openssl rand -hex 32
 
 # Optional alternative auth mode (use token OR password).
-# OPENCLAW_GATEWAY_PASSWORD=
+# OPENCLAW_GATEWAY_PASSWORD=change-me-to-a-strong-password
 
 # Optional path overrides (defaults shown for reference).
 # OPENCLAW_STATE_DIR=~/.openclaw

.github/actionlint.yaml

@@ -7,7 +7,6 @@ self-hosted-runner:
     - blacksmith-8vcpu-ubuntu-2404
     - blacksmith-8vcpu-windows-2025
     - blacksmith-16vcpu-ubuntu-2404
-    - blacksmith-32vcpu-ubuntu-2404
     - blacksmith-16vcpu-windows-2025
     - blacksmith-32vcpu-windows-2025
     - blacksmith-16vcpu-ubuntu-2404-arm

.github/labeler.yml

@@ -293,10 +293,6 @@
   - changed-files:
       - any-glob-to-any-file:
           - "extensions/kilocode/**"
-"extensions: lmstudio":
-  - changed-files:
-      - any-glob-to-any-file:
-          - "extensions/lmstudio/**"
 "extensions: openai":
   - changed-files:
       - any-glob-to-any-file:

.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
@@ -1008,9 +1001,6 @@ jobs:
       - name: Smoke test built bundled plugin singleton
         run: pnpm test:build:singleton
 
-      - name: Smoke test built bundled runtime deps
-        run: pnpm test:build:bundled-runtime-deps
-
       - name: Check CLI startup memory
         run: pnpm test:startup:memory
 

.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

@@ -4,7 +4,7 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: Release tag to publish, or a full 40-character main commit SHA for validation-only preflight (for example v2026.3.22 or 0123456789abcdef0123456789abcdef01234567)
+        description: Release tag to publish (for example v2026.3.22, v2026.3.22-beta.1, or fallback v2026.3.22-1)
         required: true
         type: string
       preflight_only:
@@ -29,14 +29,9 @@ on:
         required: true
         default: false
         type: boolean
-      sync_stable_dist_tags:
-        description: Skip publish and point both latest and beta at an already-published stable version
-        required: true
-        default: false
-        type: boolean
 
 concurrency:
-  group: openclaw-npm-release-${{ github.event_name == 'workflow_dispatch' && format('{0}-{1}-{2}-{3}', inputs.tag, inputs.npm_dist_tag, inputs.promote_beta_to_latest, inputs.sync_stable_dist_tags) || github.ref }}
+  group: openclaw-npm-release-${{ github.event_name == 'workflow_dispatch' && format('{0}-{1}-{2}', inputs.tag, inputs.npm_dist_tag, inputs.promote_beta_to_latest) || github.ref }}
   cancel-in-progress: false
 
 env:
@@ -45,31 +40,23 @@ env:
   PNPM_VERSION: "10.32.1"
 
 jobs:
-  # PLEASE DON'T ADD LONG-RUNNING OR FLAKY CHECKS TO THE npm RELEASE PATH.
-  # KEEP THIS WORKFLOW SHORT AND DETERMINISTIC OR IT CAN GET STUCK AND JEOPARDIZE THE RELEASE.
-  # RELEASE-TIME LIVE OR END-TO-END VALIDATION BELONGS IN openclaw-release-checks.yml.
   preflight_openclaw_npm:
-    if: ${{ inputs.preflight_only && !inputs.promote_beta_to_latest && !inputs.sync_stable_dist_tags }}
-    runs-on: blacksmith-32vcpu-ubuntu-2404
+    if: ${{ inputs.preflight_only && !inputs.promote_beta_to_latest }}
+    runs-on: ubuntu-latest
     permissions:
       contents: read
     steps:
-      - name: Validate release ref input format
+      - name: Validate tag input format
         env:
-          RELEASE_REF: ${{ inputs.tag }}
-          PREFLIGHT_ONLY: ${{ inputs.preflight_only }}
+          RELEASE_TAG: ${{ inputs.tag }}
           RELEASE_NPM_DIST_TAG: ${{ inputs.npm_dist_tag }}
         run: |
           set -euo pipefail
-          if [[ ! "${RELEASE_REF}" =~ ^v[0-9]{4}\.[1-9][0-9]*\.[1-9][0-9]*((-beta\.[1-9][0-9]*)|(-[1-9][0-9]*))?$ ]] && [[ ! "${RELEASE_REF}" =~ ^[0-9a-fA-F]{40}$ ]]; then
-            echo "Invalid release ref format: ${RELEASE_REF}"
+          if [[ ! "${RELEASE_TAG}" =~ ^v[0-9]{4}\.[1-9][0-9]*\.[1-9][0-9]*((-beta\.[1-9][0-9]*)|(-[1-9][0-9]*))?$ ]]; then
+            echo "Invalid release tag format: ${RELEASE_TAG}"
             exit 1
           fi
-          if [[ "${RELEASE_REF}" =~ ^[0-9a-fA-F]{40}$ ]] && [[ "${PREFLIGHT_ONLY}" != "true" ]]; then
-            echo "Full commit SHA input is only supported for validation-only preflight runs."
-            exit 1
-          fi
-          if [[ "${RELEASE_REF}" == *"-beta."* && "${RELEASE_NPM_DIST_TAG}" != "beta" ]]; then
+          if [[ "${RELEASE_TAG}" == *"-beta."* && "${RELEASE_NPM_DIST_TAG}" != "beta" ]]; then
             echo "Beta prerelease tags must publish to npm dist-tag beta."
             exit 1
           fi
@@ -83,7 +70,7 @@ jobs:
       - name: Checkout
         uses: actions/checkout@v6
         with:
-          ref: ${{ inputs.tag }}
+          ref: refs/tags/${{ inputs.tag }}
           fetch-depth: 0
 
       - name: Setup Node environment
@@ -123,42 +110,50 @@ jobs:
       - name: Build Control UI
         run: pnpm ui:build
 
-      - name: Validate release metadata
+      - name: Validate release tag and package metadata
         if: ${{ inputs.preflight_run_id == '' }}
         env:
           OPENCLAW_NPM_RELEASE_SKIP_PACK_CHECK: "1"
-          RELEASE_REF: ${{ inputs.tag }}
-          PREFLIGHT_ONLY: ${{ inputs.preflight_only }}
+          RELEASE_TAG: ${{ inputs.tag }}
           RELEASE_MAIN_REF: origin/main
           OPENCLAW_NPM_PUBLISH_TAG: ${{ inputs.npm_dist_tag }}
         run: |
           set -euo pipefail
           RELEASE_SHA=$(git rev-parse HEAD)
-          export RELEASE_SHA RELEASE_MAIN_REF
+          export RELEASE_SHA RELEASE_TAG RELEASE_MAIN_REF
           # Fetch the full main ref so merge-base ancestry checks keep working
           # for older tagged commits that are still contained in main.
           git fetch --no-tags origin +refs/heads/main:refs/remotes/origin/main
-          if [[ "${RELEASE_REF}" =~ ^[0-9a-fA-F]{40}$ ]]; then
-            MAIN_SHA="$(git rev-parse origin/main)"
-            if [[ "${RELEASE_SHA}" != "${MAIN_SHA}" ]]; then
-              echo "Validation-only SHA mode only supports the current origin/main HEAD." >&2
-              exit 1
-            fi
-            RELEASE_TAG="v$(node -p "require('./package.json').version")"
-            export RELEASE_TAG
-            echo "Validation-only SHA mode: using synthetic release tag ${RELEASE_TAG} for package metadata checks."
-          else
-            RELEASE_TAG="${RELEASE_REF}"
-            export RELEASE_TAG
-          fi
           pnpm release:openclaw:npm:check
 
-      # KEEP THIS LANE LIMITED TO FAST, REPEATABLE RELEASE READINESS CHECKS.
-      # IF A CHECK CAN TAKE A LONG TIME, NEEDS LIVE CREDENTIALS, OR IS KNOWN TO BE FLAKY,
-      # IT BELONGS IN openclaw-release-checks.yml INSTEAD OF BLOCKING npm PUBLISH.
       - name: Verify release contents
         run: pnpm release:check
 
+      - name: Validate live cache credentials
+        if: ${{ github.ref == 'refs/heads/main' }}
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+        run: |
+          set -euo pipefail
+          if [[ -z "${OPENAI_API_KEY}" ]]; then
+            echo "Missing OPENAI_API_KEY secret for release live cache validation." >&2
+            exit 1
+          fi
+          if [[ -z "${ANTHROPIC_API_KEY}" ]]; then
+            echo "Missing ANTHROPIC_API_KEY secret for release live cache validation." >&2
+            exit 1
+          fi
+
+      - name: Verify live prompt cache floors
+        if: ${{ github.ref == 'refs/heads/main' }}
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+          OPENCLAW_LIVE_CACHE_TEST: "1"
+          OPENCLAW_LIVE_TEST: "1"
+        run: pnpm test:live:cache
+
       - name: Pack prepared npm tarball
         id: packed_tarball
         env:
@@ -246,8 +241,8 @@ jobs:
           if-no-files-found: error
 
   validate_publish_request:
-    if: ${{ !inputs.preflight_only && !inputs.promote_beta_to_latest && !inputs.sync_stable_dist_tags }}
-    runs-on: blacksmith-32vcpu-ubuntu-2404
+    if: ${{ !inputs.preflight_only && !inputs.promote_beta_to_latest }}
+    runs-on: ubuntu-latest
     permissions:
       contents: read
     steps:
@@ -272,10 +267,9 @@ jobs:
           fi
 
   publish_openclaw_npm:
-    # KEEP THE REAL RELEASE/PUBLISH PATH ON A GITHUB-HOSTED RUNNER.
-    # npm trusted publishing + provenance requires this to stay on ubuntu-latest.
+    # npm trusted publishing + provenance requires a GitHub-hosted runner.
     needs: [validate_publish_request]
-    if: ${{ !inputs.preflight_only && !inputs.promote_beta_to_latest && !inputs.sync_stable_dist_tags }}
+    if: ${{ !inputs.preflight_only && !inputs.promote_beta_to_latest }}
     runs-on: ubuntu-latest
     environment: npm-release
     permissions:
@@ -413,10 +407,7 @@ jobs:
           bash scripts/openclaw-npm-publish.sh --publish "${publish_target}"
 
   promote_beta_to_latest:
-    # KEEP THE MUTATING RELEASE PATH ON A GITHUB-HOSTED RUNNER TOO.
-    # This job changes the public npm dist-tags, so we keep it aligned with the
-    # real release path instead of moving it onto the larger Blacksmith runners.
-    if: ${{ inputs.promote_beta_to_latest && !inputs.sync_stable_dist_tags }}
+    if: ${{ inputs.promote_beta_to_latest }}
     runs-on: ubuntu-latest
     environment: npm-release
     permissions:
@@ -502,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)"
@@ -511,101 +501,3 @@ jobs:
             exit 1
           fi
           echo "Promoted openclaw@${RELEASE_VERSION} from beta to latest."
-
-  sync_stable_dist_tags:
-    # This mode is for direct stable publishes where latest is correct but beta
-    # should also point at the same stable build after release.
-    if: ${{ inputs.sync_stable_dist_tags && !inputs.promote_beta_to_latest }}
-    runs-on: ubuntu-latest
-    environment: npm-release
-    permissions:
-      contents: read
-    steps:
-      - name: Require main workflow ref for dist-tag sync
-        env:
-          WORKFLOW_REF: ${{ github.ref }}
-        run: |
-          set -euo pipefail
-          if [[ "${WORKFLOW_REF}" != "refs/heads/main" ]]; then
-            echo "Dist-tag sync runs must be dispatched from main."
-            exit 1
-          fi
-
-      - name: Validate sync inputs
-        env:
-          PREFLIGHT_ONLY: ${{ inputs.preflight_only }}
-          PREFLIGHT_RUN_ID: ${{ inputs.preflight_run_id }}
-          RELEASE_NPM_DIST_TAG: ${{ inputs.npm_dist_tag }}
-        run: |
-          set -euo pipefail
-          if [[ "${PREFLIGHT_ONLY}" == "true" ]]; then
-            echo "Dist-tag sync mode cannot run with preflight_only=true."
-            exit 1
-          fi
-          if [[ -n "${PREFLIGHT_RUN_ID}" ]]; then
-            echo "Dist-tag sync mode does not use preflight_run_id."
-            exit 1
-          fi
-          if [[ "${RELEASE_NPM_DIST_TAG}" != "latest" ]]; then
-            echo "Dist-tag sync mode expects npm_dist_tag=latest because it points latest and beta at the stable version."
-            exit 1
-          fi
-
-      - name: Validate stable tag input format
-        env:
-          RELEASE_TAG: ${{ inputs.tag }}
-        run: |
-          set -euo pipefail
-          if [[ ! "${RELEASE_TAG}" =~ ^v[0-9]{4}\.[1-9][0-9]*\.[1-9][0-9]*(-[1-9][0-9]*)?$ ]]; then
-            echo "Invalid stable release tag format: ${RELEASE_TAG}" >&2
-            exit 1
-          fi
-          echo "RELEASE_VERSION=${RELEASE_TAG#v}" >> "$GITHUB_ENV"
-
-      - name: Checkout
-        uses: actions/checkout@v6
-
-      - name: Setup Node environment
-        uses: ./.github/actions/setup-node-env
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-          pnpm-version: ${{ env.PNPM_VERSION }}
-          install-bun: "false"
-          use-sticky-disk: "false"
-          install-deps: "false"
-
-      - name: Validate published stable version
-        env:
-          RELEASE_VERSION: ${{ env.RELEASE_VERSION }}
-        run: |
-          set -euo pipefail
-          if ! npm view "openclaw@${RELEASE_VERSION}" version >/dev/null 2>&1; then
-            echo "openclaw@${RELEASE_VERSION} is not published on npm." >&2
-            exit 1
-          fi
-
-          echo "Current latest dist-tag: $(npm view openclaw dist-tags.latest)"
-          echo "Current beta dist-tag: $(npm view openclaw dist-tags.beta)"
-
-      - name: Sync stable dist-tags
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          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
-          npm dist-tag add "openclaw@${RELEASE_VERSION}" beta
-
-          synced_latest="$(npm view openclaw dist-tags.latest)"
-          synced_beta="$(npm view openclaw dist-tags.beta)"
-          if [[ "${synced_latest}" != "${RELEASE_VERSION}" ]]; then
-            echo "npm latest points at ${synced_latest}, expected ${RELEASE_VERSION} after sync." >&2
-            exit 1
-          fi
-          if [[ "${synced_beta}" != "${RELEASE_VERSION}" ]]; then
-            echo "npm beta points at ${synced_beta}, expected ${RELEASE_VERSION} after sync." >&2
-            exit 1
-          fi
-          echo "Synced openclaw@${RELEASE_VERSION} to npm latest and beta."

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

@@ -1,120 +0,0 @@
-name: OpenClaw Release Checks
-
-on:
-  workflow_dispatch:
-    inputs:
-      ref:
-        description: Existing release tag or current full 40-character main commit SHA to validate (for example v2026.4.12 or 0123456789abcdef0123456789abcdef01234567)
-        required: true
-        type: string
-
-concurrency:
-  group: openclaw-release-checks-${{ inputs.ref }}
-  cancel-in-progress: false
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
-  NODE_VERSION: "24.x"
-  PNPM_VERSION: "10.32.1"
-
-jobs:
-  # THIS WORKFLOW EXISTS SO RELEASE-TIME LIVE CHECKS CAN RUN WITHOUT BLOCKING npm PUBLISH.
-  # PUT THE SLOWER, EXTERNAL, OR SOMETIMES-FLAKY RELEASE CHECKS HERE INSTEAD OF
-  # RECOUPLING THEM TO openclaw-npm-release.yml.
-  validate_release_live_cache:
-    runs-on: blacksmith-32vcpu-ubuntu-2404
-    timeout-minutes: 60
-    permissions:
-      contents: read
-    steps:
-      - name: Require main workflow ref for release checks
-        env:
-          WORKFLOW_REF: ${{ github.ref }}
-        run: |
-          set -euo pipefail
-          if [[ "${WORKFLOW_REF}" != "refs/heads/main" ]]; then
-            echo "Release checks must be dispatched from main so the workflow logic and secrets stay canonical." >&2
-            exit 1
-          fi
-
-      - name: Validate ref input
-        env:
-          RELEASE_REF: ${{ inputs.ref }}
-        run: |
-          set -euo pipefail
-          if [[ ! "${RELEASE_REF}" =~ ^v[0-9]{4}\.[1-9][0-9]*\.[1-9][0-9]*((-beta\.[1-9][0-9]*)|(-[1-9][0-9]*))?$ ]] && [[ ! "${RELEASE_REF}" =~ ^[0-9a-fA-F]{40}$ ]]; then
-            echo "Expected an existing release tag or current full 40-character main commit SHA, got: ${RELEASE_REF}" >&2
-            exit 1
-          fi
-
-      - name: Checkout selected ref
-        uses: actions/checkout@v6
-        with:
-          ref: ${{ inputs.ref }}
-          fetch-depth: 0
-
-      - name: Resolve checked-out SHA
-        id: ref
-        run: echo "sha=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT"
-
-      - name: Validate selected ref is on main
-        env:
-          RELEASE_REF: ${{ inputs.ref }}
-        run: |
-          set -euo pipefail
-          git fetch --no-tags origin +refs/heads/main:refs/remotes/origin/main
-          if [[ "${RELEASE_REF}" =~ ^[0-9a-fA-F]{40}$ ]]; then
-            MAIN_SHA="$(git rev-parse origin/main)"
-            if [[ "$(git rev-parse HEAD)" != "${MAIN_SHA}" ]]; then
-              echo "Commit SHA mode only supports the current origin/main HEAD. Use a release tag for older commits." >&2
-              exit 1
-            fi
-          else
-            git merge-base --is-ancestor HEAD origin/main
-          fi
-
-      - name: Setup Node environment
-        uses: ./.github/actions/setup-node-env
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-          pnpm-version: ${{ env.PNPM_VERSION }}
-          install-bun: "true"
-          use-sticky-disk: "false"
-
-      - name: Validate live cache credentials
-        env:
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-        run: |
-          set -euo pipefail
-          if [[ -z "${OPENAI_API_KEY}" ]]; then
-            echo "Missing OPENAI_API_KEY secret for release checks." >&2
-            exit 1
-          fi
-          if [[ -z "${ANTHROPIC_API_KEY}" ]]; then
-            echo "Missing ANTHROPIC_API_KEY secret for release checks." >&2
-            exit 1
-          fi
-
-      # KEEP RELEASE-TIME LIVE COVERAGE HERE SO OPERATORS CAN RUN IT ON DEMAND
-      # WITHOUT MAKING THE PUBLISH PATH WAIT FOR A SLOW OR FLAKY EXTERNAL CHECK.
-      - name: Verify live prompt cache floors
-        env:
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
-          OPENCLAW_LIVE_CACHE_TEST: "1"
-          OPENCLAW_LIVE_TEST: "1"
-        run: pnpm test:live:cache
-
-      - name: Summarize validated ref
-        env:
-          RELEASE_REF: ${{ inputs.ref }}
-          RELEASE_SHA: ${{ steps.ref.outputs.sha }}
-        run: |
-          {
-            echo "## Release checks"
-            echo
-            echo "- Requested ref: \`${RELEASE_REF}\`"
-            echo "- Validated SHA: \`${RELEASE_SHA}\`"
-            echo "- Check: \`pnpm test:live:cache\`"
-          } >> "$GITHUB_STEP_SUMMARY"

.github/workflows/parity-gate.yml

@@ -1,93 +0,0 @@
-name: Parity gate
-
-on:
-  pull_request:
-    types: [opened, reopened, synchronize, ready_for_review]
-    paths:
-      - "extensions/qa-lab/**"
-      - "extensions/qa-channel/**"
-      - "extensions/openai/**"
-      - "qa/scenarios/**"
-      - "src/agents/**"
-      - "src/context-engine/**"
-      - "src/gateway/**"
-      - "src/media/**"
-      - ".github/workflows/parity-gate.yml"
-
-permissions:
-  contents: read
-
-concurrency:
-  group: parity-gate-${{ github.event.pull_request.number || github.sha }}
-  cancel-in-progress: true
-
-jobs:
-  parity-gate:
-    name: Run the GPT-5.4 / Opus 4.6 parity gate against the qa-lab mock
-    if: ${{ github.event.pull_request.draft != true }}
-    runs-on: blacksmith-8vcpu-ubuntu-2404
-    timeout-minutes: 20
-    env:
-      # Fence the gate off from any real provider credentials. The qa-lab
-      # mock server + auth staging (PR N) should be enough to produce a
-      # meaningful verdict without touching a real API. If any of these
-      # leak into the job env, fail hard instead of silently running
-      # against a live provider and burning real budget.
-      OPENAI_API_KEY: ""
-      ANTHROPIC_API_KEY: ""
-      OPENCLAW_LIVE_OPENAI_KEY: ""
-      OPENCLAW_LIVE_ANTHROPIC_KEY: ""
-      OPENCLAW_LIVE_GEMINI_KEY: ""
-      OPENCLAW_LIVE_SETUP_TOKEN_VALUE: ""
-    steps:
-      - name: Checkout PR
-        uses: actions/checkout@v4
-
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "22.14.0"
-          cache: "pnpm"
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Run GPT-5.4 lane
-        run: |
-          pnpm openclaw qa suite \
-            --provider-mode mock-openai \
-            --parity-pack agentic \
-            --model openai/gpt-5.4 \
-            --alt-model openai/gpt-5.4-alt \
-            --output-dir .artifacts/qa-e2e/gpt54
-
-      - name: Run Opus 4.6 lane
-        run: |
-          pnpm openclaw qa suite \
-            --provider-mode mock-openai \
-            --parity-pack agentic \
-            --model anthropic/claude-opus-4-6 \
-            --alt-model anthropic/claude-sonnet-4-6 \
-            --output-dir .artifacts/qa-e2e/opus46
-
-      - name: Generate parity report
-        run: |
-          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 \
-            --candidate-label openai/gpt-5.4 \
-            --baseline-label anthropic/claude-opus-4-6 \
-            --output-dir .artifacts/qa-e2e/parity
-
-      - name: Upload parity artifacts
-        if: always()
-        uses: actions/upload-artifact@v4
-        with:
-          name: parity-gate-${{ github.event.pull_request.number || github.sha }}
-          path: .artifacts/qa-e2e/
-          retention-days: 14
-          if-no-files-found: warn

.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,122 +8,6 @@ Docs: https://docs.openclaw.ai
 
 ### Fixes
 
-- Agents/context engines: run opt-in turn maintenance as idle-aware background work so the next foreground turn no longer waits on proactive maintenance. (#65233) thanks @100yenadmin
-
-- Plugins/status: report the registered context-engine IDs in `plugins inspect` instead of the owning plugin ID, so non-matching engine IDs and multi-engine plugins are classified correctly. (#58766) thanks @zhuisDEV
-- Context engines: reject resolved plugin engines whose reported `info.id` does not match their registered slot id, so malformed engines fail fast before id-based runtime branches can misbehave. (#63222) Thanks @fuller-stack-dev.
-- WhatsApp: patch installed Baileys media encryption writes during OpenClaw postinstall so the default npm/install.sh delivery path waits for encrypted media files to finish flushing before readback, avoiding transient `ENOENT` crashes on image sends. (#65896) Thanks @frankekn.
-- Gateway/update: unify service entrypoint resolution around the canonical bundled gateway entrypoint so update, reinstall, and doctor repair stop drifting between stale `dist/entry.js` and current `dist/index.js` paths. (#65984) Thanks @mbelinky.
-## 2026.4.12
-
-### Changes
-
-- QA/lab: add Convex-backed pooled Telegram credential leasing plus `openclaw qa credentials` admin commands and broker setup docs. (#65596) Thanks @joshavant.
-- 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 `/verbose` 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.
-- 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.
-- CLI/exec policy: add a local `openclaw exec-policy` command with `show`, `preset`, and `set` subcommands for synchronizing requested `tools.exec.*` config with the local exec approvals file, plus follow-up hardening for node-host rejection, rollback safety, and sync conflict detection. (#64050)
-- 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.
-- QA/testing: add a `--runner multipass` lane for `openclaw qa suite` 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.
-- 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.
-- 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.
-- 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.
-- 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.
-- QA/Telegram: add a live `openclaw qa telegram` 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.
-- Models/Codex: add the bundled Codex provider and plugin-owned app-server harness so `codex/gpt-*` models use Codex-managed auth, native threads, model discovery, and compaction while `openai/gpt-*` stays on the normal OpenAI provider path. (#64298) Thanks @steipete.
-- Models/providers: add a bundled LM Studio provider with onboarding, runtime model discovery, stream preload support, and memory-search embeddings for local/self-hosted OpenAI-compatible models. (#53248) Thanks @rugvedS07.
-- Plugins/loading: narrow CLI, provider, and channel activation to manifest-declared needs, preserve explicit scope and trust boundaries, and centralize manifest-owner policy so startup, command discovery, and runtime activation avoid loading unrelated plugin runtime. (#65120, #65259, #65298, #65429, #65459) Thanks @vincentkoc.
-- Memory/active-memory: default QMD recall to search and surface better search-path telemetry so memory-backed recall works more predictably out of the box. (#65068) Thanks @Takhoffman.
-- Docs/providers: expand bundled provider docs with richer capability, env-var, and setup guidance across provider pages.
-- Docs/memory-wiki: add the recommended QMD + bridge-mode hybrid recipe plus zero-artifact troubleshooting guidance for `memory-wiki` bridge setups. (#63165) Thanks @sercada and @vincentkoc.
-
-### Fixes
-
-- fix(security): remove busybox/toybox from interpreter-like safe bins [AI-assisted]. (#65713) Thanks @pgondhi987.
-- fix(approval-auth): prevent empty approver list from granting explicit approval authorization [AI]. (#65714) Thanks @pgondhi987.
-- fix(security): broaden shell-wrapper detection and block env-argv assignment injection [AI-assisted]. (#65717) Thanks @pgondhi987.
-- Gateway/startup: defer scheduled services until sidecars finish, gate chat history and model listing during sidecar resume, and let Control UI retry startup-gated history loads so Sandbox wake resumes channels first. (#65365) Thanks @lml2468.
-- Control UI/chat: load the live gateway slash-command catalog into the composer and command palette so dock commands, plugin commands, and direct skill aliases appear in chat, while keeping trusted local commands authoritative and bounding remote command metadata. (#65620) Thanks @BunsDev.
-- CLI/update: respawn tracked plugin refresh from the updated entrypoint after package self-updates so `openclaw update` stops failing on stale hashed `dist/install.runtime-*.js` chunk imports. (#65471)
-- Memory/active-memory: keep recall runs on the resolved channel when wrappers like `mx-claw` are enabled, improve lexical fallback ranking, and keep lexical boosts out of hybrid search so recall finds the right memories more consistently. (#65049, #65395) Thanks @Takhoffman.
-- Dreaming: consume managed heartbeat events exactly once, stage light-sleep confidence from all recorded short-term signals, wake scheduled jobs immediately, raise dreaming-only promotion enough to cross the durable-memory gate, and stop dreaming from re-ingesting its own narrative transcripts.
-- Dreaming/narrative: harden transient narrative cleanup by retrying timed-out deletes, scrubbing stale dreaming session artifacts through the lock-aware session-store path, and isolating transient narrative session keys per workspace. (#65320, #61674)
-- Memory/wiki: preserve Unicode letters, digits, and combining marks in wiki slugs and contradiction clustering, and cap Unicode filename segments to safe byte lengths so non-ASCII titles stop collapsing or overflowing path limits. (#64742) Thanks @zhouhe-xydt.
-- Memory/short-term recall: allow nested daily notes under `memory/**/YYYY-MM-DD.md` to feed short-term recall, while still excluding generated dream reports under `memory/dreaming/**` so dreaming does not promote its own output. (#64682) Thanks @SARAMALI15792.
-- UI/WebChat: hide synthetic transcript-repair tool results from chat history reloads so internal recovery markers do not leak into visible chat after reconnects. (#65247) Thanks @wangwllu.
-- WhatsApp/outbound: fall back to the first `mediaUrls` entry when `mediaUrl` is empty so gateway media sends stop silently dropping attachments that already have a resolved media list. (#64394) Thanks @eric-fr4 and @vincentkoc.
-- Doctor/Discord: stop `openclaw doctor --fix` from rewriting legacy Discord preview-streaming config into the nested modern shape, so downgrades can still recover without hand-editing `channels.discord.streaming`. (#65035) Thanks @vincentkoc.
-- Gateway/auth: blank the shipped example gateway credential in `.env.example` and fail startup when a copied placeholder token or password is still configured, so operators cannot accidentally launch with a publicly known secret. (#64586) Thanks @navarrotech and @vincentkoc.
-
-- 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.
-- Agents/queueing: carry orphaned active-turn user text into the next prompt before repairing transcript ordering, so follow-up messages that arrive mid-run are no longer silently dropped. (#65388) Thanks @adminfedres and @vincentkoc.
-- Gateway/keepalive: stop marking WebSocket tick broadcasts as droppable so slow or backpressured clients do not self-disconnect with `tick timeout` while long-running work is still alive. (#65256) Thanks @100yenadmin and @vincentkoc.
-- 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.
-- 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.
-- Gateway/keepalive: stop marking WebSocket tick broadcasts as droppable so slow or backpressured clients do not self-disconnect with `tick timeout` while long-running work is still alive. (#65436)
-- Gateway/plugins: always send a non-empty `idempotencyKey` for plugin subagent runs, so dreaming narrative jobs stop failing gateway schema validation. (#65354) Thanks @CodeForgeNet.
-- Gateway/auth: blank the shipped example gateway credential in `.env.example` and fail startup when a copied placeholder token or password is still configured, so operators cannot accidentally launch with a publicly known secret. (#64586) Thanks @navarrotech.
-- Plugins/memory-core dreaming: keep bundled `memory-core` loaded alongside an explicit external memory slot owner only when that owner enables dreaming, while preserving `plugins.slots.memory = "none"` disable semantics. (#65411) Thanks @pradeep7127.
-- Doctor/Discord: stop `openclaw doctor --fix` from rewriting legacy Discord preview-streaming config into the nested modern shape, so downgrades can still recover without hand-editing `channels.discord.streaming`.
-- 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.
-- CLI/plugins: honor `memory-wiki` when `plugins.allow` is set for `openclaw wiki`, and pass the active app config into the metadata registrar so plugin-owned wiki commands resolve the live plugin config instead of falling back to defaults. (#64779, #65012)
-- QA/packaging: stop packaged QA helpers from crashing when optional scenario execution config is unavailable, so npm distributions can skip the repo-only scenario pack without breaking completion-cache and startup paths. (#65118) Thanks @EdderTalmor.
-- Media/audio transcription: surface the real provider failure when every audio transcription attempt fails, so status output and the CLI stop collapsing those errors into generic skips. (#65096) Thanks @l0cka.
-- 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.
-- Dreaming/diary: use the host local timezone for diary timestamps when `dreaming.timezone` is unset, and include the timezone abbreviation so `DREAMS.md` and the UI make local or UTC time explicit. (#65034, #65057)
-- Dreaming/promotion: raise phase reinforcement enough for repeated dreaming-only revisits to clear the default durable-memory gate after multiple days, instead of stalling just below the score threshold. (#64068) Thanks @vincentkoc.
-- Dreaming/light-sleep: compute staged candidate confidence from all recorded short-term signals instead of recall-only counts, so dreaming-only entries stop rendering as `confidence: 0.00`. (#64599) Thanks @vincentkoc.
-- Plugins/memory: restore cached memory capability public artifacts on plugin-registry cache hits so memory-backed artifact surfaces stay visible after warm loads.
-- 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.
-- 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.
-- Discord/gateway: clear stale heartbeat timers before reconnecting so zombie gateway callbacks cannot crash the process and drop in-flight replies. (#65009) Thanks @SARAMALI15792.
-- 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.
-- 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.
-- Memory/QMD: allow channel sessions in the shipped default QMD scope, while still denying groups.
-- Memory/QMD: stop registering the legacy lowercase root memory file as a separate default collection, so QMD now prefers `MEMORY.md` and the `memory/` tree without duplicate collection-add warnings.
-- Memory/memory-core: watch the `memory` directory directly and ignore non-markdown churn so nested note changes still sync on macOS + Node 25 environments where recursive `memory/**/*.md` glob watching fails. (#64711) Thanks @jasonxargs-boop and @vincentkoc.
-- WhatsApp: centralize per-account connection ownership so reconnects, login recovery, and outbound readiness stay attached to the live socket instead of drifting across monitor and login paths. (#65290) Thanks @mcaxtr and @vincentkoc.
-- iMessage: retry transient `watch.subscribe` startup failures before tearing down the monitor, and sanitize startup error logging so brief local transport stalls do not immediately bounce the channel or leak raw imsg RPC payloads into logs. (#65393) Thanks @vincentkoc.
-- CLI/audio providers: report env-authenticated providers as configured in `openclaw infer audio providers --json`, while keeping trusted workspace provider env lookup defaults stable during auth setup. (#65491)
-- Plugins/install: reinstall bundled runtime packages when the matching platform native optional child is missing, so packaged Windows installs can recover dependencies that were packed on another host OS.
-- Memory/QMD: preserve explicit `memory.qmd.command` paths, create missing agent workspaces before QMD probes, and keep the current Node binary on QMD subprocess PATH so service and gateway environments do not fall back to builtin search unnecessarily.
-
-## 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
-
-- Windows/onboarding: open provider OAuth and sign-in URLs with `explorer.exe` instead of routing them through `cmd /c start`, so quoted provider URLs cannot break out into host command execution. (#64161) Thanks @coygeek and @vincentkoc.
-- 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
@@ -140,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
 
@@ -234,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.
@@ -258,14 +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.
-- Agents/locks: unregister the session write-lock `exit` cleanup handler during teardown so repeated lock lifecycle resets stop stacking process listeners in long-running gateway processes. (#65391) Thanks @adminfedres and @vincentkoc.
-- CLI/Claude: rename the trusted inbound metadata schema to `openclaw.inbound_meta.v2` so Claude CLI no longer trips Anthropic's blocked `openclaw.inbound_meta.v1` filter on channel-originated turns. (#65399) Thanks @SzyMig and @vincentkoc.
-- Agents/inbound metadata: strip NUL bytes from serialized inbound context blocks before they reach backend spawn args, so malformed message metadata cannot crash agent spawn with `ERR_INVALID_ARG_VALUE`. (#65389) Thanks @adminfedres and @vincentkoc.
-- iMessage: retry transient `watch.subscribe` startup failures before tearing down the monitor, so brief local transport stalls do not immediately bounce the channel. (#65393) Thanks @vincentkoc.
-- Status/session_status: move shared session status text into a neutral internal status module and keep the tool importing a local runtime shim, so built `session_status` no longer depends on reply command internals or a bundler-opaque runtime import. (#65807) Thanks @dutifulbob.
 
 ## 2026.4.9
 
@@ -276,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
 
@@ -315,7 +179,6 @@ Docs: https://docs.openclaw.ai
 - Control UI/models: preserve provider-qualified refs for OpenRouter catalog models whose ids already contain slashes so picker selections submit allowlist-compatible model refs instead of dropping the `openrouter/` prefix. (#63416) Thanks @sallyom.
 - Plugin SDK/command auth: split command status builders onto the lightweight `openclaw/plugin-sdk/command-status` subpath while preserving deprecated `command-auth` compatibility exports, so auth-only plugin imports no longer pull status/context warmup into CLI onboarding paths. (#63174) Thanks @hxy91819.
 - 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.
-- npm packaging: derive required root runtime mirrors from bundled plugin manifests and built root chunks, then install packed release tarballs without the repo `node_modules` so release checks catch missing plugin deps before publish.
 
 ## 2026.4.8
 
@@ -439,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
 
@@ -770,26 +630,7 @@ Docs: https://docs.openclaw.ai
 - Agents/MCP: dispose bundled MCP runtimes after one-shot `openclaw agent --local` runs finish, while preserving bundled MCP state across in-run retries so local JSON runs exit cleanly without restarting stateful MCP tools mid-run.
 - 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.
-- Agents/subagents: fix interim subagent runtime display so `/subagents list` and `/subagents info` stop inflating short runtimes and show second-level durations correctly. (#57739) Thanks @samzong.
-- Diffs/config: preserve schema-shaped plugin config parsing from `diffsPluginConfigSchema.safeParse()`, so direct callers keep `defaults` and `security` sections instead of receiving flattened tool defaults. (#57904) Thanks @gumadeiras.
-- Diffs: fall back to plain text when `lang` hints are invalid during diff render and viewer hydration, so bad or stale language values no longer break the diff viewer. (#57902) Thanks @gumadeiras.
-- Doctor/plugins: skip false Matrix legacy-helper warnings when no migration plans exist, and keep bundled `enabledByDefault` plugins in the gateway startup set. (#57931) Thanks @dinakars777.
-- Matrix/CLI send: start one-off Matrix send clients before outbound delivery so `openclaw message send --channel matrix` restores E2EE in encrypted rooms instead of sending plain events. (#57936) Thanks @gumadeiras.
-- xAI/Responses: normalize image-bearing tool results for xAI responses payloads, including OpenResponses-style `input_image.source` parts, so image tool replays no longer 422 on the follow-up turn. (#58017) Thanks @neeravmakwana.
-- Cron/isolated sessions: carry the full live-session provider, model, and auth-profile selection across retry restarts so cron jobs with model overrides no longer fail or loop on mid-run model-switch requests. (#57972) Thanks @issaba1.
-- Matrix/direct rooms: stop trusting remote `is_direct`, honor explicit local `is_direct: false` for discovered DM candidates, and avoid extra member-state lookups for shared rooms so DM routing and repair stay aligned. (#57124) Thanks @w-sss.
-- Agents/sandbox: make remote FS bridge reads pin the parent path and open the file atomically in the helper so read access cannot race path resolution. Thanks @AntAISecurityLab and @vincentkoc.
-- Tools/web_fetch: add an explicit trusted env-proxy path for proxy-only installs while keeping strict SSRF fetches on the pinned direct path, so trusted proxy routing does not weaken strict destination binding. (#50650) Thanks @kkav004.
-- Exec/env: block Python package index override variables from request-scoped host exec environment sanitization so package fetches cannot be redirected through a caller-supplied index. Thanks @nexrin and @vincentkoc.
-- Telegram/audio: transcode Telegram voice-note `.ogg` attachments before the local `whisper-cli` auto fallback runs, and keep mention-preflight transcription enabled in auto mode when `tools.media.audio` is unset.
-- Matrix/direct rooms: recover fresh auto-joined 1:1 DMs without eagerly persisting invite-only `m.direct` mappings, while keeping named, aliased, and explicitly configured rooms on the room path. (#58024) Thanks @gumadeiras.
-- TTS: Restore 3.28 schema compatibility and fallback observability. (#57953) Thanks @joshavant.
-- Telegram/forum topics: restore reply routing to the active topic and keep ACP `sessions_spawn(..., thread=true, mode="session")` bound to that same topic instead of falling back to root chat or losing follow-up routing. (#56060) Thanks @one27001.
-- Config/SecretRef + Control UI: harden SecretRef redaction round-trip restore, block unsafe raw fallback (force Form mode when raw is unavailable), and preflight submitted-config SecretRefs before config write RPC persistence. (#58044) Thanks @joshavant.
-- Config/Telegram: migrate removed `channels.telegram.groupMentionsOnly` into `channels.telegram.groups["*"].requireMention` on load so legacy configs no longer crash at startup. (#55336) thanks @jameslcowan.
-- Gateway/SecretRef: resolve restart token drift checks with merged service/runtime env sources and hard-fail unsupported mutable SecretRef plus OAuth-profile combinations so restart warnings and policy enforcement match runtime behavior. (#58141) Thanks @joshavant.
 - 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

@@ -77,9 +77,6 @@ Welcome to the lobster tank! 🦞
 - **Tengji (George) Zhang** - Chinese model APIs, cloud, pi
   - GitHub: [@odysseus0](https://github.com/odysseus0) · X: [@odysseus0z](https://x.com/odysseus0z)
 
-- **Sliverp** - Chinese Channel: QQ, WeChat, Wecom, Dingtalk, Feishu
-  - GitHub: [@sliverp](https://github.com/sliverp) · X: [@sliver01234](https://x.com/sliver01234)
-
 ## How to Contribute
 
 1. **Bugs & small fixes** → Open a PR!
@@ -98,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

Dockerfile

@@ -116,7 +116,6 @@ RUN printf 'packages:\n  - .\n  - ui\n' > /tmp/pnpm-workspace.runtime.yaml && \
     done && \
     cp /tmp/pnpm-workspace.runtime.yaml pnpm-workspace.yaml && \
     CI=true NPM_CONFIG_FROZEN_LOCKFILE=false pnpm prune --prod && \
-    node scripts/postinstall-bundled-plugins.mjs && \
     find dist -type f \( -name '*.d.ts' -o -name '*.d.mts' -o -name '*.d.cts' -o -name '*.map' \) -delete
 
 # ── Runtime base images ─────────────────────────────────────────

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:

README.md

@@ -325,7 +325,6 @@ Send these in WhatsApp/Telegram/Slack/Google Chat/Microsoft Teams/WebChat (group
 - `/compact` — compact session context (summary)
 - `/think <level>` — off|minimal|low|medium|high|xhigh (GPT-5.2 + Codex models only)
 - `/verbose on|off`
-- `/trace on|off` — plugin trace/debug lines only
 - `/usage off|tokens|full` — per-response usage footer
 - `/restart` — restart the gateway (owner-only in groups)
 - `/activation mention|always` — group activation toggle (groups only)

USER.md

@@ -1,209 +0,0 @@
-WORK LOG
-
-Add your findings and worklogs by appending to the end of this file. Do not overwrite anything that is existing in this file. Write with the format being used.
-
-[CODEX]
-
-I've brought work into the workstream.
-
-[CLAUDE]
-
-I've assigned the work to eleqtrizit.
-
-[CODEX SECURITY FIXER]
-
-- Reviewed NVIDIA-dev/openclaw-tracking#434, GHSA-jwrq-8g5x-5fhm, related advisories GHSA-wpg9-4g4v-f9rc and GHSA-g5cg-8x5w-7jpm, and SECURITY.md.
-- Determined the issue is in scope: collect-mode batching collapses the documented owner-only/per-sender authorization boundary in shared group queues.
-- Determined a compatible hardening path exists: split collect-mode batches on authorization-context changes while preserving in-order batching for matching contexts.
-- Reviewed existing GHSA-private draft PR openclaw/openclaw-ghsa-jwrq-8g5x-5fhm#1 and incorporated the approach with tighter handling for exec defaults and queue order; preserved co-author credit for zsx <git@zsxsoft.com>.
-- Implemented the fix on branch `ag/collect-batch-context` and opened PR https://github.com/openclaw/openclaw/pull/66024.
-- Added regression coverage for mixed owner/non-owner batches, matching-context batches, exec-context splits, repeated auth flips, and authorization-key changes.
-- Validation run:
-  - `pnpm test src/auto-reply/reply/queue.collect.test.ts`
-  - `pnpm test src/auto-reply/reply/queue.dedupe.test.ts`
-  - `pnpm test src/auto-reply/reply/queue.drain-restart.test.ts`
-  - `claude -p "/review"` (addressed feedback by adding an explicit same-context regression test)
-- `pnpm tsgo` currently reports unrelated pre-existing failures on latest `origin/main` in `extensions/discord`, `extensions/feishu`, `extensions/nextcloud-talk`, `extensions/whatsapp`, `src/cron`, and `src/wizard`.
-- Posted PR link back to the tracking issue: https://github.com/NVIDIA-dev/openclaw-tracking/issues/434#issuecomment-4237703603
-
-[CLAUDE REVIEW]
-
-## Review of branch `ag/collect-batch-context` — 2026-04-13
-
-### Tracking Issue
-
-NVIDIA-dev/openclaw-tracking#434 (GHSA-jwrq-8g5x-5fhm, severity: medium)
-
-### Goal
-
-The branch fixes a security vulnerability in the collect-mode queue drain logic (`src/auto-reply/reply/queue/drain.ts`). In the default "collect" queue mode, all messages that arrive while the agent is busy are batched together and processed under a single `run` object — specifically `items.at(-1)?.run`, i.e. the **last sender's** authorization context. In a group chat where users have different authorization levels (owner vs. non-owner), this means:
-
-- A non-owner's message can be processed with `senderIsOwner=true` if an owner's message arrives later in the same batch window.
-- Per-sender tool restrictions (`toolsBySender`) are resolved against the wrong sender's identity fields.
-- `bashElevated` and `execOverrides` from the last sender are applied to all messages in the batch.
-
-The authorization confusion is order-dependent and transient (per batch cycle), but requires only standard group-chat usage to trigger — no special operator config or adversarial setup needed.
-
-### What the fix does
-
-**Commit 1 (`50c59b1`):** `fix(queue): split collect batches by auth context`
-
-Introduces three new functions:
-
-1. **`resolveFollowupAuthorizationKey(run)`** — Computes a deterministic key from all security-relevant fields on `run`: `senderId`, `senderName`, `senderUsername`, `senderE164`, `senderIsOwner`, plus `execOverrides` sub-fields (`host`, `security`, `ask`, `node`) and `bashElevated` sub-fields (`enabled`, `allowed`, `defaultLevel`). Uses `JSON.stringify` over a fixed-order array for comparison.
-
-2. **`splitCollectItemsByAuthorization(items)`** — Partitions queue items into contiguous groups where the authorization key is identical. Adjacent grouping (not deduplication): if messages arrive A→B→A, this produces 3 groups, preserving chronological message order and preventing cross-sender reordering.
-
-3. **`renderCollectItem(item, idx)`** — Adds per-message sender attribution (`(from SenderName)`) to the collected prompt so the model can distinguish message authorship within a batch.
-
-The drain loop is then changed from processing one batch with `items.at(-1)?.run` to iterating over auth groups, each using `groupItems[0]?.run` as its authorization context.
-
-**Commit 2 (`f71c702`):** `fix(queue): keep overflow summary on splits`
-
-A follow-up fix: changes the overflow summary from being attached only to the first auth group (`groupIdx === 0 ? summary : undefined`) to being included in every auth group's prompt. This ensures all split batches have visibility into queue overflow state rather than only the first one.
-
-### Test coverage added
-
-Five new integration tests in `src/auto-reply/reply/queue.collect.test.ts`:
-
-| Test                                                                | What it validates                                                                                     |
-| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| `splits collect batches when sender authorization changes`          | Non-owner + owner → 2 separate followup calls, each with correct `senderIsOwner` and isolated prompts |
-| `keeps one collect batch when authorization context matches`        | Same sender × 2 → 1 followup call (no unnecessary splitting)                                          |
-| `splits collect batches when exec context changes`                  | Same owner but different `bashElevated`/`execOverrides` → 2 calls with correct exec context on each   |
-| `preserves collect order when authorization changes more than once` | A→B→A pattern → 3 calls in order (no merging of non-adjacent same-auth items)                         |
-| `resolveFollowupAuthorizationKey` unit tests                        | Key changes when `senderIsOwner` flips; key changes when exec defaults change                         |
-
-### Best practices and standards assessment
-
-**Positive:**
-
-- **Directly addresses the root cause.** The fix splits at the authorization boundary rather than applying a heuristic like "most restrictive context." This is the correct approach given that `toolsBySender` policies are not totally ordered and cannot be safely merged.
-- **Minimal blast radius.** Only `drain.ts` production code is touched (90 lines changed). No unrelated refactors bundled in.
-- **Conservative batching preserved.** Messages from the same sender with the same auth context are still collected — the fix only splits where it must.
-- **Test coverage is thorough and targeted.** Tests validate the core vulnerability scenario (mixed owner/non-owner), the happy path (no unnecessary splitting), exec-context edge cases, and ordering preservation under repeated auth flips.
-- **Sender attribution in prompts.** Adding `(from SenderName)` to `renderCollectItem` gives the model visibility into who authored each queued message, reducing cross-sender instruction-following risk even within a correctly-scoped auth batch.
-- **Export and direct unit testing of `resolveFollowupAuthorizationKey`.** The key computation is tested in isolation, not just through integration. Good for regression confidence.
-- **No lint suppressions, no `any`, no `@ts-nocheck`.** Clean TypeScript.
-- **Commit structure.** Two focused, well-scoped commits with clear conventional-commit messages. The second commit is a genuine follow-up fix, not cleanup noise.
-
-**Observations and minor concerns:**
-
-1. **Auth key field coverage.** The key covers `senderId`, `senderName`, `senderUsername`, `senderE164`, `senderIsOwner`, `execOverrides.*`, and `bashElevated.*`. Fields **not** in the key include `authProfileId`, `elevatedLevel`, `ownerNumbers`, and `config`. For the specific vulnerability being fixed (tool authorization via `applyOwnerOnlyToolPolicy` + `resolveToolsBySender` + exec context), the coverage is correct — the omitted fields are either invariant per-session or not consulted in the downstream authorization decisions. However, if new authorization-relevant fields are added to `run` in the future, the key must be updated. A brief code comment on `resolveFollowupAuthorizationKey` noting this would be a low-cost improvement.
-
-2. **Overflow summary repetition.** After commit 2, every auth group receives the overflow summary string. For a batch split into 3 groups, the model sees the same overflow note 3 times across 3 separate followup calls. This is functionally correct (each call is independent and needs context), but slightly redundant from the model's perspective. Not a bug — just a tradeoff worth noting.
-
-3. **Error/retry semantics.** `queue.items.splice(0, items.length)` happens after all auth groups are processed. If `effectiveRunFollowup` throws partway through the loop (e.g., group 1 succeeds, group 2 fails), the catch block fires, `queue.draining` is reset, and the **entire** original item set is retried (including group 1's already-processed items). This is the **same behavior as before the fix** — it is not a regression — but it means messages could be double-delivered on partial failure. A future improvement could track which groups completed and splice more granularly.
-
-4. **`JSON.stringify` for key comparison.** Fine for same-process, same-turn comparison. If keys ever needed to be compared across processes or serialized, a hash would be more appropriate. Current usage is correct.
-
-5. **Adjacent grouping is the right choice.** The A→B→A → 3-group behavior is correct for security. Merging non-adjacent same-auth items would reorder messages across sender boundaries, which could change conversational meaning. The test explicitly validates this.
-
-### Verdict
-
-The fix is well-implemented, directly addresses the vulnerability described in GHSA-jwrq-8g5x-5fhm, follows repo coding standards, and has strong regression test coverage. The approach (split by auth context, not merge to most-restrictive) is the correct one given the `toolsBySender` semantics. No blocking issues found. Minor suggestions above (auth key comment, partial-failure granularity) are future improvements, not blockers.
-
-[CLAUDE PLAN]
-
-## Fix plan for PR #66024 review findings — 2026-04-13
-
-### Sources reviewed
-
-- NVIDIA-dev/openclaw-tracking#434 issue body + triage comment (drobison00)
-- PR openclaw/openclaw#66024 comments: Greptile (1 inline), Codex (4 inline across 2 review rounds), 1 issue-comment from eleqtrizit
-- CLAUDE REVIEW section above (5 observations)
-
-### Issue 1 (P1 — Regression): Partial failure causes duplicate delivery of already-sent auth groups
-
-**Source:** Codex inline review (both commit 1 and commit 2 reviews, `discussion_r3074150975` and `discussion_r3074188986`), CLAUDE REVIEW observation #3.
-
-**Problem:** `queue.items.splice(0, items.length)` at `src/auto-reply/reply/queue/drain.ts:194` runs after the entire auth-group `for` loop. If `effectiveRunFollowup` succeeds for group N but throws for group N+1, the catch block at line 230 fires, `queue.draining` resets in the finally block, and `scheduleFollowupDrain` re-enters — reprocessing ALL items including already-delivered group N. `effectiveRunFollowup` is not idempotent (generates a fresh UUID per call in `followup-runner.ts`), so this produces duplicate replies and duplicate tool side effects.
-
-**Is this a new regression or pre-existing?** NEW. The old single-batch code was atomic: one `effectiveRunFollowup` call then one splice. The multi-group loop broke this atomicity. Non-collect modes use `drainNextQueueItem` (in `src/utils/queue-helpers.ts:147-158`) which splices immediately after each successful run — the collect auth-group loop should follow the same pattern.
-
-**Not part of a larger hidden problem.** The `drainCollectQueueStep` early-return path (cross-channel items) already goes through `drainNextQueueItem` and splices per-item. The inbound dedupe mechanism (`claimInboundDedupe` in dispatch) operates at the dispatch layer, not the queue layer, so it does not protect against queue-level re-delivery.
-
-**Fix (in `src/auto-reply/reply/queue/drain.ts`):**
-
-1. Track a running splice offset (e.g., `let spliced = 0`).
-2. After each successful `await effectiveRunFollowup(...)` call inside the auth-group loop, immediately splice that group's items from `queue.items`: `queue.items.splice(0, groupItems.length)` and increment the offset.
-3. Remove the bulk `queue.items.splice(0, items.length)` at line 194 — it becomes a no-op since items are already spliced.
-4. Move the `clearQueueSummaryState(queue)` call to after the loop (it can stay where it is, gated on `summary`).
-
-**Test to add (in `src/auto-reply/reply/queue.collect.test.ts`):**
-
-- Enqueue items with 2 different auth contexts (non-owner + owner).
-- Have `runFollowup` throw on the 2nd call (first auth group), then succeed on retry.
-- Assert group 1's messages appear exactly once across all `calls` (not duplicated).
-- Assert group 2's messages are delivered on the retry.
-
-### Issue 2 (P2 — Behavioral regression): Use newest `run` in each auth group, not oldest
-
-**Source:** Codex inline review (both commit 1 and commit 2 reviews, `discussion_r3074150979` and `discussion_r3074188994`).
-
-**Problem:** `drain.ts:175` uses `groupItems[0]?.run` (oldest item in the group). The original pre-fix code used `items.at(-1)?.run` (newest). Within a same-auth group, all items share the same authorization key, but non-auth fields on `run` can differ: `provider`, `model`, `config`, `verboseLevel`, `thinkLevel`, `reasoningLevel`, `skillsSnapshot`. If a user changes their preferred model while the agent is busy, the batch executes with stale provider/model settings from the oldest message instead of the latest.
-
-**Is this a new regression?** YES. The old code always selected the latest run's runtime context.
-
-**Not part of a larger hidden problem.** The auth-key grouping invariant guarantees all security-relevant fields are identical within a group. Only non-auth runtime fields (model, provider, config) can differ, and using the newest run is strictly better for freshness — it matches the pre-fix behavior.
-
-**Fix (in `src/auto-reply/reply/queue/drain.ts:175`):**
-
-- Change `groupItems[0]?.run` to `groupItems.at(-1)?.run`.
-
-**Test consideration:** The existing tests don't assert non-auth runtime fields within same-auth groups. Optionally add a test where two same-sender items differ in a non-auth field (e.g., pass different `provider` values on the run) and assert the latest item's value is used.
-
-### Issue 3 (ALREADY FIXED): Overflow summary suppressed for non-first auth groups
-
-**Source:** Greptile inline review on commit 1 (`discussion_r3074152894`).
-
-**Status:** Fixed in commit 2 (`f71c702`). Current code at line 184 passes `summary` unconditionally to all auth groups. No action needed.
-
-### Issue 4 (Minor — Hardening): Auth key field coverage comment
-
-**Source:** CLAUDE REVIEW observation #1.
-
-**Problem:** `resolveFollowupAuthorizationKey` intentionally excludes `authProfileId`, `elevatedLevel`, `ownerNumbers`, and `config` because they are either invariant per-session or not consulted in downstream authorization decisions (`applyOwnerOnlyToolPolicy`, `resolveToolsBySender`). However, if future code adds new auth-relevant fields to `run`, the key must be updated. No code comment documents this design decision.
-
-**Not part of a larger hidden problem.** The excluded fields were verified against the downstream consumers in `pi-tools.ts:634-635` and `tool-policy.ts:55-66`. They do not currently influence per-message authorization.
-
-**Fix (in `src/auto-reply/reply/queue/drain.ts`, above `resolveFollowupAuthorizationKey`):**
-
-- Add a brief comment: `// Key covers fields consulted by applyOwnerOnlyToolPolicy, resolveToolsBySender, and exec-context propagation. Fields like authProfileId, elevatedLevel, ownerNumbers, and config are intentionally excluded (invariant per-session or not consulted in per-message auth). Update this key if new auth-relevant fields are added to run.`
-
-### Execution order
-
-1. Fix Issue 2 first (one-line change, `groupItems[0]` → `groupItems.at(-1)`).
-2. Fix Issue 1 (incremental splice + new test).
-3. Add Issue 4 comment.
-4. Run scoped tests: `pnpm test src/auto-reply/reply/queue.collect.test.ts`.
-5. Run broader queue tests: `pnpm test src/auto-reply/reply/queue`.
-6. Run `pnpm tsgo` to verify no type regressions from the changes.
-
-[CODEX SUMMARY]
-
-- Reviewed `USER.md`, verified Claude's plan against the current branch, and checked NVIDIA-dev/openclaw-tracking#434 for issue context.
-- Confirmed both open review findings were still real in `src/auto-reply/reply/queue/drain.ts`:
-  - collect-mode auth groups were using the oldest `run` in each group instead of the newest one, which regressed provider/model/runtime-context freshness within same-auth batches.
-  - collect-mode auth groups were only removed from `queue.items` after the full loop, which could duplicate already-processed groups if a later group failed and the drain retried.
-- Updated `src/auto-reply/reply/queue/drain.ts` to use `groupItems.at(-1)?.run`, splice each auth group immediately after a successful `effectiveRunFollowup(...)`, and added a comment documenting the intentional auth-key field coverage.
-- Added regression tests in `src/auto-reply/reply/queue.collect.test.ts` for:
-  - newest-run selection inside a matching authorization batch
-  - retrying only the remaining auth groups after a partial collect-mode failure
-- Validation:
-  - `corepack pnpm test src/auto-reply/reply/queue.collect.test.ts` ✅
-  - `corepack pnpm test src/auto-reply/reply/queue` ✅
-  - `corepack pnpm tsgo` ❌ with pre-existing unrelated failures in `extensions/discord`, `extensions/feishu`, `extensions/nextcloud-talk`, `extensions/whatsapp`, `src/cron`, and `src/wizard`; no new queue-related type failures were introduced by this work.
-
-[CODEX]
-
-- Re-read `USER.md`, pulled NVIDIA-dev/openclaw-tracking#434 with `gh issue view`, and checked open review threads on openclaw/openclaw#66024 before mutating GitHub state.
-- Verified the two still-open Codex findings were only fixed locally, not yet on the PR head, so resolving them immediately would have been premature.
-- Re-ran the scoped queue validation after the local follow-up fixes:
-  - `corepack pnpm test src/auto-reply/reply/queue.collect.test.ts` ✅
-  - `corepack pnpm test src/auto-reply/reply/queue` ✅
-- Prepared the branch for a scoped follow-up commit covering:
-  - newest-run selection per auth group in `src/auto-reply/reply/queue/drain.ts`
-  - per-group dequeue on successful collect sends to avoid duplicate retries
-  - regression coverage in `src/auto-reply/reply/queue.collect.test.ts`
-- Next step is to commit and push those fixes, then resolve the addressed PR threads and post fresh `@codex review` / `@greptile review` trigger comments.

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 = 2026041290
-        versionName = "2026.4.12"
+        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.12 - 2026-04-12
+## 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.12
-OPENCLAW_MARKETING_VERSION = 2026.4.12
+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.12"
+  "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.12</string>
+    <string>2026.4.10</string>
     <key>CFBundleVersion</key>
-    <string>2026041290</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?
@@ -1743,7 +1689,6 @@ public struct SessionsPatchParams: Codable, Sendable {
     public let thinkinglevel: AnyCodable?
     public let fastmode: AnyCodable?
     public let verboselevel: AnyCodable?
-    public let tracelevel: AnyCodable?
     public let reasoninglevel: AnyCodable?
     public let responseusage: AnyCodable?
     public let elevatedlevel: AnyCodable?
@@ -1766,7 +1711,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         thinkinglevel: AnyCodable?,
         fastmode: AnyCodable?,
         verboselevel: AnyCodable?,
-        tracelevel: AnyCodable?,
         reasoninglevel: AnyCodable?,
         responseusage: AnyCodable?,
         elevatedlevel: AnyCodable?,
@@ -1788,7 +1732,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         self.thinkinglevel = thinkinglevel
         self.fastmode = fastmode
         self.verboselevel = verboselevel
-        self.tracelevel = tracelevel
         self.reasoninglevel = reasoninglevel
         self.responseusage = responseusage
         self.elevatedlevel = elevatedlevel
@@ -1812,7 +1755,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         case thinkinglevel = "thinkingLevel"
         case fastmode = "fastMode"
         case verboselevel = "verboseLevel"
-        case tracelevel = "traceLevel"
         case reasoninglevel = "reasoningLevel"
         case responseusage = "responseUsage"
         case elevatedlevel = "elevatedLevel"

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?
@@ -1743,7 +1689,6 @@ public struct SessionsPatchParams: Codable, Sendable {
     public let thinkinglevel: AnyCodable?
     public let fastmode: AnyCodable?
     public let verboselevel: AnyCodable?
-    public let tracelevel: AnyCodable?
     public let reasoninglevel: AnyCodable?
     public let responseusage: AnyCodable?
     public let elevatedlevel: AnyCodable?
@@ -1766,7 +1711,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         thinkinglevel: AnyCodable?,
         fastmode: AnyCodable?,
         verboselevel: AnyCodable?,
-        tracelevel: AnyCodable?,
         reasoninglevel: AnyCodable?,
         responseusage: AnyCodable?,
         elevatedlevel: AnyCodable?,
@@ -1788,7 +1732,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         self.thinkinglevel = thinkinglevel
         self.fastmode = fastmode
         self.verboselevel = verboselevel
-        self.tracelevel = tracelevel
         self.reasoninglevel = reasoninglevel
         self.responseusage = responseusage
         self.elevatedlevel = elevatedlevel
@@ -1812,7 +1755,6 @@ public struct SessionsPatchParams: Codable, Sendable {
         case thinkinglevel = "thinkingLevel"
         case fastmode = "fastMode"
         case verboselevel = "verboseLevel"
-        case tracelevel = "traceLevel"
         case reasoninglevel = "reasoningLevel"
         case responseusage = "responseUsage"
         case elevatedlevel = "elevatedLevel"

docs/.generated/config-baseline.sha256

@@ -1,4 +1,4 @@
-724be329389b48a3f1697a534722702de294be4605e1d700c16ec6bbc560100d  config-baseline.json
-e4f4396307dc84c9f4b5c42280d69b985d8e07869046ca325956fc59a5a9abd0  config-baseline.core.json
-3bb312dc9c39a374ca92613abf21606c25dc571287a3941dac71ff57b2b5c519  config-baseline.channel.json
-0471a5bffb213a3829555efe5961f5b5fd5080c1d38b1ac8dd87afaabdb8bdc1  config-baseline.plugin.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 @@
-600f05b14825fa01eb9d63ab6cab5f33c74ff44a48cab5c65457ab08e5b0e91a  plugin-sdk-api-baseline.json
-99d649a86a30756b18b91686f3683e6e829c5e316e1370266ec4fee344bc55cb  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/feishu.md

@@ -6,32 +6,296 @@ read_when:
 title: Feishu
 ---
 
-# Feishu / Lark
+# Feishu bot
 
-Feishu/Lark is an all-in-one collaboration platform where teams chat, share documents, manage calendars, and get work done together.
-
-**Status:** production-ready for bot DMs + group chats. WebSocket is the default mode; webhook mode is optional.
+Feishu (Lark) is a team chat platform used by companies for messaging and collaboration. This plugin connects OpenClaw to a Feishu/Lark bot using the platform’s WebSocket event subscription so messages can be received without exposing a public webhook URL.
 
 ---
 
-## Quick start
+## Bundled plugin
 
-> **Requires OpenClaw 2026.4.10 or above.** Run `openclaw --version` to check. Upgrade with `openclaw update`.
+Feishu ships bundled with current OpenClaw releases, so no separate plugin install
+is required.
 
-<Steps>
-  <Step title="Run the channel setup wizard">
-  ```bash
-  openclaw channels login --channel feishu
-  ```
-  Scan the QR code with your Feishu/Lark mobile app to create a Feishu/Lark bot automatically.
-  </Step>
-  
-  <Step title="After setup completes, restart the gateway to apply the changes">
-  ```bash
-  openclaw gateway restart
-  ```
-  </Step>
-</Steps>
+If you are using an older build or a custom install that does not include bundled
+Feishu, install it manually:
+
+```bash
+openclaw plugins install @openclaw/feishu
+```
+
+---
+
+## Quickstart
+
+There are two ways to add the Feishu channel:
+
+### Method 1: onboarding (recommended)
+
+If you just installed OpenClaw, run onboarding:
+
+```bash
+openclaw onboard
+```
+
+The wizard guides you through:
+
+1. Creating a Feishu app and collecting credentials
+2. Configuring app credentials in OpenClaw
+3. Starting the gateway
+
+✅ **After configuration**, check gateway status:
+
+- `openclaw gateway status`
+- `openclaw logs --follow`
+
+### Method 2: CLI setup
+
+If you already completed initial install, add the channel via CLI:
+
+```bash
+openclaw channels add
+```
+
+Choose **Feishu**, then enter the App ID and App Secret.
+
+✅ **After configuration**, manage the gateway:
+
+- `openclaw gateway status`
+- `openclaw gateway restart`
+- `openclaw logs --follow`
+
+---
+
+## Step 1: Create a Feishu app
+
+### 1. Open Feishu Open Platform
+
+Visit [Feishu Open Platform](https://open.feishu.cn/app) and sign in.
+
+Lark (global) tenants should use [https://open.larksuite.com/app](https://open.larksuite.com/app) and set `domain: "lark"` in the Feishu config.
+
+### 2. Create an app
+
+1. Click **Create enterprise app**
+2. Fill in the app name + description
+3. Choose an app icon
+
+![Create enterprise app](/images/feishu-step2-create-app.png)
+
+### 3. Copy credentials
+
+From **Credentials & Basic Info**, copy:
+
+- **App ID** (format: `cli_xxx`)
+- **App Secret**
+
+❗ **Important:** keep the App Secret private.
+
+![Get credentials](/images/feishu-step3-credentials.png)
+
+### 4. Configure permissions
+
+On **Permissions**, click **Batch import** and paste:
+
+```json
+{
+  "scopes": {
+    "tenant": [
+      "aily:file:read",
+      "aily:file:write",
+      "application:application.app_message_stats.overview:readonly",
+      "application:application:self_manage",
+      "application:bot.menu:write",
+      "cardkit:card:read",
+      "cardkit:card:write",
+      "contact:user.employee_id:readonly",
+      "corehr:file:download",
+      "event:ip_list",
+      "im:chat.access_event.bot_p2p_chat:read",
+      "im:chat.members:bot_access",
+      "im:message",
+      "im:message.group_at_msg:readonly",
+      "im:message.p2p_msg:readonly",
+      "im:message:readonly",
+      "im:message:send_as_bot",
+      "im:resource"
+    ],
+    "user": ["aily:file:read", "aily:file:write", "im:chat.access_event.bot_p2p_chat:read"]
+  }
+}
+```
+
+![Configure permissions](/images/feishu-step4-permissions.png)
+
+### 5. Enable bot capability
+
+In **App Capability** > **Bot**:
+
+1. Enable bot capability
+2. Set the bot name
+
+![Enable bot capability](/images/feishu-step5-bot-capability.png)
+
+### 6. Configure event subscription
+
+⚠️ **Important:** before setting event subscription, make sure:
+
+1. You already ran `openclaw channels add` for Feishu
+2. The gateway is running (`openclaw gateway status`)
+
+In **Event Subscription**:
+
+1. Choose **Use long connection to receive events** (WebSocket)
+2. Add the event: `im.message.receive_v1`
+3. (Optional) For Drive comment workflows, also add: `drive.notice.comment_add_v1`
+
+⚠️ If the gateway is not running, the long-connection setup may fail to save.
+
+![Configure event subscription](/images/feishu-step6-event-subscription.png)
+
+### 7. Publish the app
+
+1. Create a version in **Version Management & Release**
+2. Submit for review and publish
+3. Wait for admin approval (enterprise apps usually auto-approve)
+
+---
+
+## Step 2: Configure OpenClaw
+
+### Configure with the wizard (recommended)
+
+```bash
+openclaw channels add
+```
+
+Choose **Feishu** and paste your App ID + App Secret.
+
+### Configure via config file
+
+Edit `~/.openclaw/openclaw.json`:
+
+```json5
+{
+  channels: {
+    feishu: {
+      enabled: true,
+      dmPolicy: "pairing",
+      accounts: {
+        main: {
+          appId: "cli_xxx",
+          appSecret: "xxx",
+          name: "My AI assistant",
+        },
+      },
+    },
+  },
+}
+```
+
+If you use `connectionMode: "webhook"`, set both `verificationToken` and `encryptKey`. The Feishu webhook server binds to `127.0.0.1` by default; set `webhookHost` only if you intentionally need a different bind address.
+
+#### Verification Token and Encrypt Key (webhook mode)
+
+When using webhook mode, set both `channels.feishu.verificationToken` and `channels.feishu.encryptKey` in your config. To get the values:
+
+1. In Feishu Open Platform, open your app
+2. Go to **Development** → **Events & Callbacks** (开发配置 → 事件与回调)
+3. Open the **Encryption** tab (加密策略)
+4. Copy **Verification Token** and **Encrypt Key**
+
+The screenshot below shows where to find the **Verification Token**. The **Encrypt Key** is listed in the same **Encryption** section.
+
+![Verification Token location](/images/feishu-verification-token.png)
+
+### Configure via environment variables
+
+```bash
+export FEISHU_APP_ID="cli_xxx"
+export FEISHU_APP_SECRET="xxx"
+```
+
+### Lark (global) domain
+
+If your tenant is on Lark (international), set the domain to `lark` (or a full domain string). You can set it at `channels.feishu.domain` or per account (`channels.feishu.accounts.<id>.domain`).
+
+```json5
+{
+  channels: {
+    feishu: {
+      domain: "lark",
+      accounts: {
+        main: {
+          appId: "cli_xxx",
+          appSecret: "xxx",
+        },
+      },
+    },
+  },
+}
+```
+
+### Quota optimization flags
+
+You can reduce Feishu API usage with two optional flags:
+
+- `typingIndicator` (default `true`): when `false`, skip typing reaction calls.
+- `resolveSenderNames` (default `true`): when `false`, skip sender profile lookup calls.
+
+Set them at top level or per account:
+
+```json5
+{
+  channels: {
+    feishu: {
+      typingIndicator: false,
+      resolveSenderNames: false,
+      accounts: {
+        main: {
+          appId: "cli_xxx",
+          appSecret: "xxx",
+          typingIndicator: true,
+          resolveSenderNames: false,
+        },
+      },
+    },
+  },
+}
+```
+
+---
+
+## Step 3: Start + test
+
+### 1. Start the gateway
+
+```bash
+openclaw gateway
+```
+
+### 2. Send a test message
+
+In Feishu, find your bot and send a message.
+
+### 3. Approve pairing
+
+By default, the bot replies with a pairing code. Approve it:
+
+```bash
+openclaw pairing approve feishu <CODE>
+```
+
+After approval, you can chat normally.
+
+---
+
+## Overview
+
+- **Feishu bot channel**: Feishu bot managed by the gateway
+- **Deterministic routing**: replies always return to Feishu
+- **Session isolation**: DMs share a main session; groups are isolated
+- **WebSocket connection**: long connection via Feishu SDK, no public URL needed
 
 ---
 
@@ -39,43 +303,38 @@ Feishu/Lark is an all-in-one collaboration platform where teams chat, share docu
 
 ### Direct messages
 
-Configure `dmPolicy` to control who can DM the bot:
+- **Default**: `dmPolicy: "pairing"` (unknown users get a pairing code)
+- **Approve pairing**:
 
-- `"pairing"` — unknown users receive a pairing code; approve via CLI
-- `"allowlist"` — only users listed in `allowFrom` can chat (default: bot owner only)
-- `"open"` — allow all users
-- `"disabled"` — disable all DMs
+  ```bash
+  openclaw pairing list feishu
+  openclaw pairing approve feishu <CODE>
+  ```
 
-**Approve a pairing request:**
-
-```bash
-openclaw pairing list feishu
-openclaw pairing approve feishu <CODE>
-```
+- **Allowlist mode**: set `channels.feishu.allowFrom` with allowed Open IDs
 
 ### Group chats
 
-**Group policy** (`channels.feishu.groupPolicy`):
+**1. Group policy** (`channels.feishu.groupPolicy`):
 
-| Value         | Behavior                                   |
-| ------------- | ------------------------------------------ |
-| `"open"`      | Respond to all messages in groups          |
-| `"allowlist"` | Only respond to groups in `groupAllowFrom` |
-| `"disabled"`  | Disable all group messages                 |
+- `"open"` = allow everyone in groups
+- `"allowlist"` = only allow `groupAllowFrom`
+- `"disabled"` = disable group messages
 
 Default: `allowlist`
 
-**Mention requirement** (`channels.feishu.requireMention`):
+**2. Mention requirement** (`channels.feishu.requireMention`, overridable via `channels.feishu.groups.<chat_id>.requireMention`):
 
-- `true` — require @mention (default)
-- `false` — respond without @mention
-- Per-group override: `channels.feishu.groups.<chat_id>.requireMention`
+- explicit `true` = require @mention
+- explicit `false` = respond without mentions
+- when unset and `groupPolicy: "open"` = default to `false`
+- when unset and `groupPolicy` is not `"open"` = default to `true`
 
 ---
 
 ## Group configuration examples
 
-### Allow all groups, no @mention required
+### Allow all groups, no @mention required (default for open groups)
 
 ```json5
 {
@@ -87,7 +346,7 @@ Default: `allowlist`
 }
 ```
 
-### Allow all groups, still require @mention
+### Allow all groups, but still require @mention
 
 ```json5
 {
@@ -107,14 +366,16 @@ Default: `allowlist`
   channels: {
     feishu: {
       groupPolicy: "allowlist",
-      // Group IDs look like: oc_xxx
+      // Feishu group IDs (chat_id) look like: oc_xxx
       groupAllowFrom: ["oc_xxx", "oc_yyy"],
     },
   },
 }
 ```
 
-### Restrict senders within a group
+### Restrict which senders can message in a group (sender allowlist)
+
+In addition to allowing the group itself, **all messages** in that group are gated by the sender open_id: only users listed in `groups.<chat_id>.allowFrom` have their messages processed; messages from other members are ignored (this is full sender-level gating, not only for control commands like /reset or /new).
 
 ```json5
 {
@@ -124,7 +385,7 @@ Default: `allowlist`
       groupAllowFrom: ["oc_xxx"],
       groups: {
         oc_xxx: {
-          // User open_ids look like: ou_xxx
+          // Feishu user IDs (open_id) look like: ou_xxx
           allowFrom: ["ou_user1", "ou_user2"],
         },
       },
@@ -135,23 +396,35 @@ Default: `allowlist`
 
 ---
 
+<a id="get-groupuser-ids"></a>
+
 ## Get group/user IDs
 
-### Group IDs (`chat_id`, format: `oc_xxx`)
+### Group IDs (chat_id)
 
-Open the group in Feishu/Lark, click the menu icon in the top-right corner, and go to **Settings**. The group ID (`chat_id`) is listed on the settings page.
+Group IDs look like `oc_xxx`.
 
-![Get Group ID](/images/feishu-get-group-id.png)
+**Method 1 (recommended)**
 
-### User IDs (`open_id`, format: `ou_xxx`)
+1. Start the gateway and @mention the bot in the group
+2. Run `openclaw logs --follow` and look for `chat_id`
 
-Start the gateway, send a DM to the bot, then check the logs:
+**Method 2**
 
-```bash
-openclaw logs --follow
-```
+Use the Feishu API debugger to list group chats.
 
-Look for `open_id` in the log output. You can also check pending pairing requests:
+### User IDs (open_id)
+
+User IDs look like `ou_xxx`.
+
+**Method 1 (recommended)**
+
+1. Start the gateway and DM the bot
+2. Run `openclaw logs --follow` and look for `open_id`
+
+**Method 2**
+
+Check pairing requests for user Open IDs:
 
 ```bash
 openclaw pairing list feishu
@@ -161,13 +434,23 @@ openclaw pairing list feishu
 
 ## Common commands
 
-| Command   | Description                 |
-| --------- | --------------------------- |
-| `/status` | Show bot status             |
-| `/reset`  | Reset the current session   |
-| `/model`  | Show or switch the AI model |
+| Command   | Description       |
+| --------- | ----------------- |
+| `/status` | Show bot status   |
+| `/reset`  | Reset the session |
+| `/model`  | Show/switch model |
 
-> Feishu/Lark does not support native slash-command menus, so send these as plain text messages.
+> Note: Feishu does not support native command menus yet, so commands must be sent as text.
+
+## Gateway management commands
+
+| Command                    | Description                   |
+| -------------------------- | ----------------------------- |
+| `openclaw gateway status`  | Show gateway status           |
+| `openclaw gateway install` | Install/start gateway service |
+| `openclaw gateway stop`    | Stop gateway service          |
+| `openclaw gateway restart` | Restart gateway service       |
+| `openclaw logs --follow`   | Tail gateway logs             |
 
 ---
 
@@ -176,24 +459,30 @@ openclaw pairing list feishu
 ### Bot does not respond in group chats
 
 1. Ensure the bot is added to the group
-2. Ensure you @mention the bot (required by default)
-3. Verify `groupPolicy` is not `"disabled"`
+2. Ensure you @mention the bot (default behavior)
+3. Check `groupPolicy` is not set to `"disabled"`
 4. Check logs: `openclaw logs --follow`
 
 ### Bot does not receive messages
 
-1. Ensure the bot is published and approved in Feishu Open Platform / Lark Developer
+1. Ensure the app is published and approved
 2. Ensure event subscription includes `im.message.receive_v1`
-3. Ensure **persistent connection** (WebSocket) is selected
-4. Ensure all required permission scopes are granted
+3. Ensure **long connection** is enabled
+4. Ensure app permissions are complete
 5. Ensure the gateway is running: `openclaw gateway status`
 6. Check logs: `openclaw logs --follow`
 
-### App Secret leaked
+### App Secret leak
 
-1. Reset the App Secret in Feishu Open Platform / Lark Developer
-2. Update the value in your config
-3. Restart the gateway: `openclaw gateway restart`
+1. Reset the App Secret in Feishu Open Platform
+2. Update the App Secret in your config
+3. Restart the gateway
+
+### Message send failures
+
+1. Ensure the app has `im:message:send_as_bot` permission
+2. Ensure the app is published
+3. Check logs for detailed errors
 
 ---
 
@@ -224,53 +513,42 @@ openclaw pairing list feishu
 }
 ```
 
-`defaultAccount` controls which account is used when outbound APIs do not specify an `accountId`.
+`defaultAccount` controls which Feishu account is used when outbound APIs do not specify an `accountId` explicitly.
 
 ### Message limits
 
-- `textChunkLimit` — outbound text chunk size (default: `2000` chars)
-- `mediaMaxMb` — media upload/download limit (default: `30` MB)
+- `textChunkLimit`: outbound text chunk size (default: 2000 chars)
+- `mediaMaxMb`: media upload/download limit (default: 30MB)
 
 ### Streaming
 
-Feishu/Lark supports streaming replies via interactive cards. When enabled, the bot updates the card in real time as it generates text.
+Feishu supports streaming replies via interactive cards. When enabled, the bot updates a card as it generates text.
 
 ```json5
 {
   channels: {
     feishu: {
-      streaming: true, // enable streaming card output (default: true)
-      blockStreaming: true, // enable block-level streaming (default: true)
+      streaming: true, // enable streaming card output (default true)
+      blockStreaming: true, // enable block-level streaming (default true)
     },
   },
 }
 ```
 
-Set `streaming: false` to send the complete reply in one message.
-
-### Quota optimization
-
-Reduce the number of Feishu/Lark API calls with two optional flags:
-
-- `typingIndicator` (default `true`): set `false` to skip typing reaction calls
-- `resolveSenderNames` (default `true`): set `false` to skip sender profile lookups
-
-```json5
-{
-  channels: {
-    feishu: {
-      typingIndicator: false,
-      resolveSenderNames: false,
-    },
-  },
-}
-```
+Set `streaming: false` to wait for the full reply before sending.
 
 ### ACP sessions
 
-Feishu/Lark supports ACP for DMs and group thread messages. Feishu/Lark ACP is text-command driven — there are no native slash-command menus, so use `/acp ...` messages directly in the conversation.
+Feishu supports ACP for:
 
-#### Persistent ACP binding
+- DMs
+- group topic conversations
+
+Feishu ACP is text-command driven. There are no native slash-command menus, so use `/acp ...` messages directly in the conversation.
+
+#### Persistent ACP bindings
+
+Use top-level typed ACP bindings to pin a Feishu DM or topic conversation to a persistent ACP session.
 
 ```json5
 {
@@ -314,39 +592,58 @@ Feishu/Lark supports ACP for DMs and group thread messages. Feishu/Lark ACP is t
 }
 ```
 
-#### Spawn ACP from chat
+#### Thread-bound ACP spawn from chat
 
-In a Feishu/Lark DM or thread:
+In a Feishu DM or topic conversation, you can spawn and bind an ACP session in place:
 
 ```text
 /acp spawn codex --thread here
 ```
 
-`--thread here` works for DMs and Feishu/Lark thread messages. Follow-up messages in the bound conversation route directly to that ACP session.
+Notes:
+
+- `--thread here` works for DMs and Feishu topics.
+- Follow-up messages in the bound DM/topic route directly to that ACP session.
+- v1 does not target generic non-topic group chats.
 
 ### Multi-agent routing
 
-Use `bindings` to route Feishu/Lark DMs or groups to different agents.
+Use `bindings` to route Feishu DMs or groups to different agents.
 
 ```json5
 {
   agents: {
     list: [
       { id: "main" },
-      { id: "agent-a", workspace: "/home/user/agent-a" },
-      { id: "agent-b", workspace: "/home/user/agent-b" },
+      {
+        id: "clawd-fan",
+        workspace: "/home/user/clawd-fan",
+        agentDir: "/home/user/.openclaw/agents/clawd-fan/agent",
+      },
+      {
+        id: "clawd-xi",
+        workspace: "/home/user/clawd-xi",
+        agentDir: "/home/user/.openclaw/agents/clawd-xi/agent",
+      },
     ],
   },
   bindings: [
     {
-      agentId: "agent-a",
+      agentId: "main",
       match: {
         channel: "feishu",
         peer: { kind: "direct", id: "ou_xxx" },
       },
     },
     {
-      agentId: "agent-b",
+      agentId: "clawd-fan",
+      match: {
+        channel: "feishu",
+        peer: { kind: "direct", id: "ou_yyy" },
+      },
+    },
+    {
+      agentId: "clawd-xi",
       match: {
         channel: "feishu",
         peer: { kind: "group", id: "oc_zzz" },
@@ -359,7 +656,7 @@ Use `bindings` to route Feishu/Lark DMs or groups to different agents.
 Routing fields:
 
 - `match.channel`: `"feishu"`
-- `match.peer.kind`: `"direct"` (DM) or `"group"` (group chat)
+- `match.peer.kind`: `"direct"` or `"group"`
 - `match.peer.id`: user Open ID (`ou_xxx`) or group ID (`oc_xxx`)
 
 See [Get group/user IDs](#get-groupuser-ids) for lookup tips.
@@ -370,33 +667,44 @@ See [Get group/user IDs](#get-groupuser-ids) for lookup tips.
 
 Full configuration: [Gateway configuration](/gateway/configuration)
 
-| Setting                                           | Description                                | Default          |
-| ------------------------------------------------- | ------------------------------------------ | ---------------- |
-| `channels.feishu.enabled`                         | Enable/disable the channel                 | `true`           |
-| `channels.feishu.domain`                          | API domain (`feishu` or `lark`)            | `feishu`         |
-| `channels.feishu.connectionMode`                  | Event transport (`websocket` or `webhook`) | `websocket`      |
-| `channels.feishu.defaultAccount`                  | Default account for outbound routing       | `default`        |
-| `channels.feishu.verificationToken`               | Required for webhook mode                  | —                |
-| `channels.feishu.encryptKey`                      | Required for webhook mode                  | —                |
-| `channels.feishu.webhookPath`                     | Webhook route path                         | `/feishu/events` |
-| `channels.feishu.webhookHost`                     | Webhook bind host                          | `127.0.0.1`      |
-| `channels.feishu.webhookPort`                     | Webhook bind port                          | `3000`           |
-| `channels.feishu.accounts.<id>.appId`             | App ID                                     | —                |
-| `channels.feishu.accounts.<id>.appSecret`         | App Secret                                 | —                |
-| `channels.feishu.accounts.<id>.domain`            | Per-account domain override                | `feishu`         |
-| `channels.feishu.dmPolicy`                        | DM policy                                  | `allowlist`      |
-| `channels.feishu.allowFrom`                       | DM allowlist (open_id list)                | [BotOwnerId]     |
-| `channels.feishu.groupPolicy`                     | Group policy                               | `allowlist`      |
-| `channels.feishu.groupAllowFrom`                  | Group allowlist                            | —                |
-| `channels.feishu.requireMention`                  | Require @mention in groups                 | `true`           |
-| `channels.feishu.groups.<chat_id>.requireMention` | Per-group @mention override                | inherited        |
-| `channels.feishu.groups.<chat_id>.enabled`        | Enable/disable a specific group            | `true`           |
-| `channels.feishu.textChunkLimit`                  | Message chunk size                         | `2000`           |
-| `channels.feishu.mediaMaxMb`                      | Media size limit                           | `30`             |
-| `channels.feishu.streaming`                       | Streaming card output                      | `true`           |
-| `channels.feishu.blockStreaming`                  | Block-level streaming                      | `true`           |
-| `channels.feishu.typingIndicator`                 | Send typing reactions                      | `true`           |
-| `channels.feishu.resolveSenderNames`              | Resolve sender display names               | `true`           |
+Key options:
+
+| Setting                                           | Description                             | Default          |
+| ------------------------------------------------- | --------------------------------------- | ---------------- |
+| `channels.feishu.enabled`                         | Enable/disable channel                  | `true`           |
+| `channels.feishu.domain`                          | API domain (`feishu` or `lark`)         | `feishu`         |
+| `channels.feishu.connectionMode`                  | Event transport mode                    | `websocket`      |
+| `channels.feishu.defaultAccount`                  | Default account ID for outbound routing | `default`        |
+| `channels.feishu.verificationToken`               | Required for webhook mode               | -                |
+| `channels.feishu.encryptKey`                      | Required for webhook mode               | -                |
+| `channels.feishu.webhookPath`                     | Webhook route path                      | `/feishu/events` |
+| `channels.feishu.webhookHost`                     | Webhook bind host                       | `127.0.0.1`      |
+| `channels.feishu.webhookPort`                     | Webhook bind port                       | `3000`           |
+| `channels.feishu.accounts.<id>.appId`             | App ID                                  | -                |
+| `channels.feishu.accounts.<id>.appSecret`         | App Secret                              | -                |
+| `channels.feishu.accounts.<id>.domain`            | Per-account API domain override         | `feishu`         |
+| `channels.feishu.dmPolicy`                        | DM policy                               | `pairing`        |
+| `channels.feishu.allowFrom`                       | DM allowlist (open_id list)             | -                |
+| `channels.feishu.groupPolicy`                     | Group policy                            | `allowlist`      |
+| `channels.feishu.groupAllowFrom`                  | Group allowlist                         | -                |
+| `channels.feishu.requireMention`                  | Default require @mention                | conditional      |
+| `channels.feishu.groups.<chat_id>.requireMention` | Per-group require @mention override     | inherited        |
+| `channels.feishu.groups.<chat_id>.enabled`        | Enable group                            | `true`           |
+| `channels.feishu.textChunkLimit`                  | Message chunk size                      | `2000`           |
+| `channels.feishu.mediaMaxMb`                      | Media size limit                        | `30`             |
+| `channels.feishu.streaming`                       | Enable streaming card output            | `true`           |
+| `channels.feishu.blockStreaming`                  | Enable block streaming                  | `true`           |
+
+---
+
+## dmPolicy reference
+
+| Value         | Behavior                                                        |
+| ------------- | --------------------------------------------------------------- |
+| `"pairing"`   | **Default.** Unknown users get a pairing code; must be approved |
+| `"allowlist"` | Only users in `allowFrom` can chat                              |
+| `"open"`      | Allow all users (requires `"*"` in allowFrom)                   |
+| `"disabled"`  | Disable DMs                                                     |
 
 ---
 
@@ -419,16 +727,62 @@ Full configuration: [Gateway configuration](/gateway/configuration)
 - ✅ Files
 - ✅ Audio
 - ✅ Video/media
-- ✅ Interactive cards (including streaming updates)
-- ⚠️ Rich text (post-style formatting; doesn't support full Feishu/Lark authoring capabilities)
+- ✅ Interactive cards
+- ⚠️ Rich text (post-style formatting and cards, not arbitrary Feishu authoring features)
 
 ### Threads and replies
 
 - ✅ Inline replies
-- ✅ Thread replies
-- ✅ Media replies stay thread-aware when replying to a thread message
+- ✅ Topic-thread replies where Feishu exposes `reply_in_thread`
+- ✅ Media replies stay thread-aware when replying to a thread/topic message
 
----
+## Drive comments
+
+Feishu can trigger the agent when someone adds a comment on a Feishu Drive document (Docs, Sheets,
+etc.). The agent receives the comment text, document context, and the comment thread so it can
+respond in-thread or make document edits.
+
+Requirements:
+
+- Subscribe to `drive.notice.comment_add_v1` in your Feishu app event subscription settings
+  (alongside the existing `im.message.receive_v1`)
+- The Drive tool is enabled by default; disable with `channels.feishu.tools.drive: false`
+
+The `feishu_drive` tool exposes these comment actions:
+
+| Action                 | Description                         |
+| ---------------------- | ----------------------------------- |
+| `list_comments`        | List comments on a document         |
+| `list_comment_replies` | List replies in a comment thread    |
+| `add_comment`          | Add a new top-level comment         |
+| `reply_comment`        | Reply to an existing comment thread |
+
+When the agent handles a Drive comment event, it receives:
+
+- the comment text and sender
+- document metadata (title, type, URL)
+- the comment thread context for in-thread replies
+
+After making document edits, the agent is guided to use `feishu_drive.reply_comment` to notify the
+commenter and then output the exact silent token `NO_REPLY` / `no_reply` to
+avoid duplicate sends.
+
+## Runtime action surface
+
+Feishu currently exposes these runtime actions:
+
+- `send`
+- `read`
+- `edit`
+- `thread-reply`
+- `pin`
+- `list-pins`
+- `unpin`
+- `member-info`
+- `channel-info`
+- `channel-list`
+- `react` and `reactions` when reactions are enabled in config
+- `feishu_drive` comment actions: `list_comments`, `list_comment_replies`, `add_comment`, `reply_comment`
 
 ## Related
 

docs/channels/group-messages.md

@@ -15,7 +15,7 @@ Note: `agents.list[].groupChat.mentionPatterns` is now used by Telegram/Discord/
 
 - Activation modes: `mention` (default) or `always`. `mention` requires a ping (real WhatsApp @-mentions via `mentionedJids`, safe regex patterns, or the bot’s E.164 anywhere in the text). `always` wakes the agent on every message but it should reply only when it can add meaningful value; otherwise it returns the exact silent token `NO_REPLY` / `no_reply`. Defaults can be set in config (`channels.whatsapp.groups`) and overridden per group via `/activation`. When `channels.whatsapp.groups` is set, it also acts as a group allowlist (include `"*"` to allow all).
 - Group policy: `channels.whatsapp.groupPolicy` controls whether group messages are accepted (`open|disabled|allowlist`). `allowlist` uses `channels.whatsapp.groupAllowFrom` (fallback: explicit `channels.whatsapp.allowFrom`). Default is `allowlist` (blocked until you add senders).
-- Per-group sessions: session keys look like `agent:<agentId>:whatsapp:group:<jid>` so commands such as `/verbose on`, `/trace on`, or `/think high` (sent as standalone messages) are scoped to that group; personal DM state is untouched. Heartbeats are skipped for group threads.
+- Per-group sessions: session keys look like `agent:<agentId>:whatsapp:group:<jid>` so commands such as `/verbose on` or `/think high` (sent as standalone messages) are scoped to that group; personal DM state is untouched. Heartbeats are skipped for group threads.
 - Context injection: **pending-only** group messages (default 50) that _did not_ trigger a run are prefixed under `[Chat messages since your last reply - for context]`, with the triggering line under `[Current message - respond to this]`. Messages already in the session are not re-injected.
 - Sender surfacing: every group batch now ends with `[from: Sender Name (+E164)]` so Pi knows who is speaking.
 - Ephemeral/view-once: we unwrap those before extracting text/mentions, so pings inside them still trigger.
@@ -67,7 +67,7 @@ Only the owner number (from `channels.whatsapp.allowFrom`, or the bot’s own E.
 1. Add your WhatsApp account (the one running OpenClaw) to the group.
 2. Say `@openclaw …` (or include the number). Only allowlisted senders can trigger it unless you set `groupPolicy: "open"`.
 3. The agent prompt will include recent group context plus the trailing `[from: …]` marker so it can address the right person.
-4. Session-level directives (`/verbose on`, `/trace on`, `/think high`, `/new` or `/reset`, `/compact`) apply only to that group’s session; send them as standalone messages so they register. Your personal DM session remains independent.
+4. Session-level directives (`/verbose on`, `/think high`, `/new` or `/reset`, `/compact`) apply only to that group’s session; send them as standalone messages so they register. Your personal DM session remains independent.
 
 ## Testing / verification
 

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/cli/index.md

@@ -473,7 +473,6 @@ Chat messages support `/...` commands (text and native). See [/tools/slash-comma
 Highlights:
 
 - `/status` for quick diagnostics.
-- `/trace` for session-scoped plugin trace/debug lines.
 - `/config` for persisted config changes.
 - `/debug` for runtime-only config overrides (memory, not disk; requires `commands.debug: true`).
 

docs/cli/onboard.md

@@ -43,17 +43,6 @@ openclaw onboard --non-interactive \
 
 `--custom-api-key` is optional in non-interactive mode. If omitted, onboarding checks `CUSTOM_API_KEY`.
 
-LM Studio also supports a provider-specific key flag in non-interactive mode:
-
-```bash
-openclaw onboard --non-interactive \
-  --auth-choice lmstudio \
-  --custom-base-url "http://localhost:1234/v1" \
-  --custom-model-id "qwen/qwen3.5-9b" \
-  --lmstudio-api-key "$LM_API_TOKEN" \
-  --accept-risk
-```
-
 Non-interactive Ollama:
 
 ```bash

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:
@@ -64,7 +64,6 @@ To inspect it live in a conversation:
 
 ```text
 /verbose on
-/trace on
 ```
 
 ## Turn active memory on
@@ -86,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,
@@ -112,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
 
@@ -149,24 +148,21 @@ The global form writes `plugins.entries.active-memory.config.enabled`. It leaves
 `plugins.entries.active-memory.enabled` on so the command remains available to
 turn active memory back on later.
 
-If you want to see what active memory is doing in a live session, turn on the
-session toggles that match the output you want:
+If you want to see what active memory is doing in a live session, turn verbose
+mode on for that session:
 
 ```text
 /verbose on
-/trace on
 ```
 
-With those enabled, OpenClaw can show:
+With verbose enabled, OpenClaw can show:
 
-- an active memory status line such as `Active Memory: ok 842ms recent 34 chars` when `/verbose on`
-- a readable debug summary such as `Active Memory Debug: Lemon pepper wings with blue cheese.` when `/trace on`
+- an active memory status line such as `Active Memory: ok 842ms recent 34 chars`
+- a readable debug summary such as `Active Memory Debug: Lemon pepper wings with blue cheese.`
 
 Those lines are derived from the same active memory pass that feeds the hidden
 system context, but they are formatted for humans instead of exposing raw prompt
-markup. They are sent as a follow-up diagnostic message after the normal
-assistant reply so channel clients like Telegram do not flash a separate
-pre-reply diagnostic bubble.
+markup.
 
 By default, the blocking memory sub-agent transcript is temporary and deleted
 after the run completes.
@@ -175,7 +171,6 @@ Example flow:
 
 ```text
 /verbose on
-/trace on
 what wings should i order?
 ```
 
@@ -340,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
 
@@ -573,10 +572,8 @@ Start with `recent`.
 }
 ```
 
-If you want to inspect live behavior while tuning, use `/verbose on` for the
-normal status line and `/trace on` for the active-memory debug summary instead
-of looking for a separate active-memory debug command. In chat channels, those
-diagnostic lines are sent after the main assistant reply rather than before it.
+If you want to inspect live behavior while tuning, use `/verbose on` in the
+session instead of looking for a separate active-memory debug command.
 
 Then move to:
 
@@ -604,184 +601,6 @@ If active memory is too slow:
 - reduce recent turn counts
 - reduce per-turn char caps
 
-## Common issues
-
-### Embedding provider changed unexpectedly
-
-Active Memory uses the normal `memory_search` pipeline under
-`agents.defaults.memorySearch`. That means embedding-provider setup is only a
-requirement when your `memorySearch` setup requires embeddings for the behavior
-you want.
-
-In practice:
-
-- explicit provider setup is **required** if you want a provider that is not
-  auto-detected, such as `ollama`
-- explicit provider setup is **required** if auto-detection does not resolve
-  any usable embedding provider for your environment
-- explicit provider setup is **highly recommended** if you want deterministic
-  provider selection instead of "first available wins"
-- explicit provider setup is usually **not required** if auto-detection already
-  resolves the provider you want and that provider is stable in your deployment
-
-If `memorySearch.provider` is unset, OpenClaw auto-detects the first available
-embedding provider.
-
-That can be confusing in real deployments:
-
-- a newly available API key can change which provider memory search uses
-- one command or diagnostics surface may make the selected provider look
-  different from the path you are actually hitting during live memory sync or
-  search bootstrap
-- hosted providers can fail with quota or rate-limit errors that only show up
-  once Active Memory starts issuing recall searches before each reply
-
-Active Memory can still run without embeddings when `memory_search` can operate
-in degraded lexical-only mode, which typically happens when no embedding
-provider can be resolved.
-
-Do not assume the same fallback on provider runtime failures such as quota
-exhaustion, rate limits, network/provider errors, or missing local/remote
-models after a provider has already been selected.
-
-In practice:
-
-- if no embedding provider can be resolved, `memory_search` may degrade to
-  lexical-only retrieval
-- if an embedding provider is resolved and then fails at runtime, OpenClaw does
-  not currently guarantee a lexical fallback for that request
-- if you need deterministic provider selection, pin
-  `agents.defaults.memorySearch.provider`
-- if you need provider failover on runtime errors, configure
-  `agents.defaults.memorySearch.fallback` explicitly
-
-If you depend on embedding-backed recall, multimodal indexing, or a specific
-local/remote provider, pin the provider explicitly instead of relying on
-auto-detection.
-
-Common pinning examples:
-
-OpenAI:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "openai",
-        model: "text-embedding-3-small",
-      },
-    },
-  },
-}
-```
-
-Gemini:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "gemini",
-        model: "gemini-embedding-001",
-      },
-    },
-  },
-}
-```
-
-Ollama:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "ollama",
-        model: "nomic-embed-text",
-      },
-    },
-  },
-}
-```
-
-If you expect provider failover on runtime errors such as quota exhaustion,
-pinning a provider alone is not enough. Configure an explicit fallback too:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "openai",
-        fallback: "gemini",
-      },
-    },
-  },
-}
-```
-
-### Debugging provider issues
-
-If Active Memory is slow, empty, or appears to switch providers unexpectedly:
-
-- watch the gateway logs while reproducing the problem; look for lines such as
-  `active-memory: ... start|done`, `memory sync failed (search-bootstrap)`, or
-  provider-specific embedding errors
-- turn on `/trace on` to surface the plugin-owned Active Memory debug summary in
-  the session
-- turn on `/verbose on` if you also want the normal `🧩 Active Memory: ...`
-  status line after each reply
-- run `openclaw memory status --deep` to inspect the current memory-search
-  backend and index health
-- check `agents.defaults.memorySearch.provider` and related auth/config to make
-  sure the provider you expect is actually the one that can resolve at runtime
-- if you use `ollama`, verify the configured embedding model is installed, for
-  example `ollama list`
-
-Example debugging loop:
-
-```text
-1. Start the gateway and watch its logs
-2. In the chat session, run /trace on
-3. Send one message that should trigger Active Memory
-4. Compare the chat-visible debug line with the gateway log lines
-5. If provider choice is ambiguous, pin agents.defaults.memorySearch.provider explicitly
-```
-
-Example:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "ollama",
-        model: "nomic-embed-text",
-      },
-    },
-  },
-}
-```
-
-Or, if you want Gemini embeddings:
-
-```json5
-{
-  agents: {
-    defaults: {
-      memorySearch: {
-        provider: "gemini",
-      },
-    },
-  },
-}
-```
-
-After changing the provider, restart the gateway and run a fresh test with
-`/trace on` so the Active Memory debug line reflects the new embedding path.
-
 ## Related pages
 
 - [Memory Search](/concepts/memory-search)

docs/concepts/agent-loop.md

@@ -24,7 +24,7 @@ wired end-to-end.
 
 1. `agent` RPC validates params, resolves session (sessionKey/sessionId), persists session metadata, returns `{ runId, acceptedAt }` immediately.
 2. `agentCommand` runs the agent:
-   - resolves model + thinking/verbose/trace defaults
+   - resolves model + thinking/verbose defaults
    - loads skills snapshot
    - calls `runEmbeddedPiAgent` (pi-agent-core runtime)
    - emits **lifecycle end/error** if the embedded loop does not emit one

docs/concepts/context.md

@@ -136,7 +136,7 @@ Tools affect context in two ways:
 Slash commands are handled by the Gateway. There are a few different behaviors:
 
 - **Standalone commands**: a message that is only `/...` runs as a command.
-- **Directives**: `/think`, `/verbose`, `/trace`, `/reasoning`, `/elevated`, `/model`, `/queue` are stripped before the model sees the message.
+- **Directives**: `/think`, `/verbose`, `/reasoning`, `/elevated`, `/model`, `/queue` are stripped before the model sees the message.
   - Directive-only messages persist session settings.
   - Inline directives in a normal message act as per-message hints.
 - **Inline shortcuts** (allowlisted senders only): certain `/...` tokens inside a normal message can run immediately (example: “hey /status”), and are stripped before the model sees the remaining text.

docs/concepts/memory-qmd.md

@@ -51,9 +51,6 @@ legacy `--mask` collection flags and older MCP tool names when needed.
 - OpenClaw creates collections from your workspace memory files and any
   configured `memory.qmd.paths`, then runs `qmd update` + `qmd embed` on boot
   and periodically (default every 5 minutes).
-- The default workspace collection tracks `MEMORY.md` plus the `memory/`
-  tree. Lowercase `memory.md` remains a bootstrap fallback, not a separate QMD
-  collection.
 - Boot refresh runs in the background so chat startup is not blocked.
 - Searches use the configured `searchMode` (default: `search`; also supports
   `vsearch` and `query`). If a mode fails, OpenClaw retries with `qmd query`.
@@ -117,8 +114,8 @@ collection under `~/.openclaw/agents/<id>/qmd/sessions/`.
 
 ## Search scope
 
-By default, QMD search results are surfaced in direct and channel sessions
-(not groups). Configure `memory.qmd.scope` to change this:
+By default, QMD search results are only surfaced in DM sessions (not groups or
+channels). Configure `memory.qmd.scope` to change this:
 
 ```json5
 {
@@ -167,7 +164,7 @@ with `qmd query "test"` using the same XDG dirs OpenClaw uses.
 Set to `120000` for slower hardware.
 
 **Empty results in group chats?** Check `memory.qmd.scope` -- the default only
-allows direct and channel sessions.
+allows DM sessions.
 
 **Workspace-visible temp repos causing `ENAMETOOLONG` or broken indexing?**
 QMD traversal currently follows the underlying QMD scanner behavior rather than

docs/concepts/memory-search.md

@@ -67,8 +67,6 @@ flowchart LR
 
 If only one path is available (no embeddings or no FTS), the other runs alone.
 
-When embeddings are unavailable, OpenClaw still uses lexical ranking over FTS results instead of falling back to raw exact-match ordering only. That degraded mode boosts chunks with stronger query-term coverage and relevant file paths, which keeps recall useful even without `sqlite-vec` or an embedding provider.
-
 ## Improving search quality
 
 Two optional features help when you have a large note history:

docs/concepts/model-providers.md

@@ -672,28 +672,6 @@ Plugin-owned capability split:
 - Image understanding is plugin-owned `MiniMax-VL-01` on both MiniMax auth paths
 - Web search stays on provider id `minimax`
 
-### LM Studio
-
-LM Studio ships as a bundled provider plugin which uses the native API:
-
-- Provider: `lmstudio`
-- Auth: `LM_API_TOKEN`
-- Default inference base URL: `http://localhost:1234/v1`
-
-Then set a model (replace with one of the IDs returned by `http://localhost:1234/api/v1/models`):
-
-```json5
-{
-  agents: {
-    defaults: { model: { primary: "lmstudio/openai/gpt-oss-20b" } },
-  },
-}
-```
-
-OpenClaw uses LM Studio's native `/api/v1/models` and `/api/v1/models/load`
-for discovery + auto-load, with `/v1/chat/completions` for inference by default.
-See [/providers/lmstudio](/providers/lmstudio) for setup and troubleshooting.
-
 ### Ollama
 
 Ollama ships as a bundled provider plugin and uses Ollama's native API:
@@ -792,7 +770,7 @@ Example (OpenAI‑compatible):
     providers: {
       lmstudio: {
         baseUrl: "http://localhost:1234/v1",
-        apiKey: "${LM_API_TOKEN}",
+        apiKey: "LMSTUDIO_KEY",
         api: "openai-completions",
         models: [
           {

docs/concepts/qa-e2e-automation.md

@@ -120,23 +120,7 @@ Seed assets live in `qa/`:
 - `qa/scenarios/*.md`
 
 These are intentionally in git so the QA plan is visible to both humans and the
-agent.
-
-`qa-lab` should stay a generic markdown runner. Each scenario markdown file is
-the source of truth for one test run and should define:
-
-- scenario metadata
-- docs and code refs
-- optional plugin requirements
-- optional gateway config patch
-- the executable `qa-flow`
-
-The reusable runtime surface that backs `qa-flow` is allowed to stay generic
-and cross-cutting. For example, markdown scenarios can combine transport-side
-helpers with browser-side helpers that drive the embedded Control UI through the
-Gateway `browser.request` seam without adding a special-case runner.
-
-The baseline list should stay broad enough to cover:
+agent. The baseline list should stay broad enough to cover:
 
 - DM and channel chat
 - thread behavior
@@ -148,22 +132,6 @@ The baseline list should stay broad enough to cover:
 - repo-reading and docs-reading
 - one small build task such as Lobster Invaders
 
-## Transport adapters
-
-`qa-lab` owns a generic transport seam for markdown QA scenarios.
-`qa-channel` is the first adapter on that seam, but the design target is wider:
-future real or synthetic channels should plug into the same suite runner
-instead of adding a transport-specific QA runner.
-
-At the architecture level, the split is:
-
-- `qa-lab` owns generic scenario execution, worker concurrency, artifact writing, and reporting.
-- the transport adapter owns gateway config, readiness, inbound and outbound observation, transport actions, and normalized transport state.
-- markdown scenario files under `qa/scenarios/` define the test run; `qa-lab` provides the reusable runtime surface that executes them.
-
-Maintainer-facing adoption guidance for new channel adapters lives in
-[Testing](/help/testing#adding-a-channel-to-qa).
-
 ## Reporting
 
 `qa-lab` exports a Markdown protocol report from the observed bus timeline.

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"
@@ -976,7 +972,6 @@
                   "install/fly",
                   "install/gcp",
                   "install/hetzner",
-                  "install/hostinger",
                   "install/kubernetes",
                   "vps",
                   "install/macos-vm",
@@ -1121,8 +1116,6 @@
                   "plugins/codex-harness",
                   "plugins/webhooks",
                   "plugins/voice-call",
-                  "plugins/memory-wiki",
-                  "plugins/zalouser",
                   {
                     "group": "Building Plugins",
                     "pages": [
@@ -1195,7 +1188,6 @@
                       "tools/gemini-search",
                       "tools/grok-search",
                       "tools/kimi-search",
-                      "tools/minimax-search",
                       "tools/ollama-search",
                       "tools/perplexity-search",
                       "tools/searxng-search",
@@ -1245,27 +1237,24 @@
                 "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/lmstudio",
                   "providers/minimax",
                   "providers/mistral",
                   "providers/moonshot",
@@ -1285,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"
@@ -1466,7 +1455,6 @@
                       "cli/agent",
                       "cli/agents",
                       "cli/hooks",
-                      "cli/infer",
                       "cli/memory",
                       "cli/message",
                       "cli/models",
@@ -1517,8 +1505,7 @@
                       "cli/completion",
                       "cli/dns",
                       "cli/docs",
-                      "cli/mcp",
-                      "cli/wiki"
+                      "cli/mcp"
                     ]
                   }
                 ]
@@ -1552,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/gateway/local-models.md

@@ -11,7 +11,7 @@ title: "Local Models"
 
 Local is doable, but OpenClaw expects large context + strong defenses against prompt injection. Small cards truncate context and leak safety. Aim high: **≥2 maxed-out Mac Studios or equivalent GPU rig (~$30k+)**. A single **24 GB** GPU works only for lighter prompts with higher latency. Use the **largest / full-size model variant you can run**; aggressively quantized or “small” checkpoints raise prompt-injection risk (see [Security](/gateway/security)).
 
-If you want the lowest-friction local setup, start with [LM Studio](/providers/lmstudio) or [Ollama](/providers/ollama) and `openclaw onboard`. This page is the opinionated guide for higher-end local stacks and custom OpenAI-compatible local servers.
+If you want the lowest-friction local setup, start with [Ollama](/providers/ollama) and `openclaw onboard`. This page is the opinionated guide for higher-end local stacks and custom OpenAI-compatible local servers.
 
 ## Recommended: LM Studio + large local model (Responses API)
 

docs/gateway/security/index.md

@@ -730,16 +730,15 @@ Recommendations:
 
 ## Reasoning & verbose output in groups
 
-`/reasoning`, `/verbose`, and `/trace` can expose internal reasoning, tool
-output, or plugin diagnostics that
+`/reasoning` and `/verbose` can expose internal reasoning or tool output that
 was not meant for a public channel. In group settings, treat them as **debug
 only** and keep them off unless you explicitly need them.
 
 Guidance:
 
-- Keep `/reasoning`, `/verbose`, and `/trace` disabled in public rooms.
+- Keep `/reasoning` and `/verbose` disabled in public rooms.
 - If you enable them, do so only in trusted DMs or tightly controlled rooms.
-- Remember: verbose and trace output can include tool args, URLs, plugin diagnostics, and data the model saw.
+- Remember: verbose output can include tool args, URLs, and data the model saw.
 
 ## Configuration Hardening (examples)
 

docs/help/debugging.md

@@ -29,23 +29,6 @@ Examples:
 
 `/debug reset` clears all overrides and returns to the on-disk config.
 
-## Session trace output
-
-Use `/trace` when you want to see plugin-owned trace/debug lines in one session
-without turning on full verbose mode.
-
-Examples:
-
-```text
-/trace
-/trace on
-/trace off
-```
-
-Use `/trace` for plugin diagnostics such as Active Memory debug summaries.
-Keep using `/verbose` for normal verbose status/tool output, and keep using
-`/debug` for runtime-only config overrides.
-
 ## Gateway watch mode
 
 For fast iteration, run the gateway under the file watcher:

docs/help/faq.md

@@ -3192,14 +3192,13 @@ Related: [/concepts/oauth](/concepts/oauth) (OAuth flows, token storage, multi-a
 
 <AccordionGroup>
   <Accordion title="How do I stop internal system messages from showing in chat?">
-    Most internal or tool messages only appear when **verbose**, **trace**, or **reasoning** is enabled
+    Most internal or tool messages only appear when **verbose** or **reasoning** is enabled
     for that session.
 
     Fix in the chat where you see it:
 
     ```
     /verbose off
-    /trace off
     /reasoning off
     ```
 

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/help/testing.md

@@ -69,12 +69,10 @@ These commands sit beside the main test suites when you need QA-lab realism:
   - Runs the Matrix live QA lane against a disposable Docker-backed Tuwunel homeserver.
   - Provisions three temporary Matrix users (`driver`, `sut`, `observer`) plus one private room, then starts a QA gateway child with the real Matrix plugin as the SUT transport.
   - Uses the pinned stable Tuwunel image `ghcr.io/matrix-construct/tuwunel:v1.5.1` by default. Override with `OPENCLAW_QA_MATRIX_TUWUNEL_IMAGE` when you need to test a different image.
-  - Matrix currently supports only `--credential-source env` because the lane provisions disposable users locally.
   - Writes a Matrix QA report, summary, and observed-events artifact under `.artifacts/qa-e2e/...`.
 - `pnpm openclaw qa telegram`
   - Runs the Telegram live QA lane against a real private group using the driver and SUT bot tokens from env.
   - Requires `OPENCLAW_QA_TELEGRAM_GROUP_ID`, `OPENCLAW_QA_TELEGRAM_DRIVER_BOT_TOKEN`, and `OPENCLAW_QA_TELEGRAM_SUT_BOT_TOKEN`. The group id must be the numeric Telegram chat id.
-  - Supports `--credential-source convex` for shared pooled credentials. Use env mode by default, or set `OPENCLAW_QA_CREDENTIAL_SOURCE=convex` to opt into pooled leases.
   - Requires two distinct bots in the same private group, with the SUT bot exposing a Telegram username.
   - For stable bot-to-bot observation, enable Bot-to-Bot Communication Mode in `@BotFather` for both bots and ensure the driver bot can observe group bot traffic.
   - Writes a Telegram QA report, summary, and observed-messages artifact under `.artifacts/qa-e2e/...`.
@@ -89,152 +87,6 @@ transport coverage matrix.
 | Matrix   | x      | x              | x               | x               | x              | x                | x                | x                    |              |
 | Telegram | x      |                |                 |                 |                |                  |                  |                      | x            |
 
-### Shared Telegram credentials via Convex (v1)
-
-When `--credential-source convex` (or `OPENCLAW_QA_CREDENTIAL_SOURCE=convex`) is enabled for
-`openclaw qa telegram`, QA lab acquires an exclusive lease from a Convex-backed pool, heartbeats
-that lease while the lane is running, and releases the lease on shutdown.
-
-Reference Convex project scaffold:
-
-- `qa/convex-credential-broker/`
-
-Required env vars:
-
-- `OPENCLAW_QA_CONVEX_SITE_URL` (for example `https://your-deployment.convex.site`)
-- One secret for the selected role:
-  - `OPENCLAW_QA_CONVEX_SECRET_MAINTAINER` for `maintainer`
-  - `OPENCLAW_QA_CONVEX_SECRET_CI` for `ci`
-- Credential role selection:
-  - CLI: `--credential-role maintainer|ci`
-  - Env default: `OPENCLAW_QA_CREDENTIAL_ROLE` (defaults to `maintainer`)
-
-Optional env vars:
-
-- `OPENCLAW_QA_CREDENTIAL_LEASE_TTL_MS` (default `1200000`)
-- `OPENCLAW_QA_CREDENTIAL_HEARTBEAT_INTERVAL_MS` (default `30000`)
-- `OPENCLAW_QA_CREDENTIAL_ACQUIRE_TIMEOUT_MS` (default `90000`)
-- `OPENCLAW_QA_CREDENTIAL_HTTP_TIMEOUT_MS` (default `15000`)
-- `OPENCLAW_QA_CONVEX_ENDPOINT_PREFIX` (default `/qa-credentials/v1`)
-- `OPENCLAW_QA_CREDENTIAL_OWNER_ID` (optional trace id)
-- `OPENCLAW_QA_ALLOW_INSECURE_HTTP=1` allows loopback `http://` Convex URLs for local-only development.
-
-`OPENCLAW_QA_CONVEX_SITE_URL` should use `https://` in normal operation.
-
-Maintainer admin commands (pool add/remove/list) require
-`OPENCLAW_QA_CONVEX_SECRET_MAINTAINER` specifically.
-
-CLI helpers for maintainers:
-
-```bash
-pnpm openclaw qa credentials add --kind telegram --payload-file qa/telegram-credential.json
-pnpm openclaw qa credentials list --kind telegram
-pnpm openclaw qa credentials remove --credential-id <credential-id>
-```
-
-Use `--json` for machine-readable output in scripts and CI utilities.
-
-Default endpoint contract (`OPENCLAW_QA_CONVEX_SITE_URL` + `/qa-credentials/v1`):
-
-- `POST /acquire`
-  - Request: `{ kind, ownerId, actorRole, leaseTtlMs, heartbeatIntervalMs }`
-  - Success: `{ status: "ok", credentialId, leaseToken, payload, leaseTtlMs?, heartbeatIntervalMs? }`
-  - Exhausted/retryable: `{ status: "error", code: "POOL_EXHAUSTED" | "NO_CREDENTIAL_AVAILABLE", ... }`
-- `POST /heartbeat`
-  - Request: `{ kind, ownerId, actorRole, credentialId, leaseToken, leaseTtlMs }`
-  - Success: `{ status: "ok" }` (or empty `2xx`)
-- `POST /release`
-  - Request: `{ kind, ownerId, actorRole, credentialId, leaseToken }`
-  - Success: `{ status: "ok" }` (or empty `2xx`)
-- `POST /admin/add` (maintainer secret only)
-  - Request: `{ kind, actorId, payload, note?, status? }`
-  - Success: `{ status: "ok", credential }`
-- `POST /admin/remove` (maintainer secret only)
-  - Request: `{ credentialId, actorId }`
-  - Success: `{ status: "ok", changed, credential }`
-  - Active lease guard: `{ status: "error", code: "LEASE_ACTIVE", ... }`
-- `POST /admin/list` (maintainer secret only)
-  - Request: `{ kind?, status?, includePayload?, limit? }`
-  - Success: `{ status: "ok", credentials, count }`
-
-Payload shape for Telegram kind:
-
-- `{ groupId: string, driverToken: string, sutToken: string }`
-- `groupId` must be a numeric Telegram chat id string.
-- `admin/add` validates this shape for `kind: "telegram"` and rejects malformed payloads.
-
-### Adding a channel to QA
-
-Adding a channel to the markdown QA system requires exactly two things:
-
-1. A transport adapter for the channel.
-2. A scenario pack that exercises the channel contract.
-
-Do not add a channel-specific QA runner when the shared `qa-lab` runner can
-own the flow.
-
-`qa-lab` owns the shared mechanics:
-
-- suite startup and teardown
-- worker concurrency
-- artifact writing
-- report generation
-- scenario execution
-- compatibility aliases for older `qa-channel` scenarios
-
-The channel adapter owns the transport contract:
-
-- how the gateway is configured for that transport
-- how readiness is checked
-- how inbound events are injected
-- how outbound messages are observed
-- how transcripts and normalized transport state are exposed
-- how transport-backed actions are executed
-- how transport-specific reset or cleanup is handled
-
-The minimum adoption bar for a new channel is:
-
-1. Implement the transport adapter on the shared `qa-lab` seam.
-2. Register the adapter in the transport registry.
-3. Keep transport-specific mechanics inside the adapter or the channel harness.
-4. Author or adapt markdown scenarios under `qa/scenarios/`.
-5. Use the generic scenario helpers for new scenarios.
-6. Keep existing compatibility aliases working unless the repo is doing an intentional migration.
-
-The decision rule is strict:
-
-- If behavior can be expressed once in `qa-lab`, put it in `qa-lab`.
-- If behavior depends on one channel transport, keep it in that adapter or plugin harness.
-- If a scenario needs a new capability that more than one channel can use, add a generic helper instead of a channel-specific branch in `suite.ts`.
-- If a behavior is only meaningful for one transport, keep the scenario transport-specific and make that explicit in the scenario contract.
-
-Preferred generic helper names for new scenarios are:
-
-- `waitForTransportReady`
-- `waitForChannelReady`
-- `injectInboundMessage`
-- `injectOutboundMessage`
-- `waitForTransportOutboundMessage`
-- `waitForChannelOutboundMessage`
-- `waitForNoTransportOutbound`
-- `getTransportSnapshot`
-- `readTransportMessage`
-- `readTransportTranscript`
-- `formatTransportTranscript`
-- `resetTransport`
-
-Compatibility aliases remain available for existing scenarios, including:
-
-- `waitForQaChannelReady`
-- `waitForOutboundMessage`
-- `waitForNoOutbound`
-- `formatConversationTranscript`
-- `resetBus`
-
-New channel work should use the generic helper names.
-Compatibility aliases exist to avoid a flag day migration, not as the model for
-new scenario authoring.
-
 ## Test suites (what runs where)
 
 Think of the suites as “increasing realism” (and increasing flakiness/cost):

docs/install/hostinger.md

@@ -1,94 +0,0 @@
----
-summary: "Host OpenClaw on Hostinger"
-read_when:
-  - Setting up OpenClaw on Hostinger
-  - Looking for a managed VPS for OpenClaw
-  - Using Hostinger 1-Click OpenClaw
-title: "Hostinger"
----
-
-# Hostinger
-
-Run a persistent OpenClaw Gateway on [Hostinger](https://www.hostinger.com/openclaw) via a **1-Click** managed deployment or a **VPS** install.
-
-## Prerequisites
-
-- Hostinger account ([signup](https://www.hostinger.com/openclaw))
-- About 5-10 minutes
-
-## Option A: 1-Click OpenClaw
-
-The fastest way to get started. Hostinger handles infrastructure, Docker, and automatic updates.
-
-<Steps>
-  <Step title="Purchase and launch">
-    1. From the [Hostinger OpenClaw page](https://www.hostinger.com/openclaw), choose a Managed OpenClaw plan and complete checkout.
-
-    <Note>
-    During checkout you can select **Ready-to-Use AI** credits that are pre-purchased and integrated instantly inside OpenClaw -- no external accounts or API keys from other providers needed. You can start chatting right away. Alternatively, provide your own key from Anthropic, OpenAI, Google Gemini, or xAI during setup.
-    </Note>
-
-  </Step>
-
-  <Step title="Select a messaging channel">
-    Choose one or more channels to connect:
-
-    - **WhatsApp** -- scan the QR code shown in the setup wizard.
-    - **Telegram** -- paste the bot token from [BotFather](https://t.me/BotFather).
-
-  </Step>
-
-  <Step title="Complete installation">
-    Click **Finish** to deploy the instance. Once ready, access the OpenClaw dashboard from **OpenClaw Overview** in hPanel.
-  </Step>
-
-</Steps>
-
-## Option B: OpenClaw on VPS
-
-More control over your server. Hostinger deploys OpenClaw via Docker on your VPS and you manage it through the **Docker Manager** in hPanel.
-
-<Steps>
-  <Step title="Purchase a VPS">
-    1. From the [Hostinger OpenClaw page](https://www.hostinger.com/openclaw), choose an OpenClaw on VPS plan and complete checkout.
-
-    <Note>
-    You can select **Ready-to-Use AI** credits during checkout -- these are pre-purchased and integrated instantly inside OpenClaw, so you can start chatting without any external accounts or API keys from other providers.
-    </Note>
-
-  </Step>
-
-  <Step title="Configure OpenClaw">
-    Once the VPS is provisioned, fill in the configuration fields:
-
-    - **Gateway token** -- auto-generated; save it for later use.
-    - **WhatsApp number** -- your number with country code (optional).
-    - **Telegram bot token** -- from [BotFather](https://t.me/BotFather) (optional).
-    - **API keys** -- only needed if you did not select Ready-to-Use AI credits during checkout.
-
-  </Step>
-
-  <Step title="Start OpenClaw">
-    Click **Deploy**. Once running, open the OpenClaw dashboard from the hPanel by clicking on **Open**.
-  </Step>
-
-</Steps>
-
-Logs, restarts, and updates are managed directly from the Docker Manager interface in hPanel. To update, press on **Update** in Docker Manager and that will pull the latest image.
-
-## Verify your setup
-
-Send "Hi" to your assistant on the channel you connected. OpenClaw will reply and walk you through initial preferences.
-
-## Troubleshooting
-
-**Dashboard not loading** -- Wait a few minutes for the container to finish provisioning. Check the Docker Manager logs in hPanel.
-
-**Docker container keeps restarting** -- Open Docker Manager logs and look for configuration errors (missing tokens, invalid API keys).
-
-**Telegram bot not responding** -- Send your pairing code message from Telegram directly as a message inside your OpenClaw chat to complete the connection.
-
-## Next steps
-
-- [Channels](/channels) -- connect Telegram, WhatsApp, Discord, and more
-- [Gateway configuration](/gateway/configuration) -- all config optionss

docs/plugins/architecture.md

@@ -519,30 +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, channel, and provider hints
-to narrow plugin loading before broader registry materialization:
-
-- CLI loading narrows to plugins that own the requested primary command
-- channel setup/plugin resolution narrows to plugins that own the requested
-  channel id
-- 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,101 +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`
-- channel-triggered setup/channel planning falls back to legacy `channels[]`
-  ownership when explicit channel activation metadata is missing
-- 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/memory-wiki.md

@@ -45,28 +45,6 @@ both layers in one pass with `memory_search corpus=all`.
 When you need wiki-specific ranking, provenance, or direct page access, use the
 wiki-native tools instead.
 
-## Recommended hybrid pattern
-
-A strong default for local-first setups is:
-
-- QMD as the active memory backend for recall and broad semantic search
-- `memory-wiki` in `bridge` mode for durable synthesized knowledge pages
-
-That split works well because each layer stays focused:
-
-- QMD keeps raw notes, session exports, and extra collections searchable
-- `memory-wiki` compiles stable entities, claims, dashboards, and source pages
-
-Practical rule:
-
-- use `memory_search` when you want one broad recall pass across memory
-- use `wiki_search` and `wiki_get` when you want provenance-aware wiki results
-- use `memory_search corpus=all` when you want shared search to span both layers
-
-If bridge mode reports zero exported artifacts, the active memory plugin is not
-currently exposing public bridge inputs yet. Run `openclaw wiki doctor` first,
-then confirm the active memory plugin supports public artifacts.
-
 ## Vault modes
 
 `memory-wiki` supports three vault modes:
@@ -326,47 +304,6 @@ Key toggles:
 - `render.createBacklinks`: generate deterministic related blocks
 - `render.createDashboards`: generate dashboard pages
 
-### Example: QMD + bridge mode
-
-Use this when you want QMD for recall and `memory-wiki` for a maintained
-knowledge layer:
-
-```json5
-{
-  memory: {
-    backend: "qmd",
-      "memory-wiki": {
-        enabled: true,
-        config: {
-          vaultMode: "bridge",
-          bridge: {
-            enabled: true,
-            readMemoryArtifacts: true,
-            indexDreamReports: true,
-            indexDailyNotes: true,
-            indexMemoryRoot: true,
-            followMemoryEvents: true,
-          },
-          search: {
-            backend: "shared",
-            corpus: "all",
-          },
-          context: {
-            includeCompiledDigestPrompt: false,
-          },
-        },
-      },
-    },
-  },
-}
-```
-
-This keeps:
-
-- QMD in charge of active memory recall
-- `memory-wiki` focused on compiled pages and dashboards
-- prompt shape unchanged until you intentionally enable compiled digest prompts
-
 ## CLI
 
 `memory-wiki` also exposes a top-level CLI surface:

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)