The OpenClaw project released version 2026.11.3 on GitHub at 18:53 UTC on 10 November. The Japanese blog Labmemo describes OpenClaw as an open-source project for building AI assistants that run on the user’s own machine. Its Gateway component runs continuously and relays requests from the CLI and messaging channels.

The most important change concerns subagents. A subagent is a run started by another agent run that works in the background in its own session. When a subagent’s task is marked private, its completion result no longer appears in the chat reply streamed to the user.

A parent agent can now also move on to replacement work after cancelling a subagent task: the cancelled task’s completion receipt no longer blocks the switch.

The program also reports a failed tool call that received no response. Previously, a user-facing turn could end silently as a success.

Credentials are isolated more tightly

The release includes several fixes that stop credentials and secrets ending up in the wrong place. Cached plugin results are scoped to the credentials of the connection they were fetched for. Managed Signal daemons and bundled language servers no longer inherit unrelated Gateway secrets. Environment variable credentials written directly into the configuration are masked when the configuration is read. When migrating a workspace, the program verifies the certificate before sending credentials or data. When the sandbox is mandatory, image previews stay within permitted folders even in Full Access mode.

Other fixes speed up Gateway start-up and cover scheduled jobs, update rollback and Anthropic usage-limit errors, among other things. The release notes say there are no new configuration options or features.

Performance test waiver approved

A commit by OpenClaw developer Dallin Romney states that Romney approved a waiver earlier on release day so that a failed Kova performance test would not block the release of version 2026.11.3. The waiver followed a failed measurement of the previous release candidate. Its memory usage was 1,809.8–1,819.6 megabytes against a limit of 1,800 megabytes, and peak Gateway CPU usage reached 433.7 per cent against a limit of 340 per cent. The commit says the old measurement is not valid for approving the new candidate, so the figures cannot be used to judge the released version’s performance. The waiver does not cover other tests: their failure, missing or interrupted results and other release checks would still block the release.

Separate Gateway release for the September line

Version 2026.9.37 followed about two hours later. It contains only the Gateway and is an extended-stable release from the September maintenance line, which has already been retired. The maintainers decided on the release separately, the release notes say. The notes describe the version as late-September OpenClaw with critical security updates and reliability and performance fixes added. For example, photos and screenshots taken by paired devices are no longer automatically attached to replies.

Version 2026.11.3 is available from GitHub and the npm package manager, where it was the default version when Labmemo checked. The release notes tell users to keep following the release work for the Android app, and Labmemo found no record of the app being released.