/compcat tool not working properly, Auto-compact works

Resolved 💬 5 comments Opened Apr 24, 2026 by Lyellr88 Closed Apr 24, 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?

0.124.0

What subscription do you have?

Plus

Which model were you using?

Gpt 5.5

What platform is your computer?

Windows

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

pwsh 7.1

What issue are you seeing?

/compact tool is not working only way compact happens is upon auto-compact. /compact is being sent as a normal message.

What steps can reproduce the bug?

Uploaded thread: 019db8d3-cdfd-7253-a046-53266a23a4fa

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 4 months ago

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

  • #17469
  • #18814

Powered by Codex Action

etraut-openai contributor · 4 months ago

I'm not able to repro the problem. It looks like you chose not to upload your logs and session data with /feedback (or they failed to upload for some reason), so I'm not able to use that for a diagnosis.

Are you attempting to use /compact with an argument like /compact this? That will be sent as a user message rather than being interpreted as a slash command.

What behavior are you seeing when you use /compact?

Lyellr88 · 4 months ago

Apologies not that experienced on doing PR's. It started about 2 days ago, and I noticed it, honestly nothing has changed.

I know that Codex doesn't allow text after /compact command like other CLI agents do.

Every time I use /compact now it's sent as a normal message, so I tried updating to see if that would help. Still the same issue, so I uninstalled and reinstalled and still the same issue.

etraut-openai contributor · 4 months ago

What evidence do you have that /compact is being sent as a normal message?

Lyellr88 · 4 months ago

All set, it's working now. Must of it had been some kind of bug yesterday, so as of now I have no evidence and it's operating normally.