anomalyco / anomalyco/opencode

OpenCode Go: gpt-5.6-luna still returns HTTP 500 'Internal server error' (confirmed 2026-09-07)

Open
#47,778 2 comments 0 reactions 1 assignee View on GitHub

@MrMushrooooom is already working on this.

Since Sep 7, 2026.

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

Description

Summary

gpt-5.6-luna on the OpenCode Go plan still returns HTTP 500 {"type":"error","error":{"type":"error","message":"Internal server error"}} for every request. Confirmed live on 2026-09-07 with a working Go subscription and the same API key that succeeds on other catalog models. This duplicates earlier reports (#47463, #43565) - still unfixed, adding a fresh data point with a control test.

Reproduction (2026-09-07, plan: OpenCode Go subscription)

curl -sS -o /dev/null -w "%{http_code}\n" \
  -H "Authorization: Bearer $OPENCODE_GO_API_KEY" \
  -H "x-opencode-session: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-5.6-luna","messages":[{"role":"user","content":"Reply with exactly: pong"}],"max_tokens":64}' \
  https://opencode.ai/zen/go/v1/chat/completions

Result: 500 with body

{"type":"error","error":{"type":"error","message":"Internal server error"}}
Control test (same key, same session, same endpoint)
# model: deepseek-v4-pro

Result: 200 with normal completion (content: "pong", finish_reason: "stop").

The same single key succeeds on other models (e.g. deepseek-v4-pro), so this is not an auth or billing issue - the model is listed in the catalog but not wired on the Go router.

Expected behavior

gpt-5.6-luna either works on the Go plan like other catalog models, or is removed/marked unavailable in the catalog so subscribers cannot select a model that always fails.

Context

  • Follow-up of #47463 (Bucket 1: gateway 500s) and #43565 (empty response/403) - both still open.
  • Related service stability thread: #36889.

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.