codex - 💡(How to fix) Fix re-authing in pane1 causes infinite loop when pane2 tries to remotely compact

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

While re-authing on a machine with a codex device token, I had an ongoing chat. At some point the ongoing chat said my access token had expired (sensibly because I had re-logged in again). However this happened as it was trying to remotely compact my conversation. It spun overnight, attempting over and over again to recompact the conversation. It ballooned the codex chat log into 350Gb+ and charged me ~50% of my weekly usage. I would like this addressed and my usage returned to me ideally.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.133.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.8.0-41-generic x86_64 x86_64

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

tmux

Codex doctor report

What issue are you seeing?

While re-authing on a machine with a codex device token, I had an ongoing chat. At some point the ongoing chat said my access token had expired (sensibly because I had re-logged in again). However this happened as it was trying to remotely compact my conversation. It spun overnight, attempting over and over again to recompact the conversation. It ballooned the codex chat log into 350Gb+ and charged me ~50% of my weekly usage. I would like this addressed and my usage returned to me ideally.

What steps can reproduce the bug?

  1. login to an account in pane 1
  2. do some work in pane 1
  3. get to a point where pane 1 might be about to compact
  4. in pane 2 logout and login again
  5. pane 1 will fail remote compaction
  6. pane 1 will now proceed to fail over and over again creating a 350Gb codex log that bricks the computer and consumes ~50% of weekly usage over 15 hours or so.

What is the expected behavior?

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING