Skip to content

v1.8.2 — Auto-switch false positive fix

Choose a tag to compare

View all tags
@senoldogann senoldogann released this 01 Apr 11:11
· 58 commits to main since this release
v1.8.2
99d7a27

Fix: Auto-switch no longer fires when account still has capacity

Root cause

UsageMonitor watches session files for rate-limit keywords (rate_limit, 429, quota_exceeded, etc.). Any 429 response — including temporary per-request/per-minute limits, Codex's internal retries, or even the string rate_limit appearing in your own code — would trigger an immediate account switch, even if the account was at 95% weekly and had plenty of capacity left.

What's fixed

When a keyword event fires, the app now fetches fresh rate limit data from the API first, then only switches if limitReached == true. If the API confirms the account still has capacity, the event is silently ignored.

  • Account at 95% weekly → keyword fires → API says not at limit → no switch ✓
  • Account genuinely exhausted → keyword fires → API confirms limitReached → switches ✓
  • API call fails → switches conservatively (same as before) ✓

Install

  1. Download CodexSwitcher-v1.8.2.zip
  2. Replace existing app in /Applications/
Assets 3
Loading