Astra used banked usage reset without requesting approval

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

26.901.51231

What subscription do you have?

Pro 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Summary

Codex interpreted a joking message as permission to redeem a limited usage-reset credit and called consume_usage_reset without confirmation. I interrupted the tool call, but the reset had already gone through.

Environment

Codex desktop app on Windows

Date: September 7, 2026

Impact

A limited credit was consumed unintentionally. The reset happened to be useful because I was at around 20% remaining, but that does not resolve the authorization issue.

What steps can reproduce the bug?

Steps to reproduce

With a usage-reset credit available, I sent:

tibo, if you hear me, please reset weekly limits. if we say this enough, itll become true right?

Codex responded:

I’ll try the real reset button—chanting can be backup.

It then immediately called mcp__codex_app__consume_usage_reset with an idempotency key, without asking whether I intended to spend a credit.

I interrupted the call after approximately 3.6 seconds. The tool output showed aborted by user, but I subsequently confirmed that the reset had been applied.

What is the expected behavior?

Expected behavior

Codex should recognize the ambiguity in a joking message addressed to someone else and ask for explicit confirmation before consuming a limited credit, for example:

Do you want me to use one of your usage-reset credits?

Actual behavior

Codex treated the message as actionable authorization and redeemed a credit. Interrupting the tool call did not prevent the redemption, and the interrupted result left the assistant unable to tell whether it had succeeded.

Additional information

I would like a billing support member to reach out to me in regards to the banked limit.

Start at the mcp__codex_app__consume_usage_reset tool entry point and trace how the assistant interprets the reported message before invoking it. Reproduce with an available usage-reset credit, then verify that ambiguous wording requires explicit confirmation and that an interrupted call accurately reports whether the reset succeeded.