releaseintermediate
[Release] openclaw/openclaw v2026.5.12-beta.8: openclaw 2026.5.12-beta.8
By steipetegithub
View original on githubOpenClaw v2026.5.12-beta.8 introduces significant improvements to dependency management by externalizing AWS SDK and plugin dependencies, enhances user control with persistent auto-scroll modes in the UI, adds fallback runtime backends for ACP, and fixes numerous issues across Telegram integration, session management, security sandboxing, and media handling. The release focuses on performance optimization, security hardening, and improved reliability across multiple subsystems including CLI, gateway, and agent spawning.
Key Points
- •Externalize AWS Bedrock and plugin dependencies (Slack, OpenShell, Anthropic Vertex) so core installations avoid unnecessary SDK dependencies unless explicitly used
- •Add persistent auto-scroll mode selector in Control UI/WebChat to let users choose between following streaming output, staying near-bottom, or manual scrolling with New messages button
- •Implement ACP fallbacks feature allowing configured backup runtime backends when primary backend is unavailable, improving system resilience
- •Fix subagent model scoping by applying `agents.defaults.subagents.model` before target agent primary models during session spawning
- •Improve Telegram reliability by isolating bot API polling in a durable worker thread and preserving HTML formatting through lazy delivery
- •Enhance security by blocking Windows USERPROFILE credentials in sandbox and preventing unrelated environment variables from becoming provider credentials
- •Fix session history consistency by carrying monotonic transcript message sequences through live updates and refreshing stale SSE history
- •Restore deprecated plugin SDK memory-core package subpath as alias for backward compatibility with published memory companion plugins
- •Improve reply delivery across all channels by treating rich presentation, interactive controls, and channel-native payloads as outbound content
- •Fix macOS companion TLS certificate pinning to require system trust before first-use direct gateway connections and honor explicit fingerprint configuration
Found this useful? Add it to a playbook for a step-by-step implementation guide.
Workflow Diagram
Start Process
Step A
Step B
Step C
Complete