/compact does not work.

[EnterOgawa]

What version of Codex is running?

0.44.0

Which model were you using?

gpt-5-codex high

What platform is your computer?

Windows11Pro 24H2 build 26100.6725

What steps can reproduce the bug?

If the context window is fully used, /compact cannot be executed.
Also, since the consumption is not displayed, it's difficult to determine the right timing to perform /compact.

What is the expected behavior?

I want /compact to be usable even when the context window is fully used.
Also, I’d like the remaining percentage to be displayed at all times, as it used to be, so I can know when to perform /compact.

What do you see instead?

No response

Additional information

[alienwareagent]

Also compact make codex lose context. It does not remember the latest discussion but instead it remember the middle of the previous context/discussion. Needs some improvement in how to compact efficiently without losing what was done and where it stopped before compact.

[EnterOgawa]

The following features would be ideal:

1. When less than 5% remains, prompt the user to perform /compact or perform it automatically (having this as a selectable option would be ideal).
2. In addition to /compact, enable saving a work log to a file. It would be even better if the user could define the quality of the log.

Currently, /compact alone is not sufficient, and although instructions for work logging are given in prompts and AGENTS.md, some information is missed.

If this functionality were implemented as a feature, it would greatly improve continuity.

As an urgent measure for now, I’d like the remaining percentage to be displayed as before.
That alone would be enough to handle the situation for the time being.

The main issue at the moment is that the remaining context is displayed during inference, but not when waiting for a prompt.

[aibrahim-oai]

The following features would be ideal:

1. When less than 5% remains, prompt the user to perform /compact or perform it automatically (having this as a selectable option would be ideal).
2. In addition to /compact, enable saving a work log to a file. It would be even better if the user could define the quality of the log.

Currently, /compact alone is not sufficient, and although instructions for work logging are given in prompts and AGENTS.md, some information is missed.

If this functionality were implemented as a feature, it would greatly improve continuity.

As an urgent measure for now, I’d like the remaining percentage to be displayed as before. That alone would be enough to handle the situation for the time being.

The main issue at the moment is that the remaining context is displayed during inference, but not when waiting for a prompt.

That's on our roadmap. As a work around you can edit the previous messages (using esc esc) to gain back some context then compact.

[alienwareagent]

The following features would be ideal:

1. When less than 5% remains, prompt the user to perform /compact or perform it automatically (having this as a selectable option would be ideal).
2. In addition to /compact, enable saving a work log to a file. It would be even better if the user could define the quality of the log.

Currently, /compact alone is not sufficient, and although instructions for work logging are given in prompts and AGENTS.md, some information is missed.
If this functionality were implemented as a feature, it would greatly improve continuity.
As an urgent measure for now, I’d like the remaining percentage to be displayed as before. That alone would be enough to handle the situation for the time being.
The main issue at the moment is that the remaining context is displayed during inference, but not when waiting for a prompt.

That's on our roadmap. As a work around you can edit the previous messages (using esc esc) to gain back some context then compact.

Excellent looking forward to that

[CodeAlexx]

.45 same thing, /compact name loses all context, /compact alone, 0 percent context left, even after a compact.

[EnterOgawa]

In the end, the best solution is to proceed with the work while keeping a work log.
Thank you👍

[sbaechler]

With Codex 0.45 I am getting a stream error when calling /compact. Other prompts like "hello" are working as expected. I am using gpt-5-codex on Azure AI Foundry using the responses API.

[EnterOgawa]

Thank you for the report.
For the time being, I’ll operate under the policy of not using /compact and instead clearing the context with esc -> esc -> enter to continue in a new session.
By the way, I experienced a memory error that caused Codex to crash while using 0.45, but since I can’t reproduce it, I’ll monitor the situation for now.

[jif-oai]

@EnterOgawa could you share some logs on this memory error?
You can find internal logs in ~/.codex/log/codex-tui.log

[bradvb1234]

Came across this issue and just wanted to chime in on what my experience has been. I am noticing that i need to run /compact with some minimum percentage left so that it can work. If its below a certain percentage it will fail with the stream error messages. It needs this minimum percentage because it seems to add to the context the first time /compact is run as the context % left value always decreases further on the first run. If I then run /compact again it works as expected. Maybe its doing the compact the first time and adding the compacted context to the current context before using it when compact is run again? Not sure, but this is how its working for me after the update.