v1.1.0

OpenCode 2

• The /openai menu. On OpenCode 2, /openai has the same sections as on OpenCode 1. You can add, turn on and off, remove (except the main account) and reorder accounts, change the routing mode, check quota, set quota floors and the killswitch, and clear the current session's account pin. In Diagnostics you can set the log level and turn request dumps on or off. In Reset credits you can preview an account's credits and spend one after confirming. In vault mode the menu shows only vault accounts, as on OpenCode 1.
• The quota sidebar. OpenCode 2 shows the same sidebar as OpenCode 1. OpenCode 2 always places it after its own panels, so the position preference has no effect there.
• Codex request shape. OpenCode 2 sends requests itself, and the plugin adjusts the ones that use its accounts. Over HTTP, those requests now match what the plugin sends from OpenCode 1. Each session keeps its conversation ID after a server restart, so OpenAI can keep using the prompt it cached.
• Reset credits in routing. When no account has a fresh quota reading, a new session goes to an account that holds a saved reset credit, as on OpenCode 1.

Not on OpenCode 2 yet: cache keep-warm, changes to WebSocket requests, and connecting to the vault or managing vault accounts from the menu. Model prices show OpenCode's own prices, and Pro reasoning models aren't hidden, because OpenCode 2 doesn't tell the plugin which login a model list is for.

Fixed

• Reset times are back in the sidebar. Each quota row shows the time until it resets again, such as 2h29m. (#215)
• The sidebar's routing label no longer flips back and forth. With several OpenCode processes running, a process that hadn't sent a request since a routing change wrote the old mode back. Every sidebar write now reads the current mode. (#216)
• "Main first" and "Fallback first" work in vault mode. These modes try a main account first or last, but in vault mode no account counted as main, so they acted like "Ordered". Now the vault's default OpenAI account, chatgpt:openai, is the one they try first or last. If the vault has no default account, the menu says these modes act like "Ordered". (#217)
• Vault accounts that can't serve stay in the sidebar. They show why: needs sign-in, turned off in vault, or unavailable. Your own on/off choice in /openai is shown separately. (#218)
• The sidebar shows accounts blocked by the killswitch. An account below its quota floor shows as blocked, using the same check routing uses. (#219)
• Vault setup explains the openai-native category. The docs and the empty-vault messages now say that the vault's ChatGPT logins need this category, how to check it with ck auth status, and how to fill in missing categories with ck auth reclassify --from-registry. (#220)
• Old local session pins no longer show in vault mode. After switching to the vault, the sidebar no longer shows a session on the old local main account. (#221)
• Every /openai option is visible. A section with a long header, such as Diagnostics, hid its last options, including "Set the log level" and "Back". This is fixed on OpenCode 1 and OpenCode 2. (#222)

Internal

• Uses @cortexkit/common-auth 0.18.0. Its account-file locks can no longer be run on a test's simulated clock, which let another process take over a lock that was still held. Pi's login lock keeps itself held even when the disk is very slow. When installing into Pi fails during setup, setup keeps the end of npm's error text, with credentials removed.

No upgrade steps are needed.

Full Changelog: v1.0.5...v1.1.0