You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Older Codex Chats in VS Code Disappear After 20-Chat Limit #6410
What version of the VS Code extension are you using?
0.4.38
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Linux
What issue are you seeing?
I have more than 20 chats with the Codex extension in VS Code, but once I exceed 20 chats, the older ones disappear, and I can’t search for or access them.
Later Detail Explanation below | Credit: @rockmandash
"Just want to share another perspective as someone who uses Codex pretty heavily.
For a lot of developers, each task is basically part of an ongoing workflow — debugging, multi-file refactors, or long feature work. When the history rolls over after 20 items, it becomes pretty hard to:
reopen older prompts that still matter
look back at explanations or steps that were generated earlier
search through older sessions when trying to trace how an issue evolved
The data is technically still in .codex/sessions, but digging through the raw files isn’t really a practical day-to-day solution.
Even increasing the limit a bit (like 50–100), or making it configurable, would help a lot of people who work on longer tasks or use Codex throughout the whole day.
If performance was the reason for the cap, things like lazy-loading or a simple “load more” button might already be enough to keep the UI responsive while still giving access to older tasks.
Just wanted to highlight this because the 20-task limit ends up being a noticeable friction point for anyone doing more than quick one-off prompts. Codex has been awesome so far, and having more flexible history access would make it even smoother to use daily.
Yes, the extension limits the number of displayed tasks in the task history to 20 currently. They are still present (you can find them in .codex/sessions), but the UI currently shows only the last 20.
@gpeal, was this done for performance reasons? What do you think about increasing this limit?
Is there any proper way to configure to show all the chats or search through any past chat ? , beacuse accessing through .codex/sessions is i think a rough way.
Currently, the extension hard codes the limit at 20. The Codex CLI does not have such a limit, so you can access your older conversations using the CLI.
Hi @etraut-openai , thanks for the clarification about the 20-task limit.
Just want to share another perspective as someone who uses Codex pretty heavily.
For a lot of developers, each task is basically part of an ongoing workflow — debugging, multi-file refactors, or long feature work. When the history rolls over after 20 items, it becomes pretty hard to:
reopen older prompts that still matter
look back at explanations or steps that were generated earlier
search through older sessions when trying to trace how an issue evolved
The data is technically still in .codex/sessions, but digging through the raw files isn’t really a practical day-to-day solution.
Even increasing the limit a bit (like 50–100), or making it configurable, would help a lot of people who work on longer tasks or use Codex throughout the whole day.
If performance was the reason for the cap, things like lazy-loading or a simple “load more” button might already be enough to keep the UI responsive while still giving access to older tasks.
Just wanted to highlight this because the 20-task limit ends up being a noticeable friction point for anyone doing more than quick one-off prompts. Codex has been awesome so far, and having more flexible history access would make it even smoother to use daily.
Thanks for taking a look!
Reacted by Muhammad Noman Ilyas, Steven Fletcher, lechuhuuha, blazejklisz, Margaret Thomas, Dmytro Vasin and Valeriy Pavlovich
Hi @etraut-openai , thanks for the clarification about the 20-task limit.
Just want to share another perspective as someone who uses Codex pretty heavily. For a lot of developers, each task is basically part of an ongoing workflow — debugging, multi-file refactors, or long feature work. When the history rolls over after 20 items, it becomes pretty hard to:
reopen older prompts that still matter
look back at explanations or steps that were generated earlier
search through older sessions when trying to trace how an issue evolved
The data is technically still in .codex/sessions, but digging through the raw files isn’t really a practical day-to-day solution.
Even increasing the limit a bit (like 50–100), or making it configurable, would help a lot of people who work on longer tasks or use Codex throughout the whole day.
If performance was the reason for the cap, things like lazy-loading or a simple “load more” button might already be enough to keep the UI responsive while still giving access to older tasks.
Just wanted to highlight this because the 20-task limit ends up being a noticeable friction point for anyone doing more than quick one-off prompts. Codex has been awesome so far, and having more flexible history access would make it even smoother to use daily.
Thanks for taking a look!
@rockmandash , totally ! , this was even what i faced and point i wanted to highlight @etraut-openai . Thanks!.
Reacted by Joseph, Margaret Thomas and Valeriy Pavlovich
@fdterr@AL-Cybision you can give WayLog a try. It's an opensource VS Code extension. History save automatically in .waylog/history folder, but you can search and save what you want.
Hi, this feature is really needed, there is some chat which is pure information that i need to read again. Scroll through the session files is so hard to see.
Would be a lovely to see more then 20 active chats
Activity
github-actions commentedon Nov 9, 2025
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Nov 9, 2025
Yes, the extension limits the number of displayed tasks in the task history to 20 currently. They are still present (you can find them in
.codex/sessions), but the UI currently shows only the last 20.@gpeal, was this done for performance reasons? What do you think about increasing this limit?
AL-Cybision commentedon Nov 9, 2025
Is there any proper way to configure to show all the chats or search through any past chat ? , beacuse accessing through .codex/sessions is i think a rough way.
etraut-openai commentedon Nov 9, 2025
Currently, the extension hard codes the limit at 20. The Codex CLI does not have such a limit, so you can access your older conversations using the CLI.
milisp commentedon Nov 9, 2025
You can use https://github.com/codexia-team/codexia to show all of the history based on project.
AL-Cybision commentedon Nov 10, 2025
I hope vscode extension will also cater this issue so its easy to access past 20 chats.
milisp commentedon Nov 10, 2025
I think they use the time to do more important things, so that I'll continue improving Codexia.
fdterr commentedon Nov 12, 2025
This doesn't work for me. I can see the list of chats, but they don't open when clicked
milisp commentedon Nov 12, 2025
@fdterr What's your platform? Codex version?
rockmandash commentedon Nov 17, 2025
Hi @etraut-openai , thanks for the clarification about the 20-task limit.
Just want to share another perspective as someone who uses Codex pretty heavily.
For a lot of developers, each task is basically part of an ongoing workflow — debugging, multi-file refactors, or long feature work. When the history rolls over after 20 items, it becomes pretty hard to:
The data is technically still in
.codex/sessions, but digging through the raw files isn’t really a practical day-to-day solution.Even increasing the limit a bit (like 50–100), or making it configurable, would help a lot of people who work on longer tasks or use Codex throughout the whole day.
If performance was the reason for the cap, things like lazy-loading or a simple “load more” button might already be enough to keep the UI responsive while still giving access to older tasks.
Just wanted to highlight this because the 20-task limit ends up being a noticeable friction point for anyone doing more than quick one-off prompts. Codex has been awesome so far, and having more flexible history access would make it even smoother to use daily.
Thanks for taking a look!
AL-Cybision commentedon Nov 17, 2025
@rockmandash , totally ! , this was even what i faced and point i wanted to highlight @etraut-openai . Thanks!.
etraut-openai commentedon Nov 17, 2025
@rockmandash, that's well articulated. Thanks for sharing.
shayne-snap commentedon Dec 30, 2025
@fdterr @AL-Cybision you can give
WayLoga try. It's an opensource VS Code extension. History save automatically in.waylog/historyfolder, but you can search and save what you want.lechuhuuha commentedon Jan 5, 2026
Hi, this feature is really needed, there is some chat which is pure information that i need to read again. Scroll through the session files is so hard to see.
Would be a lovely to see more then 20 active chats
Thanks codex team for the great product
MargaretThomas commentedon Jan 23, 2026
Version 0.4.62 includes an update to the chat limit. I have 26 chats in total and I can see them all.
Thank you to those who did the update.
iqdoctor commentedon Mar 23, 2026
You can ask Codex to patch the Codex plugin as described in #15368. It worked surprisingly well for me. Just give Codex the link.