v1.0.0

Before you upgrade

• Your ChatGPT login moves into the plugin's account pool. Once every OpenCode process on the machine runs 1.0.0, the plugin moves the login from OpenCode's openai slot into the pool as the account main, and leaves a placeholder in the slot. The move waits for older OpenCode processes to exit; until then /openai shows only that notice. Don't delete the placeholder: OpenCode 1 needs it to load the plugin.
• Going back to 0.11 after the move isn't supported. 0.11 doesn't understand the placeholder and would send an empty token. Stay on 1.0.0, or sign in afresh in a separate store before using an older build.
• The eight /openai-* commands are replaced by one /openai menu. Accounts, quota, routing, limits, cache, diagnostics, reset credits, the session pin and the vault are sections of it.

Added

• One account pool for every account. The main login and your other accounts are rows in one pool, with one routing order, one set of limits and one quota view. Quota readings, session pins and limits follow the account, not its position in the list.
• Claustrum vault support. A host can be served by the OpenAI accounts held in a Claustrum vault. Connect from opencode auth login or the Vault section of /openai, approve the request with ck, and grant it read access to openai-native. While connected, only the vault's accounts are used: no local account is sent with, refreshed, polled, warmed or shown, and the local account files stay exactly as they were. A request no vault account can serve is refused locally, with the remedy. Disconnect returns to the local accounts at once. A new install can start from the vault alone, with no local sign-in.
• OpenCode 2 support (tested on 2.0.22). The plugin acts only on requests made with its own login method; an API key, an environment key or OpenCode's own ChatGPT login passes through untouched.
• Pi uses the account pool. Pi's requests now route across Pi's login and the pool's accounts, and the /openai menu on Pi affects them (#153). In vault mode Pi keeps the openai-codex/ provider: its original login is set aside in a private backup while connected, so Pi can't refresh it, and is restored byte-for-byte on disconnect; a login added meanwhile is never overwritten.
• opencode auth login account menu. On a machine that's already signed in, it offers add, re-authenticate, remove, enable or disable, check quotas, the auth doctor, vault connect and delete all, for headless machines where /openai is out of reach.

Changed

• Quota reads as "% left", grouped by window, and a reading older than 15 minutes shows its age.
• The /openai menu shows only what you can act on. Information is shown as section headings, and every row is an action. In vault mode, actions that would add, remove or change local accounts are not offered.
• Prompt-cache keep-warm works for sessions served by a vault account.

Fixed

• A login in OpenCode's slot is no longer served or refreshed while the host is on the vault (#173).
• The browser sign-in callback also listens on IPv6, for systems where localhost resolves to ::1.
• On Windows, the browser sign-in link opens intact. It used to be cut at the first &.
• Several cases where two OpenCode setups share one auth.json no longer move the same login twice, or lose it.
• A provider error that repeats your account token no longer passes it on. Tokens are replaced with [credential] in error messages before they leave the plugin, on OpenCode 1, OpenCode 2 and Pi.
• Connecting to the vault mid-request can't send a local login, and a damaged local account file no longer stops vault mode from working.

Full Changelog: v0.11.0...v1.0.0