Linux Codex users cannot access or redeem banked usage resets
What issue are you seeing?
New Codex rate limit reset mechanism makes it so only Codex Desktop App users can apply a reset/view their resets etc.
Since the Codex Desktop app is supported only by Windows/MacOS, Codex users are required to purchase Microsoft Windows or a Mac device in order to use banked Codex usage resets.
What steps can reproduce the bug?
Use Linux with Codex CLI/VSCode extension, and view your usage. No reset bank counter, nor "reset usage" capability or option is present.
What is the expected behavior?
That purchasing a new OS is not required to not feel excluded from an account-level Codex update; That using linux should not block one out from ever receiving a usage reset.
Additional information
Presumably, if the reset expires while Linux users remain unable to redeem it, then this is teetering on false marketing because OpenAI (on X) said: "We’re starting Go, Plus, Pro, and Business users with one free reset:" -- which is incorrect currently for Linux users, as they are unable to access said reset.
This is misleading by omission.
17 Comments
A web implementation would also be fine. For example, the reset could be shown and redeemed from a Codex usage/settings page such as https://chatgpt.com/codex/cloud/settings/analytics
I agree, and this link doesn't solve the issue as it's not an OpenAI method. But, I hope it's a useful workaround for you in the meantime. There are things like https://github.com/ilysenko/codex-desktop-linux which allow running Codex App/Desktop on linux. App shold be native to linux. There should be other ways to reset it, like the analytics page.
There's also running a VM with Windows, even if to just boot it, click reset, and shut down. Again, just a silly workaround.
We're working on exposing this functionality in the CLI (TUI).
<img width="1108" height="851" alt="Image" src="https://github.com/user-attachments/assets/df4d80de-bea4-4344-ab2e-c68fed360ef8" />is it not rolled out for my account, i dont see it
Me neither. They did not actually roll out to all paying users, at least not yet, despite it being a few days. It's ridiculous that they would expect this to "feel good" to end users, lol. If one can see others reaping the benefit, but is left in the dust themselves, they do not feel "good" about who caused that.
Still not appearing on the CLI on linux
CLI support for viewing and redeeming available rate-limit resets has landed in #28154 and will be included in the next CLI release. Once available, eligible Linux users can open /usage and select Redeem rate limit reset.
Seems like it's merged. When will it be released?
using v0.141.0 , which has resets listed as part of change set, but I can't see the resets... anyone else?
@jayp-oai Cough, cough. It's been confusing for an awful lot of users that the reset yesterday was a hard reset rather than an issued rate-limit reset. I think we all expected them to be ones we could control from now on. Maybe it was hard reset since many users can't use them yet though. /shrug
@jayp-oai and @zeroflaw On v0.141.0, I also don't see the resets. In its release notes, there is #28143 related to app-server clients being able to do this, but they don't say the Codex CLI can do this or that it was added to '/usage'. ChatGPT looked at this, and said #28154 does add Codex CLI/TUI support to '/usage', but that #28154 was not included in v0.141.0 -- that it only included #28143.
I think this just means that it's likely to be in v0.142.0. The Github comparison between v0.141.0 and main shows #28154 is in main, but not v0.141.0, along with a number of other commits that were in main before v0.141.0 was tagged.
I don't know enough about Codex's release tagging system, but my guess is the latest main commit isn't what's tagged as a release, that maybe it lags behind a little bit for testing purposes. So, no big deal, "will be included in the next CLI release" was probably just not exactly how this is going.
I had Codex create a Python script that displays and optionally uses resets. It looked at how Codex CLI added app-server support, and connects to that endpoint directly. It doesn't connect using app-server. Download it at https://gist.github.com/darlingm/75b2e31e41ce218018afd7a8d485df85
Until v0.142.0 is released, you can use this to:
./codex-resets.py # Read-only; displays if resets available, and current limits
./codex-resets.py --json # In JSON format, with more output
./codex-resets.py --use-reset # Prompts for input, for you to confirm that you really want to use it
./codex-resets.py --use-reset --yes # Recommend against this; bypasses user confirmation
Use at your own risk. Give it and this issue to your own Codex for verification before running.
Going by some comments/posts on X, as well as here, it sounds like this isn't a bug in the app itself, but rather a backend bug. I haven't had any banked resets so far since the feature was launched, not for yesterday's reset either.
Sanitised usage/reset-credit state:
{
"plan_type": "pro",
"rate_limit_allowed": true,
"rate_limit_limit_reached": false,
"rate_limit_reached_type": null,
"rate_limit_reset_credits": {
"available_count": 0
}
}
Reset-credit list response:
{
"available_count": 0,
"credits": []
}
I have 2, and haven't used any. I thought it was limit to one reset, but apparently not?!
Nope, I've seen some people get 2, one of them was from the feature's launch and the other was from yesterday's reset. However it's also a mixed bag, some people have only had one of them too, or in my case and some others, none haha.
I guess there's more than one bug going on that's related to this feature. Hopefully they'll fix everything soon..
@Ixe1 would you mind DMing account informations to https://x.com/jaybinpark so I can further debug?
codex 0.142.5 now can using Reset-credit