v0.6.3

An account could vanish from your config file

An account whose saved sign-in details were incomplete was quietly dropped when the file was next written — by any write at all, including the routine one that happens whenever your main account's token refreshes. No deletion was requested, nothing was logged, and the account was simply gone. It cost one operator two accounts.

Such an account is now kept on disk. It stays unusable until you sign in again, which is recoverable; deleted was not. Removing one deliberately still works as before.

Two account files could overwrite each other

If you pointed the plugin at a config file whose name merely ended in openai-auth.json — say team-openai-auth.json — it shared one credentials file with the default. Two sets of accounts wrote over each other. Each config file now gets its own, and existing setups keep the file they already use.

Interrupted replies no longer re-run tools

When a connection dropped partway through a reply, the plugin could retry the turn. If tools had already run, they ran a second time — and were billed a second time. Retries now stop once a reply has begun producing output, and the turn ends instead.

The tradeoff: a connection failure very early in a reply now ends the turn rather than switching accounts. Losing a retry is better than paying twice for a tool that already ran.

Account file locking

A lock held by one process could be released in a way that also removed a lock another process had already taken, letting both write at once. The release and renewal paths now check ownership the same way the rest of the locking already did.

Dependency updates

Pi packages to 0.84.2, OpenTUI to 0.5.4, and the AI SDK, plugin, and Biome to current.