feat(kiloclaw): bump openclaw to version 2026.6.1

[kilo-code-bot]

Summary

• Bumps openclaw from 2026.5.26 to 2026.6.1 in services/kiloclaw/Dockerfile.
• Updates version references in the bundled plugin stage-root comment and the cache bust tag.
• The two existing Dockerfile patches remain in place: KiloCode DISCOVERY_TIMEOUT_MS (5s→60s) and the actionRequiresTarget channel-target fix — both guards will fail the build if the patched constants change shape, so this bump needs a successful image build to confirm they still apply cleanly.

Potential Deployment Concerns

The following changes in 2026.6.1 may warrant attention for our deployment:

Patch guards in the Dockerfile — must verify on build

The Dockerfile applies two patches to OpenClaw's compiled dist files after install:

1. DISCOVERY_TIMEOUT_MS = 5e3 → 60e3 in a provider-models-*.js chunk (guarded with grep -c assertion).
2. MESSAGE_ACTION_TARGET_MODE[action] !== "none" → (MESSAGE_ACTION_TARGET_MODE[action] ?? "none") !== "none" in a channel-target-*.js chunk.

This release touches provider and channel code extensively. If the upstream minified output changes names, splits chunks, or removes the patched constants, the build will fail fast. A successful CI image build confirms both patches still apply cleanly.

Agents/providers: streaming tool-call argument parsing

Keep streaming tool-call argument parsing record-shaped when providers emit valid non-object JSON such as null or arrays.

KiloClaw routes all turns through KiloCode. If provider streaming output previously caused silently bad argument shapes this fix is beneficial, but it's a behavioral change in the turn execution path worth watching.

Skills: stale disabled snapshot env overrides

Skip disabled skill env overrides from stale persisted snapshots so disabled skill apiKey SecretRefs cannot abort embedded or channel turns.

If any KiloClaw instance has a skill with a SecretRef that was disabled, previous versions could abort channel turns. This fix is a correctness improvement, but it changes startup/turn behavior for affected instances.

Memory: Linux file watcher fan-out and concurrent writes

Reduce Linux watcher fan-out, retry transient FileProvider-backed reads, reattach Linux native watchers when directories are recreated, rewrite generated transcript paths on rollover.

KiloClaw runs on Linux with persistent volumes at /root. The memory subsystem now handles concurrent gateway/CLI activity more safely. No action required but restarts may show changed watcher behavior on first boot after upgrade.

Doctor: disk space health checks

Add disk space health checks and stabilize post-upgrade JSON probes.

openclaw doctor (run by the controller on boot) now includes a disk space check. If a volume is near capacity this will surface as a new diagnostic warning rather than a silent failure — beneficial but worth noting.

iMessage / inbound queues moved to SQLite

Store inbound queues in SQLite and migrate iMessage monitor state to SQLite-backed tracking.

Applies to iMessage channel users. On first boot after upgrade, monitor state migrates to SQLite. Any KiloClaw instance with an active iMessage channel will go through this migration path on restart.

Verification

• Trigger a CI image build and confirm it completes successfully (both Dockerfile patch guards pass).
• Confirm openclaw --version in the built image reports 2026.6.1.
• Boot a test machine and verify openclaw doctor completes without unexpected failures.

Visual Changes

N/A

Reviewer Notes

The --force-with-lease push was needed because the remote branch already existed from a prior session. The local commit is the only change on this branch.

The two Dockerfile patch guards are the main risk vector for this bump. If either guard fails the Docker build will error with a clear message pointing at the changed constant — no silent degradation.

[kilo-code-bot]

Code Review Summary

Status: 4 Issues Found | Recommendation: Address before merge

Executive Summary

Plugin package.json files and downstream touchpoints were not updated to align with the 2026.6.1 version bump, meaning bundled plugins will build and test against the old 2026.5.26 peer and are mismatched with the shipped image.

Overview

Severity	Count
CRITICAL	0
WARNING	3
SUGGESTION	1

Other Observations (not in diff)

Issues found in unchanged files that cannot receive inline comments:

File	Line	Severity	Issue
services/kiloclaw/plugins/kilo-chat/package.json	31, 35	WARNING	peerDependencies and devDependencies still pin openclaw@2026.5.26. Per the upgrade checklist, both must be bumped to 2026.6.1 to match the Dockerfile install pin.
services/kiloclaw/plugins/kiloclaw-morning-briefing/package.json	25, 29	WARNING	Same as above — peerDependencies and devDependencies still pin openclaw@2026.5.26.
services/kiloclaw/e2e/docker-image-testing.md	144	SUGGESTION	Expected version in the verify step comment still shows 2026.5.26 — should be updated to 2026.6.1 to keep the runbook accurate.
services/kiloclaw/Dockerfile	80–84	WARNING	actionRequiresTarget patch guard asymmetry: after sed runs there is only a negative check (grep -q that fails if the old string persists), but no positive assertion confirming the patched form was written — unlike the DISCOVERY_TIMEOUT_MS patch which verifies AFTER=$(grep -c 'DISCOVERY_TIMEOUT_MS = 60e3') equals 1. If the upstream release removes or renames the constant so sed matches zero times, the negative check passes silently. Adding a count-check for (MESSAGE_ACTION_TARGET_MODE[action] ?? "none") !== "none" (analogous to $AFTER -ne 1) would close this gap.

Additionally, apps/web/src/app/(app)/claw/components/changelog-data.ts has no new entry for 2026.6.1. The prior pattern adds an Updated OpenClaw to X.Y.Z changelog entry with deployHint: "upgrade_required" for every version bump (see the 2026.5.26 and 2026.5.22 entries). This is not blocking but is inconsistent with past practice.

Files Reviewed (5 files)

• services/kiloclaw/Dockerfile — diff reviewed; guard asymmetry observation (pre-existing, out-of-diff)
• services/kiloclaw/plugins/kilo-chat/package.json — 1 issue (version not bumped)
• services/kiloclaw/plugins/kiloclaw-morning-briefing/package.json — 1 issue (version not bumped)
• services/kiloclaw/e2e/docker-image-testing.md — 1 suggestion (stale version in verify step)
• apps/web/src/app/(app)/claw/components/changelog-data.ts — missing changelog entry

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-4.6-sonnet-20260217 · 951,800 tokens}

_{Review guidance: REVIEW.md from base branch main}