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 always shows "Codex limits unavailable" (initialize timeout) with current codex-cli
Reported by keithnyc · filed Aug 22, 2026Closed upstream on 2026-08-22 by its own reporter keithnyc, as a duplicate of #7648 (R-4641). 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
What happened
The AI agent usage panel's Codex tab always shows "CODEX LIMITS UNAVAILABLE" with the status text initialize. Local token stats (tokens by day, tokens by model) populate correctly, but the live rate-limit/plan section never loads.
Root cause
/usr/share/omarchy/bin/omarchy-agent-usage-codex starts the Codex app-server with:
codex -s read-only -a untrusted app-serverThe installed codex-cli (0.149.0) no longer accepts untrusted as a value for -a/--ask-for-approval:
$ codex -s read-only -a untrusted app-server
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]Because the subprocess exits immediately on this CLI parse error instead of speaking the app-server RPC protocol, the script's initialize RPC call (in fetch_codex_rpc()) never gets a response and hits its 8-second timeout. The resulting TimeoutError("initialize") is what surfaces as the literal text initialize in the widget's status/help line.
Expected
The Codex tab should show real rate limits, or at least a clearer error, instead of silently timing out due to an invalid CLI flag value.
Steps to reproduce
- Have current
codex-cli(0.149.0+) installed and authenticated (codex login). - Open the AI agent usage panel, switch to the Codex tab.
- Observe "CODEX LIMITS UNAVAILABLE" /
initialize. - Confirm directly:
codex -s read-only -a untrusted app-servererrors with an invalid value for-a.
Suggested fix
Update the -a value passed in fetch_codex_rpc() (in omarchy-agent-usage-codex) to one of the currently accepted values (on-request or never), or drop the flag and rely on the default.
System details
- Omarchy version: 4.0.0.r1791.ged7bae4-1
- codex-cli version: 0.149.0
- Installed via mise (
~/.local/share/mise/installs/codex/latest)
View raw text
## What happened
The AI agent usage panel's Codex tab always shows "CODEX LIMITS UNAVAILABLE" with the status text `initialize`. Local token stats (tokens by day, tokens by model) populate correctly, but the live rate-limit/plan section never loads.
## Root cause
`/usr/share/omarchy/bin/omarchy-agent-usage-codex` starts the Codex app-server with:
```
codex -s read-only -a untrusted app-server
```
The installed `codex-cli` (0.149.0) no longer accepts `untrusted` as a value for `-a`/`--ask-for-approval`:
```
$ codex -s read-only -a untrusted app-server
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]
```
Because the subprocess exits immediately on this CLI parse error instead of speaking the app-server RPC protocol, the script's `initialize` RPC call (in `fetch_codex_rpc()`) never gets a response and hits its 8-second timeout. The resulting `TimeoutError("initialize")` is what surfaces as the literal text `initialize` in the widget's status/help line.
## Expected
The Codex tab should show real rate limits, or at least a clearer error, instead of silently timing out due to an invalid CLI flag value.
## Steps to reproduce
1. Have current `codex-cli` (0.149.0+) installed and authenticated (`codex login`).
2. Open the AI agent usage panel, switch to the Codex tab.
3. Observe "CODEX LIMITS UNAVAILABLE" / `initialize`.
4. Confirm directly: `codex -s read-only -a untrusted app-server` errors with an invalid value for `-a`.
## Suggested fix
Update the `-a` value passed in `fetch_codex_rpc()` (in `omarchy-agent-usage-codex`) to one of the currently accepted values (`on-request` or `never`), or drop the flag and rely on the default.
## System details
- Omarchy version: 4.0.0.r1791.ged7bae4-1
- codex-cli version: 0.149.0
- Installed via mise (`~/.local/share/mise/installs/codex/latest`)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.