subscriptions
use a plan you already pay for, ChatGPT Plus or Pro, Mistral's Vibe Pro, or a coding plan from Z.ai, Kimi or MiniMax, in place of an API key.
an API key bills each call. a plan is a monthly price you may already pay. bise can use a few plans, signed in with the provider's own login or with the plan's key.
| plan | how bise uses it | set it up |
|---|---|---|
| ChatGPT Plus or Pro | "Sign in with ChatGPT", in your browser | bise login chatgpt |
| OpenRouter | sign in in your browser: it makes an OpenRouter key for bise | bise login openrouter |
| GLM Coding Plan (Z.ai) | the plan's API key | bise login zai-coding |
| Kimi Code | the plan's API key | bise login kimi-code |
| MiniMax M plan | the plan's API key | bise login minimax |
| Vibe Pro or Team (Mistral) | the plan's API key | bise login mistral |
| Claude Max or Team | its monthly API credits, through a key of a linked Console org | bise login anthropic |
the first run asks how you want to pay for the models: ChatGPT, OpenRouter, an API key, or a coding plan key. later:
bise desktop
settings › models has a row per plan: sign in opens your browser, and the row says ✓ signed in when it's done. an expired sign-in says which agents wait on it, with sign in again.
bise terminal
/provider adds or changes any of them, or bise login <plan> in a terminal, as in the table.
ChatGPT Plus or Pro
bise signs in with OpenAI's "Sign in with ChatGPT": your ChatGPT plan pays for the calls, not an API account.
sign in
in bise, the first run's ChatGPT, or later settings › models (bise desktop) or /provider (bise terminal). in a terminal:
bise login chatgptopening your browser to sign in to ChatGPT…
or open this link:
https://auth.openai.com/...
waiting… ctrl+c cancels.
✓ signed in as you@example.com · ChatGPT Plus.sign in to ChatGPT in the browser and allow bise to use your plan. bise checks the plan with one tiny call, then main and your agents use a ChatGPT model on your plan.
over SSH, or from an agent
bise login chatgpt --no-browserit prints the link and waits. the sign-in comes back to 127.0.0.1 on the machine where bise runs, so over SSH, forward that port first; the command prints the exact line, like ssh -L <port>:127.0.0.1:<port> <host>.
a coding agent setting bise up for you can run this command, but only you can sign in: the browser asks for your consent.
the models
ChatGPT models are named chatgpt/<model>, for example chatgpt/gpt-6.1-sol. they are OpenAI's models, billed to your plan. openai/<model> stays your API key: you can have both and mix them across roles.
/models lists the models your plan offers, and says your ChatGPT plan where the others show a price.
bise config set main chatgpt/gpt-6.1-sol
bise config set small chatgpt/gpt-6-lunalimits and errors
your plan has a usage limit for apps like bise. when it's reached, the turn ends with:
▲ your ChatGPT plan's limit for bise is reached. your usage is at chatgpt.com/settings/usage, or switch model with /model.your usage is at chatgpt.com/settings/usage; /provider links it too. the other lines you may see:
| line | what to do |
|---|---|
▲ ChatGPT plan use is off for bise. turn it on in your ChatGPT settings, or pick another provider in /provider. | your account or workspace doesn't allow plan use in other apps |
▲ ChatGPT couldn't check your plan's usage. try again in a moment, or switch model with /model. | OpenAI couldn't check your usage; bise already retried |
▲ your ChatGPT sign-in expired. sign in again in /provider, or run bise login chatgpt. | sign in again |
sign out
bise logout chatgptbise tells ChatGPT to end its sign-in. if ChatGPT doesn't confirm, the line says so: then remove bise in your ChatGPT settings to be sure.
OpenRouter
bise login openrouter # asks: sign in with your browser, or paste a key
bise login openrouter --browser
bise login openrouter --key
bise login openrouter --no-browser # prints the link (SSH: forward its port, as for ChatGPT)the browser sign-in makes a normal OpenRouter API key for bise and saves it, so nothing else changes: the models are openrouter/<vendor>/<model>, paid with your OpenRouter credit.
coding plans
Z.ai, Kimi and MiniMax sell coding plans for tools like bise. each plan gives you an API key for its coding endpoint; bise has a provider for each.
| plan | provider | key variable | starts with | get the key |
|---|---|---|---|---|
| GLM Coding Plan | zai-coding | ZAI_API_KEY | zai-coding/glm-5.3 | z.ai |
| Kimi Code | kimi-code | KIMI_API_KEY | kimi-code/kimi-for-coding | kimi.com |
| MiniMax M plan | minimax | MINIMAX_API_KEY | minimax/MiniMax-M3 | platform.minimax.io |
bise login zai-codingor the first run's a coding plan key. the key is checked with one tiny call, then saved like any key (see providers and keys).
Mistral Vibe Pro or Team
Le Chat is now Vibe (Mistral's help). its Pro and Team plans include monthly usage for Vibe Code, and a plan key draws on that usage (Mistral's docs). the key calls Mistral's usual API, api.mistral.ai, so bise uses it as its mistral provider.
- on console.mistral.ai, open Code › Vibe CLI and make a key.
- paste it in bise: the first run's an API key then Mistral,
/provider, or
bise login mistralthe key is checked with one tiny call, then saved like any key. the models are mistral/<model>, for example mistral/mistral-large-4. the same key also runs voice and the Mistral connectors (web search and other tools). already set up in Vibe? when the key is in ~/.vibe/.env or MISTRAL_API_KEY, the first run finds it.
when the month's usage is spent, the key stops until the next billing period, unless pay-as-you-go is on in your Mistral organization: then it draws on your prepaid credits. pay-as-you-go is off by default, and a Pro plan bought through Google, Apple, Free Mobile or Orange can't turn it on. your usage is at Code › CLI › View organization usage (Mistral's help).
where it's saved
| file | what |
|---|---|
~/.bise/auth.json | the keys, and the ChatGPT sign-in: its tokens, your email and plan. only you can read it (0600) |
~/.bise/host-id | an id for this machine, made once before the first ChatGPT sign-in. not a secret |
the ChatGPT token renews by itself while bise runs. a token never goes in the environment, a log, or a command line.
bise auth status # every provider: how it logs in, its state. never a secret
bise auth status --json # the same, for a script or an agent
bise doctor # also says how long the ChatGPT sign-in is good forwhat bise sees from your other tools
bise looks whether Codex is signed in with ChatGPT, and whether Claude Code is signed in with a Claude plan. it looks only at whether their login is there (a file, or on a Mac a keychain entry), never at the tokens, to tell you the right next step:
- Codex with ChatGPT: the first run marks Continue with ChatGPT, "you use it in Codex already". bise still signs in on its own.
- Claude Code with a Claude plan: the first run,
/provider,bise auth statusandbise doctorpoint at the plan's monthly API credits (below).
Claude Max or Team: the monthly API credits
a Claude plan's sign-in works only in Claude Code and Anthropic's apps (Anthropic's terms), so bise never signs in with it. but Max and Team come with monthly API credits that work in any tool, bise included, through an API key:
| plan | API credits each month |
|---|---|
| Max 5x | $100 |
| Max 20x | $200 |
| Team | up to $500 |
| Pro | none |
to use them:
- on claude.ai, open Settings › Billing › API credits and click Link organization: pick or create a Console organization.
- in that Console organization, make an API key.
- paste it in bise: the first run's an API key then Anthropic,
/provider, or
bise login anthropicbise login anthropic shows these steps too. the credits pay for that organization's API calls; past them, its usual API billing applies. Anthropic's help article: support.claude.com/en/articles/17154008.
not supported
| plan | why |
|---|---|
| Claude Pro or Max sign-in | Anthropic's terms allow a plan's sign-in only in Claude Code and Anthropic's apps. Max and Team have monthly API credits for a key (above); Pro has none: use an Anthropic API key, or Claude through OpenRouter |
| GitHub Copilot | Copilot's sign-in for other tools comes from partnerships with those tools (OpenCode has one). bise has none |
| SuperGrok | the same: no partnership with xAI. an xAI API key works |
| Gemini CLI, Antigravity | Google's terms keep these logins to Google's tools. a Google AI Studio key works |