Error when switching from api to subsription based usage for codex

Resolved 💬 3 comments Opened Sep 28, 2025 by Suketug Closed Sep 29, 2025

💡 Likely answer: A maintainer (gpeal, contributor) responded on this thread — see the highlighted reply below.

What version of the VS Code extension are you using?

0.4.15

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 24.6.0 arm64 arm

What steps can reproduce the bug?

Getting the below error when switching from api to subscription auth.

stream error: unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}; retrying 1/5 in 197ms…
stream error: unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}; retrying 2/5 in 437ms…
stream error: unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}; retrying 3/5 in 838ms…
stream error: unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}; retrying 4/5 in 1.598s…
stream error: unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}; retrying 5/5 in 2.911s…
unexpected status 400 Bad Request: {
"error": {
"message": "The encrypted content gAAA...EJE= could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

gpeal contributor · 11 months ago

Are you trying to resume a conversation from your API key with your pro subscription? Do new conversations work?

carman247 · 11 months ago

I'm also experiencing the same problem, albeit the other way around. I've just hit my usage limit on some tasks using the GPT Plus account. After switching to signing into the VS Code extension using an API I'm able to create new tasks, but attempting to send a message in an existing task is failing.

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

gpeal contributor · 11 months ago

You can't resume a conversation in a different account than it was created with. This is a known limitation for now but we may improve the error messaging around this.