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

Agents panel shows the wrong Claude plan (MAX 5X) when the org tier differs from the OAuth credentials

Reported by IgorKramar · filed Aug 17, 2026Closed upstream on 2026-10-04 by the bot omarchybot; the closing comment says it was fixed by PR #14049. 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 panel shows the wrong Claude plan (MAX 5X) when the org tier differs from the OAuth credentialsrevision 1 · captured 2026-09-28 21:29 UTC via poll

What happened

The Claude Code card in the agents panel is labeled MAX 5X, but this account is on a Max 20x plan. The limit meters themselves are correct — the session/weekly percentages and reset times come from the live limits probe. Only the plan label is wrong.

Why

bin/omarchy-agent-usage-claude derives the label exclusively from the OAuth credential store:

# bin/omarchy-agent-usage-claude:592
plan = plan_label(str(login.get("rateLimitTier") or ""), str(login.get("subscriptionType") or ""))

# bin/omarchy-agent-usage-claude:596
def plan_label(tier: str, subscription: str) -> str:
  if tier:
    match = re.search(r"max_(\d+x)", tier, re.IGNORECASE)
    if match:
      return "Max " + match.group(1)

On this machine ~/.claude/.credentials.json carries a stale personal tier:

{"claudeAiOauth": {"subscriptionType": "max", "rateLimitTier": "default_claude_max_5x"}}

…while the effective plan lives in the profile that Claude Code keeps fresh in ~/.claude.json:

{"oauthAccount": {"organizationType": "claude_max",
                  "organizationRateLimitTier": "default_claude_max_20x",
                  "userRateLimitTier": null}}

The credentials file is rewritten on every token refresh (its mtime is current) and still keeps max_5x, so the label never catches up. Rate limits are enforced against the organization tier — which is exactly why the meters are right and the label isn't.

Expected

The plan label matches the effective plan (Max 20x).

Suggested fix

Prefer the profile over the credential store when it is available, e.g. resolve the tier as:

~/.claude.json → oauthAccount.userRateLimitTier → oauthAccount.organizationRateLimitTier → ~/.claude/.credentials.json → claudeAiOauth.rateLimitTier → subscriptionType

omarchy-agent-usage-claude does not read ~/.claude.json at all today.

Steps to reproduce

  1. Sign into Claude Code with an account whose organization tier differs from the tier stamped into the OAuth credentials (org on Max 20x, credentials say default_claude_max_5x).
  2. Run omarchy-agent-usage-update.
  3. Open the agents panel — the Claude Code header reads MAX 5X.

Signing out and back in does not necessarily help: the refresh rewrites the file but keeps the old tier value.

System

  • Omarchy 4.0.0-1 (omarchy version prints dev here — running under omarchy dev link)
  • Claude Code 2.1.233
  • Hyprland 0.56.2, kernel 7.1.8-arch1-3
  • CPU: 12th Gen Intel Core i5-12450H · GPU: Intel Alder Lake-P GT1 (UHD Graphics)

Current master carries the same plan_label() implementation, so this is not fixed upstream yet.

View raw text
### What happened

The Claude Code card in the agents panel is labeled **MAX 5X**, but this account is on a Max 20x plan. The limit meters themselves are correct — the session/weekly percentages and reset times come from the live limits probe. Only the plan label is wrong.

### Why

`bin/omarchy-agent-usage-claude` derives the label exclusively from the OAuth credential store:

```python
# bin/omarchy-agent-usage-claude:592
plan = plan_label(str(login.get("rateLimitTier") or ""), str(login.get("subscriptionType") or ""))

# bin/omarchy-agent-usage-claude:596
def plan_label(tier: str, subscription: str) -> str:
  if tier:
    match = re.search(r"max_(\d+x)", tier, re.IGNORECASE)
    if match:
      return "Max " + match.group(1)
```

On this machine `~/.claude/.credentials.json` carries a stale personal tier:

```json
{"claudeAiOauth": {"subscriptionType": "max", "rateLimitTier": "default_claude_max_5x"}}
```

…while the effective plan lives in the profile that Claude Code keeps fresh in `~/.claude.json`:

```json
{"oauthAccount": {"organizationType": "claude_max",
                  "organizationRateLimitTier": "default_claude_max_20x",
                  "userRateLimitTier": null}}
```

The credentials file is rewritten on every token refresh (its mtime is current) and still keeps `max_5x`, so the label never catches up. Rate limits are enforced against the organization tier — which is exactly why the meters are right and the label isn't.

### Expected

The plan label matches the effective plan (Max 20x).

### Suggested fix

Prefer the profile over the credential store when it is available, e.g. resolve the tier as:

`~/.claude.json` → `oauthAccount.userRateLimitTier` → `oauthAccount.organizationRateLimitTier` → `~/.claude/.credentials.json` → `claudeAiOauth.rateLimitTier` → `subscriptionType`

`omarchy-agent-usage-claude` does not read `~/.claude.json` at all today.

### Steps to reproduce

1. Sign into Claude Code with an account whose organization tier differs from the tier stamped into the OAuth credentials (org on Max 20x, credentials say `default_claude_max_5x`).
2. Run `omarchy-agent-usage-update`.
3. Open the agents panel — the Claude Code header reads `MAX 5X`.

Signing out and back in does not necessarily help: the refresh rewrites the file but keeps the old tier value.

### System

- Omarchy `4.0.0-1` (`omarchy version` prints `dev` here — running under `omarchy dev link`)
- Claude Code `2.1.233`
- Hyprland `0.56.2`, kernel `7.1.8-arch1-3`
- CPU: 12th Gen Intel Core i5-12450H · GPU: Intel Alder Lake-P GT1 (UHD Graphics)

Current `master` carries the same `plan_label()` implementation, so this is not fixed upstream yet.

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.