Steering Message After Compaction Won't Work

Resolved 💬 5 comments Opened Mar 9, 2026 by Kare-Udon Closed Apr 3, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.112.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.4 medium

What platform is your computer?

Darwin 25.3.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Ghostty 1.2.3 Build 12214

What issue are you seeing?

Steering messages added after the /compact command won't work.

<img width="220" height="138" alt="Image" src="https://github.com/user-attachments/assets/d9d91acb-4333-4651-b813-947cf6e0f4fe" />

The cli app also did not respond to ctrl-c, while ctrl-d do quit the app.

What steps can reproduce the bug?

  1. run /compact command
  2. when compact is going, add a steering message
  3. the steering message won't work

What is the expected behavior?

When compaction ended, steering message will be sent and there will be a response

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #13892
  • #13946
  • #13078

Powered by Codex Action

Kare-Udon · 5 months ago

Though #14048 is solved, I can still reproduce this issue with the latest codex cli.

<img width="313" height="143" alt="Image" src="https://github.com/user-attachments/assets/c726460e-8d1b-42c2-b048-75535541e9e6" />

The cli app still kind like freeze (not respond to ctrl-c signal).

Soorma718 · 5 months ago

I am having the same issue. After manual compact the model gets stuck on "working" and ctrl+c no longer works. Have to close the window and relaunch.

etraut-openai contributor · 4 months ago

Are you still seeing this problem with the latest CLI (0.118.0 or newer)? We've made significant changes to the TUI since this bug was filed, and we've fixed several bugs that could explain the behavior described above.

Kare-Udon · 4 months ago

After some simple tests, I can confirm this issue is solved. So I will close this issue.
Thank you for your contact.