Evidence record / openclaw

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-openclaw-extended-stable-advanced-to-september-and-lost-its-narrower-default-distinction

Extended-stable advanced to September and lost its narrower-default distinction. Extended-stable is no longer the August 8.35 posture. September’s default cross-agent access and all-session visibility come with it. The three previously unresolved mechanisms are present: required sandbox provenance is carried into new HTTP sessions, registered background exec is cancelled on original-operator revocation, and chunk-unsafe redaction patterns use the whole-string path. Final-argument hook approval is also backported, as section 2 establishes. The published release includes repairs for upgrades from the previous extended line, service ownership, pnpm 12, and recovery.

Channel: tagged-release. Half: both. Date: 2026-10-15.

Operator consequence: Choose 9.33 for its maintained release lineage, not to obtain narrower collaboration defaults automatically. Configure tools.agentToAgent.enabled: false and narrower session visibility when that is the intended policy, and check bot admission. Use a patched Node runtime even though the manifest accepts an older one. Coverage of these named repairs is settled; this is not a claim that 9.33 contains every later October repair or feature.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-openclaw-extended-stable-advanced-to-september-and-lost-its-narrower-default-distinction

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact