OpenClaw 2026.11.1 shipped on 5 November 2026 as a stable maintenance release for 2026.10.10. It fixes channel replies, settings saves on Mac, and update recovery, but users still reproduce 3 regressions from 2026.10.10 in this version.
OpenClaw is a self-hosted AI 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 gateway. The gateway runs agents on your server and connects them to Telegram, Discord, WhatsApp, and the Control UI in a browser. A maintenance release only adds fixes on top of the previous version, without large features.
We described the 5 regressions in 2026.10.10 in our OpenClaw 2026.10.10 review. This article checks the status of all 5 on 8 November 2026 at 09:30 WIB. It then gives an upgrade decision for each server condition.
What does OpenClaw 2026.11.1 fix?
OpenClaw 2026.11.1 contains 78 PRs on top of 2026.10.10, and the table shows the 6 fixes that users notice most.
| Area | Fix | Who notices it |
|---|---|---|
| Channel replies | Telegram, Discord, and webhookWebhookAn automatic message one system sends to another the moment something happens, for example an incoming WhatsApp message.Open the glossary conversations continue to reach the agent after the request handler finishes (PR #179200, #189457). | All users who run agents in chat |
| Mac settings | A failed settings save does not overwrite secrets. Turning off Tailscale exposure does not turn off Gateway authentication (PR #187734, #187664). | Mac app users |
| Conversation history | Oversized turns keep their history. When you stop the first ClaudeClaude ProThe paid subscription for the Claude AI assistant from Anthropic. It unlocks connectors to outside tools.Open the glossary CLI turn, the next message does not start from zero (PR #191146, #181966). | Users of the claude-cli runtime |
| Update recovery | Updates recover after an updater crash or cancel. The Windows Gateway comes back after a failed verification. Automatic migration from 2026.10.7–2026.10.9 does not crash (PR #177932, #189647, #189023). | Servers with automatic updates |
| Rate limits | The wait after a rate limit follows the provider timing, not a local backoff that grows to hours (PR #180280). | Teams with tight APIAPIThe official door 2 systems use to exchange data, without anybody copying it by hand.Open the glossary quotas |
| Prompt cache | Session tool definitions stay the same across turns, so the prompt cache misses less often (PR #175309, #176167). | Teams that monitor token cost |
The release also makes 4 security rules stricter:
- ClickClack and ClawHub refuse redirects to unrelated private services. Discord CDN downloads do not get private network access (PR #190944, #190939, #191458).
- A group allowlist that you set to empty stays empty. Before this fix, Doctor could fill it again (PR #174787).
- Non-interactive Doctor checks do not download plugins without repair consent (PR #191523).
- The managed proxy does not trust the emSign ECC G3 root CA. Restart the Gateway after the update to apply this rule (PR #179249).
The sources for this section are the OpenClaw 2026.11.1 GitHub release page and the official OpenClaw 2026.11.1 release notes. The npm package openclaw@2026.11.1 was published on 5 November 2026 at 09:41 UTC.
Why did 2026.11.1 ship after 2026.11.5-beta.1?
The number 2026.11.1 is lower, but the team built it from the 2026.10.10 branch, not from the 2026.11.5 beta branch. Fixes that exist only in the beta are not in 2026.11.1.
The release notes say that 2026.11.1 covers the history from v2026.10.10 to commit 63e490a, with 78 PRs. The 2026.11.5-beta.1 package was published on npm on 4 November 2026 and adds large features, for example Knowledge Scribes and PostgreSQL state storage.
| npm channel | Version on 8 November 2026 | Use for |
|---|---|---|
| latest | 2026.11.1 | Servers that follow stable releases |
| beta | 2026.11.5-beta.1 | Test servers |
| extended-stable | 2026.9.36 | Servers that need the fewest changes |
We read these channels from npm on 8 November 2026. To change the channel, use openclaw update --channel extended-stable or openclaw update --channel beta, as the OpenClaw update documentation shows.
Which 2026.10.10 regressions are still in 2026.11.1?
All 5 regression issues are still open, and users have reproduced 3 of them on 2026.11.1.
| Issue | Status in 2026.11.1 | Evidence | Temporary step |
|---|---|---|---|
| #191841 exec fails on old glibc | Still present | The reporter reproduced the error native child reaping is unavailable on 2026.11.1 on 5 and 6 November. The reporter also wrote that glibc 2.32 is affected because the binary needs GLIBC_2.33. | Stay on 2026.10.9. |
| #191818 and #192327 automations without an inference account | Still present | A comment on 7 November says that 2026.11.1 still ships the code from before fix #180492. 1 user reports the same error on the Codex runtime with an OpenAI model. | Stay on 2026.10.9, or test 2026.11.5-beta.1 on a test server. |
| #191847 SQLite worker stops on large sessions | Still present | 1 team reproduced the problem on 2026.10.10 and 2026.11.1 with a test session of 12,460 events and an agent database of 336 MB. | Move the conversation to a new session for the same agent. |
| #191783 memory reindex does not finish | No 2026.11.1 data yet | The issue is open since 3 November 2026. | Set memory.search.remote.batch.enabled to false. |
| #191948 Windows update fails | Related fix shipped, issue open | 2026.11.1 restores the Windows Gateway task after a failed verification (PR #189647). A new automatic report, #194818, still records a gateway-recovery-verification failure on 2026.11.1. | Run openclaw gateway status --deep after the update. |
For #191818, the reporter wrote that 2026.11.5-beta.1 fixes the problem on their server. Old jobs still need 1 manual step: openclaw automations edit <jobId> --model <provider/model>@<profile> or openclaw doctor --fix.
We checked this status on GitHub on 8 November 2026 at 09:30 WIB. Some evidence comes from user reports, not from tests by the OpenClaw team.
What new problems did users report after 2026.11.1?
In the 3 days after the release, users opened new issues that name 2026.11.1, and 4 of them are important for production servers.
- #193962 update from 2026.10.10 fails: the package-update step stops with ETIMEDOUT on a large state folder. The reporter recorded that the 10-second check runs out at about 32,000 files. The fix is in 2026.11.5-beta.1, but the installed 2026.10.10 updater still runs the old check.
- #193540 Control UI does not open in Safari on iOS 18: the problem started in 2026.10.10 and continues in 2026.11.1. The automatic review on the issue says that the browser policy now targets Safari on iOS 26.2.
- #194285 Control UI session list is slow: 1 server with 39 agents and 4,243 sessions waits 4 to 10 seconds each time it opens the session list.
- 6 automatic update failure reports name 2026.11.1 between 5 and 7 November 2026. Their types are update, invalid-config, and gateway-recovery-verification.
Advisor users must also read issue #193891, which records that every Advisor review fails. The issue title says that 2026.11.1 does not fix it, but the reproduction logs come from 2026.10.10.
How does OpenClaw 2026.11.1 feel in daily use?
For daily chat, 2026.11.1 feels calmer because incoming messages are lost less often before the agent replies.
Issue #178554 records the old symptom: the gateway stores the incoming message, but the agent replies with the error Gateway is temporarily unavailable. Release 2026.11.1 closes this path for Telegram, Discord, and webhooks.
3 small changes help daily work:
- The model picker in the Control UI shows the active context budget, not only the model maximum.
- Short session links open the correct target.
- HTTP(S) attachments in Google Chat show as links next to the caption.
The difficult parts are updates and old devices. An update from 2026.10.10 can fail on a large state folder, and the Control UI does not open on an iPhone with iOS 18. The session list can also be slow on servers with thousands of sessions.
Reports on GitHub show a careful approach. 1 production team wrote on issue #191847 that it stays on 2026.10.9 until a stable release carries a verified fix.
- Business owners: the upgrade is reasonable if the agent only replies to chats and does not use claude-cli automations.
- Marketers: the Telegram, Discord, and webhook fixes help most with lead flows and quick reports.
- Developers: check glibc, the number of state files, and automation jobs before the upgrade.
Example: an online shop with a Telegram agent and a cron report
This example is an illustration, not a client case study. An online shop runs OpenClaw 2026.10.9 on an Ubuntu 24.04 VPS. The agent replies to customer chats on Telegram, and 1 cron job makes a daily sales report through the claude-cli runtime with a stored Anthropic token.
With 2026.11.1, Telegram replies become more reliable. But the daily report job can fail with the message Automation has no recorded inference account, because fix #180492 is not in 2026.11.1.
The sensible decision is to stay on 2026.10.9 on the production server. Test 2026.11.5-beta.1 on a copy of the state on a test server. Then run the report job 1 time manually.
Do you need to upgrade to OpenClaw 2026.11.1 now?
Upgrade to 2026.11.1 if your server already runs 2026.10.10 and the 3 remaining regressions do not affect it.
| Server condition | Decision |
|---|---|
| Already on 2026.10.10, channel replies sometimes fail | Upgrade to 2026.11.1 |
| Uses the Mac app | Upgrade, because a failed settings save does not overwrite secrets |
| Linux with glibc below 2.33, for example RHEL 8 and Rocky 8 | Stay on 2026.10.9 |
| claude-cli or Codex automations with a stored account | Stay on 2026.10.9, then test the beta on a test server |
| Large chat sessions, with reported agent databases of 336 MB to 1.06 GB | Stay on 2026.10.9, or move to a new session first |
| Opens the Control UI from an iPhone with iOS 18 | Use a desktop browser, because 2026.11.1 does not restore iOS 18 support |
| Needs the fewest changes | Think about the extended-stable channel, 2026.9.36 |
How do you upgrade to OpenClaw 2026.11.1 safely?
Make a verified backup first, then test the update with a dry run before the real update.
- Check the running version with
openclaw --version. - Make a backup with
openclaw backup create --verify. - Count the state files with
find ~/.openclaw -type f | wc -l. If the result is more than 30,000, plan recovery time because of issue #193962. - Run
openclaw update --dry-runand read the result. - Run
openclaw updateon the stable channel. - Restart the Gateway with
openclaw gateway restart. - Check the result with
openclaw gateway status --deepandopenclaw update status. - Send 1 test message on Telegram or Discord, then run 1 automation job manually.
If the update fails, the OpenClaw updater tries to roll back to the previous generation and saves a Markdown report. Read the steps to go back to an older version in our OpenClaw 2026.10.9 and safe rollback guide.
Operational conclusion
Upgrade to 2026.11.1 only if your server already runs 2026.10.10 and does not use old glibc, stored-account automations, or large chat sessions. Other servers must stay on 2026.10.9 until a stable release carries fix #180492 and a SQLite worker fix.
Check the issue status again before you upgrade, because the status can change in a few days. If you need help to assess a server or to upgrade OpenClaw without downtime, see the OpenClaw installation and maintenance service from Rama Digital.
Questions and answers
Does OpenClaw 2026.11.1 fix all 2026.10.10 regressions?
No. On 8 November 2026, all 5 regression issues are still open, and users have reproduced 3 of them on 2026.11.1.
Why did 2026.11.5-beta.1 ship before 2026.11.1?
The team built the 2026.11.5 beta from the main branch and built 2026.11.1 from the 2026.10.10 branch. Thus fixes in the beta are not automatically in 2026.11.1.
Do I need to restart the Gateway after the update to 2026.11.1?
Yes. The release notes tell you to restart the Gateway so that the managed proxy stops trusting the emSign ECC G3 root CA.
Are claude-cli runtime automations safe on 2026.11.1?
Not yet. agentTurn jobs with a stored Anthropic account can still fail with the message Automation has no recorded inference account, and the fix is only in 2026.11.5-beta.1.
Can I open the 2026.11.1 Control UI from an iPhone?
Yes, if the iPhone runs iOS 26.2 or later. Safari on iOS 18 cannot open the Control UI since 2026.10.10, and 2026.11.1 does not change this.
