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

Resolved 💬 5 comments Opened Nov 13, 2025 by BobbyWang0120 Closed Feb 23, 2026

What version of Codex is running?

0.57

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

macOS using iTerm2

What issue are you seeing?

When using Codex 0.57 through iTerm2 on macOS, I frequently see random garbled output whenever the assistant's response includes calls to file-modifying tools (e.g., writing or editing files). The content of the reply becomes unreadable junk characters and the interface layout (input box, layout) is broken and scattered. This happens unpredictably, and the response becomes meaningless gibberish. It is a severe issue as the output is unreadable and the UI is corrupted.

What steps can reproduce the bug?

It's difficult to reproduce because the timing seems random. The issue appears when running Codex 0.57 via iTerm2 on a Mac and invoking tool calls that modify or write files as part of the reply. After making several tool calls that modify files, occasionally a reply that includes file operations will render as garbled text and the UI layout becomes misaligned. There is no specific code snippet; the random nature makes reproduction unpredictable.

What is the expected behavior?

Responses that include tool calls to write or edit files should still render correctly in iTerm2. The text should be readable and the interface layout (input box, etc.) should remain intact. No garbled output or broken layout should occur.

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗