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.
Omarchy 4.0.1-1 still ships incompatible Codex approval policy
Reported by naolselemon · filed Aug 26, 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 Core 7 250U, Intel Raptor Lake-U graphics, Linux 7.1.9-arch1-2, Omarchy 4.0.1-1, Codex CLI 0.149.1
What's wrong?
After updating Omarchy to 4.0.1-1 and Codex CLI to 0.149.1, the Codex rate-limit information disappeared from the Agents widget.
The widget still displays local token statistics, but the session and weekly percentages are replaced with:
Codex limits unavailable initialize
This appears to be the same compatibility problem reported in #7873 and fixed by #7649, but the currently distributed Omarchy
4.0.1-1 package still contains the incompatible invocation.
Steps to reproduce
- Install or update to Omarchy 4.0.1-1.
- Install Codex CLI 0.149.1.
- Authenticate Codex normally.
- Open or refresh the Omarchy Agents widget.
- Observe that Codex token history is present, but the session and weekly limit percentages are unavailable.
The packaged collector still starts Codex using:
codex -s read-only -a untrusted app-serverRunning that command directly returns:
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]The app server exits before responding to the initialization request, so the collector produces:
{
"limits": [],
"tierLabel": "",
"usageStatusText": "Codex limits unavailable",
"authHelpText": "initialize"
}The affected packaged file is:
/usr/share/omarchy/bin/omarchy-agent-usage-codexExpected behavior
The stable Omarchy package should include the merged fix from #7649 and launch the Codex app server using a currently supported
approval policy, such as:
-a on-request After applying that compatibility change locally, account/read and account/rateLimits/read succeed and the Agents widget
displays the Codex session and weekly percentages again.
Additional context
- Related issue: #7873
- Merged fix: #7649
- The regression appeared immediately after the August 25 system update.
- No Codex logout or account change occurred.
- No files under /usr/share/omarchy were modified during diagnosis.
This accurately reports that the fix exists upstream but is absent from the installed stable package.View raw text
### System details
Intel Core 7 250U, Intel Raptor Lake-U graphics, Linux 7.1.9-arch1-2, Omarchy 4.0.1-1, Codex CLI 0.149.1
### What's wrong?
After updating Omarchy to 4.0.1-1 and Codex CLI to 0.149.1, the Codex rate-limit information disappeared from the Agents widget.
The widget still displays local token statistics, but the session and weekly percentages are replaced with:
> Codex limits unavailable
> initialize
This appears to be the same compatibility problem reported in #7873 and fixed by #7649, but the currently distributed Omarchy
4.0.1-1 package still contains the incompatible invocation.
## Steps to reproduce
1. Install or update to Omarchy 4.0.1-1.
2. Install Codex CLI 0.149.1.
3. Authenticate Codex normally.
4. Open or refresh the Omarchy Agents widget.
5. Observe that Codex token history is present, but the session and weekly limit percentages are unavailable.
The packaged collector still starts Codex using:
```text
codex -s read-only -a untrusted app-server
```
Running that command directly returns:
```text
error: invalid value 'untrusted' for '--ask-for-approval <APPROVAL_POLICY>'
[possible values: on-request, never]
```
The app server exits before responding to the initialization request, so the collector produces:
```json
{
"limits": [],
"tierLabel": "",
"usageStatusText": "Codex limits unavailable",
"authHelpText": "initialize"
}
```
The affected packaged file is:
```text
/usr/share/omarchy/bin/omarchy-agent-usage-codex
```
Expected behavior
The stable Omarchy package should include the merged fix from #7649 and launch the Codex app server using a currently supported
approval policy, such as:
```text
-a on-request
```
After applying that compatibility change locally, account/read and account/rateLimits/read succeed and the Agents widget
displays the Codex session and weekly percentages again.
Additional context
- Related issue: #7873
- Merged fix: #7649
- The regression appeared immediately after the August 25 system update.
- No Codex logout or account change occurred.
- No files under /usr/share/omarchy were modified during diagnosis.
```
This accurately reports that the fix exists upstream but is absent from the installed stable package.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 09:16 UTC