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

Offen
#28,362 1 Kommentar 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Ruhig
Tech-Stack
rust
Bereich
cli, developer-experience

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Rust
Sterne
125k
Forks
19.5k
Ø Merge
1 Min.
Gemergte PRs (30 T.)
1k

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus openai/codex

Alle Issues in openai/codex

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.