3 posts tagged with "infrastructure"

After last week's OpenClaw 2026.4.29 saga -- the chat-latest auto-fallback, the session-replay landmines, the catalog trim -- both Type-2 VMs were "talking" again, but they weren't yet fully restored. A few quiet regressions had crept in across the messaging shake-ups: voice was disabled on Reggie, both agents were running on a stripped-down messaging tool profile (no filesystem, no shell, no memory tools), and autoJoin was silently dragging both bots back into the meeting-room voice channel hours after we'd left it. Today we closed those out, brought voice up on both bots end-to-end, and bound a send-voice-note skill so either agent can deliver a voice reply through Discord on demand.

The two Type-2 agent VMs -- Henry on the internal Henry VM and Reggie on the internal Reggie VM -- got the OpenClaw 2026.4.29 update on Friday and went silent across every channel. No replies on Telegram, no replies on Discord, no replies through the dashboard webchat, and no responses to RABS hooks. Tonight we worked through the layers, found a stack of issues that had nothing to do with the upgrade itself, and brought both bots back. Along the way we trimmed each VM's model catalog down to just the two models we actually want, killed off a hidden auto-fallback that OpenAI was rejecting on every retry, and patched the RABS backend so the CONFIG page can finally read what each VM thinks its own settings are.

If the first week of October was about building a solid Vite foundation and the second week's start was about plugging in features, the rest of that second week was about discovering that the infrastructure didn't work. The new logging and notifications system — designed as the single entry point for all admin events — was non-functional. The settings pages had broken API connections. The email system had a SQL bug that prevented message caching. And nearly every session was interrupted by a system crash, internet glitch, or connection reset.