Usage 0.28.17

Released: 2026-07-21

Release notes

BUGFIX

Long status warnings no longer crop the Claude card

When you open the Classic popover to check Claude, a long warning at the bottom will no longer hide the line you came for. Warnings such as a broken hook or a needed restart can wrap onto two lines. The popover's fixed height had not allowed for the extra roughly 30 pixels, so its footer squeezed the Claude card; because overflow was hidden, the weekly reset row got cropped. The panel now makes room for that second line. It is like packing one extra sweater into a suitcase: the old zipper caught the itinerary inside, while the new case expands and keeps the date visible.

FEATURE

Five-hour auto sessions no longer miss a quota reset

If you let Auto-start 5-hour Session keep a session alive, it will no longer miss a fresh quota window because its timing slowly drifts. The keeper used to measure its five-hour throttle from the previous ping's timestamp. That timestamp could fall out of step with the real quota reset boundary, occasionally skipping a ping altogether; the next window then started only after you spoke to Claude yourself. It now deduplicates pings against the actual reset boundary, not simply elapsed time, so drift cannot cause a miss. Think of a bus that used to schedule its next departure from the last passenger's exit time; it now follows the timetable at the stop.

Original changelog

Original changelogLong status warnings no longer crop the Claude card
**Classic popover no longer clips the Claude card when the footer status wraps to two lines.** Long status warnings (e.g. hook broken/restart) push the footer status pill onto a second line, adding roughly 30px the fixed popover height never accounted for; flex then squeezed the overflow-hidden Claude card and clipped its weekly reset row.
Original changelogFive-hour auto sessions no longer miss a quota reset
**Auto-start 5-hour Session could silently skip a reset boundary.** The keeper's fixed 5-hour self-throttle was measured from the last ping's own timestamp, which could drift out of sync with the real quota reset boundary and occasionally skip a ping entirely — leaving the next window to start only once you talked to Claude yourself. It now dedupes by the actual reset boundary instead of elapsed time, so drift can no longer cause a miss.