Skip to content

v6.14.1

Choose a tag to compare

@ndycode ndycode released this 25 Aug 12:55
· 172 commits to main since this release

https://www.npmjs.com/package/oc-codex-multi-auth/v/6.14.1

npx oc-codex-multi-auth@6.14.1 install

Fixed

A rate-limited strict model pool answered 503 instead of 429 (#235). The pool wait-time lookup matched its members against an account's raw account id, while routing matches them through the member-scoped seat identity that codex-pool actually writes. For any pool whose accounts have a resolvable member id the two never agreed, so the lookup saw an empty pool and reported no wait at all.

The result: when every account in a strict pool was rate-limited, you got a 503 telling you to check codex-health rather than a 429 carrying Try again in <time> — losing both the retry-after signal and the status class clients back off on. Pools configured with legacy workspace-wide entries kept working, which is why this went unnoticed since the strict-pool feature shipped.

Pool-exhaustion diagnostics could describe the wrong accounts, or a previous request (#234). The counts behind these messages were keyed on rotation index, which is reassigned when an account is removed mid-request, so a count taken before a removal referred to a different account afterwards. Pool size was read off the number of configured entries, which is a different quantity again: one legacy workspace-wide entry can resolve to several Business seats, and two entries can resolve to a single seat.

The strict-pool message now reports configured entries and resolved accounts separately, names entries that match no known account instead of folding them into an "unavailable" total, and separates accounts that were never attempted from ones that were tried and failed — so a mistyped pool entry reads as a mistyped entry rather than as a busy pool.

The general exhaustion message no longer inherits an earlier request's "model not supported" verdict. That state is plugin-scoped, so a request that never reached an account could report a backend rejection on "0 of 0 attempted account(s)". It also states again how many accounts are configured, which the previous wording had dropped.


#234 by @lubshad.