clawsmith.com/signal/openclaw-v2026-4-8-session-reset-regression-unbounded-growth

⚠ IssueWide OpenLive

OpenClaw 2026.4.8 Regression: Daily Session Reset Stops Firing, Sessions Grow to 639+ Messages

Since v2026.4.1, daily atHour session reset no longer fires because heartbeats update session timestamp. Sessions grow without bound: one hit 639 messages (1.87M chars) before provider corruption. Critical cost implications for API-billed users.

Product Idea from this Signal

A CLI tool that snapshots your OpenClaw state before updates, runs the upgrade in a sandboxed dry-run against your live config, and auto-rolls back if any health check fails

1667.8k ▲

OpenClaw ships updates every 2-3 days and each one risks breaking exec permissions, crashing the gateway, saturating CPU with plugin loading bugs, or silently deleting cron jobs. Four separate regressions in April 2026 alone (v2026.4.1 sandbox, v2026.4.5 CPU, v2026.4.14 memory timeouts, update command wiping Feishu and crons) hit thousands of self-hosters with no rollback path. The built-in openclaw doctor only validates config schema after the fact. This tool wraps the entire update lifecycle: snapshot state, dry-run the upgrade against your actual agent/cron/channel config, diff the before/after, and block or auto-rollback if anything regresses.

CLIOPEN-SOURCEDEVTOOLSELF-HOSTEDRELIABILITY

CompetitiveView Opportunity →