anomalyco / anomalyco/opencode
Muse Spark 1.2 Contributor works on Command Code but blocked by RegionError on OpenCode Go (same country, same IP)
@MrMushrooooom is already working on this.
Since Aug 20, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Summary
muse-spark-1.2-contributor is listed in OpenCode Go's model list and docs (marked "available in select regions"), but calling it from South Korea returns RegionError: This model is not available in your country.
However, the same model works fine on Command Code (another Go-style subscription provider) from the same country and same IP. This inconsistency suggests the region gate may be misconfigured on the OpenCode side.
Reproduction
OpenCode Go (fails)
curl -s -X POST "https://opencode.ai/zen/go/v1/chat/completions" \
-H "Authorization: Bearer $OPENCODE_GO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"muse-spark-1.2-contributor","messages":[{"role":"user","content":"Reply with exactly: OK"}],"max_tokens":20}'
Response:
{"type":"error","error":{"type":"RegionError","message":"This model is not available in your country."}}
Command Code (works) — same country (South Korea), same IP
curl -s -X POST "https://api.commandcode.ai/provider/v1/chat/completions" \
-H "Authorization: Bearer $COMMANDCODE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"meta/muse-spark-1.2-contributor","messages":[{"role":"user","content":"Reply with exactly: OK"}],"max_tokens":20}'
Response: HTTP 200, normal chat completion (model: meta/muse-spark-1.2-contributor)
Environment
- Location: South Korea (Seoul, residential IP)
- OpenCode Go model list:
muse-spark-1.2-contributorpresent (viaGET /zen/go/v1/models) - Command Code model list:
meta/muse-spark-1.2-contributorpresent (viaGET /provider/v1/models) - Both subscriptions active (paid)
Expected behavior
If the model is available to Command Code subscribers in South Korea, it should also be available to OpenCode Go subscribers in the same region — or the docs should clearly state which regions are excluded and why the exclusion differs between the two providers that offer the same Meta model.
Additional context
- Related issues: #43379 (streaming finish_reason), #43584 (reasoning stream), #43477 (Endpoint unavailable), #43680 (jitter/truncation)
- The RegionError appears before any model invocation — it is a gateway-level region check, not a model error.
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.