anomalyco / anomalyco/opencode

Hy3-preview incorrectly listed in go model list api

Open
#39,709 1 comment 0 reactions 1 assignee View on GitHub

@StarpTech is already working on this.

Since Jul 30, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

Summary

/zen/go/v1/models endpoint listing hy3-preview which cannot be called.

Expected behaviour

All models listed in /zen/go/v1/models can be called if you have a valid Go api key

Actual behavior

/zen/go/v1/models lists hy3-preview

> curl https://opencode.ai/zen/go/v1/models   -H "Authorization: Bearer $OPENCODE_API_KEY"   -H "Content-Type: application/json" | jq 

...
    {
      "id": "hy3-preview",
      "object": "model",
      "created": 1785428879,
      "owned_by": "opencode"
    },
...

But calling it results in failure:

> curl https://opencode.ai/zen/go/v1/chat/completions   -H "Authorization: Bearer $OPENCODE_API_KEY"   -H "Content-Type: application/json"   -d '{"model": "hy3-preview","messages": [{"role": "user","content": "respond with hello"}]}'                                                              


{"error":{"message":"Error from provider (Console Go): Model hy3-preview is not supported on the lite model list. Use GET /inference/go/openai/v1/models to list available models.","type":"invalid_request_error","param":"model","code":"model_not_supported"}}
Remarks

I dont know if this is the best way to report the bug, or if it should even appear here at all. Discord bug report does not target backend. This is the only place I can think of before resorting to emails.

If this isnt the place to report to, please direct me to the suitable channels. Thank you for the time taken to read my issue.

Plugins

No response

OpenCode version

No response

Steps to reproduce
  1. Open https://opencode.ai/zen/go/v1/models. Observe hy3-preview present
  2. Attempt to request with hy3-preview results in failure
Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.