Codex usage fetch fails on plan_type=prolite in v0.20

[sdewell]

Hi — CodexBar is failing to load Codex usage/rate limit data because the usage response now returns a plan_type value of prolite, which appears to be unsupported by the current decoder.

Version

• CodexBar 0.20 (build 55)
• macOS arm64
• Confirmed after upgrading on April 13, 2026

What happens

CodexBar shows:

Codex connection failed: failed to fetch codex rate limits: Decode error for https://chatgpt.com/backend-api/wham/usage: unknown variant `prolite`, expected one of `guest`, `free`, `go`, `plus`, `pro`, `free_workspace`, `team`, `self_serve_business_usage_based`, `business`, `enterprise_cbp_usage_based`, `education`, `quorum`, `k12`, `enterprise`, `edu`

Important detail

The server response itself indicates the request succeeded and the account is allowed:

{
  "plan_type": "prolite",
  "rate_limit": {
    "allowed": true,
    "limit_reached": false
  }
}

So this looks like a client-side enum/schema mismatch, not an auth or rate-limit failure.

Full response body

{
 

  "plan_type": "prolite",
  "rate_limit": {
    "allowed": true,
    "limit_reached": false,
    "primary_window": {
      "used_percent": 12,
      "limit_window_seconds": 18000,
      "reset_after_seconds": 8581,
      "reset_at": 1776111121
    },
    "secondary_window": {
      "used_percent": 2,
      "limit_window_seconds": 604800,
      "reset_after_seconds": 569914,
      "reset_at": 1776672455
    }
  },
  "code_review_rate_limit": null,
  "additional_rate_limits": [
    {
      "limit_name": "GPT-5.3-Codex-Spark",
      "metered_feature": "codex_bengalfox",
      "rate_limit": {
        "allowed": true,
        "limit_reached": false,
        "primary_window": {
          "used_percent": 0,
          "limit_window_seconds": 18000,
          "reset_after_seconds": 18000,
          "reset_at": 1776120541
        },
        "secondary_window": {
          "used_percent": 0,
          "limit_window_seconds": 604800,
          "reset_after_seconds": 604800,
          "reset_at": 1776707341
        }
      }
    }
  ],
  "credits": {
    "has_credits": false,
    "unlimited": false,
    "overage_limit_reached": false,
    "balance": "0",
    "approx_local_messages": [0, 0],
    "approx_cloud_messages": [0, 0]
  },
  "spend_control": {
    "reached": false
  },
  "promo": null
}

Expected

CodexBar should handle plan_type=prolite gracefully and continue showing usage data.

Actual

CodexBar fails decoding the response and reports a Codex connection error.

Guess

Likely just needs support for the new prolite plan enum (or a safer unknown/fallback case).