Context compression caused Codex to attribute the previous approval error to the task that needs approval this time.

What version of the Codex App are you using (From “About Codex” dialog)?

Powered by Codex & OWL Version 26.721.81911 Released Jul 29, 2026

What subscription do you have?

Pro 5x

What platform is your computer?

macOS and Darwin 27.0.0 arm64 arm

What issue are you seeing?

I’m implementing a Goal that requires my approval upon completion of each stage before proceeding.

However, today I discovered that context compression is causing Codex to attribute previous approval errors to the task currently requiring approval.

What steps can reproduce the bug?

Develop a goal-oriented coordination plan that requires my approval for each completed step before proceeding to the next.

Tasks only need to be approved once. If subsequent tasks encounter context compression issues upon completion, they may attribute previous approval errors to new tasks requiring approval, thus bypassing the approval process and continuing execution.

What is the expected behavior?

Regardless of whether context compression is triggered, Codex should request my approval to continue processing upon completion of the task.

Additional information

As you can see from the screenshot, I didn’t reply between the two contexts; there was only one context compression.

After context compression, it attributed the error of the previous task’s approval request to this task, thus skipping the current approval and continuing the task.

This was a huge mistake.

<img width="866" height="816" alt="Image" src="https://github.com/user-attachments/assets/3251cf72-d7ee-49d1-8d0c-77f54ab8fb3e" />