Excessive storage usage for sessions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
0.149.1
What subscription do you have?
pro x20
Which model were you using?
gpt 5.6 sol
What platform is your computer?
linux
What terminal emulator and version are you using (if applicable)?
No response
Codex doctor report
What issue are you seeing?
I demand (you heard me right, it's demand, not request) to stop killing our m.2 drives with writing dozens gigabytes of session data. No analytics, no telemetry allows, nothing except actual chat history. I do not care of your codex doctor, you have no consent to collect data and kill my storage! I demand that you stop this stupid practice immediately.
What steps can reproduce the bug?
Just use codex normal way it writes many GBs to ~/.codex/sessions/ .
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with Codex CLI 0.149.1 on Linux by using it normally and measuring growth under ~/.codex/sessions/. Inspect what session data is written there and identify the expected storage limit or retention behavior; done means normal use no longer produces dozens of gigabytes and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100