OpenClaw 2026.10.10 shipped on 3 November 2026 with 3,028 PRs from 454 contributors. The release adds the Details panel, Advisor, split speech mode, work in a folder on another computer, MCPMCPA standard that lets an AI program use your tools and data under clear permissions.Open the glossary Relay for ChatGPT and ClaudeClaude ProThe paid subscription for the Claude AI assistant from Anthropic. It unlocks connectors to outside tools.Open the glossary, and automations that start from MCP events. Delay the upgrade on production servers if you use RHEL 8, claude-cli automations with a stored token, or chat sessions with an 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 database above 1 GB.
OpenClaw is a self-hosted AI agent gateway. The gateway runs agents on your server and connects them to Telegram, WhatsApp, and the Control UI in the browser. MCP (Model Context Protocol) is an open protocol that connects agents to other tools and apps. The previous release focused on security patches and rollback. Read our summary of OpenClaw 2026.10.9 if your server does not run that version yet.
What changed in OpenClaw 2026.10.10?
OpenClaw 2026.10.10 adds 6 main features, and 4 of them stay off until you turn them on.
| Feature | Function | Default | Important limit |
|---|---|---|---|
| Details panel | Collects session data, task progress, PRs, and automations beside the chat | On | Opens automatically only on a wide chat pane |
| Advisor | Checks agent work and suggests a correction when the agent repeats a failed approach or drifts from the request | Off (Settings → System → Labs) | Uses extra model calls and can miss a problem |
| Split speech mode | Browser Talk uses the same chat model, with separate transcription and speech services | Off | No realtime voice switching and no camera input |
| Folder on another computer | An agent on the server works directly in a folder on a laptop that connects as a node | On | Attachments and the Files panel are not available |
| MCP Relay | ChatGPT or Claude controls OpenClaw conversations without an open Gateway port and without the Gateway password | Off (plugin) | The relay can read the content that passes through it |
| MCP event automations | An automation starts when an MCP server sends an event, not when a timer checks | Off | Only the OpenAI webhookWebhookAn automatic message one system sends to another the moment something happens, for example an incoming WhatsApp message.Open the glossary profile, and it needs a public HTTPS callback |
The table comes from the official OpenClaw 2026.10.10 release notes and the GitHub release page. The npm package openclaw@2026.10.10 was published on 3 November 2026 at 02:26 UTC.
The release also closes 2 permission paths. A plugin can no longer change the arguments of an approved tool call without a new approval (PR #142700). A generic node call can no longer bypass a denied browser tool (PR #179880). Credentials in process cleanup errors are now masked before they show (PR #170941).
Plugin authors have a new deadline. Move deprecated synchronous SDK calls to the async versions by 31 December 2026.
How does OpenClaw 2026.10.10 feel in daily use?
The largest change is on the chat screen, because task progress moves to the Details panel beside the conversation.
Before, the progress bar and the PR bar stacked above the message box. Now, Details opens beside the conversation on a wide screen and closes when the pane gets narrow. The Subagents panel shows running and finished workers, and you can read their transcripts without changing them.
If a run stops after tool use without a final reply, its progress stays visible with an Interrupted label. When a reply fails, the Control UI shows a notice with recovery actions. This notice stays after a reload.
Advisor fits long tasks, for example a refactor or multi-step research. The official documentation says Advisor uses extra model calls, can miss a problem, and can suggest an unnecessary change. Advisor does not run tools and does not approve actions, so calculate the token cost before you turn it on for all agents.
Example scenario: agent on a VPS, files on a laptop
A marketing team of 3 people runs OpenClaw on a VPS. The weekly ad report is in a folder on the admin laptop. With the folder feature, the agent on the VPS works directly in that laptop folder and does not copy the folder to the server.
The limits are clear. The laptop must connect to the Gateway as a node, and this conversation has no attachments and no Files panel. Set nodeHost.workerRuns.folders on the laptop to the folders that the agent can use, for example the report folder only. An empty list turns the feature off.
- Business owners: the Details panel lets you monitor agent tasks without reading logs.
- Marketers: the folder feature and MCP Relay make work from ChatGPT or Claude easier.
- Developers: Advisor and the Subagents panel help you supervise many agents, but check the regressions below first.
Which regressions have users reported?
In the 24 hours after the release, users opened GitHub issues for 5 problems that can stop production agents.
| Issue | Who is affected | Symptom | Temporary workaround |
|---|---|---|---|
| #191841 exec fails | Linux with glibc below 2.31, for example RHEL 8, Rocky 8, and Alibaba Cloud Linux 3 | All exec tools and cron scripts fail with the error native child reaping is unavailable | Stay on 2026.10.9. The manual patch in the issue is not an official fix. |
| #191818 and #192327 claude-cli automations | Agents on the claude-cli runtime with a stored Anthropic token profile, and cron jobs that a plugin creates | Each agentTurn job fails in less than 1 second with Automation has no recorded inference account | Fix #180492 is on main since 22 October 2026, but it is not in 2026.10.10. Stay on 2026.10.9. |
| #191847 SQLite worker crashes | Large chat sessions. The reporter used a Telegram session with about 127,000 events and a 1.06 GB agent database | The 512 MB SQLite worker crashed 13 times in about 50 minutes, and 11 of 11 turns failed | None yet. Test the upgrade on a copy of the state first. |
| #191783 memory reindex hangs | Users of OpenAI embeddings with memory.search.remote.batch.enabled=true | openclaw memory index never finishes | Set that option to false, then run the reindex again. |
| #191948 Windows update fails | 1 report of an update from 2026.10.8 on Windows | The gateway-recovery-verification phase fails and the Gateway stops | Run openclaw gateway status --deep, then start the Gateway again. |
Status on 4 November 2026 at 09:30 WIB: all 5 issues are still open. The automated reviewer on issue #191841 did not verify the glibc 2.31 limit. But that reviewer confirmed that the main code still refuses execution when the native reaper does not load.
Do you need to upgrade to OpenClaw 2026.10.10 now?
Upgrade now only if your server does not match the regression conditions above and you need the new features.
| Server condition | Action |
|---|---|
| RHEL 8, Rocky 8, CentOS 8, or glibc below 2.31 | Delay. Stay on 2026.10.9. |
| Cron automations on the claude-cli runtime with a stored Anthropic token | Delay until fix #180492 is in a stable release. |
| Long-lived chat sessions with an agent database above 1 GB | Test on a copy of the state first. |
| Ubuntu 22.04 or 24.04, no claude-cli, normal sessions | Upgrade with the steps below. |
| New production installation | Think about the extended-stable channel, which points to 2026.9.36 on 4 November 2026. |
Do not move to the extended-stable channel from 2026.10.x without a recovery plan. The OpenClaw documentation says that older versions cannot open newer database schemas.
How do you upgrade OpenClaw safely?
Make a verified backup first, check the glibc version, then test 1 exec tool and 1 automation after the update.
- Check the version and update channel:
openclaw update status --json. - Check the glibc version:
ldd --version. Delay the upgrade if the number is below 2.31. - Make a verified backup:
openclaw backup create --output ~/Backups/openclaw --verify. This command runs while the Gateway continues to serve. - See the update plan without changes:
openclaw update --dry-run. - Run the update:
openclaw update. - Check Gateway health:
openclaw gateway status --deep. - Test 1 exec tool from chat, for example the
uptimecommand. - Wait for 1 scheduled automation to run, then check the result in the Automations menu.
To go back to the old version, restore the pre-migration database together with the matching binary. Do not only lower the version marker. If you use MCP event automations, remove the event jobs before the downgrade. Sources: the OpenClaw update guide and the OpenClaw backup guide.
What are the risks of MCP Relay and MCP event automations?
Both features are off by default, and both open a new path from outside apps to your agent.
- MCP Relay: the relay can read the content that passes through it. Full role access can include administration and approvals. Give access only to apps and relays that you trust, then revoke access in Connected apps when you do not use it. Details are in the MCP Relay documentation.
- MCP event automations: this feature needs a public HTTPS callback. Forward only the path
/plugins/mcp-events/callback/to the Gateway, and do not expose other parts of OpenClaw. An event that is lost at the sender may not be recoverable. Details are in the MCP Events documentation.
If you still need to choose an MCP client for your team, read our comparison of MCP clients in Claude, ChatGPT, Gemini, OpenClaw, and Hermes.
Operational conclusion
Keep production servers on OpenClaw 2026.10.9 until the exec and claude-cli automation regressions have an official fix. On an Ubuntu test server, upgrade now with a verified backup, then try the Details panel and Advisor on 1 agent first. If you need help to install or maintain OpenClaw, see the OpenClaw installation service from Rama Digital.
Questions and answers
When did OpenClaw 2026.10.10 ship?
The npm package openclaw@2026.10.10 was published on 3 November 2026 at 02:26 UTC. The GitHub release page went live at 03:22 UTC on the same day.
Does Advisor in OpenClaw add cost?
Yes. Advisor uses extra model calls each time it reviews a task. The feature is still experimental, so turn it on for 1 agent first and monitor token use.
Why do exec tools fail after the upgrade to 2026.10.10?
Issue #191841 reports the error native child reaping is unavailable on Linux with glibc 2.28, for example RHEL 8. Check the glibc version with ldd --version, then restore the 2026.10.9 backup until an official fix ships.
Is MCP Relay safe to connect ChatGPT to OpenClaw?
MCP Relay does not open the Gateway port and does not share the Gateway password. But the relay can read the content that passes through it, so use only relays and apps that you trust.
How do you fix a memory reindex that hangs?
Run openclaw config set memory.search.remote.batch.enabled false, then run the reindex again. The reporter of issue #191783 wrote that the reindex then finished normally.
