com.openai.codex.code_sign_clone temporary directories are never cleaned up on macOS

Open 💬 1 comment Opened Jul 1, 2026 by samxiexs

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.31921

What subscription do you have?

Plus

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

On macOS, Codex leaves behind temporary directories under:

/private/var/folders/.../X/com.openai.codex.code_sign_clone/

These directories contain cloned copies of Codex.app that are not removed after the application exits.

Over time, repeated launches cause these directories to accumulate and consume a significant amount of disk space.

What steps can reproduce the bug?

Launch Codex.
Quit Codex.
Repeat the launch/quit cycle several times.
Inspect the temporary clone directory:
du -sh /private/var/folders//X/com.openai.codex.code_sign_clone/ 2>/dev/null

or

ls -lah /private/var/folders/*/X/com.openai.codex.code_sign_clone/

What is the expected behavior?

Temporary cloned application bundles should be removed automatically once they are no longer required.

Cleanup could reasonably occur:

when the application exits normally;
during the next launch;
after a successful update; or
through another safe cleanup mechanism.

Users should not need to manually delete temporary runtime artifacts.

Additional information

Based on observation, these directories appear to be temporary runtime artifacts rather than user data.

If their retention is intentional, it would be helpful to document their lifecycle and cleanup policy. Otherwise, automatic cleanup would prevent unnecessary disk usage from accumulating over time.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗