openclaw/openclaw merged commit 4aa0751 on June 29, adding target scoping to cron-based agent wakes so scheduled work reaches the intended agent surface instead of a broader wake path.
For agent operators, the morning decision is to audit scheduled and remote-control surfaces as permissions, not convenience features. Agent Pulse made the assignment concrete, and the same-day OpenClaw commits added fresh control-boundary evidence.
Facts
- The cron patch changed
cron-tool.ts, gateway cron handling, validation tests, and prompt snapshots around targeted wake behavior. - A second commit, 6ead092, required an owner for ACP runtime controls and documented the constraint.
- A third commit, 456c48f, required admin scope for browser proxy invocation and added request-scope plumbing.
Evidence
The strongest receipt is the cron patch because it turns wake targeting into tested gateway behavior. The ACP and browser-proxy commits show the same pressure on adjacent runtime controls: privileged actions need a named owner or scope before they execute.
Limits
The evidence proves source-level hardening, not a shipped release, complete security audit, or guarantee that every OpenClaw plugin surface is scoped the same way. Watch whether the next release notes and docs make these controls visible to operators before incidents force the lesson.