Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-204GitHub issuePublicDecided· Out of scope

omarchy-agent-usage-codex: account/rateLimits/read RPC timeout (4s) misreported as unavailable

Reported by tundakk · filed Sep 22, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

omarchy-agent-usage-codex: account/rateLimits/read RPC timeout (4s) misreported as unavailablerevision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

The Codex agent-usage collector sometimes reports no rate-limit data. The panel and a custom alert script show "Codex limits unavailable." The stored authHelpText is the literal string account/rateLimits/read — this is the exception text from a timeout, not an auth message.

Root cause

fetch_codex_rpc() in bin/omarchy-agent-usage-codex calls rpc_request(proc, 3, "account/rateLimits/read", timeout=4). The Codex app-server process starts fresh on every collector run. Under normal dev load (other Codex or Claude Code sessions, background builds), this call sometimes exceeds 4 seconds. rpc_request() raises TimeoutError(method). The collector stores str(exc) as authHelpText, which prints only the method name, not a timeout description.

What I expected

Either the RPC call finishes inside its timeout, or the failure text reads as a timeout, not an auth problem.

Steps to reproduce

  1. Run several concurrent Codex or Claude Code sessions, or another CPU-heavy job.
  2. Run omarchy agent usage-update codex --force a few times, or wait for the panel's normal refresh.
  3. Watch ~/.local/state/omarchy/agents/usage/codex.json. Under load, usageStatusText becomes "Codex limits unavailable" and authHelpText becomes "account/rateLimits/read".
  4. The next refresh, with no code change, often succeeds. This confirms a timing race, not an auth failure.

Suggested fix

  1. Raise the timeout on the account/rateLimits/read call, or retry once before giving up.
  2. Give a timed-out rpc_request() call a clear message, so authHelpText does not read like a permission problem.

System

  • Omarchy 4.0.4-1, Hyprland 0.56.2
  • Codex CLI 0.155.1, plan: plus
  • Framework Laptop 13 Pro (AMD Ryzen AI 300 series)
View raw text
## What happened
The Codex agent-usage collector sometimes reports no rate-limit data. The panel and a custom alert script show "Codex limits unavailable." The stored `authHelpText` is the literal string `account/rateLimits/read` — this is the exception text from a timeout, not an auth message.

## Root cause
`fetch_codex_rpc()` in `bin/omarchy-agent-usage-codex` calls `rpc_request(proc, 3, "account/rateLimits/read", timeout=4)`. The Codex app-server process starts fresh on every collector run. Under normal dev load (other Codex or Claude Code sessions, background builds), this call sometimes exceeds 4 seconds. `rpc_request()` raises `TimeoutError(method)`. The collector stores `str(exc)` as `authHelpText`, which prints only the method name, not a timeout description.

## What I expected
Either the RPC call finishes inside its timeout, or the failure text reads as a timeout, not an auth problem.

## Steps to reproduce
1. Run several concurrent Codex or Claude Code sessions, or another CPU-heavy job.
2. Run `omarchy agent usage-update codex --force` a few times, or wait for the panel's normal refresh.
3. Watch `~/.local/state/omarchy/agents/usage/codex.json`. Under load, `usageStatusText` becomes `"Codex limits unavailable"` and `authHelpText` becomes `"account/rateLimits/read"`.
4. The next refresh, with no code change, often succeeds. This confirms a timing race, not an auth failure.

## Suggested fix
1. Raise the timeout on the `account/rateLimits/read` call, or retry once before giving up.
2. Give a timed-out `rpc_request()` call a clear message, so `authHelpText` does not read like a permission problem.

## System
- Omarchy 4.0.4-1, Hyprland 0.56.2
- Codex CLI 0.155.1, plan: plus
- Framework Laptop 13 Pro (AMD Ryzen AI 300 series)

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 17:12 UTC