Bug: Codex cannot resume a section after switching login methods (Plus → API Key)

[damtt]

What version of Codex is running?

0.39

Which model were you using?

GPT-5 Codex hight / GPT-5 hight

What platform is your computer?

Macbook M1 Max (Darwin 24.5.0 arm64 arm)

What steps can reproduce the bug?

Steps to Reproduce

1. Log in to Codex with a ChatGPT Plus account.
2. Work in a section until rate limit is reached.
3. Log out.
4. Log back in using an OpenAI API key (different auth method).
5. Attempt to resume the same section (continue run/stream).

What is the expected behavior?

Section resumes/streams normally after re-authentication, regardless of login method.

What do you see instead?

Streaming fails with HTTP 400 Bad Request and an encryption verification error.

⚠️ stream error: unexpected status 400 Bad Request: {
  "error": {
    "message": "The encrypted content gAAA...dQ== could not be verified.",
    "type": "invalid_request_error",
    "param": null,
    "code": null
  }
}

Additional information

No response

[xylik]

I can nonfirm same behavior on: codex-cli 0.38.0 with WSL(Ubuntu 24.x)

Also i have been using chat gpt plus account with codex-cli and have reached limit. Than I have switched to API key and after trying to resume session i got the same error as damtt.

[dissorial]

Same exact setup and issue here as @xylik

[wbdb]

I can confirm this with Windows 11 Pro / Ubuntu 24 WSL2 and Codex CLI 0.39.0.

[tm65]

For me it is switching from API key to chatGPT Plus.

After upgrading to 0.40 I could finally login using chatGPT Plus. Was able to complete a code review without problem. Then this issue happened when asking a follow-up regarding the CR.

I did start with 'codex resume' and picked a session ended few days back.

Windows 11 Pro / Ubuntu 24 WSL2 / Codex CLI 0.40

[charanduggina]

I had the same issue on MacBook Air M1, using the VSCode Codex extension (version 0.4.14).

Initially, I was using GPT Plus.

When the weekly limit was reached, I tried logging in using an API Key and also using a different Plus account.

Both attempts resulted in the same error:

stream error: stream disconnected before completion: You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors

Suggestion for Plus users: If your limit is reached while using the Codex extension, you can still continue using the Codex web version without quota issues.

[Hucent]

It seems the problem comes from sharing the same conversation between different accounts or between the API and an account. If I start a new session from API key, that won't be a problem. Please fix this. I wanna sharing the same conversation.

[Hucent]

It works fine on 0.42

[paulpv]

I am seeing this problem in 0.45

[stef4ik]

Problem still exists in 0.46.0

[Nacho-Larreta]

+1 It's really frustrating this issue

[RW21]

It also happens when I switch between API keys.

[realtebo]

today happening when switching FROM api key to normal account

[vxtls]

This issue is very critical, it can't let me use codex normally, I don't know why it happened, I don't even do anything, it's like it's run for a small while, and it failed with that error fix this as soon as possible

[zeronycs]

Same problem here, happened just now

[mironnn]

the same

[tthrelk93]

same problem, just started happening to me

[rcanepa]

I'm being affected by the same issue now

[Bailuer]

same prob just now. Is it the server problem that some people get this prob at one time?

[pelloempire1]

same

[sharkwedy]

the same

[rcanepa]

Something broke on the OpenAI side of things; I tested different keys and tools; same response everywhere

[pelloempire1]

it was working since last 0200 am so idk

[vxtls]

Something broke on the OpenAI side of things; I tested different keys and tools; same response everywhere

[MoFusion01]

just gotta wait it out :D

[etraut-openai]

Thanks for reporting. We're aware of the problem, and the team is actively investigating. We're using #8120 to track this problem. I'll post updates there as they become available.

[kyle-mcr]

Its not working for me as well:

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

[vxtls]

It seems more stable now; the error no longer occurs frequently [update EST 15:31] still have error

[dheeraj07]

Facing the same issue!

[itsAR-VR]

can users facing this issue get some kind of compensation?

[luboda]

■ { "error": { "message": "The encrypted content gAAA...iD0= could not be verified.", "type": "invalid_request_error", "param": null, "code": "invalid_encrypted_content" } } Im now updating maybe fix is already there 0.73