Encrypted content could not be verified (broken session)

Resolved 💬 2 comments Opened Dec 16, 2025 by mikehearn Closed Dec 16, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.73.0

What subscription do you have?

API key

Which model were you using?

gpt-5.2

What platform is your computer?

Darwin 25.1.0 arm64 arm

What issue are you seeing?

Thread ID 019b2862-2623-7143-9c9f-a45075da54dd died with this error:

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

What steps can reproduce the bug?

Uploaded thread: 019b2862-2623-7143-9c9f-a45075da54dd

I have no idea how to repro it. Codex has been working fine for a while already today.

What is the expected behavior?

Server-side encrypted content should always validate.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 8 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #8100

Powered by Codex Action

etraut-openai contributor · 8 months ago

Thanks for reporting. We're aware of the problem, and the team is actively investigating.