The Plugin Catalog Had to Go
For months, OpenClaw maintained a hand-curated list of community plugins directly in its documentation. Each entry included a description, npm package name, and GitHub link. It was useful when the ecosystem had a handful of extensions. It was unsustainable at scale.
The problem with static catalogs is that they rot. A plugin gets renamed, a repository goes private, a package gets deprecated — and the documentation silently becomes wrong. The OpenClaw team removed nine of these entries in one pass, replacing the entire section with a pointer to ClawHub and a CLI search command.
This is the right call. ClawHub already indexes published plugins with metadata, version history, and security scan results. Duplicating that information in a markdown file meant two sources of truth that inevitably diverged. The consolidated page now focuses on what static docs do well: explaining how to discover plugins, how to evaluate them, and how to publish your own with a clear quality-bar checklist.
Slack Operators Finally Get the Threading Documentation They Needed
OpenClaw's Slack threading behavior has been a persistent source of confusion. The core question — “if I reply in a thread, does the bot keep that conversation separate?” — wasn't clearly answered in the documentation. Now it is.
Thread replies use the parent message's thread_ts as a session suffix, meaning each thread gets its own conversation context. Setting replyToMode="off" disables outbound threading — the bot replies in the channel instead of the thread — but it does not flatten inbound sessions. These are two different behaviors that were previously conflated in the documentation.
The Socket Mode section also got a meaningful expansion. The reconnection behavior is now documented with specific numbers: 2-second initial backoff, 30-second maximum, 12 retry attempts before giving up. Per-account overrides require all socket tuning fields to be present, not just the ones you want to change. And the docs now explicitly state that socketMode configuration keys are silently ignored when the bot is running in HTTP mode — a gotcha that has tripped up operators migrating between transport modes.
Six New Troubleshooting Scenarios
The Slack troubleshooting section went from covering the basics to addressing specific failure modes operators actually hit. Socket Mode connection failures now walk through token validation and SecretRef resolution. HTTP mode has webhook path configuration checks. Slash commands get Slack permission error messages that operators can match against their app configuration. And messages.groupChat.visibleReplies finally has a configuration example instead of just a description.
The gateway configuration reference also picks up a small but useful clarification: the clientPingTimeout defaults to 15,000 milliseconds, and the companion settings serverPingTimeout and pingPongLoggingEnabled are only passed when explicitly configured. The kind of detail that saves an operator twenty minutes of debugging.
The Changelog Mishap
While preparing the 2026.5.14 release, a commit relabeled the unreleased changelog section before the previous 2026.5.12 notes had been properly positioned. The result: features that had already shipped in 5.12 appeared under the 5.14 heading, making it look like the next release was bigger than it actually was. A quick fix restored the heading boundary and moved the notes back to where they belonged. Not dramatic, but the kind of version hygiene that matters when downstream operators are tracking what shipped when.
Three documentation updates in one day. The plugin catalog consolidation is the most significant — it signals that OpenClaw is treating ClawHub as the real front door for its extension ecosystem, not a sidecar to hand-maintained markdown files. The Slack threading clarity was overdue. And the changelog fix is a reminder that release engineering has a lot of moving parts, even for projects with 40-check CI pipelines.