›_ Codex Issues
Codex Issues / #17316

Switching global provider hides previous sessions from the sidebar

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

What feature would you like to see?

Switching the global provider should not make previous chat sessions disappear from the Codex app sidebar.

Current behavior

  • I create sessions with one provider.
  • I switch the global provider.
  • Older sessions no longer appear in the sidebar.

Expected behavior

Previous sessions should remain visible and accessible even after changing provider.

If sessions are being filtered by provider, the UI should make that explicit and let me view sessions from other providers.

Why this matters

Changing provider is a normal workflow when testing OpenAI, Azure, or local models. It should not hide session history.

View original on GitHub ↗

11 Comments

github-actions[bot] contributor · 3 months ago

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

  • #17304
  • #16901
  • #16811
  • #16817
  • #16624

Powered by Codex Action

Wangnov · 1 month 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.

steveepreston · 1 month ago

@Wangnov Thanks!

  1. has it any GUI?
  2. If we change bucket of a chat, can it be continued with new model? or it's just for read?
Wangnov · 1 month ago

@steveepreston
no gui and not planned, sry.
Yeah it can be continued, but you need to confirm that two bucket are encrypted by the same way.
Such as openai (ChatGPT Oauth) and other provider by ChatGPT Oauth just name different.
ChatGPT Oauth and Vertex/AWS/... are encrypted by different way. So will failed.

steveepreston · 1 month ago

@Wangnov thanks for explain.

can Move openai chats into 9router bucket?

Wangnov · 1 month ago

Of course you can. 

model_provider = "9router"

[model_provider.9router]
blabla

If your "9router" is like this, it will work.

steveepreston · 1 month ago

@Wangnov Thanks!

Necmttn · 29 days ago

Provider changes should not mutate session visibility without an explicit filter.

Keep model_provider as metadata on the session row, then let the sidebar default to all providers with provider badges. If a session cannot be resumed under the active provider, show a compatibility warning and the original provider/root rather than hiding it.

---

_Generated with ax._

steveepreston · 29 days ago

@Necmttn Agree

bakaburg1 · 28 days ago

Optionally, there could be a setting forbidding codex sessions to be able to see other sessions, in case one has data security issues, but I would not make it the default

bakaburg1 · 28 days ago
Provider changes should not mutate session visibility without an explicit filter. Keep model_provider as metadata on the session row, then let the sidebar default to all providers with provider badges. If a session cannot be resumed under the active provider, show a compatibility warning and the original provider/root rather than hiding it. _Generated with ax._

and in OpenCode you can change provider even midway in the session