Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Codex usage widget shows initialize after Codex CLI 0.150.0 update
Reported by tycameron · filed Sep 4, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #8460 (R-1406). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Summary
The omarchy.agents Codex widget shows local usage, but rate limits are unavailable and its help/status text is initialize.
Environment
- Omarchy:
4.0.1-1 - Codex CLI:
0.150.0
Reproduction
codex -s read-only -a untrusted app-serverOutput:
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]Omarchy's collector invokes this obsolete flag in /usr/share/omarchy/bin/omarchy-agent-usage-codex:
[codex, "-s", "read-only", "-a", "untrusted", "app-server"]Because the process exits before the first app-server RPC request, the collector catches a timeout and writes authHelpText: "initialize", which is misleading. Local stats still work; only account/rate-limit information fails.
Expected behavior
Use a currently supported Codex approval policy (or omit the flag), and report the actual startup error if initialization fails.
View raw text
## Summary The `omarchy.agents` Codex widget shows local usage, but rate limits are unavailable and its help/status text is `initialize`. ## Environment - Omarchy: `4.0.1-1` - Codex CLI: `0.150.0` ## Reproduction ```bash codex -s read-only -a untrusted app-server ``` Output: ```text error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>' [possible values: on-request, never] ``` Omarchy's collector invokes this obsolete flag in `/usr/share/omarchy/bin/omarchy-agent-usage-codex`: ```python [codex, "-s", "read-only", "-a", "untrusted", "app-server"] ``` Because the process exits before the first app-server RPC request, the collector catches a timeout and writes `authHelpText: "initialize"`, which is misleading. Local stats still work; only account/rate-limit information fails. ## Expected behavior Use a currently supported Codex approval policy (or omit the flag), and report the actual startup error if initialization fails.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.