Skip to content

codex-tui.log at 116 GB: where Codex keeps its logs on a Mac, and what is safe to delete

Why Codex's log file can grow past 100 GB on a Mac, where ~/.codex keeps logs, sessions and packages, and which parts you can delete. Measured on ours: 1.0 GB.

5 min read

Seen on X, 236K views
i had codex audit my entire macbook to see how much space we can save and it's found 500 GB to save, AWESOME prompt was: "do a FULL read only analysis on my Macbook to help me optimize storage" note: why tf is there a codex-tui.log file that is 116gb??????? WHAT ????

Where does Codex store its logs on a Mac?

In the hidden ~/.codex folder in your home folder. Older versions wrote a plain codex-tui.log there; current ones keep logs in a database file, logs_2.sqlite, beside sessions, packages and plugins.

Inside ~/.codexWhat it isOn our Mac
packagesDownloaded tool packages310 MB
pluginsInstalled plugins297 MB
sessionsSaved conversations115 MB
logs_2.sqliteLogs66 MB
computer-use, generated_imagesFeature data and images85 MB
du -sh ~/.codex/* 2>/dev/null | sort -h | tail -8
find ~/.codex -name "*.log" -size +100M -exec ls -lh {} \;

Is it safe to delete codex-tui.log?

Yes, with Codex closed. It is a record of what the terminal app did, and Codex starts a new one when it needs to. Deleting it does not touch your code, settings or sign in.

What else in ~/.codex can go?

Old sessions, if you do not need the history. Leave the config and auth files and the packages folder, which Codex would only download again. The wider picture for AI coding tools is in Codex CLI taking up space.

Common questions

Where is codex-tui.log on a Mac?

In ~/.codex, the hidden Codex folder in your home folder. Current versions keep logs in ~/.codex/logs_2.sqlite instead; on our Mac it was 66 MB in October 2026.

Can I delete codex-tui.log?

Yes. Quit Codex first. The file is only a log; Codex creates a new one as needed, and your code and settings are untouched.

Read next