Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
1170
to
+1174
| "language": "zh-Hans", | ||
| "groups": [ | ||
| { | ||
| "group": "开始", | ||
| "pages": ["zh-CN/index", "zh-CN/start/getting-started", "zh-CN/start/wizard"] | ||
| "group": "Start Here", | ||
| "pages": [ |
Contributor
There was a problem hiding this comment.
[P2] zh-Hans nav uses English group titles
In the zh-Hans navigation block, the group names were changed from Chinese (e.g. 开始) to English (Start Here, Help, etc.). If the intent is a fully localized nav for Simplified Chinese readers, it’s likely better to keep these group titles translated (or align with whatever other locales do). If the intent is to reuse the English grouping labels, then this is fine—just calling it out since it changes the visible UI text for the zh-Hans docs.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/docs.json
Line: 1170:1174
Comment:
[P2] zh-Hans nav uses English group titles
In the zh-Hans navigation block, the group names were changed from Chinese (e.g. `开始`) to English (`Start Here`, `Help`, etc.). If the intent is a fully localized nav for Simplified Chinese readers, it’s likely better to keep these group titles translated (or align with whatever other locales do). If the intent is to reuse the English grouping labels, then this is fine—just calling it out since it changes the visible UI text for the zh-Hans docs.
<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>
How can I resolve this? If you propose a fix, please make it concise.
dbachelder
pushed a commit
to dbachelder/openclaw
that referenced
this pull request
Feb 3, 2026
rishitank
added a commit
to TanksterAI/openclaw
that referenced
this pull request
Feb 3, 2026
* fix: align tool execute parameter order * Docs: expand ClawHub overview * fix: align tool definition adapter * fix: normalize tool execute args * docs: fold 2026.2.2 into 2026.2.1 * fix: handle legacy tool execute signatures * fix: satisfy tool adapter lint * docs: update 2026.2.1 changelog * docs: update appcast for 2026.2.1 * fix: guard remote media fetches with SSRF checks * style: format fetch guard signatures * fix(docker): add gateway subcommand and cloud-compatible flags The Dockerfile CMD runs without arguments, causing the CLI to print help and exit with code 1. This breaks deployment on container platforms (Render, Railway, Fly.io, etc.) that rely on the CMD. Changes: - Add `gateway` subcommand to start the server - Add `--allow-unconfigured` to allow startup without config file - Add `--bind lan` to bind to 0.0.0.0 instead of localhost (required for container health checks) Fixes openclaw#5685 * fix(docker): remove --bind lan from default CMD to work out of the box Addresses review feedback: --bind lan requires auth token, so default CMD should bind to loopback only. For container platforms needing LAN binding for health checks: 1. Set OPENCLAW_GATEWAY_TOKEN env var 2. Override CMD: ["node","dist/index.js","gateway","--allow-unconfigured","--bind","lan"] * docs: note docker allow-unconfigured behavior * fix: start gateway in docker CMD (openclaw#6635) (thanks @kaizen403) * test: cover SSRF blocking for attachment URLs * fix: polish docker setup flow * chore: We have a sleep at home. The sleep at home: * fix(update): harden global updates * chore: fix broken test. * fix: expand SSRF guard coverage * fix: stabilize docker e2e flows * fix(telegram): handle Grammy HttpError network failures (openclaw#3815) (openclaw#7195) * fix(telegram): handle Grammy HttpError network failures (openclaw#3815) Grammy wraps fetch errors in an .error property (not .cause). Added .error traversal to collectErrorCandidates in network-errors.ts. Registered scoped unhandled rejection handler in monitorTelegramProvider to catch network errors that escape the polling loop (e.g., from setMyCommands during bot setup). Handler is unregistered when the provider stops. * fix(telegram): address review feedback for Grammy HttpError handling - Gate .error traversal on HttpError name to avoid widening search graph - Use runtime logger instead of console.warn for consistency - Add isGrammyHttpError check to scope unhandled rejection handler - Consolidate isNetworkRelatedError into isRecoverableTelegramNetworkError - Add 'timeout' to recoverable message snippets for full coverage * CI: label maintainer issues * Docs i18n: harden doc-mode pipeline * Docs: add zh-CN translations * Docs: fix zh-CN template time wording What: replace <2/<30 text in zh-CN AGENTS template with safe wording Why: avoid MDX parse errors during docs build Tests: not run (doc text change) * docs: add changelog for zh-CN translations (openclaw#6619) (thanks @joshp123) * Docs: fix zh-CN ClawHub link What: wrap clawhub.com in an explicit URL link in zh-CN skills doc Why: avoid Mintlify broken-link parser treating trailing punctuation as part of the URL Tests: not run (doc text change) * Docs: use explicit ClawHub markdown link What: switch clawhub.com reference to explicit Markdown link syntax Why: MDX parser rejects angle-bracket autolinks Tests: not run (doc text change) * Docs i18n: tune zh-CN prompt + glossary What: enforce zh-CN tone (你/你的), Skills/local loopback/Tailscale terms, Gateway网关 Why: keep future translation output consistent with issue feedback Tests: not run (prompt/glossary change) * Docs: normalize zh-CN terminology + tone What: switch to 你/你的 tone; standardize Skills/Gateway网关/local loopback/私信 wording Why: align zh-CN docs with issue 6995 feedback + idiomatic tech style Tests: pnpm docs:build * Tests: stub SSRF DNS pinning (openclaw#6619) (thanks @joshp123) * fix(webchat): respect user scroll position during streaming and refresh - Increase near-bottom threshold from 200px to 450px so one long message doesn't falsely register as 'near bottom' - Make force=true only override on initial load (chatHasAutoScrolled=false), not on subsequent refreshChat() calls - refreshChat() no longer passes force=true to scheduleChatScroll - Add chatNewMessagesBelow flag for future 'scroll to bottom' button UI - Clear chatNewMessagesBelow when user scrolls back to bottom - Add 13 unit tests covering threshold, force behavior, streaming, and reset * fix: address review feedback — retryDelay uses effectiveForce, default overrides param, @State() on chatNewMessagesBelow * Docs: expand zh-Hans nav and fix assets * Docs: expand zh-Hans nav (openclaw#7242) (thanks @joshp123) * fix(ui): add core state and logic for scroll control * feat(ui): add new messages indicator button * docs: update changelog for PR openclaw#7226 * chore: fix formatting and CI * iOS: wire node services and tests * iOS: stabilize talk mode tests * Gateway: fix node invoke receive loop * Gateway: wait for snapshot before connect * Agents: add nodes invoke action * iOS: fix node notify and identity * iOS: streamline notify timeouts * iOS: add write commands for contacts/calendar/reminders * iOS: add push-to-talk node commands * iOS: pause voice wake during PTT * iOS: add PTT once/cancel * Gateway: add PTT chat + nodes CLI * iOS: wire node commands and incremental TTS * iOS: update onboarding and gateway UI * Core: update shared gateway models * iOS: improve gateway auto-connect and voice permissions * Docs: add zh-CN landing notice + AI image * Docs: add zh-CN landing note (openclaw#7303) (thanks @joshp123) * Docs: expand zh-CN landing note * Revert "iOS: wire node services and tests" This reverts commit 7b0a0f3. * Revert "Core: update shared gateway models" This reverts commit 37eaca7. * fix: resolve check errors in nodes-tool and commands-ptt * feat(config): default thinking for sessions_spawn subagents (openclaw#7372) * feat(config): add subagent default thinking * fix: accept config subagents.thinking + stabilize test mocks (openclaw#7372) (thanks @tyler6204) * fix: use findLast instead of clearAllMocks in test (openclaw#7372) * fix: correct test assertions for tool result structure (openclaw#7372) * fix: remove unnecessary type assertion after rebase * fix: validate AbortSignal instances before calling AbortSignal.any() Fixes openclaw#7269 * refactor: use structural typing instead of instanceof for AbortSignal check Address P1 review feedback from Greptile: instanceof AbortSignal may be unreliable across different realms (VM, iframe, etc.) where the AbortSignal constructor may differ. Use structural typing (checking for aborted property and addEventListener method) for more robust cross-realm compatibility. * fix: validate AbortSignal instances before calling AbortSignal.any() (openclaw#7277) (thanks @Elarwei001) * fix(tools): ensure file_path alias passes validation in read/write tools (openclaw#7451) Co-authored-by: lotusfall <[email protected]> * feat: add Tankster AI customizations for Coolify deployment - Add Dockerfile.tankster with pre-installed packages (clawdhub, auggie, summarize, gifgrep) - Add docker-compose.coolify.yml for Coolify GitHub sync deployment - Add install-tankster-extras.sh script for additional package installation - Include system packages: jq, ripgrep, ffmpeg, tmux, bash, golang-go, python3 - Configure Augment credentials mount and coolify network integration * fix: use external volumes for data persistence - Mark openclaw-data and openclaw-workspace as external volumes - Volumes are pre-created with migrated data from legacy Moltbot setup * feat: rename docker-compose.coolify.yml to docker-compose.yaml for Coolify - Coolify expects docker-compose.yaml at the root - This overrides the upstream docker-compose.yml for our deployment * fix: use Node 25 and Go 1.22 for gifgrep compatibility - Upgrade base image from node:22-bookworm to node:25-bookworm - Install Go 1.22 from official tarball instead of Debian's golang-go - gifgrep requires Go 1.21+ for toolchain directive support * fix: install corepack globally before enabling (Node 25 compat) Node 25 no longer bundles corepack by default, so we need to install it via npm first before running corepack enable. * fix: use --force flag for corepack install (fix yarnpkg symlink conflict) * chore: add CodeRabbit, CODEOWNERS, PR template; update issue templates - Add .coderabbit.yaml with OpenClaw-themed review personality - Add .github/CODEOWNERS to auto-assign @rishitank as reviewer - Add .github/PULL_REQUEST_TEMPLATE.md following project standards - Update issue templates: Clawdbot → OpenClaw references - Disable blank issues, add documentation links * ci: add security, release, and auto-merge workflows - Add .github/workflows/security.yml with CodeQL, dependency review, npm audit - Add .github/workflows/release.yml with release-please automation - Add .github/workflows/auto-merge.yml for automatic PR merging - Add release-please-config.json and .release-please-manifest.json - Update dependabot.yml: MoltbotKit → OpenClawKit, add Docker ecosystem * fix: make CI workflows resilient for fork environment - security.yml: Add continue-on-error for dependency review (requires dependency graph) - auto-merge.yml: Check if PAT_AUTO_MERGE secret exists before attempting merge - labeler.yml: Only run in upstream openclaw/openclaw repo (requires GH_APP_PRIVATE_KEY) * style: fix swiftformat violations in macOS app Auto-formatted with swiftformat 0.59.1 to fix: - sortImports: alphabetical import ordering - indent: proper indentation - trailingSpace: remove trailing whitespace - redundantProperty: simplify property definitions - docComments: use doc comments for API declarations - wrapPropertyBodies: multi-line property bodies - redundantViewBuilder: remove unnecessary @ViewBuilder * fix: shorten tone_instructions to comply with 250 char limit CodeRabbit requires tone_instructions to be at most 250 characters. Condensed the crab personality while keeping the essential wit. * perf: skip duplicate CI runs on feature branch pushes Add condition to skip workflow runs triggered by push events on non-main branches. This prevents duplicate runs when pushing to a PR branch (which triggers both push and pull_request events). Jobs now only run when: - Event is pull_request (any branch), OR - Event is push AND branch is main This halves the number of CI jobs for PR workflows. * fix: remove useless variable initialization in fetchRemoteMedia The finalUrl variable was initialized to url but immediately overwritten by result.finalUrl in the try block. If the try block throws, we exit immediately, so the initial value was never used. This fixes a CodeQL warning about useless assignment. * fix: address CodeRabbit review comments - Update .coderabbit.yaml tone to Darth Vader (matching auggie-openai-proxy) - Remove trailing blank line from .coderabbit.yaml - Add docker-compose*.yml pattern to CODEOWNERS - Use GraphQL auto-merge API in release.yml (respects branch protection) - Parameterize AUGMENT_CREDENTIALS_PATH in docker-compose.yaml - Fix curl|sh security issues in Dockerfile.tankster and install script - Change npm to pnpm in Dockerfile.tankster and install-tankster-extras.sh - Fix .ts to .js import extension in bash-tools test file * chore(deps): update dependencies to latest versions - @aws-sdk/client-bedrock: 3.980.0 → 3.981.0 - @mariozechner/pi-agent-core: 0.51.0 → 0.51.1 - @mariozechner/pi-ai: 0.51.0 → 0.51.1 - @mariozechner/pi-coding-agent: 0.51.0 → 0.51.1 - @mariozechner/pi-tui: 0.51.0 → 0.51.1 - @sinclair/typebox: 0.34.47 → 0.34.48 (with pnpm override) - @typescript/native-preview: 7.0.0-dev.20260201.1 → 7.0.0-dev.20260202.1 - oxfmt: 0.27.0 → 0.28.0 - oxlint: 1.42.0 → 1.43.0 The typebox upgrade required updating the pnpm override to force all packages to use the same version, avoiding unique symbol conflicts. * fix: make Labeler and Auto-Merge workflows resilient in forks - Add 'if: github.repository == openclaw/openclaw' to label-issues job (was missing, causing secret access failures in forks) - Simplify Auto-Merge workflow with continue-on-error for missing PAT (the previous bash secret check didn't work as intended) * style: apply formatting cleanup - Remove trailing blank lines from various files - Normalize quote styles in YAML files - Minor CSS whitespace cleanup in resizable-divider.ts * feat: migrate from tsx to Node 25 native TypeScript support Node 25 has native TypeScript support enabled by default, eliminating the need for tsx as a TypeScript loader. Changes: - Remove tsx from devDependencies - Update all 'node --import tsx' commands to just 'node' - Update Dockerfile from node:22 to node:25 - Update CI workflows to use Node 25.x - Update README to reflect native TS support This simplifies the build process and removes a dependency. * chore: use .nvmrc for Node version consistency Created .nvmrc with Node 25 and updated all GitHub Actions workflows to use node-version-file instead of hardcoded node-version values. This ensures a single source of truth for the Node.js version across local development (via nvm) and CI/CD pipelines. * refactor: rename docker-compose.yaml to docker-compose.tankster.yaml Renamed the Tankster-specific Docker Compose file to distinguish it from the upstream generic docker-compose.yml: - docker-compose.yml: Upstream/generic OpenClaw deployment (uses pre-built image) - docker-compose.tankster.yaml: Tankster AI deployment (builds from Dockerfile.tankster, includes Coolify config, additional env vars for Telegram/Slack/Discord/Augment) Also updated Coolify application settings to use the new compose file location. * fix: remove remaining tsx references for Node 25 native TS support - Remove --import tsx from gateway.sigterm.test.ts (Node 25 runs .ts natively) - Remove tsx binary check from doctor-install.ts (no longer needed) * fix: correct .nvmrc path in formal-conformance workflow The workflow checks out openclaw to a subdirectory, so the path needs to be openclaw/.nvmrc instead of .nvmrc * fix: add --experimental-transform-types for Node 25 child process Node 25's native TypeScript support with --experimental-strip-types only strips types but doesn't rewrite .js imports to .ts. The child process spawned by the test needs --experimental-transform-types to handle the .js extension imports in the codebase. * refactor: convert scripts to ES6 TypeScript with arrow functions - Convert all 5 scripts from .js to .ts with full type annotations - Replace ES5 function declarations with ES6 arrow functions - Use extensionless imports for consistency - Add proper TypeScript interfaces for all complex types - Update package.json references from .js to .ts - Update test file imports to use extensionless paths - Update pre-commit hook to reference .ts file * fix: add .ts extension to setup-git-hooks import in postinstall Node.js native TypeScript support requires explicit .ts extensions for imports when using --experimental-strip-types. * Revert "fix: add .ts extension to setup-git-hooks import in postinstall" This reverts commit e1ced92. * fix: use jiti to run postinstall script for extensionless TypeScript imports jiti provides runtime TypeScript support with proper module resolution for extensionless imports, which node's native TypeScript support (--experimental-strip-types) doesn't handle without additional flags. --------- Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: Rishi Vhavle <[email protected]> Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: cpojer <[email protected]> Co-authored-by: Christian Klotz <[email protected]> Co-authored-by: Shadow <[email protected]> Co-authored-by: Josh Palmer <[email protected]> Co-authored-by: CLAWDINATOR Bot <clawdinator[bot]@users.noreply.github.com> Co-authored-by: Marco Marandiz <[email protected]> Co-authored-by: Shakker <[email protected]> Co-authored-by: Mariano Belinky <[email protected]> Co-authored-by: Mariano Belinky <[email protected]> Co-authored-by: Tyler Yust <[email protected]> Co-authored-by: Elarwei <[email protected]> Co-authored-by: bqcfjwhz85-arch <[email protected]> Co-authored-by: lotusfall <[email protected]>
dgarson
added a commit
to dgarson/clawdbot
that referenced
this pull request
Feb 4, 2026
Comprehensive merge of upstream changes including: ### Major Features - Web UI: new Agents dashboard for managing agent files, tools, skills, models, channels, and cron jobs - Security: healthcheck skill and bootstrap audit guidance (openclaw#7641) - Config: subagent thinking level configuration (openclaw#7372) - Docs: zh-CN translations and localization improvements (openclaw#6619, openclaw#7242, openclaw#7303) ### Fixes & Improvements - Agents: repair malformed tool calls and session transcripts (openclaw#7473) - Security: SSRF protections for media fetches and skill installer downloads - Telegram: recover from grammY long-poll timeouts (openclaw#7466) - Media understanding: skip binary files from text extraction (openclaw#7475) - Multiple security hardening improvements ### Merged Local Features - Kept local @anthropic-ai/claude-agent-sdk and @modelcontextprotocol/sdk dependencies - Merged agent runtime and thinking configurations in config types - Preserved amazon-bedrock auth checking and model failover filtering fixes in CHANGELOG ### Dependency Updates - Pi packages: 0.51.0 → 0.51.1 - @aws-sdk/client-bedrock: 3.980.0 → 3.981.0 - oxlint: 1.42.0 → 1.43.0 - oxfmt: 0.27.0 → 0.28.0 All conflicts resolved by: - Taking upstream UI components for new Agents dashboard consistency - Merging config type features (runtime + skills + thinking) - Preserving local dependencies and custom fixes in CHANGELOG - Regenerating pnpm-lock.yaml to match merged package.json
HashWarlock
pushed a commit
to HashWarlock/openclaw
that referenced
this pull request
Feb 4, 2026
CompassHXM
added a commit
to CompassHXM/clawdbot
that referenced
this pull request
Feb 5, 2026
* docs: note docker allow-unconfigured behavior * fix: start gateway in docker CMD (#6635) (thanks @kaizen403) * test: cover SSRF blocking for attachment URLs * fix: polish docker setup flow * chore: We have a sleep at home. The sleep at home: * fix(update): harden global updates * chore: fix broken test. * fix: expand SSRF guard coverage * fix: stabilize docker e2e flows * fix(telegram): handle Grammy HttpError network failures (#3815) (#7195) * fix(telegram): handle Grammy HttpError network failures (#3815) Grammy wraps fetch errors in an .error property (not .cause). Added .error traversal to collectErrorCandidates in network-errors.ts. Registered scoped unhandled rejection handler in monitorTelegramProvider to catch network errors that escape the polling loop (e.g., from setMyCommands during bot setup). Handler is unregistered when the provider stops. * fix(telegram): address review feedback for Grammy HttpError handling - Gate .error traversal on HttpError name to avoid widening search graph - Use runtime logger instead of console.warn for consistency - Add isGrammyHttpError check to scope unhandled rejection handler - Consolidate isNetworkRelatedError into isRecoverableTelegramNetworkError - Add 'timeout' to recoverable message snippets for full coverage * CI: label maintainer issues * Docs i18n: harden doc-mode pipeline * Docs: add zh-CN translations * Docs: fix zh-CN template time wording What: replace <2/<30 text in zh-CN AGENTS template with safe wording Why: avoid MDX parse errors during docs build Tests: not run (doc text change) * docs: add changelog for zh-CN translations (#6619) (thanks @joshp123) * Docs: fix zh-CN ClawHub link What: wrap clawhub.com in an explicit URL link in zh-CN skills doc Why: avoid Mintlify broken-link parser treating trailing punctuation as part of the URL Tests: not run (doc text change) * Docs: use explicit ClawHub markdown link What: switch clawhub.com reference to explicit Markdown link syntax Why: MDX parser rejects angle-bracket autolinks Tests: not run (doc text change) * Docs i18n: tune zh-CN prompt + glossary What: enforce zh-CN tone (你/你的), Skills/local loopback/Tailscale terms, Gateway网关 Why: keep future translation output consistent with issue feedback Tests: not run (prompt/glossary change) * Docs: normalize zh-CN terminology + tone What: switch to 你/你的 tone; standardize Skills/Gateway网关/local loopback/私信 wording Why: align zh-CN docs with issue 6995 feedback + idiomatic tech style Tests: pnpm docs:build * Tests: stub SSRF DNS pinning (#6619) (thanks @joshp123) * fix(webchat): respect user scroll position during streaming and refresh - Increase near-bottom threshold from 200px to 450px so one long message doesn't falsely register as 'near bottom' - Make force=true only override on initial load (chatHasAutoScrolled=false), not on subsequent refreshChat() calls - refreshChat() no longer passes force=true to scheduleChatScroll - Add chatNewMessagesBelow flag for future 'scroll to bottom' button UI - Clear chatNewMessagesBelow when user scrolls back to bottom - Add 13 unit tests covering threshold, force behavior, streaming, and reset * fix: address review feedback — retryDelay uses effectiveForce, default overrides param, @state() on chatNewMessagesBelow * Docs: expand zh-Hans nav and fix assets * Docs: expand zh-Hans nav (#7242) (thanks @joshp123) * fix(ui): add core state and logic for scroll control * feat(ui): add new messages indicator button * docs: update changelog for PR #7226 * chore: fix formatting and CI * iOS: wire node services and tests * iOS: stabilize talk mode tests * Gateway: fix node invoke receive loop * Gateway: wait for snapshot before connect * Agents: add nodes invoke action * iOS: fix node notify and identity * iOS: streamline notify timeouts * iOS: add write commands for contacts/calendar/reminders * iOS: add push-to-talk node commands * iOS: pause voice wake during PTT * iOS: add PTT once/cancel * Gateway: add PTT chat + nodes CLI * iOS: wire node commands and incremental TTS * iOS: update onboarding and gateway UI * Core: update shared gateway models * iOS: improve gateway auto-connect and voice permissions * Docs: add zh-CN landing notice + AI image * Docs: add zh-CN landing note (#7303) (thanks @joshp123) * Docs: expand zh-CN landing note * Revert "iOS: wire node services and tests" This reverts commit 7b0a0f3dace575c33dafb61d4a13cdef4dd0d64e. * Revert "Core: update shared gateway models" This reverts commit 37eaca719a68aa1ad9dcbfe83c8a20e88bb6951a. * fix: resolve check errors in nodes-tool and commands-ptt * feat(config): default thinking for sessions_spawn subagents (#7372) * feat(config): add subagent default thinking * fix: accept config subagents.thinking + stabilize test mocks (#7372) (thanks @tyler6204) * fix: use findLast instead of clearAllMocks in test (#7372) * fix: correct test assertions for tool result structure (#7372) * fix: remove unnecessary type assertion after rebase * fix: validate AbortSignal instances before calling AbortSignal.any() Fixes #7269 * refactor: use structural typing instead of instanceof for AbortSignal check Address P1 review feedback from Greptile: instanceof AbortSignal may be unreliable across different realms (VM, iframe, etc.) where the AbortSignal constructor may differ. Use structural typing (checking for aborted property and addEventListener method) for more robust cross-realm compatibility. * fix: validate AbortSignal instances before calling AbortSignal.any() (#7277) (thanks @Elarwei001) * fix(tools): ensure file_path alias passes validation in read/write tools (#7451) Co-authored-by: lotusfall <[email protected]> * fix: skip audio files from text extraction to prevent binary processing (#7475) * fix: skip audio files from text extraction early Audio files should not be processed through extractFileBlocks for text extraction - they are handled by the dedicated audio transcription capability (STT). Previously, audio files were only skipped if they didn't "look like text" (looksLikeUtf8Text check). This caused issues where some audio binary data (e.g., long Telegram voice messages) could accidentally pass the heuristic check and get processed as text content. This fix: 1. Adds audio to the early skip alongside image/video (more efficient) 2. Removes the redundant secondary check that had the flawed condition Fixes audio binary being incorrectly processed as text in Telegram and other platforms. * Media: skip binary media in file extraction (#7475) (thanks @AlexZhangji) --------- Co-authored-by: Shakker <[email protected]> * fix(telegram): recover from grammY "timed out" long-poll errors (#7239) grammY getUpdates returns "Request to getUpdates timed out after 500 seconds" but RECOVERABLE_MESSAGE_SNIPPETS only had "timeout". Since "timed out".includes("timeout") === false, the error was not classified as recoverable, causing the polling loop to exit permanently. Add "timed out" to RECOVERABLE_MESSAGE_SNIPPETS so the polling loop retries instead of dying silently. Fixes #7239 Fixes #7255 * fix(telegram): recover from grammY long-poll timeouts (#7466) (thanks @macmimi23) * Docs: fix compatibility shim note * Agent: repair malformed tool calls and session files * Changelog: note tool call repair * Agents: fix lint in tool-call sanitizers * Agents: harden session file repair * Agents: flush pending tool results on drop * Docs: simplify transcript hygiene scope * fix: repair malformed tool calls and session transcripts (#7473) (thanks @justinhuangcode) * chore: Update deps. * fix(slack): fail closed on slash command channel type lookup * fix: harden exec allowlist parsing * fix(gateway): require shared auth before device bypass * style(ui): format resizable divider * chore: Fix CI. * Docs: clarify whats new FAQ heading (#7394) * feat(ui): add Agents dashboard * Security: new openclaw-system-admin skill + bootstrap audit * Security: rename openclaw-system-admin skill to healthcheck * Security: remove openclaw-system-admin skill path * Security: refine healthcheck workflow * Security: healthcheck skill (#7641) (thanks @Takhoffman) * chore: fix CI * chore: fix formatting * Security: tune bootstrap healthcheck prompt + healthcheck wording * chore: fix formatting * CLI: restore terminal state on exit * Onboarding: keep TUI flow exclusive * fix: error handling in restore failure reporting * feat (memory): Implement new (opt-in) QMD memory backend * Make memory more resilient to failure * Add more tests; make fall back more resilient and visible * Fix build errors * fix(qmd): use XDG dirs for qmd home; drop ollama docs * fix(memory-qmd): write XDG index.yml + legacy compat * fix(memory-qmd): create collections via qmd CLI (no YAML) * Add how to trigger model downloads for qmd in documentation * fix(memory/qmd): throttle embed + citations auto + restore --force * Tests: use OPENCLAW_STATE_DIR in qmd manager * Docs: align QMD state dir with OpenClaw * Memory: parse quoted qmd command * Memory: fix QMD scope channel parsing * Memory: harden QMD memory_get path checks * Memory: clamp QMD citations to injected budget * Tests: cover QMD scope, reads, and citation clamp * QMD: use OpenClaw config types * Fix build regressions after merge * Lint: add braces for single-line ifs * fix: make QMD cache key deterministic * fix: derive citations chat type via session parser * chore: apply formatter * chore: restore OpenClaw branding * chore: fix lint warnings * chore: oxfmt * fix: restore session_status and CLI examples * chore: oxfmt * fix: restore safety + session_status hints * chore: oxfmt * fix: changelog entry for QMD memory (#3160) (thanks @vignesh07) * docs: finish renaming memory state dir references * CLI: cache shell completion scripts * Install: cache completion scripts on install/update * Onboarding: drop completion prompt * chore: update changelog for completion caching * chore: Migrate to tsdown, speed up JS bundling by ~10x (thanks @hyf0). The previous migration to tsdown was reverted because it caused a ~20x slowdown when running OpenClaw from the repo. @hyf0 investigated and found that simply renaming the `dist` folder also caused the same slowdown. It turns out the Plugin script loader has a bunch of voodoo vibe logic to determine if it should load files from source and compile them, or if it should load them from dist. When building with tsdown, the filesystem layout is different (bundled), and so some files weren't in the right location, and the Plugin script loader decided to compile source files from scratch using Jiti. The new implementation uses tsdown to embed `NODE_ENV: 'production'`, which we now use to determine if we are running OpenClaw from a "production environmen" (ie. from dist). This removes the slop in favor of a deterministic toggle, and doesn't rely on directory names or similar. There is some code reaching into `dist` to load specific modules, primarily in the voice-call extension, which I simplified into loading an "officially" exported `extensionAPI.js` file. With tsdown, entry points need to be explicitly configured, so we should be able to avoid sloppy code reaching into internals from now on. This might break some existing users, but if it does, it's because they were using "private" APIs. * fix: CI: We no longer need to test the tsc build with Bun, we are always using `tsdown` to build now. * fix: Remove `tsconfig.oxlint.json` AGAIN. * feat: remove slop. * chore: clean up git hooks and actually install them again. * fix: Fix Mac app build step. * chore: Fix all TypeScript errors in `ui`. * chore: Switch to `NodeNext` for `module`/`moduleResolution` in `ui`. * chore: Merge tsconfigs, typecheck `ui` as part of `pnpm tsgo` locally and on CI. * Skills: refine healthcheck guidance * fix(voice-call): harden inbound policy * fix(matrix): harden allowlists * fix: harden Windows exec allowlist * docs: Update information architecture for OpenClaw docs (#7622) * docs: restructure navigation into 5 tabs for better IA * dedupe redirects * use 8 tabs * add missing /index extensions * update zh navigation * remove `default: true` and rearrange languages * add missing redirects * format:fix * docs: update IA tabs + restore /images redirect (#7622) (thanks @ethanpalm) --------- Co-authored-by: Peter Steinberger <[email protected]> * fix: restore OpenClaw docs/source links in system prompt * chore: prepare 2026.2.2 release * fix(ui): fix web UI after tsdown migration and typing changes * fix(skills): warn when bundled dir missing * fix(ui): refresh agent files after external edits * fix(ui): note agent file refresh in changelog * Docs: refresh zh-CN translations + i18n guidance What: - update zh-CN glossary, translation prompt, and TM - regenerate zh-CN docs and apply targeted fixes - add zh-CN AGENTS guidance for translation pipeline Why: - address zh-CN terminology and spacing feedback from #6995 Tests: - pnpm build && pnpm check && pnpm test * Docs: update zh-CN translations and pipeline What: - update zh-CN glossary, TM, and translator prompt - regenerate zh-CN docs and apply targeted fixes - add zh-CN AGENTS pipeline guidance Why: - address terminology/spacing feedback from #6995 Tests: - pnpm build && pnpm check && pnpm test * Docs(zh-CN): add AGENTS translation workflow * Channels: add Feishu/Lark support * Channels: finish Feishu/Lark integration * fix: harden control ui framing + ws origin * fix(approvals): gate /approve by gateway scopes * test: add /approve gateway scope coverage (#1) (thanks @mitsuhiko) * test: reset /approve mock per test (#1) (thanks @mitsuhiko) * chore: prep 2026.2.2 docs/release checks * chore: update appcast for 2026.2.2 * chore: add mac dSYM zip to release artifacts * fix: use build-info for version fallback * Docs: guard zh-CN i18n workflow What: - document zh-CN docs pipeline and generated-doc guardrails - note Discord escalation when the pipeline drags Why: - prevent accidental edits to generated translations Tests: - pnpm build - pnpm check - pnpm test Co-authored-by: Josh Palmer <[email protected]> * chore: bump version to 2026.2.2-1 * fix: improve build-info resolution for commit/version * Docs: drop healthcheck from bootstrap * fix(update): honor update.channel for update.run * fix: enforce Nextcloud Talk allowlist by user id * feat: add configurable web_fetch maxChars cap * fix(matrix): require unique allowlist matches in wizard * fix: add legacy daemon-cli shim for updates * iMessage: promote BlueBubbles and refresh docs/skills (#8415) * feat: Make BlueBubbles the primary iMessage integration - Remove old imsg skill (skills/imsg/SKILL.md) - Create new BlueBubbles skill (skills/bluebubbles/SKILL.md) with message tool examples - Add keep-alive script documentation for VM/headless setups to docs/channels/bluebubbles.md - AppleScript that pokes Messages.app every 5 minutes - LaunchAgent configuration for automatic execution - Prevents Messages.app from going idle in VM environments - Update all documentation to prioritize BlueBubbles over legacy imsg: - Mark imsg channel as legacy throughout docs - Update README.md channel lists - Update wizard, hubs, pairing, and index docs - Update FAQ to recommend BlueBubbles for iMessage - Update RPC docs to note imsg as legacy pattern - Update Chinese documentation (zh-CN) - Replace imsg examples with generic macOS skill examples where appropriate BlueBubbles is now the recommended first-class iMessage integration, with the legacy imsg integration marked for potential future removal. * refactor: Update import paths and improve code formatting - Adjusted import paths in session-status-tool.ts, whatsapp-heartbeat.ts, and heartbeat-runner.ts for consistency. - Reformatted code for better readability by aligning and grouping related imports and function parameters. - Enhanced error messages and conditional checks for clarity in heartbeat-runner.ts. * skills: restore imsg skill and align bluebubbles skill * docs: update FAQ for clarity and formatting - Adjusted the formatting of the FAQ section to ensure consistent bullet point alignment. - No content changes were made, only formatting improvements for better readability. * style: oxfmt touched files * fix: preserve BlueBubbles developer reference (#8415) (thanks @tyler6204) * refactor: remove unnecessary blank line in policy test file * chore: bump version to 2026.2.3 * feat: add new messages indicator style for chat interface - Introduced a floating pill element above the compose area to indicate new messages. - Styled the indicator with hover effects and responsive design for better user interaction. * Telegram: add inline button model selection for /models and /model commands * Telegram: fix model button review issues - Add currentModel to callback handler for checkmark display - Add 64-byte callback_data limit protection (skip long model IDs) - Add tests for large model lists and callback_data limits * fix: honor telegram model overrides in buttons (#8193) (thanks @gildo) * chore: update changelog for #8193 (thanks @gildo) * feat(discord): add set-presence action for bot activity and status Bridge the agent tools layer to the Discord gateway WebSocket via a new gateway registry, allowing agents to set the bot's activity and online status. Supports playing, streaming, listening, watching, custom, and competing activity types. Custom type uses activityState as the sidebar text; other types show activityName in the sidebar and activityState in the flyout. Opt-in via channels.discord.actions.presence (default false). Co-Authored-By: Claude Opus 4.5 <[email protected]> * Address PR feedback * Make openclaw consistent in this file (#8533) Co-authored-by: stephenchen2025 <[email protected]> * style: update chat new-messages button * feat: add support for Moonshot API key for China endpoint * fix: keep Moonshot CN base URL in onboarding (#7180) (thanks @waynelwz) * docs(skills): split tmux send-keys for TUI (#7737) * docs(skills): split tmux send-keys for TUI * docs(skills): soften TUI send-keys wording --------- Co-authored-by: wangnov <[email protected]> * docs: note tmux send-keys TUI guidance (#7737) (thanks @Wangnov) * fix(control-ui): resolve header logo when gateway.controlUi.basePath is set (#7178) * fix(control-ui): resolve header logo when gateway.controlUi.basePath is set * refactor(control-ui): header logo under basePath; normalize logo URL with normalizeBasePath * docs: add changelog for #7178 (thanks @Yeom-JinHo) * docs: document secure DM mode preset (#7872) * docs: document secure DM mode preset * fix: resolve merge conflict in resizable-divider * fix(security): separate untrusted channel metadata from system prompt (thanks @KonstantinMirin) * docs: update Feishu plugin docs * feat: Add Docs Chat Widget with RAG-powered Q&A (#7908) * feat: add docs chat prototype and related scripts - Introduced a minimal documentation chatbot that builds a search index from markdown files and serves responses via an API. - Added scripts for building the index and serving the chat API. - Updated package.json with new commands for chat index building and serving. - Created a new Vercel configuration file for deployment. - Added a README for the docs chat prototype detailing usage and integration. * feat: enhance docs chat with vector-based RAG pipeline - Added vector index building and serving capabilities to the docs chat. - Introduced new scripts for generating embeddings and serving the chat API using vector search. - Updated package.json with new commands for vector index operations. - Enhanced README with instructions for the new RAG pipeline and legacy keyword pipeline. - Removed outdated Vercel configuration file. * feat: enhance chat widget with markdown rendering and style updates - Integrated dynamic loading of markdown rendering for chat responses. - Implemented a fallback for markdown rendering to ensure consistent display. - Updated CSS variables for improved theming and visual consistency. - Enhanced chat bubble and input styles for better user experience. - Added new styles for markdown content in chat bubbles, including code blocks and lists. * feat: add copy buttons to chat widget for enhanced user interaction - Implemented copy buttons for chat responses and code blocks in the chat widget. - Updated CSS styles for improved visibility and interaction of copy buttons. - Adjusted textarea height for better user experience. - Enhanced functionality to allow users to easily copy text from chat bubbles and code snippets. * feat: update chat widget styles for improved user experience - Changed accent color for better visibility. - Enhanced preformatted text styles for code blocks, including padding and word wrapping. - Adjusted positioning and styles of copy buttons for chat responses and code snippets. - Improved hover effects for copy buttons to enhance interactivity. * feat: enhance chat widget styles for better responsiveness and scrollbar design - Updated chat panel dimensions for improved adaptability on various screen sizes. - Added custom scrollbar styles for better aesthetics and usability. - Adjusted chat bubble styles for enhanced visibility and interaction. - Improved layout for expanded chat widget on smaller screens. * feat: refine chat widget code block styles and copy button functionality - Adjusted padding and margin for preformatted text in chat responses for better visual consistency. - Introduced a compact style for single-line code blocks to enhance layout. - Updated copy button logic to skip short code blocks, improving user experience when copying code snippets. * feat: add resize handle functionality to chat widget for adjustable panel width - Implemented a draggable resize handle for the chat widget's sidebar, allowing users to adjust the panel width. - Added CSS styles for the resize handle, including hover effects and responsive behavior. - Integrated drag-to-resize logic to maintain user-set width across interactions. - Ensured the panel resets to default width when closed, enhancing user experience. * feat: implement rate limiting and error handling in chat API - Added rate limiting functionality to the chat API, allowing a maximum number of requests per IP within a specified time window. - Implemented error handling for rate limit exceeded responses, including appropriate headers and retry instructions. - Enhanced error handling for other API errors, providing user-friendly messages for various failure scenarios. - Updated README to include new environment variables for rate limiting configuration. * feat: integrate Upstash Vector for enhanced document retrieval in chat API - Implemented Upstash Vector as a cloud-based storage solution for document chunks, replacing the local LanceDB option. - Added auto-detection of storage mode based on environment variables for seamless integration. - Updated the chat API to utilize the new retrieval mechanism, enhancing response accuracy and performance. - Enhanced README with setup instructions for Upstash and updated environment variable requirements. - Introduced new scripts and configurations for managing the vector index and API interactions. * feat: add create-markdown-preview.js for markdown rendering - Introduced a new script for framework-agnostic HTML rendering of markdown content. - The script includes various parsing functions to handle different markdown elements. - Updated the chat widget to load the vendored version of @create-markdown/preview for improved markdown rendering. * docs: update README for Upstash Vector index setup and environment variables - Enhanced instructions for creating a Vector index in Upstash, including detailed settings and important notes. - Clarified environment variable requirements for both Upstash and LanceDB modes. - Improved formatting and organization of setup steps for better readability. - Added health check and API endpoint details for clearer usage guidance. * feat: add TRUST_PROXY environment variable for IP address handling - Introduced the TRUST_PROXY variable to control the trust of X-Forwarded-For headers when behind a reverse proxy. - Updated the README to document the new environment variable and its default value. - Enhanced the getClientIP function to conditionally trust proxy headers based on the TRUST_PROXY setting. * feat: add ALLOWED_ORIGINS environment variable for CORS configuration - Introduced the ALLOWED_ORIGINS variable to specify allowed origins for CORS, enhancing security and flexibility. - Updated the README to document the new environment variable and its usage. - Refactored CORS handling in the server code to utilize the ALLOWED_ORIGINS setting for dynamic origin control. * fix: ensure complete markdown rendering in chat widget - Added logic to flush any remaining buffered bytes from the decoder, ensuring that all text is rendered correctly in the assistant bubble. - Updated the assistant bubble's innerHTML to reflect the complete markdown content after streaming completes. * feat: enhance DocsStore with improved vector handling and similarity conversion - Added a constant for the distance metric used in vector searches, clarifying the assumption of L2 distance. - Updated the createTable method to ensure all chunk properties are correctly mapped during table creation. - Improved the similarity score calculation by providing a clear explanation of the conversion from L2 distance, ensuring accurate ranking of results. * chore: fix code formatting * Revert "chore: fix code formatting" This reverts commit 6721f5b0b7bf60b76c519ccadfa41742f19ecf87. * chore: format code for improved readability - Reformatted code in serve.ts to enhance readability by adjusting indentation and line breaks. - Ensured consistent style for function return types and object properties throughout the file. * feat: Update API URL selection logic in chat widget - Enhanced the API URL configuration to prioritize explicit settings, defaulting to localhost for development and using a production URL otherwise. - Improved clarity in the code by adding comments to explain the logic behind the API URL selection. * chore: Update documentation structure for improved organization - Changed the path for the "Start Here" page to "start/index" for better clarity. - Reformatted the "Web & Interfaces" and "Help" groups to use multi-line arrays for improved readability. * feat: Enhance markdown preview integration and improve chat widget asset loading - Wrapped the markdown preview functionality in an IIFE to expose a global API for easier integration. - Updated the chat widget to load the markdown preview library dynamically, checking for existing instances to avoid duplicate loads. - Adjusted asset paths in the chat widget to ensure correct loading based on the environment (local or production). - Added CORS headers in the Vercel configuration for improved API accessibility. * fix: Update chat API URL to include '/api' for correct endpoint access - Modified the chat configuration and widget files to append '/api' to the API URL, ensuring proper endpoint usage in production and local environments. * refactor: Simplify docs-chat configuration and remove unused scripts - Removed outdated scripts and configurations related to the docs-chat feature, including build and serve scripts, as well as the associated package.json and README files. - Streamlined the API URL configuration in the chat widget for better clarity and maintainability. - Updated the package.json to remove unnecessary scripts related to the now-deleted functionality. * refactor: Update documentation structure for improved clarity - Changed the path for the "Start Here" page from "start/index" to "index" to enhance navigation and organization within the documentation. * chore: Remove unused dependencies from package.json and pnpm-lock.yaml - Deleted `@lancedb/lancedb`, `@upstash/vector`, and `openai` from both package.json and pnpm-lock.yaml to streamline the project and reduce bloat. * chore: Clean up .gitignore by removing obsolete entries - Deleted unused entries related to the docs-chat vector database from .gitignore to maintain a cleaner configuration. * chore: Remove deprecated chat configuration and markdown preview script - Deleted the `create-markdown-preview.js` script and the `docs-chat-config.js` file to eliminate unused assets and streamline the project. - Updated the `docs-chat-widget.js` to directly reference the markdown library from a CDN, enhancing maintainability. * chore: Update markdown rendering in chat widget to use marked library - Replaced the deprecated `create-markdown-preview` library with the `marked` library for markdown rendering. - Adjusted the script loading mechanism to fetch `marked` from a CDN, improving performance and maintainability. - Enhanced the markdown rendering function to ensure security by disabling HTML pass-through and opening links in new tabs. * Delete docs/start/index.md * fix: harden voice-call webhook verification * fix(cron): fix timeout, add timestamp validation, enable file sync Fixes #7667 Task 1: Fix cron operation timeouts - Increase default gateway tool timeout from 10s to 30s - Increase cron-specific tool timeout to 60s - Increase CLI default timeout from 10s to 30s - Prevents timeouts when gateway is busy with long-running jobs Task 2: Add timestamp validation - New validateScheduleTimestamp() function in validate-timestamp.ts - Rejects atMs timestamps more than 1 minute in the past - Rejects atMs timestamps more than 10 years in the future - Applied to both cron.add and cron.update operations - Provides helpful error messages with current time and offset Task 3: Enable file sync for manual edits - Track file modification time (storeFileMtimeMs) in CronServiceState - Check file mtime in ensureLoaded() and reload if changed - Recompute next runs after reload to maintain accuracy - Update mtime after persist() to prevent reload loop - Dashboard now picks up manual edits to ~/.openclaw/cron/jobs.json * feat(cron): introduce delivery modes for isolated jobs - Added support for new delivery modes in cron jobs: `announce`, `deliver`, and `none`. - Updated documentation to reflect changes in delivery options and usage examples. - Enhanced the cron job schema to include delivery configuration. - Refactored related CLI commands and UI components to accommodate the new delivery settings. - Improved handling of legacy delivery fields for backward compatibility. This update allows users to choose how output from isolated jobs is delivered, enhancing flexibility in job management. * feat(cron): default isolated jobs to announce delivery and enhance scheduling options - Updated isolated cron jobs to default to `announce` delivery mode, improving user experience. - Enhanced scheduling options to accept ISO 8601 timestamps for `schedule.at`, while still supporting epoch milliseconds. - Refined documentation to clarify delivery modes and scheduling formats. - Adjusted related CLI commands and UI components to reflect these changes, ensuring consistency across the platform. - Improved handling of legacy delivery fields for backward compatibility. This update streamlines the configuration of isolated jobs, making it easier for users to manage job outputs and schedules. * feat(cron): enhance one-shot job behavior and CLI options - Default one-shot jobs to delete after success, improving job management. - Introduced `--keep-after-run` CLI option to allow users to retain one-shot jobs post-execution. - Updated documentation to clarify default behaviors and new options for one-shot jobs. - Adjusted cron job creation logic to ensure consistent handling of delete options. - Enhanced tests to validate new behaviors and ensure reliability. This update streamlines the handling of one-shot jobs, providing users with more control over job persistence and execution outcomes. * feat(cron): enhance delivery modes and job configuration - Updated isolated cron jobs to support new delivery modes: `announce` and `none`, improving output management. - Refactored job configuration to remove legacy fields and streamline delivery settings. - Enhanced the `CronJobEditor` UI to reflect changes in delivery options, including a new segmented control for delivery mode selection. - Updated documentation to clarify the new delivery configurations and their implications for job execution. - Improved tests to validate the new delivery behavior and ensure backward compatibility with legacy settings. This update provides users with greater flexibility in managing how isolated jobs deliver their outputs, enhancing overall usability and clarity in job configurations. * feat(cron): set default enabled state for cron jobs - Added logic to default the `enabled` property to `true` if not explicitly set as a boolean in the cron job input. - Updated job creation and store functions to ensure consistent handling of the `enabled` state across the application. - Enhanced input normalization to improve job configuration reliability. This update ensures that cron jobs are enabled by default, enhancing user experience and reducing potential misconfigurations. * refactor(cron): update delivery instructions for isolated agent - Revised the delivery instructions in the isolated agent's command body to clarify that summaries should be returned as plain text and will be delivered by the main agent. - Removed the previous directive regarding messaging tools to streamline communication guidelines. This change enhances clarity in the delivery process for isolated agent tasks. * feat(cron): enhance delivery handling and testing for isolated jobs - Introduced new properties for explicit message targeting and message tool disabling in the EmbeddedRunAttemptParams type. - Updated cron job tests to validate best-effort delivery behavior and handling of delivery failures. - Added logic to clear delivery settings when switching session targets in cron jobs. - Improved the resolution of delivery failures and best-effort logic in the isolated agent's run function. This update enhances the flexibility and reliability of delivery mechanisms in isolated cron jobs, ensuring better handling of message delivery scenarios. * refactor(cron): improve delivery configuration handling in CronJobEditor and CLI - Enhanced the delivery configuration logic in CronJobEditor to explicitly set the bestEffort property based on job settings. - Refactored the CLI command to streamline delivery object creation, ensuring proper handling of optional fields like channel and to. - Improved code readability and maintainability by restructuring delivery assignment logic. This update clarifies the delivery configuration process, enhancing the reliability of job settings in both the editor and CLI. * feat(cron): enhance legacy delivery handling in job patches - Introduced logic to map legacy payload delivery updates onto the delivery object for `agentTurn` jobs, ensuring backward compatibility with legacy clients. - Added tests to validate the correct application of legacy delivery settings in job patches, improving reliability in job configuration. - Refactored delivery handling functions to streamline the merging of legacy delivery fields into the current job structure. This update enhances the flexibility of delivery configurations, ensuring that legacy settings are properly handled in the context of new job patches. * fix(cron): fix test failures and regenerate protocol files - Add forceReload option to ensureLoaded to avoid stat I/O in normal paths while still detecting cross-service writes in the timer path - Post isolated job summary back to main session (restores the old isolation.postToMainPrefix behavior via delivery model) - Update legacy migration tests to check delivery.channel instead of payload.channel (normalization now moves delivery fields to top-level) - Remove legacy deliver/channel/to/bestEffortDeliver from payload schema - Update protocol conformance test for delivery modes - Regenerate GatewayModels.swift (isolation -> delivery) * UI: handle future timestamps in formatAgo * Changelog: move cron entries to 2026.2.3 * fix: cron announce delivery path (#8540) (thanks @tyler6204) * Telegram: use Grammy types directly, add typed Probe/Audit to plugin interface (#8403) * Telegram: replace duplicated types with Grammy imports, add Probe/Audit generics to plugin interface * Telegram: remove legacy forward metadata (deprecated in Bot API 7.0), simplify required-field checks * Telegram: clean up remaining legacy references and unnecessary casts * Telegram: keep RequestInit parameter type in proxy fetch (addresses review feedback) * Telegram: add exhaustiveness guard to resolveForwardOrigin switch * fix(telegram): include forward_from_chat metadata in forwarded message context (#8133) Extract missing metadata from forwarded Telegram messages: - Add fromChatType to TelegramForwardedContext, capturing the original chat type (channel/supergroup/group) from forward_from_chat.type and forward_origin.chat/sender_chat.type - Add fromMessageId to capture the original message ID from channel forwards - Read author_signature from forward_origin objects (modern API), preferring it over the deprecated forward_signature field - Pass ForwardedFromChatType and ForwardedFromMessageId through to the inbound context payload - Add test coverage for forward_origin channel/chat types, including author_signature extraction and fromChatType propagation * fix: trim legacy signature fallback, type fromChatType as union * fix: telegram forward metadata + cron delivery guard (#8392) (thanks @Glucksberg) * fix(imessage): unify timeout configuration with configurable probeTimeoutMs - Add probeTimeoutMs config option to channels.imessage - Export DEFAULT_IMESSAGE_PROBE_TIMEOUT_MS constant (10s) from probe.ts - Propagate timeout config through all iMessage probe/RPC operations - Fix hardcoded 2000ms timeouts that were too short for SSH connections Closes: timeout issues when using SSH wrapper scripts (imsg-ssh) * fix: address review comments - Use optional timeoutMs parameter (undefined = use config/default) - Extract DEFAULT_IMESSAGE_PROBE_TIMEOUT_MS to shared constants.ts - Import constant in client.ts instead of hardcoding - Re-export constant from probe.ts for backwards compatibility * fix(imessage): detect self-chat echoes to prevent infinite loops (#8680) * fix: align proxy fetch typing * feat: add cloudflare ai gateway provider * fix: force reload cron store * Revert "feat: Add Docs Chat Widget with RAG-powered Q&A (#7908)" (#8834) This reverts commit fa4b28d7af7464b07271bfef6c028e4135548f44. * fix(web ui): agent model selection * Docs: landing page revamp (#8885) * Docs: refresh landing page * Docs: add landing page companion pages * Docs: drop legacy Jekyll assets * Docs: remove legacy terminal css test * Docs: restore terminal css assets * Docs: remove terminal css assets * fix(app-render): handle optional model in renderApp function * chore: replace landpr prompt with end-to-end landing workflow (#8916) * 🤖 docs: mirror landing revamp for zh-CN What: - add zh-CN versions of landing revamp pages (features, quickstart, docs directory, network model, credits) - refresh zh-CN index and hubs, plus glossary entries Why: - keep Chinese docs aligned with the new English landing experience - ensure navigation surfaces the new entry points Tests: - pnpm build && pnpm check && pnpm test * 🤖 docs: note zh-CN landing revamp (#8994) (thanks @joshp123) What: - add changelog entry for the zh-CN landing revamp docs Why: - record the doc update and thank the contributor Tests: - pnpm lint && pnpm build && pnpm test * feat: add shell completion installation prompt to CLI update command * feat: add shell completion test script for installation verification * completion: export cache utilities and require cached file for installation - Export `resolveCompletionCachePath` and `completionCacheExists` for external use - Update `installCompletion` to require cache existence (never use slow dynamic pattern) - Add `usesSlowDynamicCompletion` to detect old `source <(...)` patterns - Add `getShellProfilePath` helper for consistent profile path resolution - Update `formatCompletionSourceLine` to always use cached file * doctor: add shell completion check module - Add `checkShellCompletionStatus` to get profile/cache/slow-pattern status - Add `ensureCompletionCacheExists` for silent cache regeneration - Add `doctorShellCompletion` to check and fix completion issues: - Auto-upgrade old slow dynamic patterns to cached version - Auto-regenerate cache if profile exists but cache is missing - Prompt to install if no completion is configured * doctor: integrate shell completion check into doctor command - Import and call `doctorShellCompletion` during doctor run - Checks/fixes completion issues before gateway health check * update: use shared completion helpers for shell completion setup - Replace inline completion logic with `checkShellCompletionStatus` and `ensureCompletionCacheExists` - Auto-upgrade old slow dynamic patterns silently during update - Auto-regenerate cache if profile exists but cache is missing - Prompt to install if no completion is configured * onboard: use shared completion helpers for shell completion setup - Replace inline completion logic with `checkShellCompletionStatus` and `ensureCompletionCacheExists` - Auto-upgrade old slow dynamic patterns silently during onboarding - Auto-regenerate cache if profile exists but cache is missing - Prompt to install if no completion is configured * scripts: update test-shell-completion to use shared helpers - Use `checkShellCompletionStatus` and `ensureCompletionCacheExists` from doctor-completion - Display "Uses slow pattern" status in output - Simulate doctor/update/onboard behavior for all completion scenarios - Remove duplicated utility functions * changelog: add shell completion auto-fix entry * feat: per-channel responsePrefix override (#9001) * feat: per-channel responsePrefix override Add responsePrefix field to all channel config types and Zod schemas, enabling per-channel and per-account outbound response prefix overrides. Resolution cascade (most specific wins): L1: channels.<ch>.accounts.<id>.responsePrefix L2: channels.<ch>.responsePrefix L3: (reserved for channels.defaults) L4: messages.responsePrefix (existing global) Semantics: - undefined -> inherit from parent level - empty string -> explicitly no prefix (stops cascade) - "auto" -> derive [identity.name] from routed agent Changes: - Core logic: resolveResponsePrefix() in identity.ts accepts optional channel/accountId and walks the cascade - resolveEffectiveMessagesConfig() passes channel context through - Types: responsePrefix added to WhatsApp, Telegram, Discord, Slack, Signal, iMessage, Google Chat, MS Teams, Feishu, BlueBubbles configs - Zod schemas: responsePrefix added for config validation - All channel handlers wired: telegram, discord, slack, signal, imessage, line, heartbeat runner, route-reply, native commands - 23 new tests covering backward compat, channel/account levels, full cascade, auto keyword, empty string stops, unknown fallthrough Fully backward compatible - no existing config is affected. Fixes #8857 * fix: address CI lint + review feedback - Replace Record<string, any> with proper typed helpers (no-explicit-any) - Add curly braces to single-line if returns (eslint curly) - Fix JSDoc: 'Per-channel' → 'channel/account' on shared config types - Extract getChannelConfig() helper for type-safe dynamic key access * fix: finish responsePrefix overrides (#9001) (thanks @mudrii) * fix: normalize prefix wiring and types (#9001) (thanks @mudrii) --------- Co-authored-by: Gustavo Madeira Santana <[email protected]> * Discord: allow disabling thread starter context * feat(heartbeat): add accountId config option for multi-agent routing (#8702) * feat(heartbeat): add accountId config option for multi-agent routing Add optional accountId field to heartbeat configuration, allowing multi-agent setups to explicitly specify which Telegram account should be used for heartbeat delivery. Previously, heartbeat delivery would use the accountId from the session's deliveryContext. When a session had no prior conversation history, heartbeats would default to the first/primary account instead of the agent's intended bot. Changes: - Add accountId to HeartbeatSchema (zod-schema.agent-runtime.ts) - Use heartbeat.accountId with fallback to session accountId (targets.ts) Backward compatible: if accountId is not specified, behavior is unchanged. Closes #8695 * fix: improve heartbeat accountId routing (#8702) (thanks @lsh411) * fix: harden heartbeat accountId routing (#8702) (thanks @lsh411) * fix: expose heartbeat accountId in status (#8702) (thanks @lsh411) * chore: format status + heartbeat tests (#8702) (thanks @lsh411) --------- Co-authored-by: m1 16 512 <[email protected]> Co-authored-by: Gustavo Madeira Santana <[email protected]> * TUI/Gateway: fix pi streaming + tool routing + model display + msg updating (#8432) * TUI/Gateway: fix pi streaming + tool routing * Tests: clarify verbose tool output expectation * fix: avoid seq gaps for targeted tool events (#8432) (thanks @gumadeiras) * Telegram: remove @ts-nocheck from bot.ts, fix duplicate error handler, harden sticker caching (#9077) * Telegram: remove @ts-nocheck from bot.ts and bot-message-dispatch.ts - bot/types.ts: TelegramContext.me uses UserFromGetMe (Grammy) instead of manual inline type - bot.ts: remove 6 unsafe casts (as any, as unknown, as object), use Grammy types directly - bot.ts: remove dead message_thread_id access on reactions (not in Telegram Bot API) - bot.ts: remove resolveThreadSessionKeys import (no longer needed for reactions) - bot-message-dispatch.ts: replace ': any' with DispatchTelegramMessageParams type - bot-message-dispatch.ts: add sticker.fileId guard before cache access - bot.test.ts: update reaction tests, remove dead DM thread-reaction test * Telegram: remove duplicate bot.catch handler (only the last one runs in Grammy) * Telegram: remove @ts-nocheck from bot.ts, fix duplicate error handler, harden sticker caching (#9077) * Security: Prevent gateway credential exfiltration via URL override (#9179) * Gateway: require explicit auth for url overrides * Gateway: scope credential blocking to non-local URLs only Address review feedback: the previous fix blocked credential fallback for ALL URL overrides, which was overly strict and could break workflows that use --url to switch between loopback/tailnet without passing credentials. Now credential fallback is only blocked for non-local URLs (public IPs, external hostnames). Local addresses (127.0.0.1, localhost, private IPs like 192.168.x.x, 10.x.x.x, tailnet 100.x.x.x) still get credential fallback as before. This maintains the security fix (preventing credential exfiltration to attacker-controlled URLs) while preserving backward compatibility for legitimate local URL overrides. * Security: require explicit credentials for gateway url overrides (#8113) (thanks @victormier) * Gateway: reuse explicit auth helper for url overrides (#8113) (thanks @victormier) * Tests: format gateway chat test (#8113) (thanks @victormier) * Tests: require explicit auth for gateway url overrides (#8113) (thanks @victormier) --------- Co-authored-by: Victor Mier <[email protected]> * Tests: restore TUI gateway env * Security: harden sandboxed media handling (#9182) * Message: enforce sandbox for media param * fix: harden sandboxed media handling (#8780) (thanks @victormier) * chore: format message action runner (#8780) (thanks @victormier) --------- Co-authored-by: Victor Mier <[email protected]> * Telegram: remove @ts-nocheck from bot-message.ts (#9180) * Telegram: remove @ts-nocheck from bot-message.ts, type deps via Omit<BuildTelegramMessageContextParams> * Telegram: widen allMedia to TelegramMediaRef[] so stickerMetadata flows through * Telegram: remove @ts-nocheck from bot-message.ts (#9180) * fix: cover anonymous voice allowlist callers (#8104) (thanks @victormier) (#9188) * Security: owner-only tools + command auth hardening (#9202) * Security: gate whatsapp_login by sender auth * Security: treat undefined senderAuthorized as unauthorized (opt-in) * fix: gate whatsapp_login to owner senders (#8768) (thanks @victormier) * fix: add explicit owner allowlist for tools (#8768) (thanks @victormier) * fix: normalize escaped newlines in send actions (#8768) (thanks @victormier) --------- Co-authored-by: Victor Mier <[email protected]> * Telegram: remove last @ts-nocheck from bot-handlers.ts (#9206) * Telegram: remove @ts-nocheck from bot-handlers.ts, use Grammy types directly, deduplicate StickerMetadata * Telegram: remove last @ts-nocheck from bot-handlers.ts (#9206) * Message: clarify media schema + fix MEDIA newline * fix: enforce owner allowlist for commands * fix: infer --auth-choice from API key flags during non-interactive onboarding (#9241) * fix: infer --auth-choice from API key flags during non-interactive onboarding When --anthropic-api-key (or other provider key flags) is passed without an explicit --auth-choice, the auth choice defaults to "skip", silently discarding the API key. This means the gateway starts without credentials and fails on every inbound message with "No API key found for provider". Add inferAuthChoiceFromFlags() to derive the correct auth choice from whichever provider API key flag was supplied, so credentials are persisted to auth-profiles.json as expected. Fixes #8481 * fix: infer auth choice from API key flags (#8484) (thanks @f-trycua) * refactor: centralize auth choice inference flags (#8484) (thanks @f-trycua) --------- Co-authored-by: f-trycua <[email protected]> * chore: sync plugin versions to 2026.2.3 * fix(mac): resolve cron schedule formatters * chore(mac): update appcast for 2026.2.3 * chore: update 2026.2.3 notes --------- Co-authored-by: Ayaan Zaidi <[email protected]> Co-authored-by: Peter Steinberger <[email protected]> Co-authored-by: cpojer <[email protected]> Co-authored-by: Christian Klotz <[email protected]> Co-authored-by: Shadow <[email protected]> Co-authored-by: Josh Palmer <[email protected]> Co-authored-by: CLAWDINATOR Bot <clawdinator[bot]@users.noreply.github.com> Co-authored-by: Marco Marandiz <[email protected]> Co-authored-by: Shakker <[email protected]> Co-authored-by: Mariano Belinky <[email protected]> Co-authored-by: Mariano Belinky <[email protected]> Co-authored-by: Tyler Yust <[email protected]> Co-authored-by: Elarwei <[email protected]> Co-authored-by: bqcfjwhz85-arch <[email protected]> Co-authored-by: lotusfall <[email protected]> Co-authored-by: Ji <[email protected]> Co-authored-by: mac mimi <[email protected]> Co-authored-by: Tak Hoffman <[email protected]> Co-authored-by: Justin <[email protected]> Co-authored-by: Aldo <[email protected]> Co-authored-by: Gustavo Madeira Santana <[email protected]> Co-authored-by: Vignesh Natarajan <[email protected]> Co-authored-by: Benjamin Jesuiter <[email protected]> Co-authored-by: Ethan Palm <[email protected]> Co-authored-by: Armin Ronacher <[email protected]> Co-authored-by: Josh Palmer <[email protected]> Co-authored-by: Tyler Yust <[email protected]> Co-authored-by: Ermenegildo Fiorito <[email protected]> Co-authored-by: Michelle Tilley <[email protected]> Co-authored-by: Claude Opus 4.5 <[email protected]> Co-authored-by: Stephen Chen <[email protected]> Co-authored-by: stephenchen2025 <[email protected]> Co-authored-by: Liu Weizhan <[email protected]> Co-authored-by: Wangnov <[email protected]> Co-authored-by: wangnov <[email protected]> Co-authored-by: Yeom-JinHo <[email protected]> Co-authored-by: Lucas Kim <[email protected]> Co-authored-by: Val Alexander <[email protected]> Co-authored-by: Glucksberg <[email protected]> Co-authored-by: Yudong Han <[email protected]> Co-authored-by: Iranb <[email protected]> Co-authored-by: Seb Slight <[email protected]> Co-authored-by: mudrii <[email protected]> Co-authored-by: lsh411 <[email protected]> Co-authored-by: m1 16 512 <[email protected]> Co-authored-by: Gustavo Madeira Santana <[email protected]> Co-authored-by: Victor Mier <[email protected]> Co-authored-by: f-trycua <[email protected]> Co-authored-by: Nova <[email protected]>
bestNiu
pushed a commit
to bestNiu/clawdbot
that referenced
this pull request
Feb 5, 2026
batao9
pushed a commit
to batao9/openclaw
that referenced
this pull request
Feb 7, 2026
This was referenced Feb 8, 2026
hughdidit
pushed a commit
to hughdidit/DAISy-Agency
that referenced
this pull request
Feb 8, 2026
(cherry picked from commit 7cee8c2)
FullStackKevinVanDriel
pushed a commit
to FullStackKevinVanDriel/openclaw
that referenced
this pull request
Feb 10, 2026
battman21
pushed a commit
to battman21/openclaw
that referenced
this pull request
Feb 12, 2026
battman21
pushed a commit
to battman21/openclaw
that referenced
this pull request
Feb 12, 2026
heybeaux
pushed a commit
to heybeaux/openclaw
that referenced
this pull request
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing
Greptile Overview
Greptile Summary
This PR updates the docs configuration to expand the Simplified Chinese (zh-Hans) navigation to cover the full translated doc set, and fixes an asset path on the zh-CN landing page by using a root-relative image URL so it resolves correctly when served by Mintlify. It also adds a corresponding changelog entry under the current release.
Confidence Score: 4/5
Context used:
dashboard- CLAUDE.md (source)dashboard- AGENTS.md (source)