›_ Codex Issues
Codex Issues / #19088

Azure OAI provider chat threads disappearing in thread list

Open 💬 2 comments Opened Apr 23, 2026 by jamopark
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.417.41555 (1858)

What subscription do you have?

Pro/business

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Azure OAI provider chat threads are not showing up on the chat thread list on the LHS of the codex app. It only shows the old chat threads that were created with the default OpenAI provider. However, the session can still be seen with codex resume

What steps can reproduce the bug?

  • Open a project
  • Create a chat thread using default openai provider
  • Change config.toml to be routed to an Azure OAI provider
  • Restart Codex
  • Create a new chat thread with Azure OpenAI provider
  • Restart Codex
  • The chat thread created with Azure does not show.

What is the expected behavior?

Chat threads created with Azure should be shown as well.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #17316

Powered by Codex Action

Wangnov · 3 months ago

This sounds very close to the provider-bucket visibility problem that codex-threadripper was built for.

Project: https://github.com/Wangnov/codex-threadripper

It checks how Codex threads are distributed across model_provider values in state_5.sqlite and the rollout JSONL metadata, then can reconcile them so Codex Desktop / codex resume / app-server clients see the same local history after provider switches.

Suggested safe flow:

codex-threadripper status
codex-threadripper sync

It writes backups before mutating local state. Still, please back up ~/.codex first, especially if your sessions contain important work.

Important caveat: this is an unofficial workaround for local history visibility. It does not migrate encrypted conversation ownership across accounts/providers, and it should not replace an official Codex fix for provider-aware history listing/resume behavior.