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-4734GitHub issuePublicReceived

Agents bar widget: Codex limits always show "unavailable" (stale --ask-for-approval value)

Reported by abduvaliy-engineer · filed Aug 29, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #8460 (R-1406). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Agents bar widget: Codex limits always show "unavailable" (stale --ask-for-approval value)revision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

The topbar agents widget shows "Codex limits unavailable" for Codex, even though codex is installed, authenticated, and local usage stats (prompts/tokens/sessions) collect fine.

Root cause

/usr/bin/omarchy-agent-usage-codex (installed by the omarchy package) launches the Codex app-server RPC with:

[codex, "-s", "read-only", "-a", "untrusted", "app-server"]

Current Codex CLI (codex-cli 0.150.0) no longer accepts untrusted as a value for --ask-for-approval / -a. Running it directly reproduces the failure:

$ 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, the JSON-RPC handshake (initialize / account/read / account/rateLimits/read) never completes. fetch_codex_rpc() in the collector catches the resulting failure and sets usageStatusText: "Codex limits unavailable", which is what the bar widget displays. Local stats still populate normally since those come from scanning session files, not the RPC call.

Expected

The widget should show real Codex rate-limit percentages (session/weekly windows) like it does for Claude Code.

Fix

Change the hardcoded approval policy from untrusted to a value the current CLI accepts, e.g. on-request:

- [codex, "-s", "read-only", "-a", "untrusted", "app-server"],
+ [codex, "-s", "read-only", "-a", "on-request", "app-server"],

I verified this locally: patching just this one flag value in /usr/bin/omarchy-agent-usage-codex and re-running the collector immediately produces a populated limits array (session + weekly windows, plan plus) instead of usageStatusText: "Codex limits unavailable".

Steps to reproduce

  1. Install/authenticate a recent Codex CLI (codex login).
  2. Add the Codex agent to the topbar agents widget.
  3. Open the agents panel — Codex shows local usage stats but "Codex limits unavailable" for rate limits.
  4. Reproduce directly: codex -s read-only -a untrusted app-server → CLI arg-parse error.

System details

  • Omarchy version: 4.0.1-1
  • Codex CLI version: codex-cli 0.150.0 (installed via mise)
  • OS: Linux 7.1.9-arch1-2 x86_64
View raw text
## What happened

The topbar agents widget shows "Codex limits unavailable" for Codex, even though `codex` is installed, authenticated, and local usage stats (prompts/tokens/sessions) collect fine.

## Root cause

`/usr/bin/omarchy-agent-usage-codex` (installed by the `omarchy` package) launches the Codex app-server RPC with:

```python
[codex, "-s", "read-only", "-a", "untrusted", "app-server"]
```

Current Codex CLI (`codex-cli 0.150.0`) no longer accepts `untrusted` as a value for `--ask-for-approval` / `-a`. Running it directly reproduces the failure:

```
$ 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, the JSON-RPC handshake (`initialize` / `account/read` / `account/rateLimits/read`) never completes. `fetch_codex_rpc()` in the collector catches the resulting failure and sets `usageStatusText: "Codex limits unavailable"`, which is what the bar widget displays. Local stats still populate normally since those come from scanning session files, not the RPC call.

## Expected

The widget should show real Codex rate-limit percentages (session/weekly windows) like it does for Claude Code.

## Fix

Change the hardcoded approval policy from `untrusted` to a value the current CLI accepts, e.g. `on-request`:

```diff
- [codex, "-s", "read-only", "-a", "untrusted", "app-server"],
+ [codex, "-s", "read-only", "-a", "on-request", "app-server"],
```

I verified this locally: patching just this one flag value in `/usr/bin/omarchy-agent-usage-codex` and re-running the collector immediately produces a populated `limits` array (session + weekly windows, plan `plus`) instead of `usageStatusText: "Codex limits unavailable"`.

## Steps to reproduce

1. Install/authenticate a recent Codex CLI (`codex login`).
2. Add the Codex agent to the topbar agents widget.
3. Open the agents panel — Codex shows local usage stats but "Codex limits unavailable" for rate limits.
4. Reproduce directly: `codex -s read-only -a untrusted app-server` → CLI arg-parse error.

## System details

- Omarchy version: 4.0.1-1
- Codex CLI version: codex-cli 0.150.0 (installed via mise)
- OS: Linux 7.1.9-arch1-2 x86_64

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.