[regression 2026-09-15] muse-spark-1.3-contributor-free: encrypted_content was not issued to this caller en chats nuevos de 2-3 mensajes #49188

Activity

1. github-actions

   assigned

   nexxeln

   on Sep 15, 2026
2. github-actions commented on Sep 15, 2026

   

   github-actionsBot

   on Sep 15, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Getting Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller #48973: Same error with Muse Spark 1.3 Free in short sessions
   • [Bug] Muse Spark 1.3 Free (Xhigh): reasoning encrypted_content error on follow-up prompts with images #48947: Same encrypted_content error after 2-3 messages (including with images, similar session length)
   • Muse Spark 1.3: resuming a session after idle fails with reasoning encrypted_content not issued to this caller #48915: Resuming sessions with Muse Spark 1.3 hits the same error — includes analysis of how reasoningEncryptedContent blobs expire and a proposed fix
   • Network interruption corrupts conversation state: reasoning encrypted_content was not issued to this caller #49083: Same error attributed to network interruption corrupting conversation state
   • [Bug] muse-spark-1.3-contributor-free: reasoning encrypted_content was not issued to this caller when switching models in same session #48805: Same error when switching models mid-session
   • Opencode Zen critical errors on Muse Spark family when model recieves a image/does a tool call #48741: Original report of the error class for Muse Spark family

   Your report specifically highlights that this is now occurring in very short new sessions (2-3 messages) as of 2026-09-15, which could indicate a regression worth tracking separately. The root cause analysis you provided (encrypted blob from turn N being rejected at turn N+1) matches the discussion in #48915.
3. arfoux commented on Sep 16, 2026

   

   arfoux

   on Sep 16, 2026

   Last edited by arfoux

   More actions

   Correction — OpenCode version matters:

   My earlier comment recommended github:arfoux/rs-guard, but that plugin is OpenCode V2 only (@opencode/plugin v2 API: context/compaction/generate + retry hooks for stateless replay and retry-without-reasoning). It will not load on OpenCode V1.

   • OpenCode V2 — full self-heal (github:arfoux/rs-guard):

     opencode plugin add github:arfoux/rs-guard

     Forces stateless full replay on every request (no previous_response_id, store: false, no include: reasoning.encrypted_content), strips server-issued ids (rs_*, msg_*) from metadata, keeps at most 1 newest encrypted blob. On a matching error it retries once with no reasoning at all.
   • OpenCode V1 — best-effort (github:arfoux/rs-guard-v1):

     opencode plugin add github:arfoux/rs-guard-v1

     V1 (@opencode-ai/plugin) has no request/retry hooks, so it works with what V1 offers: chat.params strips include: reasoning.encrypted_content / continuation ids and forces store: false; experimental.chat.messages.transform strips stale ids/blobs; experimental.session.compacting keeps reasoning state out of summaries; session.error shows a guidance toast (retry, or fresh session if it persists).

   Tested on: muse-spark-1.3-contributor-free via Gateway Console — fails on message 2–3 without the plugin, works consistently with the V2 plugin. (For the report by @egkike on opencode 1.18.31 / V1: use rs-guard-v1; it reduces the failure surface but cannot auto-retry — if the error still appears, just retry, or start a fresh session.)

   Caveat: Both are client-side mitigations, not a server fix. The root cause is upstream replaying stale encrypted/reasoning state that the Console free tier rejects. Same family as #28678 / #29000 but for Console/Gateway models.
4. egkike commented on Sep 16, 2026

   

   egkike

   on Sep 16, 2026

   More actions

   Same symptom here on a fresh short session: muse-spark-1.3-contributor-free (exact model ID opencode/muse-spark-1.3-contributor-free) via the Console gateway fails at turn 2 with reasoning encrypted_content was not issued to this caller, no model switching, no resume/compact involved. opencode 1.18.31, Ubuntu 24.04. Consolidating my report #49368 here.
5. egkike commented on Sep 16, 2026

   

   egkike

   on Sep 16, 2026

   More actions

   Extra data point: the same rejection also reproduces outside opencode. Running the same Console models (muse-spark-1.3-contributor-free via the command-code provider) from the Pi coding agent hits the same reasoning encrypted_content was not issued to this caller failure. No opencode client code involved on that path, which supports the gateway-side root cause — stale encrypted/reasoning state rejected by the Console free tier regardless of client.
6. Tarquinen commented on Oct 20, 2026

   

   Tarquinen

   on Oct 20, 2026

   Member

   More actions

   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 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
7. Tarquinen

   closed this as not plannedon Oct 20, 2026