Unexpected Codex usage attribution: 500 credits consumed in less than 1 hour

Hi,

I’m trying to understand a possible Codex usage attribution issue.

In Codex Analytics, I noticed that around 500 credits were consumed in less than 1 hour, which seems highly disproportionate compared to my intentional usage.

What I can currently see:

  • weekly usage limit exhausted

  • 5-hour limit still at 100%

  • 0 credits remaining

  • product activity shows 8 threads and 265 turns over 1 month

  • most visible activity appears to be associated with the IDE extension

My question is mainly technical:

  • can IDE extension activity consume credits unexpectedly in the background?

  • can old or inactive sessions continue to generate counted turns?

  • is there a way to identify the exact source of the counted usage (Cloud, CLI, IDE extension, code review)?

  • has anyone seen analytics/usage attribution behaving disproportionately like this?

I’m not asking about subscription refunds here — I’m trying to determine whether this is expected Codex behavior, an extension/session issue, or a usage tracking anomaly.

Thanks.

Hi @Fabiio

Yeah, this is a really fair question.

Codex is credit-based, but credits are tied to how much data is processed (input, output, and context) and not just the number of turns. So usage can climb faster than it looks, especially with larger code context or multi-step tasks.

On your points:

IDE extension: yes, it can use credits if it’s analyzing files or running tasks. Work started earlier (especially cloud tasks) can continue, which may feel like background usage.

Inactive sessions: idle chats shouldn’t consume credits, but async/cloud tasks can keep running until they finish.

Spikes: can happen with large context or longer-running tasks, but if it doesn’t match your activity, it’s a valid thing to question.

If it still doesn’t add up, it’s worth reaching out to Support with your workspace ID, they can dig into the usage details and help pinpoint what happened.

~Smith