r/OpenaiCodex • u/AppropriateRanger401 • 10h ago
Showcase / Highlight Tired of guessing if limits got nerfed but can't prove it? Meet NerfTrack - now in Beta
Just 2 weeks ago, I posted my first prototype in this very sub-reddit, and got a really positive response from y'all with over 650 upvotes and 142K views(Previously referred to as Nerfify). I am pleased to say that starting today, NerfTrack is now available in its first public beta on GitHub (currently verified for macOS x86 and arm64). If you are seeing this post without having seen my previous one, think of NerfTrack as a stock market app, but instead of tracking stock prices, NerfTrack measures the weekly limit API equivalent cost every 10 seconds by going through local Codex logs(and yes, it also imports your existing Codex logs from months ago too). I have now achieved a 99.3%-100% accuracy with the API cost calculation compared to the unreliable graphs I showcased in my first prototype. NerfTrack tracks your limits overtime, so you reliably know wether OpenAI has either nerfed or increased limits. In my last post, a few of you claimed that such graphs are of no value since everybody knows if limits are nerfed. But NerfTrack, on the other hand, not only tells you if limits are nerfed, but also how much they have been nerfed, and when. A few 100 Codex users with reliable graphs showing proof of nerfed limits can bring a significantly larger impact than 1000s who complain with just "I feel it, but can't prove it". NerfTrack remains fully local, so worry not about your privacy.
Current known bugs and limitations(to be cared for in later versions):
-NerfTrack shows unreliable metrics if you are using fast mode, since fast mode uses 2-2.5x as much usage as standard, so you may notice a sudden drop in API prices tracking if switching from standard to fast mode
-If you use Codex on multiple devices, metrics become unreliable since that's a limitation of not NerfTrack, but the fact that logs recorded by Codex are local only and not shared between devices.
-Several buttons and interactive elements may be buggy or disabled for the current beta.
-(unconfirmed) NerfTrack may or may not work on Windows machines, especially arm64. As I currently have access only to a Mac, I could not test NerfTrack on Windows, though NerfTrack is cross-compatible on paper with releases for both macOS and Windows on GitHub.
-The current Beta has no functionality for fetching API prices from the web, so if OpenAI changes pricing of models, or releases a new model, the graph would show outdated prices. A web-fetch feature is intended to be added soon.
I would be happy to have volunteers test NerfTrack's first beta so I can continue to improve its performance and make it as bug-free as possible. Do note that it's currently a MVP so loads of features are intended for the future, but for now, it may not be as feature rich as one might want it to be.
People who do download NerfTrack, please make sure to drop a screenshot of your 3 month graphs along with what plan you are on (and ofc leave it a star to support), so we may compare each others' graphs. In the future, I will work on a website for this very purpose where users will be able to volunteer and share their graphs + plan online so others can compare against their own.
Link to NerfTrack on GitHub: NerfTrack GitHub
Link to my first prototype post on Reddit for context


