anomalyco / anomalyco/opencode
Getting Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning `encrypted_content` was not issued to this caller
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
Getting -> Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller
while using Muse Spark 1.3 with Opencode Zen
Plugins
No plugins
OpenCode version
v1.18.30
Steps to reproduce
Select model Muse spark 1.3 Free
Send a chat
u get error -> Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller
Screenshot and/or share link
Operating System
Windows 11
Terminal
Opencode App
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.
Research direction
Start by reproducing the error with OpenCode v1.18.30 on Windows 11: select Muse Spark 1.3 Free in the OpenCode app and send a chat. Trace the provider request that produces the Console error and determine the expected handling of the encrypted_content response; done means the model request completes without this upstream error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100