Skip to content
HEY Research Lab
Menu

Claude Resets

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

Independent tracker for publicly announced Claude usage-limit resets

What HEY knows

Development

Last shipped 11 days agoActive: 3 counted ships in 30 days; latest ship 11 days ago. Evidence Source

Build Momentum 34How it is measured

Latest: Code changes, week of 2026-10-19 – 2026-10-25 · 3 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Claude Resets on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Claude Resets

No account? Email me Claude Resets’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
More detail
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 3 counted ships in the last 30 days, the newest 2026-10-22.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 3 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 9 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 6 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 28m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 41d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 9d ago.

Code and packages

  • Repository detailsMeasuredRead 5d ago.
  • Published packagesMeasuredRead 5d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-19 – 2026-10-25 · 3 commits

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

1 active day in silnt-awaken/claude-resets.

This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:270d11bb… · HEY counts it as building; it does not judge the release’s quality.

View evidence ↗ (opens in a new tab)

Shared change · Official source change

Claude Resets' official site changed.

Official sitemap changed: 2 sections added, 0 removed. Added section….

Observed by HEY on 2026-10-24Source: Project’s official site

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Claude Duet: one full limit reset when you are admitted

    AnnouncementSource-backed

    Pro and Max subscribers with a US Claude account who are admitted to the Claude Duet research preview get one full limit reset, covering both the five-hour session and weekly limits. Use it by November 30, 2026 from Settings → Usage on the web or desktop ("Reset for free").… Show all

    Pro and Max subscribers with a US Claude account who are admitted to the Claude Duet research preview get one full limit reset, covering both the five-hour session and weekly limits. Use it by November 30, 2026 from Settings → Usage on the web or desktop ("Reset for free"). Admission is by waitlist in waves; Duet itself draws on the same plan limits as chat, including background work. Subscriber-redeemed reset credit. Stated expiry: 2026-11-30. Check Claude for account availability and the exact deadline. Not counted as an already-applied reset. Audience: Pro and Max subscribers with a US…

    View evidence: Claude Duet: one full limit reset when you are admitted (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 9 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in silnt-awaken/claude-resets.

    How HEY read this week

    This week HEY looked inside 1 of 9 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 9 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 6 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in silnt-awaken/claude-resets.

    How HEY read this week

    This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 6 commits (opens in a new tab)

  4. Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in silnt-awaken/claude-resets.

    How HEY read this week

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits (opens in a new tab)

  5. Opus 5.5: a reset you can save for later

    Feature releaseSource-backed

    Get extra wiggle room to explore Opus 5.5. Anthropic says subscribers can save this reset and use it when they choose. Find the Resets card in Claude under Settings → Usage. Subscriber-redeemed reset credit. Stated expiry: 2026-10-22. Check Claude for account availability and… Show all

    Get extra wiggle room to explore Opus 5.5. Anthropic says subscribers can save this reset and use it when they choose. Find the Resets card in Claude under Settings → Usage. Subscriber-redeemed reset credit. Stated expiry: 2026-10-22. Check Claude for account availability and the exact deadline. Not counted as an already-applied reset. Announced on 2026-09-22 (exact time not established). Audience: subscription users. Windows: unspecified. Source: @AnthropicAI https://www.anthropic.com/claude-opus-5-5

    View evidence: Opus 5.5: a reset you can save for later (opens in a new tab)

  6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 39 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in silnt-awaken/claude-resets.

    How HEY read this week

    This week HEY looked inside 3 of 39 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 39 commits (opens in a new tab)

  7. Weekly limits reset for Max plans

    Feature releaseSource-backed

    Lydia Hallie announced that weekly limits had just been reset for everyone on a Claude Max plan, citing the Fable 5.1 release and a long weekend ahead. The post does not mention 5-hour limits or other plans. Audience: everyone on a Claude Max plan. Windows: weekly. Source… Show all

    Lydia Hallie announced that weekly limits had just been reset for everyone on a Claude Max plan, citing the Fable 5.1 release and a long weekend ahead. The post does not mention 5-hour limits or other plans. Audience: everyone on a Claude Max plan. Windows: weekly. Source: @lydiahallie https://x.com/lydiahallie/status/2095967323412930677

    View evidence: Weekly limits reset for Max plans (opens in a new tab)

  8. 5-hour and weekly limits reset for all users

    Feature releaseSource-backed

    ClaudeDevs announced that, alongside the Fable 5.1 release, 5-hour and weekly limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced that, alongside the Fable 5.1 release, 5-hour and weekly limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2094856679250919746

    View evidence: 5-hour and weekly limits reset for all users (opens in a new tab)
Earlier ships (10)

  1. 5-hour and weekly limits reset for all users

    AnnouncementSource-backed

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. The post was published at 03:58 UTC on July 16, which was the evening of July 15 in US time zones. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. The post was published at 03:58 UTC on July 16, which was the evening of July 15 in US time zones. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2077603834453770467

    View evidence: 5-hour and weekly limits reset for all users (opens in a new tab)

  2. 5-hour and weekly limits reset for all users

    AnnouncementSource-backed

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2075279141352706215

    View evidence: 5-hour and weekly limits reset for all users (opens in a new tab)

  3. Limits reset for everyone as Fable 5 returns

    AnnouncementSource-backed

    ClaudeDevs announced that everyone's 5-hour and weekly rate limits were reset, tied to Fable 5 being ready to build with again. Audience: everyone. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced that everyone's 5-hour and weekly rate limits were reset, tied to Fable 5 being ready to build with again. Audience: everyone. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2072429181565288665

    View evidence: Limits reset for everyone as Fable 5 returns (opens in a new tab)

  4. Limits reset for everyone across all plans

    AnnouncementSource-backed

    In a follow-up to the June 19 targeted reset, ClaudeDevs announced that 5-hour and weekly usage limits were reset for everyone, across all plans. Audience: everyone, across all plans. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    In a follow-up to the June 19 targeted reset, ClaudeDevs announced that 5-hour and weekly usage limits were reset for everyone, across all plans. Audience: everyone, across all plans. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2068122937308426676

    View evidence: Limits reset for everyone across all plans (opens in a new tab)

  5. Limits reset for users affected by a usage-display bug

    AnnouncementSource-backed

    ClaudeDevs reported that about 3% of Claude Code Max and Pro users hit a bug showing an incorrect weekly usage limit, and said 5-hour and weekly limits were being reset for everyone affected. This reset was limited to affected users. Audience: everyone affected (about 3% of… Show all

    ClaudeDevs reported that about 3% of Claude Code Max and Pro users hit a bug showing an incorrect weekly usage limit, and said 5-hour and weekly limits were being reset for everyone affected. This reset was limited to affected users. Audience: everyone affected (about 3% of Claude Code Max and Pro users). Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2067802163498352929

    View evidence: Limits reset for users affected by a usage-display bug (opens in a new tab)

  6. 5-hour and weekly limits reset for all users

    AnnouncementSource-backed

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2065621176735646006

    View evidence: 5-hour and weekly limits reset for all users (opens in a new tab)

  7. 5-hour and weekly limits reset for all users at the Fable 5 launch

    Feature releaseSource-backed

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users to mark the Fable 5 release. Alex Albert relayed the same reset shortly after, describing it as applying across Anthropic's products. Audience: all users. Windows: five_hour, weekly. Source… Show all

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users to mark the Fable 5 release. Alex Albert relayed the same reset shortly after, describing it as applying across Anthropic's products. Audience: all users. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2064464557951852643

    View evidence: 5-hour and weekly limits reset for all users at the Fable 5 launch (opens in a new tab)

  8. Limits reset for Pro and Max users after a subagent bug

    AnnouncementSource-backed

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users on Pro and Max plans, after fixing an issue that made some Claude Code sessions spawn excessive parallel subagents. Audience: all users on Pro and Max plans. Windows: five_hour, weekly. Source… Show all

    ClaudeDevs announced that 5-hour and weekly rate limits were reset for all users on Pro and Max plans, after fixing an issue that made some Claude Code sessions spawn excessive parallel subagents. Audience: all users on Pro and Max plans. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2061501787769893055

    View evidence: Limits reset for Pro and Max users after a subagent bug (opens in a new tab)

  9. Everyone's 5-hour and weekly limits reset

    AnnouncementSource-backed

    ClaudeDevs announced on a Friday that everyone's 5-hour and weekly rate limits had been reset. Audience: everyone. Windows: five_hour, weekly. Source: @ClaudeDevs Show all

    ClaudeDevs announced on a Friday that everyone's 5-hour and weekly rate limits had been reset. Audience: everyone. Windows: five_hour, weekly. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2055347539923308703

    View evidence: Everyone's 5-hour and weekly limits reset (opens in a new tab)

  10. Usage limits reset for all subscribers after the Claude Code post-mortem

    AnnouncementSource-backed

    After publishing a post-mortem on three Claude Code quality issues, ClaudeDevs announced that usage limits were reset for all subscribers. The post does not say which limit windows were reset. Boris Cherny linked to the post-mortem the same day. Audience: all subscribers.… Show all

    After publishing a post-mortem on three Claude Code quality issues, ClaudeDevs announced that usage limits were reset for all subscribers. The post does not say which limit windows were reset. Boris Cherny linked to the post-mortem the same day. Audience: all subscribers. Windows: unspecified. Source: @ClaudeDevs https://x.com/ClaudeDevs/status/2047371123185287223

    View evidence: Usage limits reset for all subscribers after the Claude Code post-mortem (opens in a new tab)

Other changes on HEY’s record

22 changes on HEY’s record for Claude Resets: 4 releases · 1 new Verified Builder or owner proof · 1 official source change · 10 other ships · 6 other changes in 2 more kinds.

All 22 changes for Claude Resets →

The full change record holds 4 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Questions HEY can answer about Claude Resets — as of 2 Nov

Show the answers
Is Claude Resets still being built?
DerivedActive: 3 counted ships in 30 days; latest ship 11 days ago. Evidence
What did Claude Resets ship last?
FactCode changes, week of 2026-10-19 – 2026-10-25 · 3 commits — Code activity, 11 days ago. Evidence
What does HEY not know about Claude Resets?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

Sources

3 places HEY reads for Claude Resets