v1.5.0

New

• Set the order of vault accounts from /openai. In vault mode, /openai → Routing → "Set order" now lists your vault accounts by name and saves the order you choose, on OpenCode 1, OpenCode 2 and Pi. In Ordered routing the next request tries the accounts in that order. Every other account action stays in the vault, and local mode is unchanged (common-auth #3).
• Workspace credits show in vault mode before any request (#229). The background usage readings from insula now carry each account's workspace credits, including whether they are unlimited. Before, credits appeared only after the account had served a request. Credits routing uses these readings too, so an account whose usage limits are spent but which has credits can serve before one without, while accounts with free quota still come first. If an older insula build reports neither a balance nor whether the credits are unlimited, an account already known to be unlimited stays unlimited.

Fixed

• On OpenCode 2, when the last account that can serve a request hits a rate limit, the plugin now keeps OpenCode's own wait and retry instead of ending the step. It moves the retry to another account at once only when another account can actually serve (common-auth #1).
• In vault mode, cancelling a request while the vault checks a login again after a 401 no longer counts as a failed login on OpenCode 1 and Pi, or for OpenCode 2's cache keep-warm (common-auth #4).
• Connecting to a Claustrum vault that is too old to connect plugins now stops after one attempt, both in npx @cortexkit/opencode-openai-auth setup --claustrum and in /openai → Vault → Connect, with a message that names ck upgrade.

Internally, the plugin now uses common-auth 0.25.0 and Claustrum client 0.13. No plugin upgrade steps are needed. A vault too old to connect plugins still needs ck upgrade, as above.