Skip to content

feat(kiloclaw): bump openclaw to version 2026.3.22#1390

Open
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
feat/kiloclaw-bump-openclaw-2026.3.22
Open

feat(kiloclaw): bump openclaw to version 2026.3.22#1390
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
feat/kiloclaw-bump-openclaw-2026.3.22

Conversation

@kilo-code-bot
Copy link
Contributor

@kilo-code-bot kilo-code-bot bot commented Mar 23, 2026

Summary

  • Bumps openclaw in kiloclaw/Dockerfile from 2026.3.13 to 2026.3.22.

Verification

  • Confirmed current version (2026.3.13) is older than the target (2026.3.22); update is appropriate.
  • Reviewed release notes for v2026.3.22 from the openclaw/openclaw repository.

Visual Changes

N/A

Reviewer Notes

The following breaking changes from the v2026.3.22 release notes warrant attention for our deployment:

High priority — action likely required:

  • jq removed from exec safe-bin allowlistjq is installed in our Dockerfile (apt-get install -y ... jq). Agents that previously ran jq commands without an explicit approval prompt will now be blocked by default. This could break automation or agent workflows that rely on jq silently being allowed. Operators must explicitly opt jq back into the trusted path if needed. The release notes also note that the jq -n env builtin is blocked even when opted back in, to prevent secret leakage.

  • Browser/Chrome MCP: legacy Chrome extension relay removeddriver: "extension", bundled extension assets, and browser.relayBindHost are all gone. We install chromium in the image. If any user config or skills reference these settings, they will break. The fix path is openclaw doctor --fix on affected instances. This is safe for container-fresh setups (new onboards), but existing volumes with old configs may need remediation.

  • Config/env: CLAWDBOT_* and MOLTBOT_* env var names removed — Only OPENCLAW_* names are accepted now. Our controller/bootstrap code should be checked to confirm no legacy env var names are used. Unlikely to affect us since KiloClaw has always used OPENCLAW_* naming, but worth confirming.

  • Config/state: .moltbot state-dir migration fallback removed — Auto-detection of ~/.moltbot is gone. We use /root/.openclaw already (created explicitly in the Dockerfile), so this should have no impact on new or existing volumes.

  • Plugins/SDK: openclaw/extension-api removed — Any custom skills or plugins that import from openclaw/extension-api will fail to load. The replacement is openclaw/plugin-sdk/*. The skills in kiloclaw/skills/ should be audited to confirm they do not use the old import path.

Notable improvements in this release:

  • Gateway cold-start fix — Bundled channel plugins now load from compiled dist/extensions instead of recompiling TypeScript on every gateway startup. WhatsApp-class cold starts are expected to drop from tens of seconds to seconds. Positive for container startup time.
  • Default agent timeout raised from 600s to 48h — Long-running ACP and agent sessions will no longer time out prematurely. Positive for our use case.
  • Multiple security hardening fixes across exec approvals, pairing, SSRF, and webhook auth.

@kilo-code-bot
Copy link
Contributor Author

kilo-code-bot bot commented Mar 23, 2026

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 files)
  • kiloclaw/Dockerfile

Reviewed by gpt-5.4-20260305 · 286,706 tokens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants