Configure OpenCode

Add providers under unique IDs, pick the right AI SDK package, and manage OMO configuration.

OpenCode stores providers under provider.<id> in opencode.json, so several connections coexist in one configuration. Every Provider ID must be unique, and editing one provider preserves the others. Remove from tool deletes only that entry, not the others. Its default directory is ~/.config/opencode, and OcHub can also manage its MCP servers and skills.

Add an OpenCode connection

Enter a stable ID such as openrouter or company_ai.

Choose an AI SDK package that matches the upstream:

Upstream	Common package
OpenAI-compatible third party	`@ai-sdk/openai-compatible`
Official OpenAI	`@ai-sdk/openai`
Anthropic / Claude	`@ai-sdk/anthropic`
Amazon Bedrock	`@ai-sdk/amazon-bedrock`
Google Gemini	`@ai-sdk/google`

Enter Base URL and API key. An official SDK may use its default endpoint.
Add model IDs, display names, and optional context and output limits.
Add options.* extensions or request headers only when required.
Confirm that the preview changes only the intended provider.<id>.
Save, add or switch, then choose the provider and model in OpenCode.

Option extensions parse booleans and numbers as literals. They can express setCacheKey or Bedrock region and credentials. Verify the expected type.

OMO configuration

Advanced tools can read and disable OMO / OMO Slim. Disabling deletes the corresponding file and clears current markers on related connections:

Read OMO or OMO Slim first.
Back up the OpenCode directory.
Disable only when it is no longer needed.
Return to the OpenCode page and verify the current connection.

After saving, follow the verification checklist to confirm the new connection works. For configuration layers, credentials, AI SDK protocol selection, and sharing, see Advanced OpenCode pitfalls.