openclaw

OpenClaw became a more predictable system this week through 9 stability fixes that eliminated silent failures and configuration drift. The most critical fix protected bootstrap files like MEMORY.md and SOUL.md from accidental deletion during AI memory flushes, preventing workspace corruption that previously required manual git recovery. Telegram exec approvals were completely non-functional with "unknown approval id" errors blocking all elevated operations until we fixed approval ID handling and thread routing. Web search citations were disappearing when using Perplexity through OpenRouter, degrading research quality for users who depend on source tracking. We also stopped duplicate messages in Telegram during provider timeout scenarios and fixed the Sessions table layout breaking on mobile screens. The pattern across all fixes was clear: making broken configurations fail fast and explicitly rather than degrading silently. Two infrastructure improvements support this direction - cron jobs now track structured failure reasons (auth, rate limit, billing) and bug reports collect provider routing details to diagnose vanishing issues. The system is now more reliable but also more transparent about what's broken when things go wrong. We'll use the improved error classification next week to build smarter retry logic for provider routing failures.