You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Missing API Key error with OpenCode Go provider (Kimi K2.5) while same API key works with OpenCode Zen #17541
When attempting to use the OpenCode Go provider with the Kimi K2.5 model, the application displays a "Missing API Key" error. However, the exact same API key works correctly when switching to the OpenCode Zen provider.
I am uncertain whether OpenCode Go is expected to use the same API key as OpenCode Zen, or if a separate/different API key should be created. I need guidance on where to obtain the correct API key for the OpenCode Go provider.
Related Issues Reviewed
I have reviewed the following related issues and they do not address this specific scenario:
This issue has been resolved after reinstalling OpenCode.
Resolution: I uninstalled and reinstalled OpenCode using npm on Windows. After the fresh installation, the Kimi K2.5 model works correctly with the OpenCode Go provider using the same API key.
Previous Version: 1.2.26 Current Version: 1.3.2
It appears the installation may have been corrupted. A clean reinstall resolved the issue.
Activity
sdhector commentedon Mar 26, 2026
Update - Issue Resolved
This issue has been resolved after reinstalling OpenCode.
Resolution: I uninstalled and reinstalled OpenCode using npm on Windows. After the fresh installation, the Kimi K2.5 model works correctly with the OpenCode Go provider using the same API key.
Previous Version: 1.2.26
Current Version: 1.3.2
It appears the installation may have been corrupted. A clean reinstall resolved the issue.
LML87 commentedon Jun 26, 2026
I'm reading this issue to understand the resolution - how was this fixed?