Custom provider docs incorrect

Description

The below is incorrect there is no other option after running /connect in opencode

[Custom provider](https://opencode.ai/docs/providers/#custom-provider)
To add any OpenAI-compatible provider that’s not listed in the /connect command:

Tip

You can use any OpenAI-compatible provider with opencode. Most modern AI providers offer OpenAI-compatible APIs.

Run the /connect command and scroll down to Other.

Terminal window
$ /connect

┌  Add credential
│
◆  Select provider
│  ...
│  ● Other
└

OpenCode version

No response

Steps to reproduce

$ opencode
type and run '/connect'
search for "other"

Screenshot and/or share link

No response

Operating System

mac OS 15.5

Terminal

vs code terminal

This issue might be a duplicate of existing issues. Please check:

[FEATURE]: Include custom providers in /provider and /connect command #5250: Request to include custom providers in /provider and /connect command

Feel free to ignore if none of these address your specific case.

Oof good catch!

I can fix this, in the meantime try opencode auth login instead

/oc can you fix /connect in the tui (and maybe the server too if needed so that you can connect a custom provider too)?

Created PR #6014

opencode session | github run

+1

I see no reason not to add this feature. Does literally nobody need the custom options?

If you want to use your own endpoint, you need to follow these steps to set it up:

First, configure your opencode.json (remember to swap the baseURL with your own):

{
  "$schema": "https://opencode.ai/config.json",
  "model": "new-api/claude-opus-4-5-20251101",
  "provider": {
    "new-api": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "new-api",
      "options": {
        "baseURL": "http://10.10.10.1:2333/v1",
        "setCacheKey": true
      },
      "models": {
        "claude-opus-4-5-20251101": {
          "name": "Claude 4.5 Opus"
        }
      }
    }
  }
}

Then use opencode auth login {provider.custom_name} (or maybe the connect command?) to cache the api-key for your custom endpoint.
If you don't want to cache it, you can set the apiKey directly inside the provider's options.
You can modify custom_name to whatever endpoint name you prefer.

Important: The top-level model field (indicated in the structure above) is crucial. If it's left blank or incorrect, your opencode will keep receiving 429 errors (I don't even know where these 429s are coming from; my custom endpoint never received those requests).

Finally, open opencode again and type /model. You should be able to see your configured endpoint and model name.

Yesterday, I spent 2 hours digging through the source code and official documentation to debug this. After finally setting it up, I entered my project and ran /init... and opencode just froze dead.

I started the init task yesterday at 22:51:24. I watched my API endpoint logs: it received a request at 22:51:24, a second one at 22:51:28, a third at 22:53:04, and a fourth at 22:53:10. Then, absolutely nothing. No further requests were sent to my endpoint up until 23:07, yet opencode still displayed that it was "running".

It wasted nearly 3 hours of my time yesterday, and I got absolutely nothing out of it.

I saw official accounts on WeChat hyping this thing to the sky, saying how "easy" it is. They even claimed you could just say "Help me install the Oh My OpenCode plugin" inside opencode and it would auto-configure everything. The result? I just got a response saying: "It seems the user has a misunderstanding; opencode is installed successfully but there is no Oh My OpenCode plugin."

Maybe the official team is afraid that once this is actually set up, coding will become a breeze. So, they intentionally set the barrier for configuring custom endpoints as high as the Himalayas, just to ensure you don't miss out on the pain of coding without AI assistance.

Btw: To be honest, this is the biggest pile of sh*t I've eaten in 2026. If I were a QA for opencode, finding such terrible UX, I would absolutely never have let this be released.

Apologies for the outburst, this is the first time I've vented like this on GitHub.
It's just frustrating to see people hyping it up as effortless, when in reality, the actual hands-on experience is incredibly difficult. Combined with the fact that I spent 3 hours—time that should have been used for something meaningful—struggling with configuration only to end up with nothing.
I know that when a product fails like this, it's not just one person's error but usually a chain of oversights, but I just can't help being angry about it.

opencode web cannot select custom providers

@Zhen-Bo

Thanks @Zhen-Bo for describing your method for creating custom endpoints here! I just spent two hours trying to get it to work. Why isn't it better documented?

Hi followed the instructions above but I get an error about the PromptCacheKeys

Bad Request: Bad request: json: unknown field "promptCacheKey"

opencode version 1.1.25

EDIT: having a look as the opencode node_modules folder in ~/.opencode I can see the npm package @ai-sdk/openai-compatible is not installed, is that the issue?

Use @ai-sdk/openai or @ai-sdk/anthropic instead and try to update your api proxy.
OR you can try to do a fresh install with curl -fsSL https://opencode.ai/install | bash

@srggrs

@srggrs just don't set this "setCacheKey": true

Thank you it worked!

I used this

"provider": {
    "qwen-coding-plan": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Qwen Coding Plan",
      "options": {
        "baseURL": "https://coding-intl.dashscope.aliyuncs.com/v1",
        "apiKey": "{env:QWEN_API_KEY}"
      },
      "models": {
        "qwen3-coder-plus": {
          "name": "qwen3-coder-plus"
        }
      }
    }
  },

for the qwen coder coding plan. Docs are def out of sync because the schema doesn't match anymore

I'm also having the same issue.

Why do we have to set models manually in the config? Can we let opencode connect to v1/models to fetch the full list of models on the custom provider?

+1

It's been a year. When are you gonna fix this piece of shit bug?

The documentation corresponding to this issue is: Custom provider | Providers | OpenCode

Please either:

Implement the functionality to be inline with the current docs.
Replace the docs with something that is actually usable, e.g. Custom provider docs incorrect #5937 (comment).

For llama.cpp users you can also refer to llama.cpp | Providers | OpenCode.

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

There is no "other" option when using /connect

Navigation Menu

Repository navigation

Custom provider docs incorrect #5937

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

6 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Custom provider docs incorrect #5937

Description

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

github-actions commented on Dec 22, 2025

rekram1-node commented on Dec 22, 2025

rekram1-node commented on Dec 23, 2025

opencode-agent commented on Dec 23, 2025

aiyinyuedejustin commented on Jan 3, 2026

Aaalice233 commented on Jan 6, 2026

Aaalice233 commented on Jan 6, 2026

Zhen-Bo commented on Jan 6, 2026

mudssky commented on Jan 7, 2026

RomainTFasst commented on Jan 12, 2026

6 remaining items

Zhen-Bo commented on Jan 19, 2026

rekram1-node commented on Jan 19, 2026

srggrs commented on Jan 19, 2026

lucapette commented on Jan 23, 2026

merge-maestro commented on Feb 22, 2026

lahwaacz commented on Mar 19, 2026

LeiCraft commented on Apr 19, 2026

LOYINuts commented on Apr 22, 2026

brlin-tw commented on May 1, 2026

brlin-tw commented on May 1, 2026

github-actions commented on Jul 3, 2026

tanvirrb commented on Sep 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions