Repository navigation
v0.7.7
Fixed
- Codex usage sync now requires ccusage 20.0.33 or newer to read Zstandard-compressed
.jsonl.zstsession logs. Scheduled syncs detect changes to compressed logs in active
sessions, archives, and customCODEX_HOMElocations instead of treating them as unchanged.
Server
- The API now rejects implausible usage at ingest, for every CLI version. A row (device, day,
agent, model) may hold at most 1T tokens in any token field, and its cost may not exceed
$2,000 per million tokens plus $250, with a ceiling of $1M. The heaviest real row so far is 110.7B
tokens and $131k. Rows outside these limits are dropped one by one without failing the sync.
Each drop is logged with the user and device, and counted per device on the admin page. A cost
above the limit is never kept by the cost freeze. On 2026-10-05, fabricated uploads of up to
$2.7×10²⁹⁶ and 8.6×10¹⁵ tokens a day reached the leaderboard. - Usage totals on the leaderboard, stats, profiles and admin page no longer fail once a sum passes
the 64-bit integer range. That overflow is what made/internalreturn 500. - The site shows large amounts in compact form (1.2M dollars, 4.5B tokens), and anything at or
above a quadrillion shows as a capped>999T, so absurd values can no longer stretch the
leaderboard or profile layout.
Install:
npm install -g @851-labs/tokenmaxxing@0.7.7