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

Abierto
#28,362 1 comentario 5 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
rust
Área
cli, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
125k
Forks
19.5k
Merge medio
1 min
PR fusionados (30 d)
1k

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openai/codex

Todos los issues de openai/codex

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.