v0.8.0

Account management moves into the places you already work, and the standalone openai-auth command is gone.

Managing accounts

In OpenCode, opencode auth login now offers an account menu once you are signed in: add a fallback account, re-authenticate the current one, force a quota check, run a diagnosis of the stored credentials, apply the repairs it finds, or delete every fallback. This is the path for machines where the slash commands are out of reach. A first sign-in on a new machine behaves exactly as before.

One oddity worth knowing: the menu prints Failed to authorize when it returns, even when the action worked. It writes its own changes and deliberately reports none of them back as a sign-in, because a fallback account must never be filed as your main credential. Confirm with /openai-account.

In Pi, there are now openai-account, openai-quota and openai-routing commands. Pi previously had no account management at all. These manage the stored accounts; Pi requests do not route through them yet.

The openai-auth binary has been removed. If you have scripts calling npx @cortexkit/opencode-openai-auth openai-auth login, they will stop working. Use the slash commands, or opencode auth login on a headless machine.

Fixes

• A turn that died the instant the connection dropped was thrown away instead of being retried, even though nothing had reached you yet.
• The dropped-connection message no longer carries wording that could cause a turn to be repeated after you had already seen part of it.
• Tool definitions survive request dumps intact, so a captured request can be replayed.

Under the hood

Both packages now share one implementation of accounts, quota, routing and the reset flow, so a fix lands in both at once instead of being ported. Each host keeps its own account store.