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

Aberta
#28,362 1 comentário 5 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Pouca atividade
Stack de tecnologia
rust
Domínio
cli, developer-experience

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
125k
Forks
19.5k
Merge médio
1min
PRs com merge (30d)
1k

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de openai/codex

Todas as issues de openai/codex

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.