Codex Security plugin burned through 60–70% of my weekly quota on 200$ plan with no results
What version of the Codex App are you using (From “About Codex” dialog)?
Powered by Codex & OWL Version 26.803.61601 Released Aug 9, 2026
What subscription do you have?
200
What platform is your computer?
Mac m4
What issue are you seeing?
Sorry for AI written post but it's better than I'm in explaining the issue clearly.
So today I launched the Security plugin in Codex and something went wrong.
I'm on the latest version of the desktop app, on mac.
At first, the security scan reported that my CLI was outdated. I updated the CLI and started the scan again.
It then ran for around 3 hours without returning results and at that point I steered the agent and told it to stop/close the scan if it couldn't return any results within the next 15 minutes.
15 minutes later, Codex told me it was no longer watching the process but the process itself apparently kept running in the background.
Eventually it reported that the process had terminated which happened due to my subscription usage limit being completely exhausted by it.
Before starting this, I had around 60–70% of my weekly quota left.
The usage dashboard says 91% of today's usage came from the SDK.
And after all of that, the security scan still didn't produce any result. Literally nothing. It;s just long scroll of "its still working" messages.
It looks like either the underlying process continued consuming tokens after the agent stopped watching it, or something got stuck in a runaway loop.
What steps can reproduce the bug?
Feedback ID: 019ff558-5195-72e3-929d-d02aa855af0d
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
+1. Same here for the last 2 days — Codex/GPT feels clearly dumber:
worse instruction following, more context loss, more retries, and higher token usage for lower-quality results.
Not normal variance. Can share thread IDs if needed