Error "The encrypted content gAAA...HQ== could not be verified."
Resolved 💬 4 comments Opened Dec 17, 2025 by yusun029 Closed Dec 17, 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.72.0
What subscription do you have?
Enterprise
Which model were you using?
gpt-5.2
What platform is your computer?
Linux 4.18.0-553.63.1.el8_10.x86_64 x86_64 x86_64
What issue are you seeing?
Half way via doing git show command, the following error popped out:
■ {
"error": {
"message": "The encrypted content gAAA...HQ== could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": "invalid_encrypted_content"
}
}The session became unusable after this - any further conversation will repeat the above error.
What steps can reproduce the bug?
Feedback thread ID: 019b28d7-4309-7531-824e-1d13502b4a77
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
It's seems the problem still exist on Codx CLI v0.80.0, but #8120 has been locked and limited to collaborators.
@PeterDaveHello, that issue was diagnosed and resolved. If you're seeing a similar error or behavior, then it's a different issue. Please open a new bug report using
/feedbackso we can look at your logs and session details.@etraut-openai got it, thanks!