The encrypted content gAAA...n-s= could not be verified

Resolved 💬 0 comments Opened Dec 16, 2025 by smaira Closed Dec 16, 2025

What version of Codex is running?

codex-cli 0.73.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.2 medium

What platform is your computer?

Darwin 22.6.0 x86_64 i386

What issue are you seeing?

Today, after updating the CLI and pasting in logs from my server application, I started seeing the following error intermittently.

■ {
"error": {
"message": "The encrypted content gAAA...n-s= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": "invalid_encrypted_content"
}
}

Once this error occurs in a session, it persists for that session regardless of the user message. Even after the session resumes, the same issue occurs. It only gets fixed when a new session is started but then I lose the context.

What steps can reproduce the bug?

Uploaded thread: 019b28ae-d4bc-70d0-90d1-7d88fb82031c

What is the expected behavior?

I should not see the error and continue conversations without being blocked.

Additional information

_No response_

View original on GitHub ↗