Skip to content

5-hour usage limit consumed unusually fast in Codex CLI #46645

Open

Description

@Marax-github

What version of Codex CLI is running?

codex-cli 0.155.1

What subscription do you have?

ChatGPT Plus

Which model were you using?

GPT-6 Astra (Low), then GPT-5.6 Sol (High)

What platform is your computer?

Linux 7.0.0-31-generic x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

No response

Codex doctor report

What issue are you seeing?

Codex CLI is consuming my 5-hour usage allowance much faster than before. Today, a single request using GPT-6 Astra with Low reasoning consumed almost 50% of my 5-hour limit. I then switched to GPT-5.6 Sol with High reasoning, but after only two additional requests the remaining 5-hour allowance was exhausted. The entire limit was consumed within approximately 10 minutes. Previously, similar coding workflows, including running scripts and collecting data, allowed me to work for around 2 hours or longer before reaching the limit. This appears to be a significant recent regression in usage consumption.

What steps can reproduce the bug?

Uploaded thread: 019d1c26-a115-79f2-8508-58fde2d42a79

What is the expected behavior?

Usage should be comparable to previous Codex CLI behavior. Similar development sessions previously allowed approximately 2–3 hours or more of work before exhausting the 5-hour allowance. A single normal task should not consume almost half of the entire allowance unless there is an exceptional reason.

Additional information

No response

Activity

  1. added
    CLIIssues related to the Codex CLI
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Sep 19, 2026
  2. github-actions commented on Sep 19, 2026

    @github-actions
    Contributor
  3. jdg511 commented on Oct 6, 2026

    @jdg511

    This sounds similar to my issue: no-active-thread-01a110cf-8630-7742-b060-3818eb3e2f72

    I'll be away from chatgpt desktop all day, but then login to see my 5hrs is up, and that I'll get new usage at, (for example: 4am, when it is currently 5am)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIbugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions