The encrypted content ... could not be verified

Resolved 💬 2 comments Opened Dec 16, 2025 by tehom Closed Dec 16, 2025

What version of Codex is running?

codex-cli 0.73.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

Linux 6.12.41+deb13-amd64 x86_64 unknown

What issue are you seeing?

For every prompt, it responds with ■ {
"error": {
"message": "The encrypted content gAAA...6KFQ could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": "invalid_encrypted_content"
}

What steps can reproduce the bug?

Uploaded thread: 019b28c5-ea98-77a0-ad7a-ceb9885247f6

I don't have a recipe as such to reproduce it. It's stuck that way so I can't go from "clean" to the bug.

What is the expected behavior?

Respond to my prompt as usual.

Additional information

This started after I copied some of ChatGPT's output where I had asked it about the same bug Codex was struggling with. The problem persisted thru many variations on the prompt, an update of codex, and a new session. The new session changed the hash of what could not be verified, but was otherwise the same result.

Note that it originally manifested on the previous version of Codex, I've just updated and that didn't fix it.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗