OpenClaw v2026.10.4 keeps your Gateway running when your computer sleeps

When your computer slept or the system clock jumped, the OpenClaw Gateway restarted itself, because its ownership heartbeat looked stale. Now the Gateway takes its state back and keeps running.

Slide text

01 02 03 04 Gateway

openclaw/openclaw · CHANGELOG/2026.10.4.md

OpenClaw v2026.10.4 keeps your Gateway running when your computer sleeps

After sleep After a clock jump

Stopping or restarting the OpenClaw Gateway could hang on a stalled transcript worker. Shutdown now gives that worker a bounded wait, and lets in-flight session lifecycle events publish before the Gateway exits.

A long reply-tagged stream no longer ties up the OpenClaw Gateway, and a reply that quotes tool-call XML stops re-parsing Markdown on every token. In the Control UI, a delayed heartbeat no longer forces a reconnect.

On macOS, app recovery replaced a newer OpenClaw Gateway with an older one. It now keeps any compatible newer Gateway, and the gateway restart command works from a verified terminal outside the app.

Agents, models and the browser.

Typing /compact during a run used to abort that run and drop the request you had waiting. OpenClaw now lets the active run settle first, then compacts the conversation.

When an OpenAI reasoning model ran through the Completions routes of the OpenAI API, any turn that called a tool failed with a bad request error. Those tool turns now go through.

An agent turn launched by a plugin no longer fails with a writer-claim error. And a Claude CLI session keeps a single history, where before it forked across message routes.

When a site asked for a passkey, the page in OpenClaw's headless browser stopped responding to clicks. Your agent can now keep clicking on that page while the site waits for the passkey.

Security, and the chat channels.

In a Tlon group DM, OpenClaw treated the other participants as its owner, which let them impersonate you. OpenClaw now never gives a group DM author owner status.

On Discord, agent consults keep working after a voice change. On Feishu, a config hot-reload no longer orphans conversation bindings. And on IRC, long replies with non-ASCII characters arrive instead of getting lost.

Updates, networking and Android.

On a slower machine, the update repair command timed out before it ran any tools, and a slow host admission held the database writer and disrupted the Gateway. Now the update finishes, even when an optional cleanup step fails.

A tailnet that refuses Tailscale Serve no longer cuts you off from OpenClaw on your own machine. An interrupted start also cleans up its serve process, and Doctor now checks the Tailscale prerequisites you configured.

If you run OpenClaw on Android, there is no new APK this time. The Android app stays on its August build until a later release ships one.

This OpenClaw release is a stability patch, so your configuration stays as it is. The steps for your install, and how to roll back, are in OpenClaw's Updating guide.