[FEATURE]:Complete the Desktop configuration workflow for Anthropic-compatible custom providers #34016

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Description

• I have searched the existing issues and found similar feature requests, but this appears to describe a different problem.

Summary

This issue is related to #11692 ("Add Provider Type in custom provider").

"This request is based on behavior observed in OpenCode Desktop v1.17.11. During testing, I found that Anthropic-compatible providers already function correctly when configured manually, suggesting the runtime already supports them. This request is specifically about completing the Desktop configuration workflow."

From testing, Anthropic-compatible providers already appear to be supported by the runtime through @ai-sdk/anthropic. However, the Desktop application and current documentation do not provide a complete workflow for configuring them.

As a result, the feature exists but is difficult to discover and requires manual editing of internal configuration files before it can be used.

Environment

• OpenCode Desktop: v1.17.11
• Operating System: Debian GNU/Linux 13 (trixie) x86_64

Current Behavior

While integrating OpenModel's Anthropic-compatible API, I initially concluded that Anthropic-compatible custom providers were unsupported.

After extensive debugging, I discovered they work correctly.

To make the provider functional, I had to manually edit:

• ~/.config/opencode/opencode.jsonc
• ~/.local/share/opencode/auth.json

Specifically:

• configure the provider using npm: "@ai-sdk/anthropic"
• set the base URL to https://api.openmodel.ai/v1
• manually add the provider credential to auth.json

Without manually editing these files, I could not configure the provider through the Desktop UI.

I also followed the documentation and attempted to configure:

"options": {
  "apiKey": "{env:ANTHROPIC_API_KEY}"
}

However, on OpenCode Desktop v1.17.11, this property is rejected by the Desktop configuration validator, so the documented approach could not be used.

Requested Enhancement

Provide a complete Desktop workflow for Anthropic-compatible custom providers, similar to the existing OpenAI-compatible workflow.

For example:

• Add Anthropic-compatible provider
• Enter Provider ID
• Enter Display Name
• Enter Base URL
• Enter API Key
• Save credentials
• Provider automatically appears in /models

The goal is that no manual editing of internal configuration files should be required for a supported provider type.

Why this would help

From my testing, the runtime already supports Anthropic-compatible providers successfully.

The missing piece is that configuring them currently requires discovering and editing internal files (opencode.jsonc and auth.json) that are not part of the normal Desktop workflow.

This makes the feature appear unsupported even though it already works.

Completing the Desktop workflow and documenting it would:

• Make an existing capability discoverable.
• Eliminate manual configuration for supported providers.
• Reduce confusion during provider setup.
• Improve the onboarding experience for Anthropic-compatible providers such as OpenModel and other gateways implementing the Anthropic Messages API.

Plugins

None

OpenCode version

v1.17.11

Steps to reproduce

1. Install OpenCode Desktop v1.17.11.

2. Attempt to configure an Anthropic-compatible provider (for example, OpenModel) using only the Desktop UI and current documentation.

3. Observe that there is no complete workflow for configuring the provider.

4. Manually edit:

   • ~/.config/opencode/opencode.jsonc
   • ~/.local/share/opencode/auth.json

5. Restart OpenCode.

6. Observe that the provider now loads and functions successfully.

Screenshot and/or share link

No response

Operating System

Debian GNU/Linux 13 (trixie) x86_64

Terminal

Konsole

Note: This request is different from previous provider-support feature requests. It does not request backend support for Anthropic-compatible providers. Instead, it requests exposing an already-functional capability through the Desktop UI and documentation so users can configure it without manually editing internal configuration files.