Codex Computer Use Logs Taking Up My Entire Computer Storage

Open 💬 3 comments Opened Jun 2, 2026 by BeamoINT
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

This was Desktop but I don't want to open the app again cause it will bloat my computer so I submit the report in the cli here

What subscription do you have?

Pro $200/month

Which model were you using?

_No response_

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

_No response_

Codex doctor report

What issue are you seeing?

Codex logs took up my entire storage (this happened in the desktop app just passively and not in the CLI session at all)

What steps can reproduce the bug?

Uploaded thread: 019e8797-cf3b-7ab1-a491-d19b2a5c7f64

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 months ago

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

  • #24931
  • #24682

Powered by Codex Action

etraut-openai contributor · 2 months ago

Which logs are you referring to? Can you provide more details?

BeamoINT · 2 months ago

The Computer Use component (SkyComputerUseClient) accumulates large amounts of
disk space during a session that cannot be reclaimed until Codex is fully
quit.

What happens: The process writes temporary files (likely screen captures /
automation buffers), immediately unlinks them from the filesystem, but keeps
the file handles open. On macOS, disk space for a deleted file is only freed
when the last open handle is closed. Over a long session this silently grew to
~118 GB — invisible to Finder, du, and df since the files are unlinked.

How I found it: lsof +L1 (lists open files with link count 0 — i.e., deleted
but still held open) showed SkyComputerUseClient (PID 5439) holding hundreds
of deleted file handles totaling ~118 GB.

How it was fixed: Quitting Codex completely released all 118 GB instantly.

Expected behavior: Temporary files should either be closed promptly after use
or the process should be periodically flushing/closing old handles so disk
space doesn't accumulate across a long session.

Environment: macOS, Codex Desktop, Computer Use feature enabled.