Reinventing.AI

OpenClaw Trends

OpenClaw 2026.11.4 Keeps Unanswered Messages Through Restarts and Makes Side Chat and Device Captures Private

The OpenClaw 2026.11.4 stable release preserves unanswered prompts across Gateway restarts, fixes dropped WhatsApp and Signal replies, keeps Side chat private to its viewer, and blocks unsafe database upgrades.

AI Agent Insights Team6 min
OpenClaw 2026.11.4 Reliable Replies and Private Side Chat

OpenClaw published version 2026.11.4 on November 16, 2026 as a stable release. Its notes list six highlights and record 99 pull requests since 2026.11.3. Three of the highlights matter most to a person or small business that runs one assistant across chat apps: replies that are no longer lost when the Gateway restarts, conversation data that stays with the person who is allowed to see it, and an upgrade check that stops a newer command line tool from changing a database an older Gateway is still using.

Unanswered messages are kept across a restart

The Gateway is the process that holds every channel connection, so a restart during an update or a configuration change has been a moment when a message could go unanswered. The release notes describe the fix under the heading Reliable replies. OpenClaw now preserves unanswered prompts across Gateway restarts, keeps WhatsApp final replies across unrelated reloads, and prevents Signal reconnects from skipping buffered messages.

The longer fixes list adds detail. Under restart recovery, the notes say the release will “keep original unanswered prompts and accepted executions through restart capture,” keep local final replies, and “send an uncertainty notice if Telegram final recovery cannot confirm delivery.” The last item means a Telegram user is told when the assistant cannot confirm that its final reply arrived, where before there was no message at all.

The channel documentation explains why the WhatsApp and Signal fixes sit together. The WhatsApp channel page states that the Gateway owns the WhatsApp socket and its reconnect loop. The Signal channel page states that the Gateway talks to signal-cli over HTTP. In both cases the connection can drop and return while a customer message is waiting. In 2026.11.4 a WhatsApp final reply is no longer suppressed by a reload that has nothing to do with that conversation, and Signal messages buffered during a reconnect are delivered.

Scheduled work received a related fix. The notes list delivery of session-targeted cron and system-event responses under background replies, and a separate entry keeps active turns running across the automatic idle or daily session rollover. Operators who rely on scheduled jobs, covered in the OpenClaw cron jobs guide, are the group most likely to see the difference.

Side chat and device captures are private by default

The fourth highlight is titled Private conversation data. It says the release will keep Side chat scoped to its authenticated viewer, keep photos and screenshots from paired nodes private by default, and keep internal model prompt projections out of display output. A paired node is a phone or computer connected to the Gateway, so the second item covers images captured on those devices.

Several smaller entries follow the same direction. The release stops persisting pasted setup codes on iOS devices. It redacts credential-shaped text in quoted compaction summary sections while leaving stored history unchanged. It refuses to replace a stored secret reference with a plaintext API key when a skill key is saved. For IRC, an explicitly empty channel sender list is now treated as deny-all, where it previously fell back to broader sender access.

For a solo operator who shares one Gateway with a contractor or a family member, the Side chat change is the one to test. Each signed-in viewer should see only their own Side chat. This continues the work in 2026.11.3, described in this site’s report on credential scoping and visible tool failures.

A newer CLI can no longer migrate past an older Gateway

The Safer upgrades highlight addresses a specific failure. A machine can hold two OpenClaw installations, for example a newly updated command line tool and an older Gateway service that is still running. According to the notes, 2026.11.4 will “prevent a newer CLI from migrating a shared database beyond an older installed Gateway daemon while allowing unrelated installation databases to remain independent.”

The rollback and recovery documentation explains the risk this guards against. It says downgrading the package does not reverse configuration or database migrations, and that once state has migrated beyond the format an older release supports, the supported recovery is to restore a verified backup made before the update, with its matching release. The same page lists a check for mismatched installations: compare openclaw --version with openclaw status and openclaw gateway status --deep, because the first reports the CLI version and the status commands report the Gateway service.

Two further fixes help anyone who updates without supervision. The release preserves the previous rollback snapshot when its replacement cannot be fully written, and it keeps official plugin selectors on the stable channel, where the notes say they had been repeatedly returning to beta. The documentation recommends openclaw update over a raw package install because the command validates the target, runs the required Doctor migrations and verifies the activated Gateway.

Large stores start faster and Doctor uses less memory

The first two highlights concern installations with a long history. Large transcript trimming, paged memory exports and Doctor repairs are now bounded so they do not exhaust worker memory. At startup, plugins and their services start before the scan for orphaned work, and that scan no longer loads unrelated retained session summaries. The Doctor documentation describes openclaw doctor as the repair and migration tool for OpenClaw, which is why a Doctor run that fails for lack of memory can block an upgrade. This site’s report on the 2026.11.5 beta covers the paged history work that is still in pre-release.

Stable and beta are now two separate lines

The 2026.11.5 line remains in pre-release. Version 2026.11.5-beta.4 was published on the same day and adds interactive widgets rendered as Telegram messages along with its own automation and update fixes. Operators on the stable channel receive 2026.11.4. The beta features arrive on stable only after promotion, so a release note for the beta does not describe a stable Gateway.

A short checklist for operators

  • Create a verified backup before updating, as the rollback and recovery page instructs.
  • Run openclaw update --dry-run first and read any named preflight check.
  • Compare the CLI version with the Gateway service version after the update, so the two installations match.
  • Send a test message on WhatsApp or Signal, restart the Gateway before the reply arrives, and confirm the reply is delivered afterward.
  • Where more than one person signs in, confirm each viewer sees only their own Side chat.

This site’s guide to recovering a failed agent run covers what to check when a reply is still missing after a restart. The OpenClaw chat apps guide covers the channels named in this release, and the AI agent harness guide compares how other agent systems handle restarts and stored state.

Sources