Codex Desktop on macOS sometimes renders conversation view incorrectly

Open 💬 2 comments Opened Jul 9, 2026 by ndj888

Summary

Codex Desktop on macOS sometimes renders a conversation incorrectly. The session view can become visually inconsistent while an agent is still working: older turn content remains partially visible, the latest assistant response appears cut off or hidden behind the composer, and the input composer overlays the conversation area. This makes the current state of the session hard to read and hard to control.

The issue has a major impact on the user experience because the user cannot reliably tell whether Codex is still thinking, whether the latest response has completed, or whether a follow-up message will be applied to the correct turn.

Environment

  • App: Codex Desktop
  • Platform: macOS desktop app
  • macOS: 26.2, build 25C56
  • Codex app version: 26.623.141536
  • Codex app build: 4753

What happened

During normal use of Codex Desktop, the conversation display became abnormal:

  • The visible conversation showed stale/previous turn content mixed with the current turn.
  • The assistant response area appeared partially cut off.
  • The message composer floated over the conversation content and obscured text.
  • The left side of the conversation area showed repeated dotted/placeholder-like vertical artifacts.
  • The user could not comfortably read the latest response or continue the session with confidence.

The reporter is using the macOS desktop version. A screenshot was captured showing the broken state.

Expected behavior

Codex Desktop should keep the conversation view stable and readable:

  • Current and previous turns should render in the correct order.
  • The latest assistant response should not be clipped or hidden behind the composer.
  • The composer should stay anchored below the visible transcript without covering content.
  • Any in-progress state should remain visually clear and recoverable.

Actual behavior

The conversation transcript and composer overlapped visually, making the session appear corrupted or out of sync.

Request

Please fix the conversation rendering/state issue in Codex Desktop. Since this kind of UI failure can consume user time and usage while the session is not reliably readable or controllable, please also provide a one-time reset opportunity for affected users.

Notes

This appears to be a desktop app/session rendering issue rather than a model response quality issue.

View original on GitHub ↗

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