Allowance percentages seem wrong and my accounts got suspended

[T-Higgins]

Hi there,

I'm seeing a couple of issues at the moment.
Could they be related?

1. Allowances are wrong.
   Codex-auth list shows a certain allowance for an account, but it is not correct.
   Example: it shows 100%, but actually the account is 0%.

2. I had two paid accounts suspended permanently.
   OpenAI say it's a breach of the ToS, but I have no other details.
   I only use these accounts for Codex.
   Could Codex-auth be the reason?

[T-Higgins]

Forgot a third issue.

3. Codex-auth switch is no longer working since I updated.
   It silently fails.

[T-Higgins]

Anyone there :D

[T-Higgins]

Just saw the disclaimer way at the end of the Readme.
Should be right up at the top @Loongphy not at the end.
It's cost me two accounts!

[Loongphy]

Hi @T-Higgins,

Thanks for reporting this. To help me investigate, could you please clarify the following:

1. Account type
   What type of account(s) were suspended — Free, Plus, Pro, Team/Business, or Enterprise?

2. How did you determine the allowance was wrong?
   You mentioned codex-auth list shows 100% but the account is actually 0%. How did you verify the actual 0% — was it through the
   ChatGPT web analytics https://chatgpt.com/codex/cloud/settings/analytics, or by hitting a rate limit during actual Codex usage?

3. codex-auth version and switch failure

• What version of codex-auth are you running? (codex-auth --version or the npm version)
• For the silent switch failure — could you share the exact command you ran and any output (or lack thereof)? For example,
  does codex-auth switch exit silently with no TUI, or does the TUI appear but the switch doesn't take effect?

I've tested with a Business and Plus account, it still works well.

[T-Higgins]

1. Two Plus accounts, used only for Codex. 2. I verified it in the Usage panel on Codex Cloud after noticing that Codex said it was 0% even though codex-auth said 100% 3. Whatever version is available right now via npm. As for the switch, the process steps work up to the point where I choose the account I want to switch to. Then it silently fails.

…

On Thu, 28 May 2026, 17:13 Loongphy, ***@***.***> wrote: *Loongphy* left a comment (Loongphy/codex-auth#121) <#121 (comment)> Hi @T-Higgins <https://github.com/T-Higgins>, Thanks for reporting this. To help me investigate, could you please clarify the following: 1. Account type What type of account(s) were suspended — Free, Plus, Pro, Team/Business, or Enterprise? 2. How did you determine the allowance was wrong? You mentioned codex-auth list shows 100% but the account is actually 0%. How did you verify the actual 0% — was it through the ChatGPT web analytics https://chatgpt.com/codex/cloud/settings/analytics, or by hitting a rate limit during actual Codex usage? 3. codex-auth version and switch failure - What version of codex-auth are you running? (codex-auth --version or the npm version) - For the silent switch failure — could you share the exact command you ran and any output (or lack thereof)? For example, does codex-auth switch exit silently with no TUI, or does the TUI appear but the switch doesn't take effect? ze — Reply to this email directly, view it on GitHub <#121?email_source=notifications&email_token=AMVZVMCUFKOSRX2VFCG4EYT45BQRVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGYYDGNRQGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4566036034>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVZVMA62GKNGZWWZ4OLAUD45BQRVAVCNFSM6AAAAACZNPQZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKNRWGAZTMMBTGQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMVZVMBNDTUN77RZJZYWFG345BQRVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGYYDGNRQGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AMVZVMGD2UKKAI7YLZLRXSD45BQRVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJWGYYDGNRQGM2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[T-Higgins]

How is it closed? I lost two accounts.

[T-Higgins]

Then why did you add the disclaimer? I only used those accounts (plural, not just one) for Codex. Nothing else. This is the only third party tool I use.

…

On Tue, 2 Jun 2026, 00:34 Loongphy, ***@***.***> wrote: *Loongphy* left a comment (Loongphy/codex-auth#121) <#121 (comment)> I’m sorry about the account ban. I don’t think this was caused by our tool, as it only checks quota information and does not send messages through your Codex account or consume tokens. This should not trigger OpenAI’s risk controls, and I haven’t seen similar ban cases involving third-party quota-checking tools. It may be related to factors like payment, region, network inconsistencies, or account sharing. If we receive similar reports in the future, I’ll reopen this issue and investigate further. — Reply to this email directly, view it on GitHub <#121?email_source=notifications&email_token=AMVZVMFP2QMLKYUG3ML662345YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4597335821>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVZVMBGBWB6U6ADVAJYQET45YHJTAVCNFSM6AAAAACZNPQZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOJXGMZTKOBSGE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMVZVMHRHN5YAJSROXMRGE345YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AMVZVMC65MYZQWMGYXNV62D45YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[T-Higgins]

And excuse me. How dare you cast insinuations!! I don't do any of those things. Way, way out of order man. Take that back.

…

On Tue, 2 Jun 2026, 00:34 Loongphy, ***@***.***> wrote: *Loongphy* left a comment (Loongphy/codex-auth#121) <#121 (comment)> I’m sorry about the account ban. I don’t think this was caused by our tool, as it only checks quota information and does not send messages through your Codex account or consume tokens. This should not trigger OpenAI’s risk controls, and I haven’t seen similar ban cases involving third-party quota-checking tools. It may be related to factors like payment, region, network inconsistencies, or account sharing. If we receive similar reports in the future, I’ll reopen this issue and investigate further. — Reply to this email directly, view it on GitHub <#121?email_source=notifications&email_token=AMVZVMFP2QMLKYUG3ML662345YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4597335821>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVZVMBGBWB6U6ADVAJYQET45YHJTAVCNFSM6AAAAACZNPQZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKOJXGMZTKOBSGE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AMVZVMHRHN5YAJSROXMRGE345YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AMVZVMC65MYZQWMGYXNV62D45YHJTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINJZG4ZTGNJYGIY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>