2x Rate Limits not implemented

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #10663
• #11535

Powered by Codex Action

The 2x rate limits are in effect. Can you share why do you think you're capped to the same level as you were prior to the 2x promotion? The usage is reported to clients as a percentage, not absolute numbers. Are you just going off of vibes — it doesn't feel like you're getting more usage? That might be explained by a change in model, reasoning level, or task complexity.

<img width="1249" height="380" alt="Image" src="https://github.com/user-attachments/assets/cbb908d1-c00d-4697-82e6-61880649ea1c" /> The quota limits were not applied because the usage columns on my dashboard for the quota metrics remain identical to the values before I started using the JetBrains Codex plugin. In other words, the dashboard did not register any change in usage after the plugin was introduced, which indicates that the limits tracking mechanism was not triggered.

My conclusion is not based on subjective perception. I am referring specifically to the percentage-based usage indicators shown on the dashboard. After the 2x promotion was announced, the percentage columns for CLI, JetBrains, and Exec continued to reach 100% at approximately the same workload and time intervals as before.

Since usage is displayed as a percentage of the total quota, a doubling of the limit should result in the same workload consuming a lower percentage of the quota. However, I did not observe any proportional decrease in percentage consumption.

The model, reasoning level, and task complexity remained consistent during the comparison period, so those variables do not explain the unchanged percentage behavior.

<img width="1315" height="786" alt="Image" src="https://github.com/user-attachments/assets/56de0be4-a837-4067-8a97-d34b5191c37c" />

@etraut-openai - I think my gripe is subjective but I am seeing something similar. This is my weekly usage, I rarely went over 50% usage on week over week. The last column is current week and I have around 20% left. I did use the CLI more but still weird for app having 2x, I'd expect it to be much lower. No scientific proof here, but was also looking at threads:

https://www.reddit.com/r/codex/comments/1r9cb10/is_2x_usage_no_longer_2x_usage/

<img width="2590" height="864" alt="Image" src="https://github.com/user-attachments/assets/359afdf5-5fc0-4147-9497-d393b57d4238" />

Title: Clarification on the “2× Codex Limits” Promotion (Rate vs Usage)

I’m posting this to close the loop on a confusion I had regarding the recent “2× Codex limits” promotion.

Initially, I interpreted the announcement as a doubling of the total usage quota available within the billing cycle. After clarification from support and reviewing the documentation, I now understand that the promotion applied to rate limits (throughput), not to the total usage limit.

In practical terms:

• Rate limit (throughput) = how many requests can be processed per unit of time.
• Usage limit = the total allocation available during the billing cycle.

The 2× promotion increased throughput — meaning requests can be processed faster and with higher concurrency. However, the total usage quota remained unchanged.

This distinction is important because:

• With higher throughput, work completes faster.
• Since the total quota is the same, accelerating processing can lead to consuming the available allocation more quickly.
• From a user perspective, this may feel like “no increase” — or even a faster exhaustion of quota — if one expects the total allowance to double.

So the system behaved correctly: the promotion improved processing speed, not total available usage.

Sharing this in case others had the same interpretation.

I also don't have 2x limits. I burned 18% of my weekly Codex limit in one day, which would be impossible if the 2× limits were active on my account. Normally I burn around 18% per day.

Title: Clarification on the “2× Codex Limits” Promotion (Rate vs Usage) I’m posting this to close the loop on a confusion I had regarding the recent “2× Codex limits” promotion. Initially, I interpreted the announcement as a doubling of the total usage quota available within the billing cycle. After clarification from support and reviewing the documentation, I now understand that the promotion applied to rate limits (throughput), not to the total usage limit. In practical terms: Rate limit (throughput) = how many requests can be processed per unit of time. Usage limit = the total allocation available during the billing cycle. The 2× promotion increased throughput — meaning requests can be processed faster and with higher concurrency. However, the total usage quota remained unchanged. This distinction is important because: With higher throughput, work completes faster. Since the total quota is the same, accelerating processing can lead to consuming the available allocation more quickly. * From a user perspective, this may feel like “no increase” — or even a faster exhaustion of quota — if one expects the total allowance to double. So the system behaved correctly: the promotion improved processing speed, not total available usage. Sharing this in case others had the same interpretation.

---

Copying the promo text directly from https://developers.openai.com/codex/pricing/

<img width="1632" height="194" alt="Image" src="https://github.com/user-attachments/assets/3d9b6daa-5fcb-4ddf-8d29-867440ff3055" />

and pasting it in GPT 5.2 Thinking chat with this question:

---

"What does the 2x mean here? For a limited time, try Codex for free in ChatGPT Free and Go, or enjoy 2x Codex rate limits with Plus, Pro, Business and Enterprise subscriptions."

---

Yields:

---

“2x” means your Codex usage/rate limits are doubled for a limited-time promotion if you’re on Plus, Pro, Business, or Enterprise (and in some materials, Edu).

In practice, Codex limits are tracked as things like:

• Local messages and cloud tasks within a shared rolling 5-hour window
• Code reviews per week

So “2x rate limits” = you can do roughly twice as much Codex work before hitting the cap in those windows (and it applies anywhere you use Codex: app/CLI/IDE/cloud).

To see your current remaining limits, check the Codex usage dashboard or run /status in an active Codex CLI session.

---

View the original chat here https://chatgpt.com/s/t_69a67432027c8191a2efe72030f12b17

So the implication is that usage limits are also increased.