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 agents widget: "limits unavailable" — collector passes removed `-a untrusted` approval value
Reported by cstljuan · filed Sep 11, 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
The omarchy.agents panel never shows the Codex plan or rate-limit meters. The Codex usage record ends up with usageStatusText: "Codex limits unavailable" and authHelpText: "initialize".
Cause
bin/omarchy-agent-usage-codex fetches the plan/limits by spawning:
codex -s read-only -a untrusted app-serverCurrent Codex CLI (0.154.0) removed untrusted as an --ask-for-approval value — it is now only on-request / never. So the subprocess exits immediately:
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]fetch_codex_rpc() then blocks on the initialize RPC until it times out, raising TimeoutError("initialize"), which is what lands in authHelpText.
Fix
In fetch_codex_rpc() (around line 531 of bin/omarchy-agent-usage-codex):
- [codex, "-s", "read-only", "-a", "untrusted", "app-server"],
+ [codex, "-s", "read-only", "-a", "never", "app-server"],Verified the RPC handshake (initialize → account/read → account/rateLimits/read) returns the expected plan and primary/secondary rate-limit windows with -a never. After the change the Codex tab shows its plan and limit meters normally.
Steps to reproduce
- Sign in to Codex CLI (
codex login) on a ChatGPT plan and use it enough to record session activity. - Open the agents panel (default
SUPER + A). - Codex tab shows token/history stats but "Codex limits unavailable";
~/.local/state/omarchy/agents/usage/codex.jsonhas emptylimitsandtierLabel.
System
- Omarchy 4.0.0-1
- codex-cli 0.154.0
- AMD Ryzen 3 3250U w/ Radeon Vega
View raw text
The `omarchy.agents` panel never shows the Codex plan or rate-limit meters. The Codex usage record ends up with `usageStatusText: "Codex limits unavailable"` and `authHelpText: "initialize"`.
## Cause
`bin/omarchy-agent-usage-codex` fetches the plan/limits by spawning:
```
codex -s read-only -a untrusted app-server
```
Current Codex CLI (0.154.0) removed `untrusted` as an `--ask-for-approval` value — it is now only `on-request` / `never`. So the subprocess exits immediately:
```
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]
```
`fetch_codex_rpc()` then blocks on the `initialize` RPC until it times out, raising `TimeoutError("initialize")`, which is what lands in `authHelpText`.
## Fix
In `fetch_codex_rpc()` (around line 531 of `bin/omarchy-agent-usage-codex`):
```diff
- [codex, "-s", "read-only", "-a", "untrusted", "app-server"],
+ [codex, "-s", "read-only", "-a", "never", "app-server"],
```
Verified the RPC handshake (`initialize` → `account/read` → `account/rateLimits/read`) returns the expected plan and `primary`/`secondary` rate-limit windows with `-a never`. After the change the Codex tab shows its plan and limit meters normally.
## Steps to reproduce
1. Sign in to Codex CLI (`codex login`) on a ChatGPT plan and use it enough to record session activity.
2. Open the agents panel (default `SUPER + A`).
3. Codex tab shows token/history stats but "Codex limits unavailable"; `~/.local/state/omarchy/agents/usage/codex.json` has empty `limits` and `tierLabel`.
## System
- Omarchy 4.0.0-1
- codex-cli 0.154.0
- AMD Ryzen 3 3250U w/ Radeon VegaValidation
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.