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
idk if I am alone upset/frustrated with zed.dev few ux things the options keeps shifting for ACP registry or providers thingy
I wish they have stable thing and in menubar the command to navigate it flawlessly currently it kinda becoming dashboard hell multiple places exploration needed to find simple options
in menubar there is command for extensions but not for ACP
idk if I am supposed to create bug request in zed's repo it!
@Paranjayy / @Hona this is not an OpenCode issue nor a Zed issue.
This issue is confusing the three different ways to run OpenCode in Zed: OpenCode in a Terminal Thread (literally the opencode CLI in a Terminal that's opened as a tab in Zed without any integrations), OpenCode as an External Agent (opencode CLI in a Terminal in Zed that is connected to Zed through ACP and offering nice integrations), and OpenCode as a provider in Zed Agent (Zed Agent calling OpenCode inference APIs). I agree that the three options available are a bit confusing and that the differences are not immediately clear 😅
The screenshots posted here show that OpenCode as an External Agent was indeed installed (right side of the screenshot - ACP Registry tab) but that OpenCode as a provider in Zed Agent is used (left side of the screenshot - New Zed Agent Thread). To use OpenCode ACP you'd click on that New -> External Agents -> OpenCode.
OpenCode as an External Agent shows Kimi K3 correctly, appearing as OpenCode Go / Kimi K3 in the ACP model select.
OpenCode as a provider in Zed Agent uses a hard-coded model list and will get Kimi K3 as an option when zed-industries/zed#61199 is merged and will appear as Go: Kimi K3 in the Zed Agent model selector.
Closing because this is not an OpenCode ACP model-list defect. As clarified above, the screenshots use Zed Agent with OpenCode as an inference provider, whose model list is maintained by Zed. OpenCode as an ACP External Agent already exposes OpenCode Go / Kimi K3; Zed provider support is tracked by zed-industries/zed#61199. No OpenCode repository change is required.
Activity
Paranjayy commentedon Jul 17, 2026
Vlaaaaaaad commentedon Jul 20, 2026
@Paranjayy / @Hona this is not an OpenCode issue nor a Zed issue.
This issue is confusing the three different ways to run OpenCode in Zed: OpenCode in a Terminal Thread (literally the
opencodeCLI in a Terminal that's opened as a tab in Zed without any integrations), OpenCode as an External Agent (opencodeCLI in a Terminal in Zed that is connected to Zed through ACP and offering nice integrations), and OpenCode as a provider in Zed Agent (Zed Agent calling OpenCode inference APIs). I agree that the three options available are a bit confusing and that the differences are not immediately clear 😅The screenshots posted here show that OpenCode as an External Agent was indeed installed (right side of the screenshot - ACP Registry tab) but that OpenCode as a provider in Zed Agent is used (left side of the screenshot - New Zed Agent Thread). To use OpenCode ACP you'd click on that New -> External Agents -> OpenCode.
OpenCode as an External Agent shows Kimi K3 correctly, appearing as
OpenCode Go / Kimi K3in the ACP model select.OpenCode as a provider in Zed Agent uses a hard-coded model list and will get Kimi K3 as an option when zed-industries/zed#61199 is merged and will appear as
Go: Kimi K3in the Zed Agent model selector.Semi-related: zed-industries/zed#57408 and zed-industries/zed#61199
opencode-agent commentedon Jul 23, 2026
Closing because this is not an OpenCode ACP model-list defect. As clarified above, the screenshots use Zed Agent with OpenCode as an inference provider, whose model list is maintained by Zed. OpenCode as an ACP External Agent already exposes
OpenCode Go / Kimi K3; Zed provider support is tracked by zed-industries/zed#61199. No OpenCode repository change is required.