anomalyco / anomalyco/opencode
[FEATURE]: Support Responses API for deepseek-v4-flash on opencode-go
Open
@MrMushrooooom is already working on this.
Since Jul 31, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
DeepSeek's formal deepseek-v4-flash-0731 checkpoint (released Jul 31, 2026) natively supports the OpenAI Responses API (https://api.deepseek.com → /v1/responses). However, opencode-go only serves deepseek-v4-flash via /v1/chat/completions:
POST https://opencode.ai/zen/go/v1/responseswithdeepseek-v4-flash→HTTP 400: Error from provider (Console Go): Upstream request failed- The same endpoint works fine for GPT-5.x models (e.g.
gpt-5.6-luna) - The same request succeeds against DeepSeek's official Responses API
This blocks Codex-style clients (which speak the Responses protocol) from using DeepSeek V4 Flash through opencode-go.
Proposed behavior:
- Switch
deepseek-v4-flashupstream to the 0731 checkpoint that supports Responses API natively. - Forward
/v1/responsesrequests fordeepseek-v4-flashto the upstream Responses endpoint (like GPT-5.x models). - Keep
/v1/chat/completionsworking for backwards compatibility.
Additional context:
- DeepSeek official docs: https://api-docs.deepseek.com/zh-cn/guides/responses_api
- Related: #39823 (is the 0731 checkpoint live?), #39827 (Go gateway outage today)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.