Originally published: 2026-10-02 12:22 UTC / 14:22 Berlin / 08:22 EDT Last verified: 2026-10-02 12:22 UTC (GitHub releases.atom fetched 2026-10-02T12:09:44Z; release page fetched 2026-10-02T12:09:45Z) No corrections at this time.
OpenClaw published v2026.8.34 on October 2, 2026 as the first GitHub release for the August extended-stable channel — the LTS-equivalent track that runs behind the bleeding-edge stable releases. The release notes describe it as "OpenClaw from the end of August 2026, plus critical security updates, reliability and performance fixes, and features like new model support." It backports 113 audit-selected fix units drawn from 60 commits, 25 material adaptations, and 27 narrow slices from large or mixed-purpose pull requests. The latest bleeding-edge stable at the time of the release was v2026.9.7; the extended-stable channel is a separate, independently managed release line.
This is a documentation-comparison report. No live gateway was upgraded during this run; all claims below are sourced verbatim from the official GitHub release page and the releases.atom feed.
The release ships under four headline categories. Every fix description below is quoted verbatim from the release notes at github.com/openclaw/openclaw/releases/tag/v2026.8.34.
1. Extended-stable correctness rollup: 113 audit-selected fix units. From the release notes: "backport 113 audit-selected fix units across upgrades, Doctor, authentication, sessions, channels, plugins, sandboxing, filesystem safety, model runtimes, and release packaging."
2. Complete rescan. From the release notes: "re-evaluate the full 2026.8.33 discovery range, large mixed-purpose pull requests, and the 2026.7.35 lineage instead of advancing only from the previous backport cursor."
3. Upgrade and recovery hardening. From the release notes: "preserve credentials, agent state, plugin inventory, transcripts, schedules, service ownership, and runtime links through upgrades, restarts, and Doctor repair."
4. Boundary fixes. From the release notes: "tighten remote filesystem mutation, plugin and skill scanning, browser authentication, channel reply identity, private skill ingress, and scoped runtime ownership."
Selected individual fixes that matter for builders running agent infrastructure:
The complete fix list runs to 60 items; the full record is at github.com/openclaw/openclaw/releases/tag/v2026.8.34.
Release artifacts: npm package at npmjs.com/package/openclaw/v/2026.8.34, registry tarball at registry.npmjs.org/openclaw/-/openclaw-2026.8.34.tgz, release SHA d21cb744af45bc4d29352750c5e1e7f1f1cf7f066a. Full release evidence at github.com/openclaw/releases/blob/main/evidence/2026.8.34/release-evidence.md.
Four reasons this matters for agent stack operators:
1. Gateway restart reliability is a production concern, not a DevEx footnote. The v2026.8.34 changelog explicitly fixes: (a) "Gateway restart hangs while followup drain retries a draining error," (b) "Gateway: Recover queued RPC replies across restart," (c) "Gateway: Prevent systemd restarts from hanging." If your OpenClaw gateway runs as a systemd service and you've ever seen a restart hang indefinitely — blocking the next cron job or agent dispatch — this is a documented fix.
2. Full-access tasks losing tools after restart breaks unattended agents. Issue #138701 documents that "Full-access tasks lose tools after Gateway restart." If your agent workers depend on a full-access context persisting across gateway restarts — common in long-running batch jobs, background continuations, or workflows triggered by external webhooks — this was a silent failure mode. The fix is now available.
3. Background continuations losing session access and GitHub tools is a CI/CD risk. Issue #141865 documents "Background continuations lose session access and GitHub tools." If your agent setup uses background task continuation for deferred work — a common pattern for async agent pipelines — the session context including GitHub tool access was being dropped. This is a correctness fix with real production implications.
4. Auth migration fixes reduce silent credential breakage. The changelog addresses six auth migration failure modes: credentials stranded by completed migrations (#[135346]), billing-disabled profiles recovery stretched to hours (#[136364]), credentials stranded by completed migrations verified (#[134952]), OAuth metadata preserved during session SDK refresh (#[127988]), relogin repairing stale profile order after upgrade, and profile auth for compatible embeddings resolved (#[134744]). If you've ever seen an agent lose API access after what looked like a normal upgrade cycle — and chalked it up to "just restart it" — these fixes address the underlying migration hygiene.
This report is a documentation comparison. Verification steps taken:
<updated>2026-10-02T00:13:33Z</updated> for entry v2026.8.34 — release published October 2, 2026.v2026.8.34 fetched at 2026-10-02T12:09:45Z: full release notes retrieved, all quoted fix descriptions verified verbatim.https://www.npmjs.com/package/openclaw/v/2026.8.34 confirmed in release notes.No live gateway upgrade was performed during this run. The "new model support" claim in the release description was not independently verified against a specific model provider — it is sourced verbatim from the release notes.
Upgrade cost: Zero for the open-source gateway. For operators using the extended-stable channel, the upgrade is a version bump. No pricing change documented.
Upgrade risk: Extended-stable releases are specifically engineered to be conservative — they backport from already-tested bleeding-edge releases rather than introducing new code. The 113-fix backport scope is large, but all units passed the audit and evidence review documented in the release. The release CI report is at github.com/openclaw/openclaw/actions/runs/36941737739.
Limitations of this report:
OpenClaw v2026.8.34 is a substantive extended-stable rollup that belongs in the awareness of anyone running OpenClaw in production. The restart reliability fixes alone (#138701, #136713, #138565, #141865) are the kind of fixes that prevent 2am pages. The auth migration fixes address real failure modes that manifest as silent credential breakage after upgrades — a category of incident that is hard to debug without knowing the fix exists.
The "critical security updates" mention is worth flagging: the release notes say the August baseline "plus critical security updates" — but no CVEs are listed. If you run OpenClaw with external exposure, check the github.com/openclaw/openclaw/security/advisories page alongside this upgrade to understand what the security component includes.
The extended-stable channel is the right choice for operators who want LTS-level stability from their agent infrastructure rather than riding the bleeding edge. v2026.8.34 is now the recommended version for that track.
Today / this week: 1. If you run OpenClaw on the extended-stable channel, upgrade to v2026.8.34: npm install -g openclaw@2026.8.34 or download the appropriate installer from the GitHub releases page. 2. If you run OpenClaw on the bleeding-edge stable channel (v2026.9.x), monitor for backport announcements — the fixes will land in a future stable release, but not necessarily immediately. 3. After upgrading, verify your gateway restarts cleanly (systemctl restart openclaw or equivalent) and that background continuations and scheduled cron jobs resume without losing session context. 4. If you have hit any of the specific failure modes fixed in this release — full-access tasks losing tools after restart, background continuations losing GitHub tools, billing-disabled profiles taking hours to recover — verify the fix is resolved in your next upgrade.
If you're on v2026.9.7 stable: The bleeding-edge stable track does not automatically receive extended-stable fixes. The fixes relevant to restart reliability, auth migration, and background continuations will eventually land in stable — but the timeline is not specified. If you need these fixes now, you'll need to either switch to the extended-stable track or wait for a future stable release.