Skip to content

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

Closed as not planned

Description

@egkike

Description

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

  1. 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.
  2. Send one message → succeeds; the assistant message stores an encrypted reasoning item.
  3. Send a second message in the same session → 400 reasoning encrypted_content was not issued to this caller. Further turns keep failing.

Same session, same model, no model switch involved. Related: earendil-works/pi#9634, Gentleman-Programming/gentle-ai#4595.

Plugins

None (client is the Pi coding agent, not the opencode CLI)

OpenCode version

1.18.31 installed locally; the failing endpoint is the Console gateway driven by pi-ai 0.85.1

Screenshot and/or share link

No response

Operating System

Ubuntu-based Linux (x86_64)

Terminal

No response

Activity

  1. github-actions commented on Sep 16, 2026

    @github-actions
    Contributor

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

    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.

  2. egkike commented on Sep 16, 2026

    @egkike
    Author

    Duplicate of #49188 — same model, same error, same fresh-session symptom. Consolidated my confirmation there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions