Changelog

What's actually shipped on this tracker, newest first. No planned/upcoming items — only things that are live.

Pro vs Max usage limits section, weekly-limit question heading, Claude Code reset FAQ, statusline page title 2026-10-15

  • /usage-limits/ gains a "Claude Pro vs Max plan: how the usage limits differ" section (Max 5x vs Pro, Max 20x vs Pro, session reset, weekly limit), sourced to Anthropic's Max plan article and pricing page. It lists no prices and links to Anthropic's pricing page for current ones; how Max's weekly limit compares with Pro's is shown as "Not published", as Anthropic hasn't said.
  • The "The weekly limit" section on /usage-limits/ is now headed "What is Claude's weekly limit?", and its FAQ gains "When does Claude Code usage reset?" (Claude Code and claude.ai share the same five-hour and weekly windows; /usage shows each window's reset time). All of this is in English, Japanese, Spanish and Chinese.
  • /usage-check/ is retitled "Claude Code Statusline & Usage Check: 5-Hour and Weekly Limits", and its status-line script section is headed "Claude Code statusline: show your 5-hour and weekly usage".

Scheduled reset announcements, shown in Pacific and Beijing time side by side 2026-10-02

  • resets.json can now optionally carry a products.claude.scheduled block for a reset Anthropic announced or a team member hinted at ahead of time. When present (status == "scheduled"), the home page shows a banner in all four languages, the Atom feed gains an entry, calendar.ics gains an event, and /api/v1/forecast.json gains an additive scheduled field — all a no-op today, since real Claude data has scheduled: null.
  • The displayed time is always 24-hour, in every language — no AM/PM or morning/afternoon marker anywhere. With an exact scheduled_for instant, both Pacific and Beijing local time are shown side by side (e.g. "Oct 2, 10:00 PDT (Pacific) / Oct 3, 01:00 Beijing time"); Pacific is derived from scheduled_for via America/Los_Angeles, never trusting the upstream tz_label or a tweet's own "10am PST" text, which can be wrong across a DST boundary.
  • Upstream note_zh (ad hoc Chinese commentary written for one specific post) is never rendered — same rule as every other piece of event data on this site. The sentence text is this site's own four-language wording instead, and differs for an announced vs. a hinted reset, and again once the announced time has passed without a confirmed delivery.
  • build.official_signal_components() now reads the real howtok schema's announced_at field (there is no ts field upstream) instead of a ts field that never existed in production data, falling back to ts only for backward compatibility.

Delivery lag: announced vs. delivered, on every reset row 2026-09-27

  • Upstream reset data can now optionally carry when a reset actually finished landing on accounts (delivered_at, with a delivered_source citation), separately from when Anthropic announced it (the existing ts/announced_at field, unchanged). When present, event rows on the home page, /timeline/, each per-day event page and /banked-reset/ show both an "Announced …" and a "Delivered …" time.
  • When a reset was announced within the last 24 hours and no delivered_at is recorded yet, rows show "Announced … — rolling out; it can take a while to reach every account" instead of implying it already reached every account — the home page's "Claude reset today" answer line uses the same rolling-out phrasing while it applies. This is re-checked client-side every minute, so the note disappears on its own once the 24-hour window passes, even between builds.
  • A delivery_note field (e.g. a reported delay with weaker evidence than a confirmed delivered_at) renders as a small labeled note under the event when present.
  • /api/v1/timeline.json and /api/v1/banked.json events gained delivered_at, delivered_source and delivery_note fields (null when unknown); the Atom feed adds a "Delivered: …" line when known. All three fields are optional and additive — every event in the current data has none of them, so every page renders exactly as before this change.

Reset-probability numbers now come from whenreset.app, shared across the whole site group 2026-09-24

  • The 24h/48h/7-day reset-probability estimate, the typical gap, and the reference date shown on the home page, /timeline/, /worth-it/ and /forecast-method/ now come from whenreset.app's shared climatology forecast model, instead of this site's own forecast engine — agentresets.com, codexreset.ai and claudereset.org now all show the same numbers as whenreset.app, avoiding four sites giving four different answers to the same question.
  • This site's own forecast.py engine (rhythm term + official/status signals, backtested rhythm-model selection) is no longer shown as the site's forecast anywhere — it's kept as a labeled research archive on /forecast-method/ and at /api/v1/research/forecast.json, for anyone who wants to inspect or reuse it.
  • /api/v1/forecast.json now serves whenreset.app's numbers (with a source/source_url field) instead of this site's own p24/p48; the retired engine's identical pre-2026-09-24 output moved to the new /api/v1/research/forecast.json path. The MCP server's get_reset_forecast tool follows the same change, and a new get_research_forecast tool exposes the retired engine.
  • When whenreset.app's snapshot is missing or older than 6 hours, every page shows a localized "unavailable" message instead of falling back to this site's own calculation or an old number.
  • scripts/collect_signals.py now also fetches whenreset.app's two public endpoints into data/whenreset.json, and scripts/run-signals.sh's redeploy fingerprint tracks whenreset's own rounded numbers instead of this site's retired p24 bucket.

Simplified Chinese, Japanese and Spanish versions of the site 2026-09-23

  • Added /zh/, /ja/ and /es/ translated routes for the 10 main pages (home, timeline, forecast method, banked reset, worth it?, usage limits, usage check, status, developers, about) — full hreflang alternates, a language switcher, and localized JSON-LD. English stays at the root, unchanged.
  • Reset-event summaries are never translated or machine-translated — they always render in their original English, labeled as such, on every language's pages.
  • Fact pages (/usage-limits/, /banked-reset/) get per-language content files whose source citations are identical to the English version, in the same order — only the surrounding text is translated.
  • All reader-facing strings in worth.js, usage-check.js, alerts.js, forecast-live.js, status-live.js and app.js are now localized via a small JSON blob embedded in each page, with the English text kept as a fallback.
  • Titles, H1s and descriptions for the zh/ja/es pages are based on real Google Autocomplete results, not guesses — see docs/keyword-autocomplete-i18n-2026-09-23.json and docs/i18n-titles.md.

Rhythm-model auto-selection, in-tab alerts, usage-check workbench 2026-09-23

  • The forecast's rhythm term now auto-selects between a cooldown model and a memoryless (Poisson) model by backtest each build, instead of always assuming the cooldown model is right.
  • Added an opt-in, tab-only notification button on the home page and /status/ — no account, no push service, nothing sent anywhere.
  • Added /usage-check/: parse a Claude Code status line locally (nothing uploaded) to see 5-hour and weekly usage, plus a copyable status line script.
  • Switched the event freshness heartbeat to howtok's own successful-check timestamp (previously a log file's mtime), and added a live in-browser freshness check against howtok.net.
  • Added /changelog/ and /privacy/.

Banked vs. global reset distinction, freshness banner, seed attribution 2026-09-23

  • Separated banked credits from global resets throughout the site — gap math, the homepage's reset cards, the timeline, and the JSON API.
  • Added a stale-data banner and a heartbeat deploy so a stopped data pipeline is visible instead of silently going quiet.
  • Added attribution for rows bulk-imported from claude-resets.com's public archive.

Usage-limits and banked-reset pages 2026-09-23

  • Added /usage-limits/ and /banked-reset/, each fact sourced to an official Anthropic page with a link.
  • Fixed a same-day banked-reset display edge case and added the www → apex redirect.

Initial launch 2026-09-23

  • First release: the tracker, the open-formula forecast, the full reset timeline, a free JSON API, an MCP server, an Atom feed, and an iCalendar feed.