Credit usage feels much higher than before and harder to sustain for real development work
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 静か
- 技術スタック
- rust
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Rust
- スター
- 125k
- フォーク
- 19.5k
- 平均マージ
- 1分
- マージ済み PR（30日）
- 1k
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
openai/codex のほかの issue
-
enhancement remote
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
bug CLI windows-os
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 オープンbug CLI sandbox
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
bug CLI TUI
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
-
CLI config enhancement skills
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
似ている issue
-
risk:low runtime status:in-progress type:test
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
zeroclaw-labs/zeroclaw#11023 ·
-
good first issue refactor
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
EricSpencer00/Resilient#4835 · コメント 1 件 ·
-
agent:ready documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
cesarferreira/stax#890 ·
-
bug
難易度 1/5 1時間未満 初心者へのやさしさ 90/100