Desktop app: context overflow can terminate a turn before any compaction runs, then reset status to '100% left (0 used / 760K)' and finish with no agent message

[DMontgomery40]

What version of Codex is running?

Codex Desktop / app-backed session
cli_version: 0.108.0-alpha.12

What subscription do you have?

Pro

Which model were you using?

gpt-5.4

What platform is your computer?

macOS (Desktop app-backed session)

What issue are you seeing?

I hit:

Codex ran out of room in the model's context window. Start a new thread or clear earlier history before retrying.

But this does not appear to be the same failure mode as the existing remote compaction failures.

In my case, the turn appears to overflow before compaction runs at all:

• the local session JSONL contains zero type:"compaction" events
• immediately after the failure, the UI/status showed:
  • 100% left
  • 0 used / 760K
• the turn then ended with task_complete and last_agent_message: null

So from the user side it looks like Codex both:

1. says it ran out of context, and
2. simultaneously says there is effectively a fresh / empty context window.

That combination is misleading and makes this look different from:

• remote compaction failing with context_length_exceeded
• compaction loops
• post-compaction percentage display bugs

Why I think this is a distinct issue

Related issues I found:

• Codex ran out of room in the model's context window. Start a new conversation or clear earlier history before retrying. #8190
• Spark ran out of context #12468
• ERROR codex_core::compact_remote: remote compaction failed #13271
• Error running remote compact task #9800
• Repeated 413 errors on compaction #11440
• Context percentage shows zero after compaction #9417

Those are close, but this report is specifically about:

• no compaction attempt being recorded at all
• a silent task termination
• a reset/misleading status readout after failure (100% left, 0 used / 760K)
• likely a single oversized in-flight turn/tool payload that overflows before auto-compaction can trigger

What steps can reproduce the bug?

I do not have a minimal repro yet, but this happened in a fresh thread while the agent was doing web/doc lookups.

The pattern seems to be:

1. Start a fresh thread in Codex Desktop
2. Ask Codex to inspect/open multiple large docs/web pages and keep working in the same turn
3. The turn eventually errors with the normal "ran out of room" message
4. Instead of showing a compaction attempt/failure, the session:
   • records no compaction events
   • resets the visible status to 100% left (0 used / 760K)
   • ends with no last agent message

What is the expected behavior?

One of these should happen instead:

• auto-compaction should run before the turn is terminated, or
• Codex should surface a clear pre-compaction overflow error saying the current in-flight request was too large to compact, or
• the UI should not reset to 100% left / 0 used immediately after a context overflow if that is not actually the usable state

Additional information

Affected session ID:

019cc407-9cbf-7f40-9586-1c5f12f5a7bf

Local session inspection found:

• compaction_events = 0
• final token/status events showing model_context_window = 760000
• then a reset-like status event with 0 used / 760K
• then task_complete with last_agent_message = null

This looks like:

pre-compaction turn overflow + misleading post-failure context status + silent task completion

[github-actions]

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

• Spark ran out of context #12468
• Codex ran out of room in the model's context window #12790
• Compaction progress state not clearing in Windows app when compaction task fails (stuck "자동으로 컨텍스트를 압축하는 중") #13659

Powered by Codex Action

[yassirusa]

When will this be worked on. Codex-5.3 and codex-5.3-spark are completely useless and they keep churning tokens without editing any code until they "run out of room"