Evidence record / omnigent
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-omnigent-ci-usage-telemetry-suppression-is-repaired-after-the-stable-cut
CI usage telemetry suppression is repaired after the stable cut. The main-only repair preserves CI markers and explicit DISABLE_TELEMETRY/DO_NOT_TRACK opt-outs when launching a local background server. Usage suppression is evaluated in the server’s startup environment. The maintainer explanation describes automated jobs being counted as users when daemon startup lost their context. An already running server does not adopt a later caller’s CI environment.
Channel: main-unreleased. Half: both. Date: 2026-10-13T13:18:02Z merged.
Operator consequence: For CI suppression, inspect and control the server launch environment, not just the invoking job’s variables. Track the first containing stable release; this repair is not in the 0.18.0 wheel. Restart the relevant server with the desired environment when adopting it.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-omnigent-ci-usage-telemetry-suppression-is-repaired-after-the-stable-cut
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-13-omnigent-ci-usage-telemetry-suppression-is-repaired-after-the-stable-cutgithub.com/omnigent-ai/omnigent/commit/3aed65725827d02451ed59afd8d94d43ba5de5d7tagged commit file2026-10-13-omnigent-ci-usage-telemetry-suppression-is-repaired-after-the-stable-cutomnigent-ai/omnigent / omnigent/cli.py#L3599-L3630
Versioned source: run artifact