codex - 💡(How to fix) Fix `/goal` + exhausted credits = bug inside the TUI.

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…

Error Message

■ Error running remote compact task: You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 3:09 PM.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.5 xhigh

What platform is your computer?

Linux 6.8.0-111-generic x86_64 x86_64

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

Tabby

Codex doctor report

What issue are you seeing?

Described in my tweet: https://x.com/ZypherHQ/status/2056025841906196915

SUMMARY: The issue happens when credits run out while /goal is active: it keeps looping this message:

■ Error running remote compact task: You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 3:09 PM.

This continues until it completely blocks the session and forces the context window to be compacted, which should never happen.

<img width="1916" height="821" alt="Image" src="https://github.com/user-attachments/assets/96a8dbf1-5067-4b15-8c3f-7d4fa0b18bf5" />

What steps can reproduce the bug?

Finish the credits while having /goal task activated.

What is the expected behavior?

It should not keep looping the “credits exhausted” message. It should simply wait and check every hour, or even better, check the current time with the appropriate date command in the terminal and calculate how much time is left until the reset.

The problem is that people like me use tmux to store Codex sessions with /goal; when we come back to them, they are all broken and it is no longer possible to continue the update that was being done through goal.

So instead of breaking everything, it should wait and resume later, so it does not interrupt the feature-creation flow midway.

This will save time, money, and mental health for everyone working through Codex.

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