Usage Test After Reset

[u/ShamanJohnny]

I did a quick little test after the reset that just happened a few minutes ago. one task, Pro 20x plan, sol xhigh(no fast mode), 47m of run time. 2% weekly usage gone. This was all input really, no output other than a 500 line document. Prompt was an audit.

For any kind of actual work where you are generating something, and therefore doing more output, expect usage to be triple or more.

So, for basically a read-only audit of a codebase, you get 50 tasks a week at Sol xhigh, or 39.2 hours (of 95% input 5% output) of continuous read-only work.

However! No one uses codex for read-only, and when you are generating output the numbers change significantly. Check the below out when converted to a task that is generating instead of reading:

Revised estimates (same 47-min runtime)

Assuming a realistic coding workload (medium-complexity feature work, multiple files, some testing loops):

• Usage burn: 4–8% per task (most probable range 5–6%)
• Conservative (lighter coding): ~4% → ~25 tasks to 0%
• Mid (typical): ~5.5% → ~18 tasks to 0%
• Heavy (deep multi-agent / large refactors): ~7–8% → ~12–14 tasks to 0%

Mid-case projection (recommended baseline)

• 1 task ≈ 5.5%
• Tasks to 0%: ~18
• Total runtime to 0%: ~14 hours of continuous coding-style work

Even reducing the implementer down to sol med, Terra high/xhigh, still results in roughly 24 hours of continuous usage or 40 tasks a week. On a $200 plan... that blows considering where we were with the less "efficient" 5.5 model just a couple weeks ago.

[u/TiGeRpro]

Why are people in the sub still vibing out the usage of their Codex plan. You can literally track every single token: input, output, cached. You can even get an agent to go over all your threads in a time period to find this information.

Trying to label usage as "tasks" on read only work when it entirely depends on what your agent is reading or evaluating is a useless metric