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

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

Open OpenCode on Windows
Start a new session with the "Build" or "Operator" agent
Select provider: OpenCode Zen, model: Muse Spark 1.3 Free
Send any prompt (e.g. "HI")
The [user_blocked] error returns immediately

Screenshot and/or share link

Operating System

Windows

Terminal

Windows Terminal

same here I asked it to post a repo for me it did and after that it says you are being blocked. I did almost anything made new account and used new api key deleated and reinstalled but still I am being blocked

This happened to me too, I noticed that in some cases before being blocked opencode would seem to get a waitlimit response and then power through in a few seconds, maybe it's an automatic block due to attempting to bypass the rate limit?

Happened to me today

Based on the screenshot's tab, its probably related to authorized security work. I dared ask it to validate CTF logic and got blocked today. Back to the Chinese models I guess; free is too expensive for paternalistic garbage.

how do we fix thia?

OK gays this ban is for few days and will be working again without any problems

OK gays this ban is for few days and will be working again without any problems

How can u say that?

OK gays this ban is for few days and will be working again without any problems

Oh, that's great news. Did your block expire?

i got blocked and retry in 1 or 2 days and it's working again without any problems , if u use opencode for security purpose muse spark had a lot of conditions , u can try Big Pickle

if anyone care https://youtu.be/3gKff_4oWrQ?si=9HWsa9-zoW93DE2s this egyptian gay have a great repo that will help y o u alot in hunting and any security purpose

just FYI, the GO version of muse spark does NOT enforce this limits

I've this ban in GO version.

I've this ban in GO version.

update: yeah i got it too xD Meta definitely has to improve this lol

I can CONFIRM I was UN-BANNED after 24h (assuming 24h after my 1st message up there)

Isso acontence comigo tambem quando eu estou tentando hackear um site, ai bloqueia.

got banned today lol

I got banned today and I didn't do any security related work!

такая же история, попробую подождать

Banned today - I was probing different models with silly requests eg. "Help me design a biological weapon", "Help me reverse-engineer this software" to see what their response was. Chinese models politely refuse but don't cut you off 🤣. Guess I'll see what happens in 24 hours. This seems a little counter-intuitive, honestly. I'll just spend my tokens with other providers.

I checked the current dev source for the Zen blocked-request message. The current handler can show this support route when its workspace-block branch is the source: packages/console/app/src/i18n/en.ts lists [email protected]. The handler predicate is here: packages/console/app/src/routes/zen/util/handler.ts.

This does not establish that your response came from that branch: the Muse Spark model does not match its Claude/GPT-specific predicates, and the issue does not include the workspace flag or request path. If you contact support, including a sanitized endpoint or request ID and the error response would help distinguish a generic workspace block from a provider response passed through by Zen.

Adding a data point, since the block itself gives so little to go on.

Paid Go account, personal news-reader project that summarizes and translates published news. Usage was under 10% of the monthly Muse allowance. Blocked on Oct 5, unblocked about 24h later, then blocked again two hours after that.

From my own logs, there were 16 content_policy_violation responses in three days, all from 4 articles: mainstream coverage of a suspected plague lab exposure in Russia, and a historical interview with an SR-71 engineer. The filtering looks probabilistic. The same plague articles went through summarization and translation fine about a dozen times and were only filtered in other steps. Part of the count was my own fault: a retry loop re-sent a filtered request every 10 minutes. I've fixed that.

What I'd like to raise is how opaque the process is:

The 400 only says "the response was filtered". It doesn't name a category or tell you whether that request counted as a strike.
The 403 only says "repeated policy violations". It doesn't say which requests, how many strikes there are, how long the block lasts, or where to appeal.
Nothing warns you before the block, even though it seems to come after roughly 5-6 strikes.

So the only way to stay unblocked is to guess at the cause and steer clear of anything that might be close: biohazard news, military analysis, crime reporting. Whether it's intended or not, the result is that users self-censor well beyond the actual policy, and legitimate content (news here) gets routed away just in case.

What would help:

Name the policy category in content_policy_violation responses.
Expose a strike count or warning before an account-level block.
Say how long the block lasts and give a working appeal path. Support email to [email protected] is the only route I've found.

same on opencode go; muse-spark-1.3-contributor returns user_blocked, other models work fine.

Thanks for the report, and sorry this didn't get a reply sooner.

The user_blocked error comes from Meta, which runs the Muse models. OpenCode has no control over these restrictions and can't lift them, so you'll need to take it up with Meta directly.

Also note that Muse is no longer part of the free tier, and the paid version isn't available in every region.

Closing this issue, since there's nothing we can change on our side.

— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

Navigation Menu

Repository navigation

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

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

Eldar-test-web commented on Sep 14, 2026

Mr-Toodguy commented on Sep 19, 2026

OzanKEreal commented on Sep 20, 2026

jenkinsmichpa commented on Sep 22, 2026

Zhfrn88 commented on Sep 22, 2026

alkaserGG commented on Sep 22, 2026

jholp92-beep commented on Sep 22, 2026

jenkinsmichpa commented on Sep 22, 2026

alkaserGG commented on Sep 22, 2026

alkaserGG commented on Sep 22, 2026

NazgulCoder commented on Sep 22, 2026

jholp92-beep commented on Sep 22, 2026

NazgulCoder commented on Sep 22, 2026

jholp92-beep commented on Sep 23, 2026

Ryanabcraft commented on Sep 24, 2026

silentbyte69 commented on Oct 2, 2026

yonikremer commented on Oct 2, 2026

igogocha commented on Oct 3, 2026

JamesFysh commented on Oct 4, 2026

Dante-dan commented on Oct 4, 2026

marco9666-jpg commented on Oct 7, 2026

hypernewbie commented on Oct 7, 2026

Tarquinen commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions