anomalyco / anomalyco/opencode

[user_blocked] Muse Spark 1.3 Free access restricted via OpenCode Zen — no appeal path

Open
#49,057 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

While using OpenCode with the Muse Spark 1.3 Free model through the OpenCode Zen provider, every message returns the following error, in both new and existing sessions:

Error: Error from provider (Console): Upstream request failed: [user_blocked] Your access has been restricted due to repeated policy violations.

I was not doing anything unusual — just normal prompting for a project I'm currently working on. The block persists across brand-new sessions with no context carried over, and there is no visible way to see what specific "policy violation" triggered it or how to appeal it from within the app.

Plugins

None / default installation (no custom plugins)

OpenCode version

v2.0.3

Steps to reproduce
  1. Open OpenCode on Windows
  2. Start a new session with the "Build" or "Operator" agent
  3. Select provider: OpenCode Zen, model: Muse Spark 1.3 Free
  4. Send any prompt (e.g. "HI")
  5. The [user_blocked] error returns immediately
Screenshot and/or share link
Image
Operating System

Windows

Terminal

Windows Terminal

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.

Research direction

Reproduce the reported steps on Windows using OpenCode Zen and the Muse Spark 1.3 Free model, then determine whether the [user_blocked] response is generated by OpenCode or the provider. The issue names no source file, test, or project-owned expected change; progress requires an agreed handling or appeal-path scope before implementation can be considered done.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.