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

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

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 ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗