Slow response after resuming chat with multiple terminal images

Open 💬 1 comment Opened Jul 6, 2026 by nima20002000

What happened?

When a Codex CLI chat contains multiple images in the terminal, pausing and then resuming the chat can cause the model to take a long time before it starts responding again.

Steps to reproduce

  1. Start a Codex CLI chat in a terminal.
  2. Add or display multiple images in the terminal/chat context.
  3. Pause the chat.
  4. Resume the same chat.
  5. Send a follow-up message.

Expected behavior

After resuming the chat, the model should begin responding within the normal latency range, even if the prior terminal history contains multiple images.

Actual behavior

The resumed chat takes a long time before the model starts responding. The slowdown appears correlated with having multiple images present in the terminal before pausing/resuming.

Environment

  • Codex CLI: codex-cli 0.142.5
  • OS: Linux 7.0.0-27-generic x86_64
  • Terminal: local terminal

Notes

This looks like a resume/session hydration or image-context handling performance issue. It may be reprocessing or serializing terminal image data when restoring the paused chat.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗