openai / openai/codex

Astra XHigh from 60%+ to 12% to remaining tokens in less than 5 minutes.

Open
#44,205 30 comments 24 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

0.153.4

What subscription do you have?

Pro 200

What platform is your computer?

Linux

What issue are you seeing?
main now contains all three committed fixes. The remaining 11 modified and 4 untracked files.
I preserved these changes. They are uncommitted and unvalidated, and were excluded from the rebuilt executable.

A few seconds before I had run /status twice on a difference instance and got 60%.

› can you validate them?

• I’ll validate the uncommitted code and prompt changes, then review the project-network proposal for consistency. I’ll leave the changes uncommitted.

• Explored ....

Read a few files, write a few tail statements.

Noticed this:
⚠ Heads up, you have less than 25% of your weekly limit left. Run /status for a breakdown.

Checked and got:

Image
What steps can reproduce the bug?

Feedback ticket: 01a08611-2b24-7741-b139-fb9e2e39c56a

What is the expected behavior?

Not consume 50% of the 200 USD account in a few turns of doing nothing.

Additional information

Feedback ticket: 01a08611-2b24-7741-b139-fb9e2e39c56a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with feedback ticket 01a08611-2b24-7741-b139-fb9e2e39c56a and reproduce the report on Codex App 0.153.4 under Linux, using /status before and after similar validation activity. Compare the reported account usage with the actual work performed; done means the unexpected rapid token reduction is explained and no longer occurs under the reproduced scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.