Agent DailyAgent Daily
releaseintermediate

[Release] openclaw/openclaw v2026.5.12: openclaw 2026.5.12

By github-actions[bot]github
View original on github

OpenClaw v2026.5.12 is a maintenance release focused on dependency externalization, UI improvements, and stability fixes. Key changes include externalizing AWS Bedrock and plugin dependencies to reduce bloat, adding persistent auto-scroll controls in the UI, implementing ACP fallback backends, and fixing numerous issues across Telegram, Slack, authentication, and session management. The release addresses 40+ bug fixes spanning security, performance, and user experience improvements.

Key Points

  • Externalize Bedrock, Slack, OpenShell, and Anthropic Vertex as optional dependencies so core installations don't pull unnecessary AWS SDK or provider packages
  • Add persistent auto-scroll mode selector in Control UI/WebChat with three options: keep current behavior, always follow streaming, or manual control via New messages button
  • Implement ACP fallbacks feature allowing configured backup runtime backends when primary backend is unavailable, improving reliability
  • Fix Telegram polling stability by moving ingress to isolated worker with durable local spool, preventing event-loop stalls
  • Improve security by blocking Windows USERPROFILE in sandbox and restricting provider credentials to structured env SecretRefs instead of broad env var inference
  • Fix subagent model scoping by applying agents.defaults.subagents.model before target agent primary models during session spawning
  • Preserve HTML formatting and message metadata through lazy delivery and rich content across multiple delivery paths (follow-up, heartbeat, cron, ACP)
  • Enhance CLI/onboarding by forwarding provider-specific auth flags through wizard to skip redundant prompts in non-interactive environments
  • Fix OAuth profile handling by reclaiming dead-owner stale file locks and classifying token-refresh failures as authentication errors for proper user guidance
  • Improve macOS companion security by requiring system TLS trust before certificate pinning and honoring explicit gateway.remote.tlsFingerprint 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
Quality

Concepts