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

omarchy-agent-usage-codex: Codex limits always empty ('Codex limits unavailable') on Codex >=0.13

Reported by lasurius · filed Aug 27, 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

omarchy-agent-usage-codex: Codex limits always empty ('Codex limits unavailable') on Codex >=0.13revision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

The omarchy.agents bar widget shows the Codex subscription tab with no rate limits — limits: [], tierLabel: "", and the panel reports "Codex limits unavailable", even though Codex is signed in.

Expected

Real usage limits fill the Codex tab (5-hour + weekly windows, plan tier), like the Claude tab.

Root cause

/usr/bin/omarchy-agent-usage-codex (line 531) launches the app-server with:

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

-a untrusted is no longer a valid value for --ask-for-approval. On installed Codex CLI 0.149.1 the accepted values are on-request and never, so codex exits immediately with:

error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
  [possible values: on-request, never]

Because stderr is redirected to DEVNULL and no stdout line ever arrives, rpc_request() hits EOF and raises TimeoutError("initialize"), leaving limits: [].

Fix (verified)

Changing untrusted → never on that line makes the record populate correctly:

"limits": [
  {"label": "5h window", "percent": 0.69, "resetsAt": "2026-08-27T21:44:40+00:00"},
  {"label": "Weekly (7-day)", "percent": 0.11, "resetsAt": "2026-09-03T16:44:40+00:00"}
],
"tierLabel": "plus"

Suggested fix:

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

Possibly pick never from the current APPROVAL_POLICY set rather than hard-coding, to survive future value changes.

System

  • Omarchy 4.0.1-1
  • codex-cli 0.149.1 (Arch via mise)
  • Reproduced via $OMARCHY_PATH/bin/omarchy-agent-usage-update codex
View raw text
## What happened
The `omarchy.agents` bar widget shows the Codex subscription tab with no rate limits — `limits: []`, `tierLabel: ""`, and the panel reports **"Codex limits unavailable"**, even though Codex is signed in.

## Expected
Real usage limits fill the Codex tab (5-hour + weekly windows, plan tier), like the Claude tab.

## Root cause
`/usr/bin/omarchy-agent-usage-codex` (line 531) launches the app-server with:

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

`-a untrusted` is no longer a valid value for `--ask-for-approval`. On installed Codex CLI 0.149.1 the accepted values are `on-request` and `never`, so `codex` exits immediately with:

```
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
  [possible values: on-request, never]
```

Because stderr is redirected to `DEVNULL` and no stdout line ever arrives, `rpc_request()` hits EOF and raises `TimeoutError("initialize")`, leaving `limits: []`.

## Fix (verified)
Changing `untrusted` → `never` on that line makes the record populate correctly:

```json
"limits": [
  {"label": "5h window", "percent": 0.69, "resetsAt": "2026-08-27T21:44:40+00:00"},
  {"label": "Weekly (7-day)", "percent": 0.11, "resetsAt": "2026-09-03T16:44:40+00:00"}
],
"tierLabel": "plus"
```

Suggested fix:

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

Possibly pick `never` from the current `APPROVAL_POLICY` set rather than hard-coding, to survive future value changes.

## System
- Omarchy 4.0.1-1
- codex-cli 0.149.1 (Arch via mise)
- Reproduced via `$OMARCHY_PATH/bin/omarchy-agent-usage-update codex`

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.