Skip to content

Unable to Connect to DeepSeek Provider in OpenCode 1.16.2 – Vendor Missing from /connect List #31242

Closed as not planned

Description

@jixiong398-blip

After upgrading to OpenCode version 1.16.2, the DeepSeek provider is no longer visible when running the /connect command to add a new AI vendor. Following the official integration guide from DeepSeek's documentation (which requires OpenCode >= v1.14.24), entering deepseek in the /connect interface returns "no matching provider found" or the vendor simply never appears in the selection list. This issue did not occur in earlier versions (tested and verified working on v1.14.24 and v1.15.x)

Install or upgrade OpenCode to version 1.16.2.

Launch OpenCode in any project directory.

Type /connect and press Enter.

In the vendor/provider selection interface, type deepseek (or scroll through the list).

Observe that the "deepseek" option does not appear; only other providers such as OpenCode Zen, OpenCode Go, OpenRouter, etc., are shown.

(Optional) Attempt to manually add the provider via opencode.json configuration as a workaround. While this allows the provider to be used, it does not resolve the underlying /connect visibility issue.

Typing deepseek in the /connect command interface should display the DeepSeek provider option, allowing users to seamlessly authenticate and configure the provider as described in the official integration guide.

Activity

  1. jixiong398-blip commented on Jun 7, 2026

    @jixiong398-blip
    Author

    The DeepSeek provider is completely absent from the vendor selection list. The /connect command only shows OpenCode Zen, OpenCode Go, OpenRouter, and possibly a few others — but no deepseek entry. Manually typing deepseek yields no result

  2. github-actions commented on Jun 7, 2026

    @github-actions
    Contributor

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

    These issues describe similar symptoms — the DeepSeek provider not being visible or searchable in the provider/connect interface. Please review that issue to see if your problem is already tracked there, and if so, consider closing this one or adding any new information as a comment there.

  3. jixiong398-blip commented on Jun 7, 2026

    @jixiong398-blip
    Author

    Bug Report: Disconnecting a provider permanently disables it without UI recovery option

    Issue: After disconnecting a provider (e.g., DeepSeek) via the OpenCode UI, the provider is added to disabled_providers in opencode.json and completely removed from the /connect vendor list. There is no way to re-add it or update its API key through the UI – users are forced to manually edit the configuration file.

    Affected Version

    • OpenCode version: 1.16.2 (likely all versions)
    • Platform: Windows 10/11 (also observed on others)

    Steps to Reproduce

    1. Add a provider (e.g., DeepSeek) via /connect and provide an API key.
    2. Use the provider normally.
    3. Later, decide to change the API key or disconnect the provider for any reason.
    4. From the provider management interface, choose "Disconnect" or "Remove" (exact wording may vary).
    5. Observe that:
      • The provider disappears from the /connect vendor list.
      • A line "provider_name" is added to the disabled_providers array in ~/.config/opencode/opencode.json.
    6. Try to reconnect the same provider via /connect – it is not listed, even when typing its name directly.

    Expected Behavior

    • Disconnecting should only clear stored credentials (API key, base URL, etc.), not permanently disable the provider.
    • The provider should remain visible in /connect, allowing the user to re-enter new credentials and reconnect.
    • Alternatively, there should be explicit commands like /provider enable <name> and /provider disable <name> to control the disabled state.

    Actual Behavior

    • Disconnecting equals permanent disabling.
    • The only way to restore the provider is to:
      1. Manually edit opencode.json.
      2. Remove the provider name from disabled_providers.
      3. (Optional) update API key or other settings.
      4. Restart OpenCode.

    Impact

    Suggested Fix

    • Change the “Disconnect” action to only clear credentials (API key, etc.) without disabling the provider.
    • Add a new command /provider enable <name> to re-enable a previously disabled provider (and remove it from disabled_providers automatically).
    • Ensure the provider always appears in /connect unless explicitly disabled by a separate “Disable” action.

    Workaround (for affected users)

    Manually edit opencode.json:

    • Locate the file at ~/.config/opencode/opencode.json.
    • Find the "disabled_providers" array and remove the provider name (e.g., "deepseek").
    • (Optional) Update API key inside the provider's options block.
    • Save and restart OpenCode.

    Additional Context

    This issue is not specific to DeepSeek; it affects any provider that is disconnected via the UI. The current behavior violates the principle of least surprise and should be addressed as a user experience bug.

  4. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions