Skip to content

Credit usage feels much higher than before and harder to sustain for real development work #28362

@brolabitalia

Description

@brolabitalia

What variant of Codex are you using?

0.139.0

What feature would you like to see?

I use Codex CLI heavily on a real development project, not just for testing. I use it for debugging, audits, fixes, code review, patching, and verification.

In recent versions, credit consumption feels much higher than before. For similar tasks, credits seem to run out much faster than they did a few versions ago.

This makes Codex harder to use as a stable development tool, especially on larger projects where a normal workflow requires multiple cycles of analysis, patching, and verification.

I am not asking for free usage. I have already purchased and spent a significant amount of credits. The issue is that the current consumption feels too aggressive and difficult to manage during real work.

I would like Codex to provide better control and predictability over credit usage, so independent developers can keep using it seriously without burning through credits too quickly.

Additional information

Codex is extremely useful and I want to keep using it, but the current credit usage feels much less sustainable than before.

The main problem is not paying for the tool. The problem is that, during real development work, credits can disappear very quickly before a complete audit/fix/verification cycle is finished.

This feedback comes from actual day-to-day usage on a complex project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIenhancementNew feature or requestrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions