Summary
codex-tui.log grows extremely fast because codex_core::file_watcher logs every Access(Open) event at INFO. On my system it reached ~536 MB (2,294,753 lines) within a short time. ~2,320,855 lines are identical file-watcher open events.
Version
Evidence (top normalized messages)
2320855 INFO codex_core::file_watcher: file watcher received filesystem event event_kind=Access(Open(Any)) event_paths=[...] event_attrs=EventAttributes { inner: None }
13046 INFO codex_core::skills::manager: skills cache cleared (… entries)
Sample log lines
2026-02-09T16:12:40.861463Z INFO codex_core::file_watcher: file watcher received filesystem event event_kind=Access(Open(Any)) event_paths=["/home/.codex/skills/.system/skill-installer/assets"] event_attrs=EventAttributes { inner: None }
2026-02-09T16:12:40.861491Z INFO codex_core::file_watcher: file watcher received filesystem event event_kind=Access(Open(Any)) event_paths=["/home/.codex/skills/.system/skill-installer/scripts"] event_attrs=EventAttributes { inner: None }
Impact
- Log file grows to hundreds of MB quickly.
- Disk churn and noise makes the log hard to use for debugging.
Expected behavior
Access(Open) events should be either debounced, aggregated, or logged at DEBUG/TRACE (not INFO).- Ideally, file watcher should log high-level changes, not every open access.
Actual behavior
- Every
Access(Open) event is logged at INFO.
Notes
Most of the events point into .codex/skills directories (assets/scripts/agents). It looks like something is repeatedly scanning or touching those paths, and every open is emitted at INFO.
If you need more detail (or a full log excerpt), I can provide it.
Summary
codex-tui.loggrows extremely fast becausecodex_core::file_watcherlogs everyAccess(Open)event at INFO. On my system it reached ~536 MB (2,294,753 lines) within a short time. ~2,320,855 lines are identical file-watcher open events.Version
Codex: 0.99.0
Log path:
/home/.codex/log/codex-tui.logEvidence (top normalized messages)
Sample log lines
Impact
Expected behavior
Access(Open)events should be either debounced, aggregated, or logged at DEBUG/TRACE (not INFO).Actual behavior
Access(Open)event is logged at INFO.Notes
Most of the events point into
.codex/skillsdirectories (assets/scripts/agents). It looks like something is repeatedly scanning or touching those paths, and every open is emitted at INFO.If you need more detail (or a full log excerpt), I can provide it.