Error: Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller #50397

Activity

1. opencode-agent

   added

   2.0

   on Sep 21, 2026
2. euwbah commented on Sep 21, 2026

   

   euwbah

   on Sep 21, 2026

   More actions

   possible cause: https://github.com/hailongcoding/opencode-session-rescue/blob/main/Fix-EncryptedContent-Portable.bat
3. rekram1-node

   self-assigned this

   on Oct 15, 2026
4. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   More actions

   Thanks for the report! This error comes from the model provider: it is rejecting encrypted reasoning that OpenCode sent back from an earlier turn, saying that reasoning wasn't issued to the current caller. To work out why, could you share:

   • The output of opencode --version
   • The provider and model you were using (e.g. GitHub Copilot, OpenAI, OpenCode Zen, or a custom/proxy provider), and how you are logged in (OAuth/subscription or API key)
   • Whether it happens in a new session, or only when continuing a session started before the upgrade, or after switching model, account or API key in the middle of a session
   • Your operating system and how you installed OpenCode
   • Any relevant log lines around the error, if you can get them

   Until then, starting a fresh session with the same model might get you working again. If that helps, please tell us, since it narrows down the cause.

   You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.
5. opencodejr

   added

   triaging

   on Oct 28, 2026
6. opencodejr

   closed this as not plannedon Oct 31, 2026
7. opencodejr commented on Oct 31, 2026

   

   opencodejrBot

   on Oct 31, 2026

   More actions

   We haven't heard back here, so I'm closing this issue for now. We can't look into the reasoning encrypted_content was not issued to this caller error without knowing your OpenCode version, the provider and model (and how you're logged in), and whether it happens in a new session or only when continuing an existing one.

   If it still happens, please reply with those details and we can reopen this, or open a new issue that links back to #50397. Starting a fresh session may also work around it in the meantime.