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.
agents: Codex tab never shows — account/read RPC exceeds 4s timeout (codex-cli 0.157), no local stats without ~/.codex/sessions
Reported by AlexanderMavrov · filed Sep 30, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
Intel i9-11900, Intel UHD 750 + NVIDIA GTX 960, Omarchy 4.0.4-1, codex-cli 0.157.0 (ChatGPT Plus login)
What's wrong?
The omarchy.agents bar widget never shows the Codex subscription, although codex is signed in and working. Only Claude appears.
~/.local/state/omarchy/agents/usage/codex.json always ends up as:
"limits": [], "totalPrompts": 0, "totalSessions": 0, "activeDays": 0,
"usageStatusText": "Codex limits unavailable", "authHelpText": "account/read"so providerHasData() in Main.qml is false and the tab is hidden. There are two independent causes:
1. `account/read` exceeds the 4 s RPC timeout
fetch_codex_rpc() in bin/omarchy-agent-usage-codex sends account/read (timeout 4 s) before account/rateLimits/read. With codex-cli 0.157.0 the account/read response consistently takes ~31 s, and it blocks the following request too, so TimeoutError("account/read") is raised and no limits are recorded. The delay reproduces with a clean CODEX_HOME containing only auth.json, and network access to chatgpt.com is fine (~20 ms over IPv4).
Minimal repro (same calls as the collector, longer timeouts):
initialize -> 0.1 s
account/read -> 31 s
account/rateLimits/read -> 31 s (answered right after account/read)Sending only account/rateLimits/read (skipping account/read) returns in ~0.9 s with primary/secondary windows and planType: "plus". Since plan already prefers limits.planType, dropping account/read (or making it optional / non-blocking) would fix the limits.
2. No local stats with current Codex session storage
~/.codex/sessions/ doesn't exist on this machine; current Codex (CLI + desktop app) keeps thread/rollout state in ~/.codex/state_5.sqlite (tables threads, rollout_migration_state, …). The collector only scans the native session files, so local stats are always zero, and the widget can't fall back to them either.
Expected: Codex tab appears with 5h/weekly limits (and ideally local token stats).
Steps to reproduce
- Sign in with
codex login(ChatGPT account), codex-cli 0.157.0. - Run
omarchy-agent-usage-codex --force. - Observe
"limits": []and"authHelpText": "account/read"; the widget shows only Claude.
View raw text
### System details
Intel i9-11900, Intel UHD 750 + NVIDIA GTX 960, Omarchy 4.0.4-1, codex-cli 0.157.0 (ChatGPT Plus login)
### What's wrong?
The `omarchy.agents` bar widget never shows the Codex subscription, although `codex` is signed in and working. Only Claude appears.
`~/.local/state/omarchy/agents/usage/codex.json` always ends up as:
```json
"limits": [], "totalPrompts": 0, "totalSessions": 0, "activeDays": 0,
"usageStatusText": "Codex limits unavailable", "authHelpText": "account/read"
```
so `providerHasData()` in `Main.qml` is false and the tab is hidden. There are two independent causes:
**1. `account/read` exceeds the 4 s RPC timeout**
`fetch_codex_rpc()` in `bin/omarchy-agent-usage-codex` sends `account/read` (timeout 4 s) before `account/rateLimits/read`. With codex-cli 0.157.0 the `account/read` response consistently takes ~31 s, and it blocks the following request too, so `TimeoutError("account/read")` is raised and no limits are recorded. The delay reproduces with a clean `CODEX_HOME` containing only `auth.json`, and network access to chatgpt.com is fine (~20 ms over IPv4).
Minimal repro (same calls as the collector, longer timeouts):
```
initialize -> 0.1 s
account/read -> 31 s
account/rateLimits/read -> 31 s (answered right after account/read)
```
Sending **only** `account/rateLimits/read` (skipping `account/read`) returns in ~0.9 s with `primary`/`secondary` windows and `planType: "plus"`. Since `plan` already prefers `limits.planType`, dropping `account/read` (or making it optional / non-blocking) would fix the limits.
**2. No local stats with current Codex session storage**
`~/.codex/sessions/` doesn't exist on this machine; current Codex (CLI + desktop app) keeps thread/rollout state in `~/.codex/state_5.sqlite` (tables `threads`, `rollout_migration_state`, …). The collector only scans the native session files, so local stats are always zero, and the widget can't fall back to them either.
**Expected:** Codex tab appears with 5h/weekly limits (and ideally local token stats).
**Steps to reproduce**
1. Sign in with `codex login` (ChatGPT account), codex-cli 0.157.0.
2. Run `omarchy-agent-usage-codex --force`.
3. Observe `"limits": []` and `"authHelpText": "account/read"`; the widget shows only Claude.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 20:22 UTC