Skip to content

Azure OAI provider chat threads disappearing in thread list #19088

Open

Description

@jamopark

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

Activity

  1. added
    appIssues related to the Codex desktop app
    on Apr 23, 2026
  2. added
    bugSomething isn't working
    azureIssues related to the Azure-hosted OpenAI models
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Apr 23, 2026
  3. github-actions commented on Apr 23, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  4. Wangnov commented on May 22, 2026

    @Wangnov

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appazureIssues related to the Azure-hosted OpenAI modelsbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions