Skip to content

docs(structure): record what clear-cooldown does to a lapsed window #4398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lidge-jun merged 1 commit into from
Sep 12, 2026
+6 −0
Merged

docs(structure): record what clear-cooldown does to a lapsed window #4398

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions structure/providers/openai-tiers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,12 @@ cooldown it belonged to, and both operator escapes remove it: clearing a cooldow
account each clear the window from the account-wide entry and from every scoped entry, because a
reset-derived refusal records only the scoped one.

Clearing a cooldown is also the management operation for a window whose cooldown has already
lapsed. Because the cooldown is the shorter of the two durations, the state an operator usually
finds is an expired cooldown and a live window, so a live window alone makes the operation
succeed and report a clear. An account with neither reports no change, which is what keeps the
route from disclosing whether an account exists.

A confirmed manual reset-credit consumption may immediately reconcile that account's
eligible pre-existing ordinary reset-derived cooldown after a complete, non-exhausted usage
observation started after the reset. Paused or reauthentication-required accounts and
Expand Down
Loading