Rank, 14 days: 83 on the Codex sheet
3 people reported

All time, since Nov 4, including 1 thumbs-up on GitHub.

Chat provider mismatch blocks resume

“Selecting either provider leaves existing chats associated with the other provider unable to continue.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/25505/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Existing chats won't resume when their provider differs from current provider. Opening a chat shows "Switch to" the other provider to continue; chats tied to either configured provider are blocked after the desktop update.

Is this your bug?

File my report
Where
Desktop app
Error text
This chat uses 'provider1', but your current provider is 'provider2'. Switch to 'provider1' to continue.
Versions
0.166.0 to 26.1029.61003
Platforms
Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Desktop app loses ChatGPT account and chats with custom provider2 people
  2. Send disabled after quota exhausted21 people
  3. Invalid codex_app MCP transport3 people

Original reports2, newest first

  1. Urgent: Desktop openai/caveman provider mismatch blocks existing chats and agent orchestrationOn GitHub#59461
  2. Desktop update blocks existing chats that use a different configured model providerOn GitHub#59323

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.