Codex context burn remains high after compaction/new session

What version of Codex CLI is running?

codex --cli 0.142.0

What subscription do you have?

Pro 5x

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 7.0.11-76070011-generic x86_64 x86_64

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

Cosmic

Codex doctor report

Doctor/update behavior:
  I was asked to check for an update and run codex doctor before filing. codex doctor
  completed in the managed Linux Codex session, but showed sandbox/network-related
  failures: 13 ok, 1 idle, 4 notes, 3 warn, 1 fail. The failure was provider
  reachability/DNS blocked inside the sandbox, plus optional Socket MCP reachability
  and update probe warnings.

  Then the update check/npm update attempt hung with no output under restricted
  network and the terminal/session crashed before I could capture codex doctor
  --json. No stray codex/npm/node update process was left running afterward, and the
  install still reports codex-cli 0.142.0.

What issue are you seeing?

Main bug:
Context burn remains abnormally high after compaction and even after starting a new session. After compacting and starting a totally new session, context was already around 46% left. This happened repeatedly today and forced multiple compactions much sooner than normal along with higher token burn and much slower work flow than usual for what we are working on.

What steps can reproduce the bug?

Uploaded thread: 019efc4e-c11e-72c3-ba71-68712bc5dbf5

We did multiple compacts, hit our 5 hour cooldown faster than usual. I allowed the cooldown, restarted my session fully compacted and ready to continue and on one tool update we had to compact again. We decided to start a brand new fresh session to see if that would fix the issue and got to one briefing and one tool update and had 46% left to compact. Workflow was still slow and token burn is heavier than normal for the type of work we are doing right now updating our security read-only tools from cyber security blogs.

What is the expected behavior?

On a normal day we don't come close to our 5 hour cooldown doing this type of work. We move much faster updating than we have been because the tools are established it is just adding new content. Normally we can knock these out during my morning but today it has been all day compacting.

Additional information

This started with the new update and is the first time we have encountered this type of compacting issue, slow responses, and length of time to complete a daily ritual / standard practice.