Random garbled output and broken layout in iTerm2 on macOS with Codex 0.57 when file-modifying tool calls are executed

Bug Description:
When using Codex version 0.57 through iTerm2 on macOS, responses that include tool calls for file modifications or writes sometimes result in the output area becoming unreadable. The content appears as garbled or corrupted text, and the interface layout (including input fields) becomes broken and scattered across the terminal window.

Steps to Reproduce:
The issue occurs intermittently and unpredictably. It seems to happen after Codex executes a tool call that modifies or writes files, but the exact conditions are unclear. Because of the random nature, there is no reliable way to reproduce it; sometimes everything works fine, and other times the very next response will be corrupted.

Expected Behavior:
Codex should consistently display readable output and maintain the correct layout in the terminal, even after file-modifying tool calls.

Actual Behavior:
Occasionally, after a tool call that modifies or writes files, the output turns into gibberish and the layout breaks, making it impossible to read the response or interact normally.

Environment:

• Platform: macOS using iTerm2
• Codex version: 0.57

Additional Information:
Because the issue is random and hard to reproduce, more debugging information may be needed. Any guidance on logs or debugging steps would be appreciated.

Thank you for investigating this issue.