OpenClaw 2026.11.6 retains subagent results through Gateway restarts
OpenClaw’s new stable version retains subagent results through Gateway restarts and does not redeliver results that have already been consumed. It also fixes the update path from version 2026.11.5.
The OpenClaw project released stable version 2026.11.6 of OpenClaw on GitHub on 19 November. OpenClaw is an open-source platform for personal AI agents. The release notes say the version brings together 189 pull requests since version 2026.11.5.
Several changes concern long-running agent jobs and the Gateway, OpenClaw’s always-on server component. Subagents are helper agents that work separately from the main agent. Their results are now retained when the Gateway restarts.
The fix prevents two faults. A finished result is no longer lost. When requester settlement resumes, OpenClaw does not redeliver an already-consumed result to the agent that requested it. OpenClaw also now distinguishes actual delivery failures from successful consumption.
The same principle runs through other fixes. Subagents and background tasks keep running when settings are edited mid-job. If a restart interrupted sending, OpenClaw delivers the final answer. Conversations that use OpenAI’s Responses API recover from conflicts in stored conversation items without repeating actions already taken.
The version also bridges the 2026.11.5 updater to the current release path. The Japanese site labmemo said the release notes do not explain when this fix helps. If an update did not complete, the site advises running the openclaw doctor diagnostics first. On Windows, OpenClaw now validates the dependencies of staged plugins correctly.
When reading configuration, OpenClaw now redacts environment credentials written inline in the configuration. Skill API keys remain SecretRef references: the configuration stores a reference to the secret, not the secret itself. The keys do not become plaintext.
On machines with limited resources, the Gateway now uses less memory at startup and in continuous operation, although the release notes give no figures. For installations that use a PostgreSQL database, the update stops before replacing the running installation if a PostgreSQL backup cannot be made.
The version is distributed through npm. On 20 November, labmemo verified that the latest tag points to it. The site said the version requires Node.js 24.16.0 or later in the 24 series and 26.1.0 or later in the 26 series, and does not support the 25 series. No Android app was released with the version.
Read more: How an agent works · Agent map