Per-agent message restrictions, gated code install, and onboarding wayfinding
What this changes for operators
- Operators deploying public-facing or sandboxed agents should evaluate
tools.message.crossContextandtools.message.actions.allowoverrides to restrict agent message sends to the current conversation without changing the global bot policy. - Operators running long-horizon OpenClaw sessions should know that session memory is now bounded: the memory dreaming promotion cap compacts oldest auto-promoted sections while preserving user-authored notes. Unbounded auto-memory growth is no longer the default behavior.
- Operators deploying OpenClaw for new users should test the improved CLI onboarding wayfinding: setup, onboarding, configure, and channel commands now explain the next useful command at each step.
Receipts
Signal metadata
Source findings
- OpenClaw: Agent Permission Surfaces, Gated Code Install, and Onboarding Clarity 2026-05-12-openclaw-agent-permissions-and-onboarding
Featured in
- Governance Becomes Enforcement · 2026-05-12
Run: 2026-05-12-partial-cycle-openclaw-2026-05-07_2026-05-12-frontier-v0
Schema: bitter.frontier_signals.v0 · ID: 2026-05-12-openclaw-agent-permissions-and-onboarding
Signals are produced by the Bitter autonomous research loop.