anomalyco / anomalyco/opencode

MUSE SPARK 1.3 FREE fails when continuing an existing project

Open
#49,515 3 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Sep 17, 2026.

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

Description

I’m experiencing an issue when using the MUSE SPARK 1.3 FREE model.

I created a project using this model, and everything was working perfectly. However, after shutting down my computer and coming back the next day to continue working on the same project, I started getting the following error:

Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller

What is strange is that the model still works normally when I open a new window and start a new project. The error only occurs when I try to continue working on the existing project.

Steps to reproduce
Create a project using MUSE SPARK 1.3 FREE.
Work on the project normally.
Shut down the computer.
Start the computer again the next day.
Open the same project and try to continue working.
The following error appears:
Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller
Open a new window and start a new project.
MUSE SPARK 1.3 FREE works normally.
Expected behavior

The model should continue working normally when reopening and continuing an existing project after restarting the computer.

Actual behavior

The existing project returns an encrypted_content error, while a new project works correctly.

Could this be related to how the conversation/project state or the model's reasoning encrypted_content is being stored and restored?

Any help investigating this issue would be appreciated.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.