OpenClaw 2026.11.4 was released on npm on 16 November 2026 with 125 fix pull requests. Upgrade if you need the cron, WhatsApp, and Telegram fixes, but wait if your agentAI agentAn AI program that performs work steps by itself, for example reading a message, drafting a reply, and recording the result.Open the glossary uses the claude-cli backend. In this version, that backend fails on every second message.
OpenClaw is an AI agent gateway that runs on your server. The gateway connects AI models to chat channels such as Telegram, WhatsApp, Slack, and Signal. A patch release brings fixes and small settings, not large features.
Main changes in OpenClaw 2026.11.4
OpenClaw 2026.11.4 fixes the update process, chat channels, cron, and security, and adds 2 new access controls.
The official OpenClaw 2026.11.4 release notes list 125 pull requests, 106 direct commits, and 90 contributors. This table shows the changes that you will see most on a production server.
| Area | Change | Effect for you |
|---|---|---|
| Update and Doctor | A failed update can now go back to the old release when the state is safe. Doctor no longer truncates MEMORY.md when a legacy memory merge fails. | Lower risk of a dead server after an update. |
| Chat channels | Final WhatsApp replies no longer disappear when settings reload. Telegram buttons no longer show "This action is no longer available". Signal messages are no longer skipped after a reconnect. | Customers do not lose replies. |
| Cron | Recurring jobs are no longer skipped silently when the scheduler wakes late and cron.skipMissedJobs is on. Automatic cleanup no longer archives sessions that cron jobs use. | Scheduled reports keep running. |
| Security | Delegated persistent changes now need approval when authority is restricted. Policy plugins can inspect images before the images reach the model. The Control UI uses DOMPurify 3.4.17. | An agent cannot change settings without permission. |
| Models | Some ClaudeClaude ProThe paid subscription for the Claude AI assistant from Anthropic. It unlocks connectors to outside tools.Open the glossary 5 requests are no longer limited to 32,000 output tokens. Conversations through the OpenAI Responses APIAPIThe official door 2 systems use to exchange data, without anybody copying it by hand.Open the glossary no longer fail repeatedly after compaction. | Long answers are not cut off. |
Who should wait before the upgrade
Wait if your agent uses the claude-cli backend, because 2 user reports show alternating message failures since 2026.11.4.
Issue #200096, filed on 16 November 2026, shows the pattern. The first message starts a new Claude CLI process and succeeds. The second message reuses that process and fails in about 1.5 seconds with the error "Native tool authority capture is no longer active." The Telegram user receives "OpenClaw couldn't finish this request."
Issue #200189 reports the same error with Claude Sonnet 5. The fix, PR #198426, was merged into main on 15 November 2026. The OpenClaw team closed both reports and noted that release 2026.11.4 does not contain that fix.
This release also has 3 behavior changes. Check all 3 before you update:
- IRC: an empty sender list now denies all senders. Fill the list, or remove the override so that the channel inherits access.
- fs-safe 0.26.7: replace
FS_SAFE_PYTHON_MODEorOPENCLAW_FS_SAFE_PYTHON_MODEwithFS_SAFE_NATIVE_MODEorOPENCLAW_FS_SAFE_NATIVE_MODE. Keep the same value. - PostgreSQL: the bridge now follows your PostgreSQL commit durability setting. Writes can be slower.
Some update fixes work only when the updater process already contains the fix. An update from 2026.11.3 still runs with the old updater.

How it feels in daily use
For chat users, 2026.11.4 is more stable, because replies, buttons, and scheduled jobs are lost less often.
Example: an online shop runs an agent on Telegram. The agent answers stock questions and sends a sales summary at 08.00 through cron. In 2026.11.3, that summary could be skipped without an error when the scheduler woke late and cron.skipMissedJobs was on. In 2026.11.4, the job runs.
The "Yes" and "No" buttons that the agent sends are also more reliable. A choice that no plugin handles now reaches the agent as data. Buttons sent before the update keep the old behavior, so send those buttons again.
The update process is the difficult part. Issue #200289 records a Control UI update that ran for more than 3 hours: about 150 minutes of validation and about 74 minutes of activation. The update failed because the SQLite database was locked, and the operator needed SSH to recover the Gateway.
Issue #200022 records an update that failed at the backup step, but the Gateway recovered and served 2026.11.4. On 17 November 2026, the OpenClaw team had not found the root cause of these 2 reports.
| Your setup | Decision | Reason |
|---|---|---|
| WhatsApp or Telegram with a direct API model | Upgrade this week | The reply, button, and cron fixes help at once. |
Agent with the claude-cli backend | Wait | Messages fail in turns until a release contains PR #198426. |
| IRC, PostgreSQL, or fs-safe Python mode | Change settings first | 3 behavior changes can block messages or the update. |
What our package check found
We read the release manifests on GitHub and npm on 17 November 2026 for 4 items that decide the upgrade.
- DOMPurify:
ui/package.jsonat tag v2026.11.3 has 3.4.16. Tag v2026.11.4 has 3.4.17. The problem that we recorded in our OpenClaw 2026.11.3 article is closed in this stable release. - Node.js: the 2026.11.4 package needs Node.js
>=24.16.0 <25or>=26.1.0. - npm tags:
latestpoints to 2026.11.4,betapoints to 2026.11.5-beta.4, andextended-stablepoints to 2026.9.37. - claude-cli fix: the PR #198426 commit is not in the history of tag v2026.11.4.
We did not run the update on a production server for this check. These results come from the official manifests and Git history.
How to upgrade to 2026.11.4 safely
Upgrade safely in 7 steps: check the backend, check the changed settings, make a backup, and test 3 flows after the update.
- Check the agent backend. If the agent uses
claude-cli, wait until the next release contains PR #198426. - Check the Node.js version with
node --version. Use 24.16.0 or later on the 24 line, or 26.1.0 or later. - Replace the fs-safe Python mode variables with the NATIVE variables. Keep the same value.
- Check IRC channels that have an empty sender list. Fill the list or remove the override.
- Back up the state folder and the database. Pick a quiet hour, because 1 report records an update of more than 3 hours.
- Prepare SSH access to the server before you update from the Control UI.
- After the update, run
openclaw doctor. Then test 1 WhatsApp or Telegram message, 1 button, and 1 cron job.
If your agent also uses Claude Code as a backend, read the permission changes in Claude Code 2.1.325 before you combine the 2 updates.

Questions and answers
Must I install OpenClaw 2026.11.4 now?
No. The release notes do not mention a CVE or an exploited vulnerability. Upgrade in 1 to 2 weeks if you need the cron, WhatsApp, or Telegram fixes.
Why does the claude-cli backend fail on every second message?
The second message reuses the warm Claude CLI process and fails with the error "Native tool authority capture is no longer active." The fix has been in the main branch since 15 November 2026.
Does OpenClaw 2026.11.4 still ship DOMPurify 3.4.16?
No. Tag v2026.11.4 has DOMPurify 3.4.17. Versions 2026.11.2 and 2026.11.3 still have 3.4.16.
What is the difference between 2026.11.4 and the 2026.11.5 beta?
2026.11.4 is the stable release with the latest tag on npm. 2026.11.5-beta.4 is a test release. Do not install a beta on a production server.
Conclusion: your action this week
Install 2026.11.4 this week if your agent uses WhatsApp, Telegram, or cron with a direct API model. Wait if your agent uses claude-cli, and watch for the next release. If you need an upgrade with a backup and channel tests, see OpenClaw Installation Service.

