400 bad request

[guidedways]

What version of Codex is running?

0.30.0

Which model were you using?

gpt-5 high / medium

What platform is your computer?

macOS

What steps can reproduce the bug?

⚠️ stream error: unexpected status 400 Bad Request: {
  "error": {
    "message": "The encrypted content for item rs_68bbb6866b78819d95a31224f799dc3d0252e016e8922fc9
could not be verified.",
    "type": "invalid_request_error",
    "param": null,
    "code": null
  }
}; retrying 1/5 in 217ms…

⚠️ stream error: unexpected status 400 Bad Request: {
  "error": {
    "message": "The encrypted content for item rs_68bbb6866b78819d95a31224f799dc3d0252e016e8922fc9
could not be verified.",
    "type": "invalid_request_error",
    "param": null,
    "code": null
  }
}; retrying 2/5 in 421ms…

Constantly seeing this for any prompt

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response

[pakrym-oai]

I apologize for the disruption, this error was a caused by a bug that's been fixed now.

[awdrgyjilplij]

I apologize for the disruption, this error was a caused by a bug that's been fixed now.

So what should I do to solve the problem. I have tha same error.

[nelsonjoppi-stone]

I apologize for the disruption, this error was a caused by a bug that's been fixed now.

So what should I do to solve the problem. I have tha same error.

switch your extension version to pre-release, worked for me

[mmaunder]

Seeing the same issue with:

⚠️ stream error: unexpected status 400 Bad Request: { "error": { "message": "The encrypted content gAAA...tyI= could not be verified.", "type": "invalid_request_error", "param": null, "code": null } }; retrying 5/5 in 2.911s…

Steps to reproduce: Codex 0.36.0 on ubuntu linux. Use codex resume on a session 12 hours old. Try to continue interacting with the agent. Seems like a security token may have expired.

Fix: Just enter /new. But the old session is unrecoverable.

[microsoftbuild]

Switching from API to ChatGPT auth is another way to reproduce this. Ran into it today.

Apparently, logging out and switching back to the API auth fixed this issue on my end.