Provider authentication belongs to the connected OpenCode service, not to the browser device or one CodeNomad project. Model-display preferences, subscription quotas and web-search choices have different scopes.
- Open a workspace, then Settings → Providers. Models starts expanded; expand Web search for search providers. Images holds the image settings.
- In that group, choose Select provider, then Connect.
- For a model provider, complete the native Authentication method offered: API key, OAuth or command. For OAuth, use Open authorization page and submit an authorization code only when requested. Search providers connect with an API key.
- Check the configured-provider row after completion. Models rereads after connections, account changes and reconnects; Web search also has Refresh.
Search-only integrations appear under Web search, not Models. Saving authentication does not choose a model or change the default search provider. API keys and OAuth credentials are saved by the active OpenCode server. The browser receives connection metadata, not saved credential secrets. A connection sourced from environment variables is read-only in this UI: change its owning environment rather than trying to disconnect it here.
If the authorization window is blocked, use Open authorization page, Open in this tab or Copy link from the flow. Do not publish the authorization link or code in diagnostics.
- In the provider's row, use Active account to select a saved credential.
- Use Add account to authenticate another connection.
- To manage a different saved account, select it first, then use Rename account or Remove account. Renaming uses Account label and Save; Remove account acts immediately, without a confirmation.
Selection, renaming and removal affect that integration across the OpenCode service, including other projects and clients. Removing a credential can leave those clients without authentication; it does not delete conversation history or revoke the provider's remote account. Environment connections cannot be selected as writable saved credentials or removed here. If an operation fails, CodeNomad rereads the accounts: check Active account again before acting.
With multiple saved credentials on a supported integration, Auto-select account opts into quota-based selection before the next prompt/custom-command admission through CodeNomad. The setting is per integration in CodeNomad configuration; a resulting account selection is service-wide.
| Eligible integration | Eligible account type |
|---|---|
| OpenAI / Codex | Codex browser/device OAuth subscription accounts, not OpenAI pay-as-you-go keys or the ChatGPT sign-in method whose usage OpenAI does not provide. |
| OpenCode Go | Go key, or OpenCode Console sign-in/key used for the Go provider only, not Zen pay-as-you-go credits. |
| Anthropic | OpenCode's Claude Pro/Max OAuth login, not the Claude Code login. |
| GitHub Copilot | OAuth with readable premium-request quota; enterprise-endpoint credentials are not readable candidates. |
| Coding plans | Key-based zai-coding-plan, zhipuai-coding-plan, kimi-for-coding, minimax-coding-plan, minimax-cn-coding-plan. |
Only a full current account triggers switching; merely having a fuller alternative does not. Reads examine explicit saved credentials without activating candidates or exchanging refresh tokens. Codex, Copilot and coding plans require a demonstrably available candidate. Go, Console and Claude may use an unknown-quota candidate unless a recent native quota failure marks it exhausted. OpenCode Go readings depend on the available API and credential permissions.
This is not in-flight failover. It neither retries failed requests nor replays prompts, commands or mutations. It does not rotate environment connections, arbitrary providers, pay-as-you-go balances or external Claude Code logins. Manual account changes are respected during selection preparation; there is no cross-client account lock. On quota/authentication errors, inspect Active account, refresh Usage and sign in with the credential's owner as needed before deliberately sending again.
- Choose Manage models beside a model provider.
- Search by name/ID and change visibility; Show all and Hide all affect that provider's selector list. Drag across the checkboxes to change several models at once.
- In a conversation's Model selector, use Add to favorites or Remove from favorites; Show all models leaves favorites-only filtering.
- Use Thinking in the composer for variants the selected model exposes.
Visibility and favorites organize CodeNomad's selectors; they do not uninstall models, remove credentials or prevent other OpenCode clients from using them. Hiding a model is not account disconnection. Thinking selects a model variant for subsequent sends, not the visibility of reasoning already in the transcript. Restore hidden models with Manage models → Show all.
Use Usage in the right panel for the active conversation's provider-plan windows, reset times and supported balances. These provider readings are different from per-message Tokens and cost estimates: a subscription quota is not a bill calculated from the visible transcript. A missing, stale or unknown reading is not zero usage or proof of remaining capacity. Provider credit balance in Settings → Advanced controls supplemental balance display.
For Google connections using OpenCode's Gemini CLI authentication method, Usage shows per-model limits; for Antigravity connections, it shows 5 hours and Weekly limits, with separate model-family pools where supplied. Unavailable quota shows “Usage is temporarily unavailable.” These connections stay under manual account selection.
Google's Antigravity FAQ states that using third-party software with an Antigravity login violates its terms and may lead to account suspension or termination.
For free OpenCode Zen models, Usage estimates consumption from this service's recorded steps since 00:00 UTC, using an assumed reference of 200 requests/day and the next UTC midnight as an estimated reset. Steps approximate requests; other traffic and changing IP-based limits can make the estimate differ from actual quota usage.
OpenAI does not provide usage for one ChatGPT sign-in method: Usage says so instead of showing quota windows. Choose View ChatGPT usage to review app usage and manage access to your plan and credits in ChatGPT. Chatting still works, and reconnecting the same login does not restore the reading.
Usage credential sources depend on the provider. Claude through anthropic/claude uses OpenCode's Anthropic OAuth. OpenCode's Claude Agent provider (claude-agent) and the claude-code provider use the Claude Code login on the daemon's host, including its WSL distribution: CLAUDE_CODE_OAUTH_TOKEN, then the stored login, with CLAUDE_SECURESTORAGE_CONFIG_DIR / CLAUDE_CONFIG_DIR or ~/.claude determining file storage; local macOS can use Keychain. CodeNomad does not substitute one Claude login for the other.
Usage readers may refresh access tokens only in server memory and only for providers whose refresh token stays stable on each use, including Gemini CLI and Antigravity. OpenCode retains ownership of the saved connection. For other expired provider logins, refresh/sign in through their owner—OpenCode, Claude Code or Codex CLI—then refresh CodeNomad. A CodeNomad server-login expiry is separate: reconnect/sign in to CodeNomad without assuming a failed provider request will be resent. See Troubleshooting.
When MiniMax successfully returns no limits, Usage shows MiniMax doesn't share its limits in place of quota values.
OpenRouter Key Limit shows the key's remaining USD allowance against its spending limit; a key without a spending limit has no such row. Account credits appear separately when the API permits access. Usage uses the provider's configured baseURL, including its path prefix, or https://openrouter.ai/api/v1 when absent. Use a public HTTPS hostname without credentials, an explicit port, query or fragment; IP addresses and localhost are rejected. An invalid URL or a gateway without /key makes usage unavailable; the key stays at the configured destination and redirects are rejected.
For z.ai and Zhipu, Usage prefers the configured apiKey, including {env:…} and {file:…} values resolved by OpenCode on its host, then uses the saved credential if that key is unavailable. A missing key with no saved credential is shown as unconfigured. Business errors show a translated provider error and its numeric code when available, instead of quota values. Plan credits use the five-hour and weekly windows; MCP tools have a separate allowance.
GitHub Copilot Usage shows consumed allowance as used / limit used, or consumed credits for an unlimited pool when GitHub supplies them; otherwise it shows Unlimited. Premium requests keep their own label. The footer includes the recognized plan name. Enterprise connections use https://api.<host>/copilot_internal/user from the saved connection's host or HTTPS root URL. Use a qualified hostname without credentials, an explicit port (even :443), a path beyond /, query or fragment; IP addresses and localhost are rejected before sending the token. Redirects are rejected. An invalid destination or a server without this API leaves usage unavailable. Enterprise connections stay outside automatic account selection.
Kimi supports kimi-code-plan-cn (kimi.com), kimi-code-plan-global (kimi.ai), kimi-for-coding and kimi. Usage tries each integration's active saved key, starting with the conversation's integration, within one shared deadline. It shows available five-hour, weekly, Monthly and Monthly coding caps as percentages used. Monthly caps follow the provider's reset date; a kimi-for-coding account with either monthly cap exhausted is unavailable for automatic selection even when a shorter window has capacity.
OpenCode Go API keys show the available used percentages and reset times. OpenCode Console sign-in also reads the wallet balance in USD when billing access permits it. Enable Provider credit balance to show that separate balance (off by default); Go quotas and Extra Usage remain separate. A wallet balance alone leaves automatic selection's quota unknown. When The OpenCode Go key has expired. appears, choose Create a new key in OpenCode Console, then replace it. Create a key under Account → Personal API keys (or ask an admin for a service-account key), then replace the saved key through the provider connection flow. An expired key requires replacement.
Cursor Enterprise uses private dashboard APIs on a best-effort basis. With a team membership and team ID in the profile, Usage shows the identified gpt-4 request bucket and separate Per-user limit / Team limit amounts in USD when supplied. A cap with unknown spend appears as a cap alone; request counts with an unknown cap appear as used-only counts. Unknown buckets and reset dates stay unavailable. Missing team membership, forbidden access and expired tokens have distinct messages; verified partial readings remain visible.
Supply a current Cursor access token through the variables below. Enterprise reads require permission to read that team's dashboard data; the Admin API uses a separate administrative key. Update an expired token and restart the backend with the updated environment.
Set these in the environment of the CodeNomad backend process before launching it. They are usage-reader credentials, not browser settings or model-selection controls. Changing the session Environment Variables editor does not update a running backend's process.env for these readers. Restart the backend under the intended environment when changing them; do not restart the shared OpenCode service just for a usage-reader variable.
| Usage integration | Environment variable |
|---|---|
| Cursor | CURSOR_ACCESS_TOKEN, falling back to CURSOR_TOKEN |
| Ollama Cloud | OLLAMA_CLOUD_COOKIE |
| OpenCode Go supplemental usage | OPENCODE_GO_WORKSPACE_ID and OPENCODE_GO_AUTH_COOKIE together |
| ZenMux | ZENMUX_PLATFORM_API_KEY — platform key, distinct from the inference key |
| exe.dev | EXE_DEV_USAGE_TOKEN |
| Command Code | COMMAND_CODE_API_KEY fallback when a native credential is unavailable |
Keep tokens/cookies out of shell history, screenshots and reports. Optional readers depend on provider APIs and credential validity; configuring a variable is not a guarantee of usable quota data.
- In Settings → Providers, expand Web search and connect the search integration with its API key if it needs one.
- Choose Default search for Global configuration.
- Use For the current project to override it for the active Location. Hover or focus that selector to see Search in this project with the effective result.
Changes save automatically. Default / inherited uses inherited configuration or the saved native choice; a Project override wins over Global. Disabled turns search off at the selected scope; Automatic provider requests native automatic provider selection. Web search loads its connections and choices only while expanded. Disconnect removes a saved search key; a connection supplied by an environment variable is labelled read-only and has no Disconnect.
Search credentials remain service-global even when the provider choice is Project-scoped. Saving a key does not select it as the search default. If reading/saving fails, refresh before retrying; do not replace configuration blindly. For native configuration details, see OpenCode documentation and OpenCode setup.
- In Settings → Providers, expand Images.
- Image generation is On, automatic model unless you change it: choose one of the image models offered by your connected providers instead, or Off to turn it off in the Global configuration.
- Check Store images once to keep each attached or generated image a single time instead of inside every message that uses it.
Changes save automatically to the Global OpenCode configuration and apply to every project. Both are experimental OpenCode features: Images shows only the settings the connected OpenCode version supports. Agents get the image tool only while a connected provider offers an image model. Each image is generated in the background and saved as a file; the agent reports its path. Store images once applies to new messages. If the project's own OpenCode configuration file decides Store images once, the box shows the value used there and saving also writes it to that file. Otherwise, when another OpenCode configuration, such as the project's own, decides a setting instead, Images says so under that setting. If saving would hide the experimental settings of another OpenCode configuration file, Images stays read-only and says so; change the options in that file instead.
To create, compare and refine images in a dedicated conversation, see Create images with the Design extension.