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

Grok disappears from Agents panel when weekly usage percentage is absent

Reported by vwpro-nl · filed Sep 20, 2026Closed upstream on 2026-10-02 by dhh; the closing comment says it was fixed by PR #13992. 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

Grok disappears from Agents panel when weekly usage percentage is absentrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Intel HP EliteBook 850 G5, Omarchy 4.0.1-1, Grok CLI 1.0.34

What's wrong?

The Grok tab disappears from the Agents panel shortly after the weekly usage period resets.

I traced this to the Grok billing response.

The read-only endpoint used for Grok limits:

GET https://cli-chat-proxy.grok.com/v1/billing?format=credits

can return a valid weekly period and reset time while omitting creditUsagePercent.

For example, I received:

"currentPeriod": {
"start": "2026-09-19T16:26:02.206145+00:00",
"end": "2026-09-26T16:26:02.206145+00:00",
"type": "USAGE_PERIOD_TYPE_WEEKLY"
},
"billingPeriodEnd": "2026-09-26T16:26:02.206145+00:00"

There was no creditUsagePercent.

At that point omarchy-agent-usage-grok --force reported Grok as not ready with:

Grok's billing endpoint returned no weekly limit.

and Grok disappeared from the Agents panel.

After some Grok usage, the server started returning creditUsagePercent: 1. Without any Omarchy configuration change, Grok then automatically reappeared in the Agents panel showing:

  • Weekly: 1%
  • Reset: 6d 13h

The official Grok CLI behaves differently when creditUsagePercent is absent: its /usage screen keeps the weekly limit visible, displays 0%, and still shows the reset time. The 0% appears to be a client fallback rather than an explicit server value.

I think Omarchy should keep Grok available when a valid weekly currentPeriod exists, even if creditUsagePercent is temporarily absent. The percentage could remain unknown while the valid reset time is still reported.

I reproduced the same edge case in agent-status-tui and changed its handling so creditUsagePercent and currentPeriod.end are treated independently:

https://github.com/vwpro-nl/agent-status-tui

This seems especially relevant immediately after a weekly reset, before the billing endpoint starts returning a whole percentage again.

<img width="385" height="646" alt="Image" src="https://github.com/user-attachments/assets/f217904b-31e0-419f-b296-9a921e97bd03" />

<img width="389" height="242" alt="Image" src="https://github.com/user-attachments/assets/a96b2833-be5b-4e90-b058-3dc6c8238f59" />

<img width="432" height="105" alt="Image" src="https://github.com/user-attachments/assets/633c4574-2c9a-46b8-9149-1b58c3d89607" />

<img width="430" height="108" alt="Image" src="https://github.com/user-attachments/assets/5cfe65a7-ac32-4be6-b783-18985cca4e25" />

View raw text
### System details

Intel HP EliteBook 850 G5, Omarchy 4.0.1-1, Grok CLI 1.0.34

### What's wrong?

The Grok tab disappears from the Agents panel shortly after the weekly usage period resets.

I traced this to the Grok billing response.

The read-only endpoint used for Grok limits:

GET https://cli-chat-proxy.grok.com/v1/billing?format=credits

can return a valid weekly period and reset time while omitting creditUsagePercent.

For example, I received:

    "currentPeriod": {
      "start": "2026-09-19T16:26:02.206145+00:00",
      "end": "2026-09-26T16:26:02.206145+00:00",
      "type": "USAGE_PERIOD_TYPE_WEEKLY"
    },
    "billingPeriodEnd": "2026-09-26T16:26:02.206145+00:00"

There was no creditUsagePercent.

At that point omarchy-agent-usage-grok --force reported Grok as not ready with:

    Grok's billing endpoint returned no weekly limit.

and Grok disappeared from the Agents panel.

After some Grok usage, the server started returning creditUsagePercent: 1. Without any Omarchy configuration change, Grok then automatically reappeared in the Agents panel showing:

- Weekly: 1%
- Reset: 6d 13h

The official Grok CLI behaves differently when creditUsagePercent is absent: its /usage screen keeps the weekly limit visible, displays 0%, and still shows the reset time. The 0% appears to be a client fallback rather than an explicit server value.

I think Omarchy should keep Grok available when a valid weekly currentPeriod exists, even if creditUsagePercent is temporarily absent. The percentage could remain unknown while the valid reset time is still reported.

I reproduced the same edge case in agent-status-tui and changed its handling so creditUsagePercent and currentPeriod.end are treated independently:

https://github.com/vwpro-nl/agent-status-tui

This seems especially relevant immediately after a weekly reset, before the billing endpoint starts returning a whole percentage again.

<img width="385" height="646" alt="Image" src="https://github.com/user-attachments/assets/f217904b-31e0-419f-b296-9a921e97bd03" />

<img width="389" height="242" alt="Image" src="https://github.com/user-attachments/assets/a96b2833-be5b-4e90-b058-3dc6c8238f59" />

<img width="432" height="105" alt="Image" src="https://github.com/user-attachments/assets/633c4574-2c9a-46b8-9149-1b58c3d89607" />

<img width="430" height="108" alt="Image" src="https://github.com/user-attachments/assets/5cfe65a7-ac32-4be6-b783-18985cca4e25" />
  • f217904b-31e0-419f-b296-9a921e97bd03
  • a96b2833-be5b-4e90-b058-3dc6c8238f59
  • 633c4574-2c9a-46b8-9149-1b58c3d89607
  • 5cfe65a7-ac32-4be6-b783-18985cca4e25

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.