self.md radar — 2026-10-16
a 503 that may be safe to repeat
A sandbox that wakes after idling needs to say whether a request ever reached it. A permissions rule needs to mean the same thing to the scanner and the agent runtime. Today’s release notes are full of those small, expensive distinctions.
1. OpenSandbox adds wake-on-access for paused sandboxes
OpenSandbox 1.2.0-rc.1
adds an opt-in idle policy for its fast sandbox runtime: pause after a chosen timeout, then wake when traffic arrives. The setting is deliberately narrow: idleTimeoutSeconds runs from 30 to 86,400 seconds; onIdle must be pause; an optional active probe can register real activity.
The useful part sits in the failure path. SDKs retry only a 503 carrying OpenSandbox-Wake: expired, which means the gateway parked the request before it was forwarded. A plain 503 remains a plain 503. That distinction stops a wake-up retry from becoming a second command with the same side effects.
reading: OpenSandbox 1.2.0-rc.1
2. Browser Use’s OpenAI driver leaves several doors shut
Browser Use 0.13.13 ships an OpenAI browser-tool driver after 0.13.12 introduced the integration. It offers 18 default tools and six optional actions across a local browser, Browser Use Cloud, or a borrowed session; this release also fixes temporary empty Cloud-tab URLs and coordinates on scaled displays.
The earlier release is unusually clear about what did not come with the adapter: no uploads, downloads, scoped reads, console or network diagnostics, or Bash. The integration is browser-shaped, not general computer use.
reading: 0.13.13 release · 0.13.12 integration notes
3. agent-config-audit follows the runtime, not the spelling
The latest agent-config-audit update
adjusts its checks to current Claude Code behaviour. Bash(rm:*) and similar rules now count as wildcards because Claude treats :* as trailing *; wrappers such as timeout 30 and VAR=value no longer hide the command underneath.
The same pass learned to stop calling dontAsk a prompt bypass. It denies by default. Another check catches hook events that claude plugin validate --strict accepts in a manifest but says will be ignored at runtime.
reading: current rule-model commit · repository and scan scope
4. OpenCode turns version 2 into a separate decision
OpenCode 1.19.2
changes its updater so a 1.x installation is offered only 1.x releases in the ordinary path. Moving to OpenCode 2 now requires /update or opencode upgrade --major; the install script also refuses to install 2.x.
The split is literal: routine updates stay on 1.x; version 2 requires a major-upgrade command. That avoids turning a migration with provider settings and local configuration into background upkeep.
reading: OpenCode 1.19.2
Related self.md routes
- Personal AI OS tools — the control-plane map for personal agents, receipts, memory, and tools
- AI coding assistants — compare coding workbenches by review surface, permissions, cost, logs, and escape hatches
- Browser agents — where browser automation helps, where it lies, and how to keep it observable