Signals / omnigent profile

omnigent

Sourced signals for omnigent: release changes, governance moves, runtime shifts, and operator consequences. Each links to the run that produced it. The omnigent profile carries the current evergreen state.

August 2026

  1. 2026-08-03 / omnigent

    Omnigent's spend cap is enforced before the call, and is a downgrade gate rather than a ceiling

    • An operator who sets max_cost_usd expecting spend to stop at that number has not configured that. Spend continues past the cap on any model outside expensive_models. Set the cap and the expensive_models list together, and treat the number as the point where the session gets cheaper rather than the point where it ends.
  2. 2026-08-03 / omnigent

    The only write confinement for Omnigent's unsandboxed workers did not bind on Windows

    • The fix is on main and in no tag: v0.7.0 was published 2026-07-27, six days before the fix merged, and is still the newest release. An operator running the tagged release with unsandboxed implementer workers on a Windows runner does not have absolute-path confinement. Run main, or do not run those worker specs on Windows until the next tag.

<- All signals