codex - 💡(How to fix) Fix Possible macOS resource-pressure issue when running Codex CLI inside zellij/Ghostty during long-lived sessions [2 comments, 2 participants]

TL;DR

Investigate memory management and resource usage of Codex CLI within zellij/Ghostty to mitigate potential resource-pressure issues on macOS.

Guidance

• Review the memory footprint of codex-aarch64-apple-darwin processes and their impact on system resources during long-lived sessions.
• Analyze APFS ENOSPC log lines and system health status to understand the correlation between Codex usage and system resource pressure.
• Consider optimizing TUI streaming and large file operations within zellij to reduce memory retention and disk churn.
• Examine existing zellij compatibility reports (e.g., #9345) for potential insights into similar issues.

Example

No specific code snippet is provided due to the lack of detailed implementation information.

Notes

The issue may be related to the interaction between Codex CLI, zellij, and Ghostty, and further investigation is needed to determine the root cause. The provided information suggests a potential resource-pressure issue, but more data and logs may be required to confirm.

Recommendation

Apply workaround: Optimize Codex CLI usage within zellij/Ghostty to reduce memory usage and disk churn, as the issue seems to be related to resource management rather than a specific version problem.