Skip to content

Switching between threads is very slow #11011

Open

Description

@ImanYZ

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

Version 260206.1448 (565)

What subscription do you have?

ChatGPT Pro

What issue are you seeing?

After updating Codex last night, switching between threads is super slow and not responsive.

What steps can reproduce the bug?

I have multiple tabs in the Codex App on my MacBook Pro M4 Max.
Every thread is on a different project, in totally separate folders, without sharing anything.
Some of the threads are on git repos, and some are not.
When I send a prompt in one thread and switch to another thread, for a while the Codex app is frozen.
If I send prompts in two separate threads, they get super slow, and sometimes the app crashes and closes.
I did not experience these issues before updating the Codex app last night.

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Feb 7, 2026
  2. github-actions commented on Feb 7, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. awlee01 commented on Feb 7, 2026

    @awlee01

    +1 - app currently unusable for me

  4. ImanYZ commented on Feb 8, 2026

    @ImanYZ
    Author

    After updating the app to the new version, I cannot use it anymore!

  5. tomoliveri commented on Feb 10, 2026

    @tomoliveri

    +1 app completely unusable (MacOS)

  6. gulla0 commented on Feb 10, 2026

    @gulla0

    +1
    The app is hung and completely unusable. Restarting the app does not resolve the issue. Archiving project threads also has no effect. The problem persists across relaunches.

  7. liampongracz commented on Feb 10, 2026

    @liampongracz

    Yes please fix this, its bad. 2021 M1 MBP

  8. gunnartorfis commented on Feb 12, 2026

    @gunnartorfis

    Have to put a +1 here, it is barely usable at least when you have multiple big threads going.

  9. virgildotcodes commented on Feb 17, 2026

    @virgildotcodes

    Same experience, M1 Max.

    Just discovered that in one particular thread, there was a very large diff of unstaged changes that seemed to be choking the whole app's performance. Getting rid of that solved the performance issues on that thread at least.

  10. michaeltyson commented on Feb 18, 2026

    @michaeltyson

    I’m seeing very similar behavior, but in the Codex IDE extension running inside Cursor, not the standalone Codex desktop app.

    In my case:

    • Switching between long-running threads causes a full UI freeze for 10–30 seconds.
    • The freeze happens immediately on selecting the thread, even before sending a new prompt.
    • CPU spikes during the switch.
    • The behavior worsens with longer transcripts.

    From observation, it appears that the entire conversation is being loaded and rendered synchronously when switching threads. If the desktop app is using a similar rendering model, that might explain why multiple large threads cause the UI to hang or crash.

    By contrast, Cursor’s native chat interface progressively hydrates messages (loading recent content first and backfilling on scroll), which avoids blocking the UI thread.

    If the Codex app and extension are eagerly hydrating full transcripts on thread switch, implementing:

    • Message virtualization
    • Incremental/lazy loading
    • Background hydration off the main thread

    would likely resolve both the freezing and the memory growth issues people are reporting.

    Happy to provide more detailed reproduction info from the extension side if helpful.

  11. faraponov-agima commented on Feb 21, 2026

    @faraponov-agima

    +1
    I'm running into the same performance issues. The lag is making it difficult to use.

  12. 9yo commented on Feb 25, 2026

    @9yo

    + 1

  13. 100tomer commented on Mar 7, 2026

    @100tomer

    +1

  14. sebastien78 commented on Mar 18, 2026

    @sebastien78

    Same here, on huge Mac Ultra, I just have about 10 threads on my Codex app.
    Each time I switch from on thread/tab to another, there is 6-10sec of loading. It's a real pain.

  15. wbdb commented on Mar 18, 2026

    @wbdb

    Same here - Windows / WSL - 26.313.41514

  16. philbeliveau commented on Mar 21, 2026

    @philbeliveau

    Same here - M2 max

  17. wbdb commented on Mar 22, 2026

    @wbdb

    @etraut-openai Can you do something agianst this big_model_radar spam on all your Github issues? Can you block that somehow? It doesn't even help to block the user. Reports to Github were also unsuccessful.

  18. redfox05 commented on Apr 23, 2026

    @redfox05

    Seems this has not been updated since March, but just to highlight, 23rd April, and this is still an issue for me.
    Codex Mac App, Version 26.417.41555 (1858).
    macOS Tahoe 26.3
    Can't be limited resources, running on a Apple M3 Pro, 36GB memory. And very few other windows open.

  19. virgildotcodes commented on Apr 23, 2026

    @virgildotcodes

    Just wanted to back up @redfox05 . Previously, it was far worse, made the entire app chug and borderline unusable. Now though, it can still take a couple of seconds to swap to a different chat thread. Are we always pulling the chats down from OpenAI's servers? It seems like it would make sense to cache them locally, no?

  20. djh00t commented on Apr 28, 2026

    @djh00t

    I am seeing the same thing Codex Version 26.422.62136 (2176) MBP M2 32GB RAM macOS 15.7 (24G207)

    THe only apps I've got open are Chrome and Codex. Theres tonnes of CPU, GPU, RAM etc available. It feels like some kind of an io/locking issue.

  21. alexyorke commented on Jul 16, 2026

    @alexyorke

    Here is my feedback id: 019f57d8-c57e-7be3-b6ed-c211ab2785b1 (same issue, very slow switching tabs on Windows)

  22. andybergon commented on Aug 9, 2026

    @andybergon

    Still reproducible on macOS with ChatGPT/Codex Desktop 26.803.41515 (build 6321) and bundled Codex 0.147.0-alpha.6.5.

    I captured two cold task switches immediately after a full Desktop restart:

    • First task: maybe_resume_started, then maybe_resume_owner_discovery_failed exactly 5,000 ms later. The fallback thread/read took 2 ms and thread/resume took 40 ms.
    • Second task: the same owner-discovery timeout after 5,001 ms, followed by a 2 ms thread/read.
    • One affected task history was only 1.5 MiB, so a large transcript was not required to reproduce it.
    • Reopening a task after the first cold load is faster.
    • Desktop reached about 3.3 GiB resident memory across its backend, renderers, and services within a few minutes. That may amplify UI jank, but it does not explain the fixed five-second boundary.

    The task data is present and readable. The visible delay is the owner-discovery watchdog before the fast read/resume fallback, not the actual history read. This looks like the same specific owner-discovery path tracked in #37398 under the broader thread-switching symptom here.

  23. alexyorke commented on Aug 10, 2026

    @alexyorke

    I am on Version 26.803.41515 on Windows, a workaround I did was:

    • I closed ChatGPT
    • I moved the files ~/.codex/logs_2.sqlite, ~/.codex/logs_2-wal.sqlite and ~/.codex/logs_2-shm.sqlite to a quarantine folder on my desktop
    • Restarted my computer (not sure if needed)
    • Restarted ChatGPT

    And switching threads is much faster. Not instantaneous, but way faster. I still have all of my chats, settings, etc. Of course, do so at your own risk, I am not sure of the ramifications of deleting the logs database.

  24. nicolas-palermo commented on Aug 17, 2026

    @nicolas-palermo

    +1

  25. phplego commented on Oct 18, 2026

    @phplego

    Another Linux Desktop report of noticeable thread-switching latency: selecting a chat typically takes roughly 2-5 seconds before I can comfortably inspect it. Long-chat scrolling also drops frames, and the sidebar/chat list feels sluggish.

    Intel Core i7; on Desktop 26.1007.21434, with many saved chats. Version 26.1013.40934 is installed on disk pending restart and has not yet been tested. I have not established whether cold/warm loading differs or what causes the delay.

    The app remains usable, but the repeated waits make navigation unpleasant. UI responsiveness is my main concern, and I am considering the CLI because of it. A shorter click-to-visible path and smoother navigation would make a substantial difference.

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 appbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions