Skip to content
Archived update

This post is kept for reference, but it is not part of the main hosted OpenClaw VPS blog feed.

OpenClaw 2026.1.30 โ€” What Shipped (Operator Guide)

Operator-focused summary of OpenClaw 2026.1.30: what shipped, what matters for hosted bots, and what to check after upgrade.

Jason Cochran
January 31, 2026

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

What shipped

Changes

  • CLI: add completion command (Zsh/Bash/PowerShell/Fish) and auto-setup during postinstall/onboarding.
  • CLI: add per-agent models status (--agent filter). (#4780) Thanks @jlowin.
  • Agents: add Kimi K2.5 to the synthetic model catalog. (#4407) Thanks @manikv12.
  • Auth: switch Kimi Coding to built-in provider; normalize OAuth profile email.
  • Auth: add MiniMax OAuth plugin + onboarding option. (#4521) Thanks @Maosghoul.
  • Agents: update pi SDK/API usage and dependencies.
  • Web UI: refresh sessions after chat commands and improve session display names.
  • Build: move TypeScript builds to tsdown + tsgo (faster builds, CI typechecks), update tsconfig target, and clean up lint rules.
  • Build: align npm tar override and bin metadata so the openclaw CLI entrypoint is preserved in npm publishes.
  • Docs: add pi/pi-dev docs and update OpenClaw branding + install links.

Fixes

  • Security: restrict local path extraction in media parser to prevent LFI. (#4880)
  • Gateway: prevent token defaults from becoming the literal "undefined". (#4873) Thanks @Hisleren.
  • Control UI: fix assets resolution for npm global installs. (#4909) Thanks @YuriNachos.
  • macOS: avoid stderr pipe backpressure in gateway discovery. (#3304) Thanks @abhijeet117.
  • Telegram: normalize account token lookup for non-normalized IDs. (#5055) Thanks @jasonsschin.
  • Telegram: preserve delivery thread fallback and fix threadId handling in delivery context.
  • Telegram: fix HTML nesting for overlapping styles/links. (#4578) Thanks @ThanhNguyxn.
  • Telegram: accept numeric messageId/chatId in react actions. (#4533) Thanks @Ayush10.
  • Telegram: honor per-account proxy dispatcher via undici fetch. (#4456) Thanks @spiceoogway.
  • Telegram: scope skill commands to bound agent per bot. (#4360) Thanks @robhparker.
  • BlueBubbles: debounce by messageId to preserve attachments in text+image messages. (#4984)
  • Routing: prefer requesterOrigin over stale session entries for sub-agent announce delivery. (#4957)
  • Extensions: restore embedded extension discovery typings.
  • CLI: fix tui:dev port resolution.
  • LINE: fix status command TypeError. (#4651)
  • OAuth: skip expired-token warnings when refresh tokens are still valid. (#4593)
  • Build: skip redundant UI install step in Dockerfile. (#4584) Thanks @obviyus.

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

Start your free 7-day Pro trial

Source

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

Get the free guide

Get the free plain-English PDF on the 10 costly mistakes people make when hosting an AI assistant themselves, plus a few short follow-up tips.

Ready to run OpenClaw without infrastructure headaches?

Start your free 7-day Pro trial on OpenClaw VPS and get a production-ready bot online with managed hosting, updates, and support.

Share this post

Related Posts

Free plain-English PDF

Get the free DIY VPS checklist

Before you host an AI assistant yourself, learn the 10 common mistakes that cause downtime, lost keys, missed alerts, and painful recovery work.

Send me the free PDF

We will send the plain-English PDF on the 10 costly mistakes people make when hosting an AI assistant themselves, plus short follow-up tips. Unsubscribe anytime.