Repository navigation
[BUG] Refusal response is hidden and conversation history disappears (OpenCode Go) #44958
Closed as not planned
Description
Description
While using muse-spark-1.2-contributor through an OpenCode Go subscription, a run can finish without showing any response or error in the UI. In other occurrences, the run remains active indefinitely.
In the captured occurrence, the HTTP stream completed successfully and contained a refusal message:
event: response.completed
data: {"response":{"status":"completed","error":null,"output":[{"role":"assistant","content":[{"type":"refusal","refusal":"I'm sorry, but I can't help with that request."}]}]}}
OpenCode did not display that refusal or any error. The conversation view became empty, previous messages were no longer visible, and /revert could not recover them.
This report is about how OpenCode presents and preserves the session after this response. It does not assume why the model returned a refusal.
Steps to Reproduce
- Use
muse-spark-1.2-contributorwith an OpenCode Go subscription. - Continue an existing conversation and send a prompt.
- Encounter a response containing a
refusalcontent block.
Actual Behavior
- The run may end with no visible response or error, or remain active indefinitely.
- The refusal returned by the provider is not shown.
- The conversation view becomes empty and previous messages disappear.
/revertcannot recover the missing conversation.
Expected Behavior
- OpenCode shows the provider response or a visible error.
- Existing conversation history remains available.
- The session reaches a clear completed or failed state.
Environment
- OpenCode:
1.18.22 - Provider: OpenCode Go subscription
- Model:
muse-spark-1.2-contributor - OS: macOS
Screenshot
The conversation area is empty after the run, with no refusal or error shown:
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 25, 2026
This issue might be a duplicate of existing issues. Please check:
stop_reason: refusalresponses (from Vertex provider) are not properly surfaced in the OpenCode UI — the underlying problem of refusal responses not being displayed overlaps with your second bug (OpenCode silently emptying the conversation instead of showing the refusal message). Your issue adds detail about thetype: "refusal"content block in the responses API format and the retry loop behavior, which may be distinct enough to warrant a separate fix, but the UI surfacing gap is closely related.refusalfield in requests — different direction but same concept area if you encounter 400 errors when replaying conversations.rekram1-node commentedon Aug 25, 2026
?? lol no
bojackduy commentedon Aug 25, 2026
Clarification on the bug report:
Sorry for the confusion in my initial description.
Let me clarify the actual issue:
The root cause is NOT about which tools are being sent. The model may refuse for any reason - safety filter, content policy, model limitations, etc. Thats expected behavior from the model.
The actual bugs are:
"content":[{"type":"refusal","refusal":"Im sorry, but I cant help with that request."}]but OpenCode shows nothing to the user. The conversation just empties silently./revertcannot restore them.[-][BUG] muse-spark-1.2-contributor refuses 753-tool requests + OpenCode doesn't display refusal responses[/-][+][BUG] Refusal response is hidden and conversation history disappears (OpenCode Go)[/+]khaclbit commentedon Aug 27, 2026
@rekram1-node got this same problem too, pls help
khaclbit commentedon Aug 27, 2026
opencode/muse-spark-1.2-free works normally for me with the same prompt, tools, and session. However, opencode-go/muse-spark-1.2-contributor through the OpenCode GO subscription consistently hits this bug.
Could someone help clarify what might be different between these two? Since this is a paid subscription, I’d really appreciate some guidance on how I can get this issue debugged or investigated. Thank you!
khaclbit commentedon Aug 28, 2026
Looks like the Muse Spark model was updated, and I no longer get the refusal response. That said, the empty visibility issue probably still needs attention in case a refusal occurs again in the future.
thdxr commentedon Oct 11, 2026
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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊