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
[FEATURE]: add Responses API support for Go service #23655
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Feature Request
Is your feature request related to a problem? Please describe.
The OpenCode Go service currently only supports the /v1/chat/completions endpoint (OpenAI Chat Completions API format).
However, the OpenAI Responses API is becoming the new standard for agentic workflows. Some tools (such as Claude Code adapters and other agent frameworks) expect the Responses API format rather than the Chat Completions format.
Currently, if I want to use the Go service with a tool that expects Responses API, I cannot.
Describe the solution you'd like
Add /v1/responses endpoint support for the Go service (https://opencode.ai/zen/go/v1/responses).
Why this is feasible
The Zen service already supports the Responses API endpoint: /zen/v1/responses
This means the routing logic and handler implementation already exist in the codebase. The Go service likely just needs the same route added.
Describe alternatives you've considered
Using Chat Completions endpoint with a translation layer – not ideal, adds latency and complexity
Switching to Zen service – but that uses different models (GPT series) and is more expensive
Additional context
Zen service Responses endpoint: https://opencode.ai/zen/v1/responses
Models affected: GLM-5.1, GLM-5, Kimi K2.5, MiniMax M2.5 (all Go service models)
Would you be willing to contribute?
No, I am just submitting a feature request.
Use case
I purchased the OpenCode Go plan and want to use it with Claude Code (via an adapter that expects Responses API format). Adding this endpoint would unlock the Go service for many similar use cases.
Reacted by Trasis33, CHNtentes, Rakib, Yan Ang, Zane, Niklas Sheth, Yohei Okabayashi, Ivan Mironov, Muhammad Mohsin Lakhani, Bryan Kok and 21 more
I am an OpenCode Go subscriber and would like this prioritized for deepseek-v4-flash.
DeepSeek V4 Flash now supports the Responses API, but Go currently routes it
through /zen/go/v1/chat/completions. Codex custom providers only use the
Responses protocol, so this requires a Responses-to-Chat bridge.
In real usage with Codex + CC Switch, tool-heavy requests intermittently fail
or stop after partial output. The upstream error observed is:
Failed to deserialize the JSON body into the target type: tools[14].function: missing field name
Please expose:
POST /zen/go/v1/responses
for deepseek-v4-flash, with full streaming completion semantics and tool-call
compatibility. This would let Codex use V4 Flash without a protocol conversion
layer.
Could you confirm whether this is planned, and whether Go entitlement will
cover this endpoint?
Reacted by Dmitry, 日常无语者 / SilentPerson, Tony Liu, Tendo, GuiLuan, MMMaoTS, Murat Eroğlu, Zhang Yaowei, Arnakii, Aalivexy and 17 more
To restate it: you'd like the OpenCode Go service to offer an OpenAI Responses API endpoint (https://opencode.ai/zen/go/v1/responses), as Zen already does at /zen/v1/responses. Tools that only speak the Responses format, such as Claude Code adapters, could then use Go models like GLM-5.1, Kimi K2.5 and MiniMax M2.5.
This is a change to the hosted Go service, not to the OpenCode app, so it can't be added with an OpenCode plugin. I've marked it as a feature request, and the maintainers will consider it.
Activity
github-actions commentedon Apr 21, 2026
This issue might be a duplicate of existing issues. Please check:
These issues discuss similar Responses API support, though your request is specifically scoped to the Go service endpoint.
lightrao commentedon Apr 28, 2026
/api/v1/chat/completions
vs
/api/v1/responses
I am opencode go sub, I need "/api/v1/responses" api end point.
rakibdev commentedon May 2, 2026
responses api also provides websocket mode https://developers.openai.com/api/docs/guides/websocket-mode
would be nice to have it in go
anthonyespirat commentedon Jul 6, 2026
any update on this ?
BacLuc commentedon Jul 13, 2026
Jetbrains IDEs only support responses API.
It would be really nice if this was supported.
miups commentedon Aug 3, 2026
I am an OpenCode Go subscriber and would like this prioritized for
deepseek-v4-flash.DeepSeek V4 Flash now supports the Responses API, but Go currently routes it
through
/zen/go/v1/chat/completions. Codex custom providers only use theResponses protocol, so this requires a Responses-to-Chat bridge.
In real usage with Codex + CC Switch, tool-heavy requests intermittently fail
or stop after partial output. The upstream error observed is:
Failed to deserialize the JSON body into the target type: tools[14].function: missing field namePlease expose:
POST /zen/go/v1/responsesfor
deepseek-v4-flash, with full streaming completion semantics and tool-callcompatibility. This would let Codex use V4 Flash without a protocol conversion
layer.
Could you confirm whether this is planned, and whether Go entitlement will
cover this endpoint?
ronething commentedon Sep 13, 2026
I also hope to support this feature. The current implementation, especially when I Use Computer Use, is prone to problems.
opencodejr commentedon Oct 29, 2026
Thanks for the request, @xiaoyingv!
To restate it: you'd like the OpenCode Go service to offer an OpenAI Responses API endpoint (
https://opencode.ai/zen/go/v1/responses), as Zen already does at/zen/v1/responses. Tools that only speak the Responses format, such as Claude Code adapters, could then use Go models like GLM-5.1, Kimi K2.5 and MiniMax M2.5.This is a change to the hosted Go service, not to the OpenCode app, so it can't be added with an OpenCode plugin. I've marked it as a feature request, and the maintainers will consider it.
trim21 commentedon Nov 8, 2026
they already have
https://opencode.ai/zen/go/v1/responsesfor someone still waiting for this featurehttps://opencode.ai/docs/console/go/#endpoints