You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Console rejects its own encrypted_content on same-session replay — 'reasoning encrypted_content was not issued to this caller' (muse-spark-1.3 free tier, turn 2) #49368
Using the Console gateway with muse-spark-1.3-contributor-free (reasoning effort medium), any multi-turn conversation dies on the second turn:
OpenAI API error (400): ... [invalid_request_error] reasoning `encrypted_content` was not issued to this caller
Turn 1 succeeds and returns a reasoning item with encrypted_content. On turn 2 the same session replays that reasoning item back (required for reasoning continuity on the openai-responses protocol), and Console rejects its own token issued ~2 minutes earlier in the same session. Retrying keeps failing with the same 400.
It looks like Console binds encrypted_content to a caller that isn't stable across requests — my guess is the free tier rotates upstream credentials between calls, so the caller validating the replay is not the one that issued the token.
Cross-model switches to plain-reasoning models (deepseek/glm/kimi) work fine, which is why this took a while to isolate. I verified on the client side that history sanitization is correct: same-model reasoning signatures are kept (protocol-required replay), cross-model ones are dropped (pi-ai 0.85.1, transformMessages). I first reported this on the Pi client tracker (earendil-works/pi#9634) and was correctly pointed upstream, so filing here since Console owns the validation.
Steps to reproduce
Client: Pi 0.85.1 (@earendil-works/pi-ai 0.85.1), provider opencode (Console), model muse-spark-1.3-contributor-free, reasoning effort medium.
Send one message → succeeds; the assistant message stores an encrypted reasoning item.
Send a second message in the same session → 400 reasoning encrypted_content was not issued to this caller. Further turns keep failing.
This appears to be a widespread issue with encrypted_content validation on the Console gateway for muse-spark models. Please search through the above issues and consider adding a reaction or comment to an existing one rather than filing a new report.
Activity
github-actions commentedon Sep 16, 2026
This issue might be a duplicate of existing issues. Please check:
encrypted_contentwas not issued to this caller #48973: Getting Error from provider (Console): Upstream request failed: [invalid_request_error] reasoningencrypted_contentwas not issued to this callerencrypted_contentwas not issued to this caller #49247: Error from provider (Console): Upstream request failed: [invalid_request_error] reasoningencrypted_contentwas not issued to this callerThis appears to be a widespread issue with
encrypted_contentvalidation on the Console gateway for muse-spark models. Please search through the above issues and consider adding a reaction or comment to an existing one rather than filing a new report.egkike commentedon Sep 16, 2026
Duplicate of #49188 — same model, same error, same fresh-session symptom. Consolidated my confirmation there.