Signals

2026-08-20 / Codex

Guardian V2 is in Codex 0.148.0 and the feature flag is still off

Edited by Michael Ruescher

After ten days with npm latest frozen at 0.147.0, rust-v0.148.0 cut stable on 2026-08-18 (381 commits vs 0.147.0) and rust-v0.149.0 cut on 2026-08-20 (242 more). The 0.148.0 tree contains guardian-v2. At that tag Feature::GuardianV2 is UnderDevelopment and default_enabled false; Feature::GuardianApproval is Stable and default_enabled true. The extension returns unless both flags are on. The marketed New Features list does not name Guardian V2. npm latest is 0.149.0.

What this changes for operators

  • Upgrade the default install to 0.149.0 if you stayed on 0.147.0. Treat it as a large upgrade, not a point release.
  • Do not plan as if a model now gates every tool call. Turning Guardian V2 on is a feature flag. If you enable it, prefer 0.149.0: scoring errors fail open in 0.148.0. Search configs for untrusted before 0.149.0. Evidence that would settle residual: a config dump from a stock 0.149.0 install showing features.guardianv2 enabled, or vendor docs stating the default.
  • If you embed the SDK, the vendor's own 2026-08-20 post says the app owns approvals. That is the opposite of an invisible in-harness reviewer. Reconcile which seat you actually run.

Signal metadata

Source findings

Featured in

Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0

Schema: bitter.frontier_signals.v0 / ID: 2026-08-20-codex-guardian-v2-in-the-tag-off-by-default

Research evidence and publication history are open in the repository.