AI Projects

OpenClaw Update 4.1 (MASSIVE Critical Fixes)

Published
Apr 2, 2026
Duration
7:59
Click to load the YouTube player

Video summary

Companion notes

OpenClaw 4.1 is a 24-hour hotfix for 3.31's three production failures, with six features bolted on top.

## Six new features in 4.1 The release ships /tasks (a live in-chat task board modeled on Hermes agents' Discord behavior — running, done, queued, retry counts), bundled SearXNG web search (open source, self-hostable, no third-party API keys), Bedrock guardrails, agents default params, OpenClaw cron tools, and macOS voice wake. The two most useful for most users are /tasks and SearXNG. GLM model support is also added.

## Gateway startup hang — fixed After 3.31 upgrades, gateways appeared healthy then silently stopped responding ~1 minute later. Root cause: a SQLite database maintenance task was blocking the main event loop, triggered by 3.31's new task registry activity. Fix: maintenance moved off the main thread.

## Config restart loop — fixed 3.31's tightened gateway auth made OpenClaw generate new security tokens on startup, treat auto-generated values as config changes, and trigger a full restart every boot. 4.1 saves a fingerprint of generated values and only restarts on real config changes.

## Approval amnesia — fixed (4 sub-bugs) Tightened exact approvals in 3.31 caused "allow always" to behave like "allow once." 4.1 fixes the trust persistence bug, remote exact timeouts on Slack/Discord, cron jobs dead-ending in approval paths, and a Windows hard crash when no valid execution plan could be built.

## Memory and compaction bugs — fixed Full re-indexes were silently skipping session transcripts on restart; QMD collections collided due to a config preference conflict; compaction model overrides now work consistently across CLI, gateway, and cron.

## Community validation User Vox confirmed 4.1 fixed his 3.31 complaint after running 6 production agents on a single VPS — he now has 47 trusted commands persisted across gateway restarts. Edge cases remain for wrapper paths and inline eval. Catherine posted a two-file, five-setting config workaround for users still hitting approval walls.

Watch on YouTube

Prefer the native player? Open it on YouTube: https://www.youtube.com/watch?v=JHfbLt9iKDc