None of the models from OpenCode Zen work. #47940

Activity

1. github-actions

   assigned

   MrMushrooooom

   on Sep 8, 2026
2. github-actions commented on Sep 8, 2026

   

   github-actionsBot

   on Sep 8, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • 403 Forbidden on zen free models (mimo-v2.5-free and others) for 2+ weeks #45132: 403 Forbidden on zen free models (mimo-v2.5-free and others) for 2+ weeks
   • all models are free do not work #46247: all models are free do not work
   • [bug] GPT-5.6 Luna/Terra return unsupported_country_region_territory via Zen from Hong Kong #40162: GPT-5.6 Luna/Terra return unsupported_country_region_territory via Zen (country restriction)
   • [Zen] AuthError: "Request blocked by upstream provider" — all Zen models broken, account recreated #39827: [Zen] AuthError: "Request blocked by upstream provider" — all Zen models broken

   If your issue is distinct from these, please add more details about which specific models you tried and the exact error messages you received.
3. seven7763 commented on Sep 8, 2026

   

   seven7763

   on Sep 8, 2026

   More actions

   The two error shapes in your report point at different layers, and there's a quick way to tell them apart — worth doing before this gets closed as a duplicate of one family when you're likely hitting both.

   Shape 1 — "not available in this country" (the Meta models). That wording comes from the upstream model provider's geo policy, relayed through Zen. It's per model family, not per account, and no client-side setting changes it. The same shape is tracked in #40162 (Luna/Terra from unsupported regions) — there the provider rejects the request wherever the egress IP lands in an unsupported territory.

   Shape 2 — bare Forbidden with a {"model":"..."} body (the rest). That's the free-model family: #45132 records the exact body — 403 {"model":"mimo-v2.5-free"} — persisting 2+ weeks across multiple accounts and models (nemotron/laguna/mimo), with hy3-free working. Since it reproduces for many users with valid keys, it's very unlikely to be an account flag on your side.

   The distinguishing test: take one model from each group and call the Zen REST endpoint directly, outside the client, with the same key:

   curl https://opencode.ai/zen/v1/chat/completions \
     -H "Authorization: Bearer <your-key>" \
     -H "Content-Type: application/json" \
     -d '{"model":"<model-id>","messages":[{"role":"user","content":"hi"}]}'
   

   • If the direct curl fails with the same body → the model/region/family itself is rejecting the key; nothing in OpenCode Desktop is involved.
   • If the direct curl succeeds but the client fails → then it's a client-side routing/header issue and worth a fresh non-duplicate report with the model IDs.

   That split will also tell the maintainers which of the open dupes (#40162, #45132) your report actually belongs to.
4. thdxr commented on Oct 11, 2026

   

   thdxr

   on Oct 11, 2026

   Member

   More actions

   Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
5. thdxr

   closed this as not plannedon Oct 11, 2026