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
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