Codex Sessions 61GB ?????? #18849

Activity

1. vural2123

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Apr 21, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   on Apr 21, 2026
3. github-actions commented on Apr 21, 2026

   

   github-actionsBot

   on Apr 21, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Startup time 20 seconds and resume 20 seconds. #18839
   • Desktop performance collapses in profiles with a few very large local conversation histories (typing, scrolling, thread list, random exits) #18693
   • Long Chat = Extreme Unresponsive. #18568
   • Auto-archive and zstd-compress inactive local rollout files to reduce disk usage #17000

   Powered by Codex Action
4. etraut-openai commented on Apr 21, 2026

   

   etraut-openai

   on Apr 21, 2026

   Contributor

   More actions

   I'm not sure what bug you're reporting here. The behavior you're describing (other than the 15 second freeze when opening) looks normal. Codex doesn't load all of your session content when starting. It enumerates your recent sessions so it can display them in the app. It tracks this with a local sqlite db so it doesn't need to do file system enumerations.
5. etraut-openai

   closed this as completedon Apr 21, 2026
6. vural2123 commented on Apr 21, 2026

   

   vural2123

   on Apr 21, 2026

   Last edited by vural2123

   Author

   More actions

   I'm not sure what bug you're reporting here. The behavior you're describing (other than the 15 second freeze when opening) looks normal. Codex doesn't load all of your session content when starting. It enumerates your recent sessions so it can display them in the app. It tracks this with a local sqlite db so it doesn't need to do file system enumerations.

   I already know why it loaded late: it’s uploading 61 GB of sessions.
   The issue here is why it saved 61 GB of sessions.
7. etraut-openai commented on Apr 21, 2026

   

   etraut-openai

   on Apr 21, 2026

   Contributor

   More actions

   Unless you have a single rollout that is 61GB in size (which is unlikely — and not what your screen shots show), then it will not load 61GB of content when starting. It will load session content on demand when you open that session in the UI.

   It's quite possible that you have created 61GB of sessions over multiple months of usage. You must be using Codex a lot!
8. vural2123 commented on Apr 21, 2026

   

   vural2123

   on Apr 21, 2026

   Author

   More actions

   Unless you have a single rollout that is 61GB in size (which is unlikely — and not what your screen shots show), then it will not load 61GB of content when starting. It will load session content on demand when you open that session in the UI.

   It's quite possible that you have created 61GB of sessions over multiple months of usage. You must be using Codex a lot!

   How can you say it’s normal for it to save 61 GB of sessions? If I keep using Codex for a few more months, my disk will fill up — it’ll be over 120 GB.

   So what now, am I supposed to delete data from a bunch of my projects? Am I the only person in the world who’s been using Codex for months? Millions of people have been using it for months and will keep using it for years. You need to come up with a solution for this now
   .
   I’m paying thousands of dollars a month for Codex, and now I’m supposed to pay for a new drive too? You must be joking. For now, I’m the one raising this complaint, but soon other people will be complaining about it too. In fact, there are already people complaining about even 7 GB of sessions.