{
"$type": "site.standard.document",
"bskyPostRef": {
"cid": "bafyreigcyvkrhoawqbaogccpbfflubqyouqnjw5qrc3iwaimfp5x2lyn7i",
"uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlkx2hm4jpt2"
},
"path": "/t/codex-usage-limits-seem-to-be-draining-unusually-fast-since-10-may-2026-even-with-light-gpt-5-3-codex-use-while-the-usage-tracking-ui-also-appears-buggy-or-missing/1380649#post_3",
"publishedAt": "2026-05-11T08:58:18.000Z",
"site": "https://community.openai.com",
"textContent": "Honestly pretty disappointed with the OpenAI support experience right now.\n\nI submitted:\n\n * screenshots,\n\n * timestamps,\n\n * usage inconsistencies,\n\n * UI bugs,\n\n * and even video proof showing the Codex usage tracker disappearing entirely.\n\n\n\n\nI also explained the logical inconsistency where my weekly limit suddenly jumped to ~90–94% while the 5-hour limit was still much lower, which clearly suggests something abnormal with tracking/accounting.\n\nInstead of actually investigating the issue, checking backend logs, or escalating it to engineering, I’m mostly getting generic copy-paste responses explaining how token usage works — things that are already available in the docs and chatbot responses.\n\nThat’s the frustrating part. I didn’t contact support to be told basic documentation again. I contacted them because there appears to be a real bug or accounting issue.\n\nWhat makes it worse is:\n\n * other users have reported similar Codex tracking issues in the past,\n\n * OpenAI has previously acknowledged tracking problems publicly\n\n\n\n\nAs a paying user who actively tracks usage, this honestly makes me disappointed. Support should investigate customer-specific evidence instead of responding like another automated chatbot.\n\nHas anyone else here managed to get an actual engineering escalation for Codex usage/accounting issues recently?",
"title": "Codex usage limits seem to be draining unusually fast since 10 May 2026, even with light GPT-5.3 Codex use, while the usage-tracking UI also appears buggy or missing"
}