v0.6.5

A rejected account no longer fails silently

If OpenAI stopped accepting one of your accounts, the plugin kept using it until the saved token happened to expire on its own — which could be a day or more. During that time the account was dead, the sidebar showed old numbers as if they were current, and /openai-quota said only fetch failed — Refresh to retry. One report ran 34 hours before anyone could tell what was wrong.

Three changes:

The rejection is now noticed immediately. When the quota check comes back rejected, the plugin refreshes the sign-in straight away rather than waiting for the local expiry. An account that can recover does so on the next check instead of hours later.

An account that cannot recover says so. If the sign-in itself is being refused, retrying cannot help — the account has to be removed and added again. /openai-quota now says that, instead of suggesting a refresh that will not work.

Quota bars show their age. Numbers older than about fifteen minutes are labelled — 3h old, 2d old — so a stale reading can no longer look current. The age comes from when that reading was taken, not when the last check ran, because a check can succeed while skipping an account entirely.

Request dumps keep working across a restart

With dumps enabled, the first request after restarting had nothing to compare against, so it reported no differences at all. That is the request where differences matter most. It now compares against the previous dump on disk.

Dependency updates

OpenTUI, the AI SDK, the Pi packages, Biome, and the OpenCode plugin move to current versions.

---

The silent-outage report and the follow-up scoping came from @iceteaSA.