Skip to content

Codex Computer Use Logs Taking Up My Entire Computer Storage #25815

Open

Description

@jallieson

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

Activity

  1. github-actions commented on Jun 2, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  2. etraut-openai commented on Jun 2, 2026

    @etraut-openai
    Contributor

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

  3. jallieson commented on Jun 2, 2026

    @jallieson
    Author

    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.

  4. changed the title [-]Codex Random Logs Taking Up My Entire Computer Storage[/-] [+]Codex Code Use Logs Taking Up My Entire Computer Storage[/+] on Jun 2, 2026
  5. changed the title [-]Codex Code Use Logs Taking Up My Entire Computer Storage[/-] [+]Codex Computer Use Logs Taking Up My Entire Computer Storage[/+] on Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-useperformance

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions