Skip to content

Mimir v1.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Jun 19:17
· 51 commits to main since this release
v1.5
58a8f5d

Changed

  • Quota notifications reworked around the 5-hour and weekly windows. Live Claude/Codex warn once when the 5h window drops below 20% or the weekly window below 10%; the 5h "refilled" notice fires only after the window fully drains to 0% and resets to 100%, while the weekly "refilled" fires on every reset. Per-model rows no longer notify, and messages are now English with the live percentage and reset countdown
  • Antigravity notifications limited to a single reliable event — its weekly refill. Usage/low and 5h alerts are dropped because Antigravity data is only live while the IDE is open; but the weekly reset time is deterministic and the quota can't be spent while the IDE is closed, so "weekly quota refilled" fires exactly when that time passes, even with the IDE closed and even if the quota was never touched

Fixed

  • A service card could silently vanish on a transient failure. The last-known snapshot pattern (previously Antigravity-only) now covers Claude and Codex too: each service's last live reading is persisted and, when a live fetch fails, shown instead of hidden — fresh windows live-from-cache, reset-passed windows blanked, all-stale as a dimmed "güncel değil" card. Only a service that has never once produced a reading is hidden
  • Claude no longer hammers the usage API with a dead token. Mimir reads the token's expiresAt and, if it has already expired, skips the API call entirely (this was what escalated to HTTP 429), showing last-known data with a "token expired — open Claude Code" note. Mimir stays read-only — it never refreshes Claude's token (which could rotate Claude Code's own credentials out from under it); live data returns automatically once Claude Code refreshes the keychain
  • Added per-service fetch backoff: after an HTTP 429 (honoring Retry-After) or an expired token, Mimir parks that service from network polling for a cooldown and serves it from the snapshot, clearing the cooldown on the next live success

SHA256: 9565649128bc2dde8686c750878064fd6842c558a1b9be00c8ed2b19a87ddba7

Assets 3
Loading