OpenClaw v2026.4.24-beta.4: Browser automation gets coordinate clicks, longer, operator field notes

The source record for v2026.4.24-beta.4 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

A small field test

The details that affect a runbook

Plugin and model infrastructure is lighter at startup

static model catalogs, manifest-backed model rows, lazy provider dependencies, and external runtime-dependency repair for packaged installs.

Check Plugin and model infrastructure is lighter at startup with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Packaged installs

preserve package-root runtime dependencies and their exported subpaths when bundled plugin runtime mirrors fall back to copying shared chunks, fixing Windows npm updates that could fail to load copied dist modules.

Use Packaged installs to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

Heartbeat

clamp oversized scheduler delays through the shared safe timer helper, preventing every values over Node's timeout cap from becoming a 1 ms crash loop. Fixes #71414.

The acceptance test for Heartbeat is idempotence under interruption: start once, stop the transport, resume, and compare the final record with the original request.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Google Meet joins OpenClaw as a bundled participant.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Exercise the named capability with a non-sensitive prompt, including the fallback or refusal result if it occurs.
4. Force a timeout or provider fallback in a disposable session and verify that no side effect is repeated.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

Packaged installs. preserve package-root runtime dependencies and their exported subpaths when bundled plugin runtime mirrors fall back to copying shared chunks, fixing Windows npm updates that could fail to load copied dist modules. Treat the fix as a boundary condition and retain the source wording beside your local result.

Heartbeat. clamp oversized scheduler delays through the shared safe timer helper, preventing every values over Node's timeout cap from becoming a 1 ms crash loop. Fixes #71414. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.4.24-beta.4 source record; the release index and model provider reference remain the references to use for migrations and support boundaries.