codexquota
Menu
This sessionChanges only this browser's quota compartment, never your official account.Loading local profiles…

New local profile

This changes only the quota compartment in this tab. It never switches your official account. Nothing is saved until you choose Save.

Leave this profile?

Unsaved input, readings and plans in this tab will be cleared. Saved history stays on this device.

On this page only. Nothing is saved yet.No quota read yet

What these results mean

Readings, budgets and public announcements answer different questions.

Reading your quota

The parser looks for explicit quota-window labels and used or remaining percentages. Missing windows are not filled in. Used and remaining values must agree within their stated precision. Unsupported fields, incomplete times and contradictions require confirmation.

Your confirmation is not an authenticated online account read. Unless you explicitly provide the observation time, it remains unknown. Importing or reopening a reading does not make it current.

Allocating work

Algorithm budget.v1. An allocation is not a prediction.

Each selected window is calculated separately: budget = remaining percentage points − your reserve, never below zero. Work time before the cutoff determines each session's share. Every allocation rounds down to 0.1 percentage point and exposes the unallocated remainder. Windows are never combined into one number.

Known reset times bound the plan. An unknown reset requires a planning cutoff you choose; that cutoff is not presented as a reset. No future allowance is borrowed. This calculation does not predict task duration, token use, hours until a limit or the chance of finishing a task, and it reports no ranges or confidence levels.

Synthetic example: recompute an allocation

Synthetic numbers, not a real account.

  1. A window reports 31% remaining. You keep a reserve of 7 percentage points.
  2. Budget: 31 − 7 = 24 percentage points.
  3. You plan 3 work sessions of 50 minutes each before the reset, so each gets an equal share.
  4. Each session: 24 ÷ 3 = 8.0 percentage points; unallocated remainder 0.0.

A second window, such as a weekly limit, gets its own budget the same way; the smaller one is not applied to the other.

Where each fact comes from

Evidence types and what they can establish
EvidenceWhat it can establishWhat it cannotStatus
Official rulesHow limits, credits and resets work in general, with a check date (usage limits)Your own balance or eligibilityReviewed; oldest source read 2026-09-26
User-imported official outputThe windows and percentages you pasted from /status, at the time you confirmAn online, authenticated account readAvailable
Local official readA reading taken by the local companion through the official clientAnything on another device or accountUnverified: not yet tested with a real account
Public contextConfirmed public reset announcements and source healthThat your account changedAvailable

Public facts come from the codex-reset.com read-only publication. Confirmed announcements, verified historical archive entries and unconfirmed clues have different labels. An archive record is not a new broadcast. A public event or clue never writes or changes a private reading.

A countdown reaching zero means it is time to check. It does not prove that a reset took effect. A change notification only prompts a complete new reading, and a change in one window cannot establish access across every limit. Percentages from different windows are never added together.

If a source stops answering, the page keeps its last check date and points to the official usage dashboard instead of guessing.

Public source contract · Official account-reading interface · Official usage dashboard · Rule sources and check dates