OpenClaw 2026.2.3 — What Shipped (Operator Guide)

This post covers what shipped in v2026.2.3 and what it means for OpenClaw VPS operators.

What shipped

Changes

• Telegram: remove last @ts-nocheck from bot-handlers.ts, use Grammy types directly, deduplicate StickerMetadata. Zero @ts-nocheck remaining in src/telegram/. (#9206)
• Telegram: remove @ts-nocheck from bot-message.ts, type deps via Omit<BuildTelegramMessageContextParams>, widen allMedia to TelegramMediaRef[]. (#9180)
• Telegram: remove @ts-nocheck from bot.ts, fix duplicate bot.catch error handler (Grammy overrides), remove dead reaction messagethreadid routing, harden sticker cache guard. (#9077)
• Onboarding: add Cloudflare AI Gateway provider setup and docs. (#7914) Thanks @roerohan.
• Onboarding: add Moonshot (.cn) auth choice and keep the China base URL when preserving defaults. (#7180) Thanks @waynelwz.
• Docs: clarify tmux send-keys for TUI by splitting text and Enter. (#7737) Thanks @Wangnov.
• Docs: mirror the landing page revamp for zh-CN (features, quickstart, docs directory, network model, credits). (#8994) Thanks @joshp123.
• Messages: add per-channel and per-account responsePrefix overrides across channels. (#9001) Thanks @mudrii.
• Cron: add announce delivery mode for isolated jobs (CLI + Control UI) and delivery mode config.
• Cron: default isolated jobs to announce delivery; accept ISO 8601 schedule.at in tool inputs.
• Cron: hard-migrate isolated jobs to announce/none delivery; drop legacy post-to-main/payload delivery fields and atMs inputs.
• Cron: delete one-shot jobs after success by default; add --keep-after-run for CLI.
• Cron: suppress messaging tools during announce delivery so summaries post consistently.
• Cron: avoid duplicate deliveries when isolated runs send messages directly.

Fixes

• Heartbeat: allow explicit accountId routing for multi-account channels. (#8702) Thanks @lsh411.
• TUI/Gateway: handle non-streaming finals, refresh history for non-local chat runs, and avoid event gap warnings for targeted tool streams. (#8432) Thanks @gumadeiras.
• Shell completion: auto-detect and migrate slow dynamic patterns to cached files for faster terminal startup; add completion health checks to doctor/update/onboard.
• Telegram: honor session model overrides in inline model selection. (#8193) Thanks @gildo.
• Web UI: fix agent model selection saves for default/non-default agents and wrap long workspace paths. Thanks @Takhoffman.
• Web UI: resolve header logo path when gateway.controlUi.basePath is set. (#7178) Thanks @Yeom-JinHo.
• Web UI: apply button styling to the new-messages indicator.
• Onboarding: infer auth choice from non-interactive API key flags. (#8484) Thanks @f-trycua.
• Security: keep untrusted channel metadata out of system prompts (Slack/Discord). Thanks @KonstantinMirin.
• Security: enforce sandboxed media paths for message tool attachments. (#9182) Thanks @victormier.
• Security: require explicit credentials for gateway URL overrides to prevent credential leakage. (#8113) Thanks @victormier.
• Security: gate whatsapp_login tool to owner senders and default-deny non-owner contexts. (#8768) Thanks @victormier.
• Voice call: harden webhook verification with host allowlists/proxy trust and keep ngrok loopback bypass.
• Voice call: add regression coverage for anonymous inbound caller IDs with allowlist policy. (#8104) Thanks @victormier.
• Cron: accept epoch timestamps and 0ms durations in CLI --at parsing.
• Cron: reload store data when the store file is recreated or mtime changes.
• Cron: deliver announce runs directly, honor delivery mode, and respect wakeMode for summaries. (#8540) Thanks @tyler6204.
• Telegram: include forwardfromchat metadata in forwarded messages and harden cron delivery target checks. (#8392) Thanks @Glucksberg.
• macOS: fix cron payload summary rendering and ISO 8601 formatter concurrency safety.

What matters for hosted operators

• Validate channel delivery behavior (web chat + Telegram).
• Verify model/provider settings and fallback behavior.
• Run a smoke test after deploy: message flow, tool call, and response quality.

Post-upgrade checklist

1. Send/receive test messages in active channels.
2. Confirm bot settings and auth paths still behave as expected.
3. Check billing/usage visibility and dashboard status.
4. Log regressions immediately and keep rollback notes.

Related reading

• OpenClaw Release Notes Hub (2026)
• Best OpenClaw Hosting in 2026
• Pricing · Why OpenClaw VPS · FAQ

Start your free 7-day Pro trial

• Start your free 7-day Pro trial

Source

• https://github.com/openclaw/openclaw/releases/tag/v2026.2.3