/goal continuations appear to keep running after subscription quota is exhausted

Resolved 💬 4 comments Opened May 7, 2026 by beskyee Closed May 22, 2026

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What issue are you seeing?

/goal appears to continue autonomous work after the relevant Codex usage quota is exhausted, instead of stopping at the quota boundary or following the normal credits/billing fallback behavior.

What steps can reproduce the bug?

Run a long-running /goal workflow until the relevant usage quota is exhausted, then observe whether goal continuation turns keep running.

What is the expected behavior?

/goal continuation turns should follow the same quota and credits accounting behavior as normal Codex turns.

Additional information

This may be related to goal continuation turns being initiated by the runtime rather than by an explicit user message.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 3 months ago

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

#18018
#21198

Powered by Codex Action

etraut-openai contributor · 3 months ago

Please use /feedback to upload logs and session details, then post the session ID here.

beskyee · 3 months ago

Please use /feedback to upload logs and session details, then post the session ID here.

After the remote compact failure, the affected session disappeared from codex resume. I also tried codex resume --all, but it did not appear there either.
details:

Codex version: v0.128.0
Model: gpt-5.5 medium
Environment: Debian

etraut-openai contributor · 3 months ago

Yes, the resume issues is a known problem if you start the thread with /goal prior to submitting any other user prompts. I'm working on a fix for that.

If you're able to repro the original bug you reported, please use /feedback.