Release coverage
The headline is a browser-origin security fix, but the release also carries meaningful changes for Ollama onboarding, Discord thread behavior, ACP session continuity, memory indexing, and cost-aware operations.
Why this release matters
The release enforces browser origin validation for browser-originated WebSocket connections, closing a cross-site WebSocket hijacking path in trusted-proxy mode. For anyone running remote or shared setups, that is not cosmetic hardening.
First-class Ollama setup, local-or-cloud guidance, and curated model suggestions reduce the gap between “I want to try OpenClaw” and “I can actually use it.”
Discord auto-thread controls, ACP session resume, memory indexing improvements, and gateway fixes all point in the same direction: OpenClaw is being shaped for serious operators, not just hobby demos.
What changed
The top-line security fix closes a cross-site WebSocket hijacking path that could otherwise expose admin-grade access in trusted-proxy deployments. This alone makes the release worth noting in search and monitoring pages.
Local mode, cloud + local mode, browser-based cloud sign-in, and better model suggestions make Ollama a much clearer entry path for self-hosters.
Channel-level auto-archive duration for auto-created Discord threads is a small but operator-useful improvement, especially for communities using Discord as an AI workflow surface.
sessions_spawn for runtime acp now supports resumeSessionId, which matters for persistent coding flows, thread continuity, and longer-lived harness sessions.
Opt-in multimodal image and audio indexing plus Gemini embedding support pushes OpenClaw further toward richer memory search and retrieval workflows.
Telegram delivery, Discord chunking, fallback handling, gateway auth, cooldown behavior, and cron reliability all see fixes that reduce the kind of paper-cut instability operators actually notice.
Operator read
Traffic angle
OpenClaw release-note searches are high-intent. People looking for a specific version are often debugging, evaluating an upgrade, or researching what changed before they deploy. That makes release pages an unusually good bridge into monitoring, changelog, and dashboard pages.
Next move
Today the page earns search traffic and captures attention. Tomorrow the same audience is the perfect buyer for alerts, dashboards, and operator tooling around OpenClaw.