Building ai_resets: tracking AI usage limit resets across Claude, Codex and Gemini

I am Jeremy Koski, an independent Computer and Information Research Scientist in Honolulu. I develop with several AI coding tools in parallel, including six Codex accounts, Claude Code, Antigravity, and Cursor. I built ai_resets, a Python project backed by the PostgreSQL database ai, to track resets, plan changes, credits, promotions, and student offers. The most useful design decision was keeping three things separate: a provider's published rule, an account's observed state, and a prediction derived from those inputs. A reset is not one universal event. Rolling windows, fixed daily boundaries, billing cycles, weekly pools, and manual claims require different calculations and different evidence. The engine accepts an explicit now value so boundary behavior is reproducible. Time is stored with its context, including timezone aware timestamps. Claims are verified against evidence for the specific stored assertion. Account state is collected without crossing user boundaries. Uncertainty belongs in the interface beside the clock.

Authors

Publication Details

Journal
Figshare
Published
2026-11-12
DOI
https://doi.org/10.6084/m9.figshare.34993615
Primary Topic
Software Engineering Research
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
preprint

Building ai_resets: tracking AI usage limit resets across Claude, Codex and Gemini

Jeremy Koski
Figshare
Software Engineering Research
preprint

Building ai_resets: tracking AI usage limit resets across Claude, Codex and Gemini

Jeremy Koski
preprint en

Abstract

I am Jeremy Koski, an independent Computer and Information Research Scientist in Honolulu. I develop with several AI coding tools in parallel, including six Codex accounts, Claude Code, Antigravity, and Cursor. I built ai_resets, a Python project backed by the PostgreSQL database ai, to track resets, plan changes, credits, promotions, and student offers. The most useful design decision was keeping three things separate: a provider's published rule, an account's observed state, and a prediction derived from those inputs. A reset is not one universal event. Rolling windows, fixed daily boundaries, billing cycles, weekly pools, and manual claims require different calculations and different evidence. The engine accepts an explicit now value so boundary behavior is reproducible. Time is stored with its context, including timezone aware timestamps. Claims are verified against evidence for the specific stored assertion. Account state is collected without crossing user boundaries. Uncertainty belongs in the interface beside the clock.

Figshare
Software Engineering Research
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon