Skip to content

Agent in goal modus automatically using banked reset #41502

Open
Open
Agent in goal modus automatically using banked reset#41502
Labels
appIssues related to the Codex desktop appbugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reportingwindows-osIssues related to Codex on Windows systems

Description

@SvenPepermans
SvenPepermans
opened on Aug 29, 2026

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

26.825.32147

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I had 2 agents running (on the same repo) when going to bed (5.6 Sol Medium). Both were merely "orchestrators" for creating and distributing tasks to 5.6 Luna Max subagents.
Agent 1:
Was instructed to review a PR.
Agent 2:
Running in /goal. Was instructed to implement and create PR's for predefined set of github issues.

Both were instructed to finish their work without human intervention.

Usage seems to be reset by an Agent as Agent 2 reported the usage was reset (both 5h and weekly usage) at 7:16am. At this point I had still not "checked" in on its progress.

First interaction with codex was at 8:52am with Agent 1.

Image Image

What steps can reproduce the bug?

Instruct an agent with a long-running task in /goal to work autonomously without any human interaction.

Once usage limit is hit, when a banked reset is available it will get used.

In attachment, a sanitized version of Agent 2's session .jsonl file.

Session id: 01a04a18-daef-7a40-8f31-051a1d0b5c3c (local)

rollout-2026-08-29T08-52-22-01a04c4a-73d6-7c41-a1db-3831537aa704-sanitized.json

What is the expected behavior?

Codex does not automatically use banked resets.

Additional information

No response

Activity

  1. SvenPepermans
    added
    appIssues related to the Codex desktop app
    on Aug 29, 2026
  2. github-actions
    added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Aug 29, 2026

  3. github-actions commented on Aug 29, 2026

    @github-actions
    github-actionsBot
    on Aug 29, 2026 – with GitHub Actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  4. scottfalconer commented on Sep 4, 2026

    @scottfalconer
    scottfalconer
    on Sep 4, 2026 – with ChatGPT Codex Connector

    Additional confirmed reproduction: ambiguous phrase consumed a reset while usage was already full

    I encountered the same underlying authorization failure on 2026-09-04 in the ChatGPT desktop/Codex app on macOS.

    Verified sequence

    1. A reset had already been used and Codex usage was fully available: 0% used / 100% remaining.
    2. At 2026-09-04 10:28:35.853 AM MDT, I sent exactly: “usage reset”.
    3. This was not an explicit instruction to consume another banked reset credit.
    4. At 10:28:46.235 AM MDT (16:28:46.235Z), the assistant nevertheless invoked the usage-reset consumption operation without an action-time confirmation or product-level approval.
    5. At 10:28:49.746 AM MDT, the operation returned outcome: reset; the remaining banked-reset count became 0.
    6. The assistant subsequently acknowledged that it had misread the message and consumed the reset incorrectly.

    This case strengthens the original report because the reset was consumed when the usage allowance was already fully available, so the scarce credit provided no practical benefit.

    Requested safeguards

    • Require explicit, immediate confirmation that specifically states a banked reset credit will be irreversibly consumed.
    • Do not treat an ambiguous noun phrase such as “usage reset” as authorization.
    • Reject or safely no-op redemption when the affected allowance is already fully available.
    • Provide a supported remediation path for confirmed erroneous redemptions.

    The exact Codex task ID and idempotency key have been supplied privately to OpenAI Support and are intentionally omitted here.

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

    appIssues related to the Codex desktop appbugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reportingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions