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

Ouverte
#28,362 1 commentaire 5 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Calme
Stack technique
rust
Domaine
cli, developer-experience

Piste de recherche

The report concerns Codex CLI 0.139.0 and credit consumption during audit, fix, and verification workflows; begin by reproducing and measuring comparable workflows against earlier versions. Done would require a concrete, agreed usage-control or predictability change, but this issue names no files, tests, or entry point.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

CLI enhancement rate-limits
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.

Langage dominant
Rust
Étoiles
125k
Forks
19.5k
Merge moyen
1 min
PR mergées (30 j)
1k

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de openai/codex

Toutes les issues de openai/codex

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.