invalid_request_error invalid_encrypted_content The encrypted content ... could not be verified

Resolved 💬 3 comments Opened Dec 16, 2025 by drew-dirac 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?

Plus

Which model were you using?

gpt-5.1-codex-mini

What platform is your computer?

Linux 6.18.0 x86_64 unknown

What issue are you seeing?

I am frequently seeing the following error message:

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

This will often happen immediately after sending the prompt, but it will sometimes happen well into generation.
The model never reaches the point where it begins editing files, so I suspect that it may be having troubles with that.

What steps can reproduce the bug?

Uploaded thread: 019b289e-5e24-7d72-aefb-920633fafb22

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 8 months ago

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

  • #8126
  • #8125
  • #8123
  • #8121
  • #8120

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.

KustomKode · 8 months ago

Same happens to me, but it was in the middle of editing files when it happened. I am thankful for version control.