Repository navigation
Cannot fix "the encrypted content <b64 content> could not be verified" for old session #10585
Description
Description
I'm using for the truncated base64 looking data in the log / messages.
Durring a session I got the following error using ChatGPT 5.2 Codex (via Zen): the encrypted content <REDACTED> could not be verified
If I switch model (ChatGPT 5.2) during the session the error goes. I did the following:
opencode models --refresh: Issue continued from that sessionrm -rf ~/.cache/opencode: Issue continued from that session
I then noticed the error doesn't occur on new sessions only the current broken session. Can send full debug logs if necessary.
Section of log with errors:
INFO 2026-01-25T20:53:26 +9ms service=session.processor process
INFO 2026-01-25T20:53:26 +1ms service=llm providerID=opencode modelID=gpt-5.2-codex sessionID=ses_4152a97ebffeP4Si0TkBcY1A7u small=false agent=plan mode=primary stream
INFO 2026-01-25T20:53:26 +0ms service=provider status=started providerID=opencode getSDK
INFO 2026-01-25T20:53:26 +0ms service=provider providerID=opencode pkg=@ai-sdk/openai using bundled provider
INFO 2026-01-25T20:53:26 +0ms service=provider status=completed duration=0 providerID=opencode getSDK
INFO 2026-01-25T20:53:26 +11ms service=bus type=session.status publishing
INFO 2026-01-25T20:53:26 +19ms service=bus type=message.updated publishing
INFO 2026-01-25T20:53:26 +1ms service=llm providerID=opencode modelID=gpt-5-nano sessionID=ses_4152a97ebffeP4Si0TkBcY1A7u small=true agent=title mode=primary stream
INFO 2026-01-25T20:53:26 +0ms service=provider status=started providerID=opencode getSDK
INFO 2026-01-25T20:53:26 +0ms service=provider status=completed duration=0 providerID=opencode getSDK
INFO 2026-01-25T20:53:26 +83ms service=bus type=session.updated publishing
INFO 2026-01-25T20:53:26 +0ms service=bus type=session.diff publishing
INFO 2026-01-25T20:53:27 +857ms service=session.summary title=Help request summary title
INFO 2026-01-25T20:53:27 +1ms service=bus type=message.updated publishing
ERROR 2026-01-25T20:53:27 +354ms service=llm providerID=opencode modelID=gpt-5-nano sessionID=ses_4152a97ebffeP4Si0TkBcY1A7u small=true agent=title mode=primary error={"error":{"name":"AI_APICallError","url":"https://opencode.ai/zen/v1/responses","requestBodyValues":{"model":"gpt-5.2-codex","input":[{"role":"developer", ...CUT SOME STUFF OUT HERE TO MAKE IT MORE READABLE.., "responseBody":"{\n \"error\": {\n \"message\": \"The encrypted content <b64 content> could not be verified.\",\n \"type\": \"invalid_request_error\",\n \"param\": null,\n \"code\": \"invalid_encrypted_content\"\n }\n}","isRetryable":false,"data":{"error":{"message":"The encrypted content <b64 content> could not be verified.","type":"invalid_request_error","param":null,"code":"invalid_encrypted_content"}}}} stream error
ERROR 2026-01-25T20:53:27 +4ms service=session.processor error=The encrypted content <b64 content> could not be verified. stack="AI_APICallError: The encrypted content <b64 content> could not be verified.\n at <anonymous> (../../node_modules/.bun/@ai-sdk+provider-utils@3.0.20+d6123d32214422cb/node_modules/@ai-sdk/provider-utils/dist/index.mjs:936:18)\n at processTicksAndRejections (native:7:39)" process
My guess is something from the old session is still being used in the request to opencode.ai/zen/... and there is no way to force opencode to refresh it?
Additional points:
- This session was left open for a couple days (was working and then failed after the long pause)
- I could have upgraded opencode inbetween (unfortunately I cannot remember)
Plugins
n/a
OpenCode version
1.1.36
Steps to reproduce
I can only recreate on my specific session
Screenshot and/or share link
https://opncd.ai/share/kBcY1A7u
Operating System
macOS Sonoma 14.8
Terminal
Ghostty
Activity
github-actions commentedon Jan 25, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
[-]Cannot fix "the encrypted content <REDACTED> could not be verified" for old session[/-][+]Cannot fix "the encrypted content <b64 content> could not be verified" for old session[/+]github-actions commentedon Mar 27, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.