Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.271 ·

New /limit-reset command and 'Cedar Ember' rate-limit reset option

Max/Pro users can now claim an early rate-limit reset via /limit-reset or a 'cedar-ember' option offered in the usage-limit menu

TierUse it nowhow much it should matter to you
Useful5my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaRate Limitswhat it touches
KindNew Featuresin v2.1.271,
Group of 5 Use it now Notable No documentation found

Max/Pro users can now claim an early rate-limit reset via /limit-reset or a 'cedar-ember' option offered in the usage-limit menu

What

  • A new hidden slash command, /limit-reset, lets a Max/Pro user immediately consume an available session-limit reset, with a confirmation dialog and messaging for success, already-used, and unconfirmed cases.
  • Internally this is the "cedar_ember" feature: it fetches eligibility and status from a cedar_ember status block, offers a reset when a hard rate limit or an early/anytime limit is hit, and calls a reset_rate_limits server endpoint with program cedar_ember. It tracks separate grants for five_hour, seven_day, seven_day_opus, and seven_day_sonnet limits.
  • The rate-limit options menu shown when hitting usage limits gained a second offer type, "cedar-ember", alongside the existing "juniper-tide" offer, described as "Use your reset now ({left} left, until {date})".
  • New notification/interrupt kinds cedar-ember and cedar-ember-spent were added to notification-priority and interrupt-suppression handling, and the usage-fetch function gained a third read mode, cedar_ember, hitting /api/oauth/usage?cedar_ember=1&skip_spend=1, feeding two new notice-bar kinds, cedar-ember-offer and cedar-ember-spent.

Why This gives eligible users a self-service way to claim an early reset of their usage limits instead of waiting out the full window, offered both as a direct command and right when a limit is actually hit.

Read from
Names in the bundle/limit-reset

See this entry in the whole of v2.1.271 →