Airplane Wi-Fi Was Dropping Constantly, So He Tested OpenClaw’s Offline Reconnect While He Was at It

OpenClaw’s web interface just got two new capabilities: offline usability, and smarter WebSocket compression and reconnect logic. Peter Steinberger posted this on X, with a screenshot of the interface from when he was working on a plane. Airplane Wi-Fi has always been the best stress-testing environment—and you don’t have to buy extra load-testing services.

The conversation in the screenshot mentions a clear scope: GitHub will become a bundled default extension, and GitLab will become an optional npm/ClawHub plugin; both use the same narrow host contract. Peter said the released GitHub behavior and configuration will be preserved. For ordinary readers, you can think of it as splitting different code-hosting platforms into pluggable modules: the default functionality stays, and additional platforms can be installed as needed.

WebSocket can be understood as a persistent connection kept open between the browser and the server. When the network is poor, this connection is prone to dropping. This time OpenClaw added compression and reconnect logic, with the focus on being able to recover after a disconnect: operations get queued and are resent after reconnecting. A user asked whether, if the Wi-Fi drops for half an hour while you’re in the middle of editing, everything will be queued and replayed, or whether the last bit of content will be lost. Peter replied that of course it queues, and you usually won’t notice—you’ll just see a small reconnecting bubble.

Someone else added: reconnect logic can keep a session online under bad Wi-Fi, but a true offline mode requires a local model and doesn’t use the socket at all. That distinction is pretty important. “The web interface is usable offline” and “the model runs entirely locally” are not the same thing.

Someone in the replies also asked whether airplane Wi-Fi had conveniently become the test suite for the reconnect logic. Peter said that on a flight last month it wasn’t working well, so he ran some loops and fixed it.

Regarding OpenClaw’s positioning, a user asked how it differs from products like ChatGPT Dots, Grok bot, and Claude Code. Peter’s answer was fairly direct: tinkering with your own agent is a lot of fun; no one can tell you it won’t work, and no one limits which model you use. In some scenarios, abliterated DeepSeek works quite well. He also mentioned that if he wants to use a hosted solution for work, he often uses dots, and he doesn’t want to give up either side.

Someone also asked about hosting. Peter said these OpenClaw bots run on a rented bare-metal Linux machine. Someone else asked whether it is now a web version; he replied that OpenClaw has always had a web UI—it’s just been made better and faster in recent months.

The comments weren’t all praise. A user said they wished people really needed the web UI, that they had hardly ever used it, and complained that OpenClaw tends to break after every update. Peter’s response was that there is now a good auto-update process, computer use already works on any operating system, and he asked the other person when they had last tried it.

Original tweet here: https://x.com/steipete/status/2115397368229060636