prompt_cache.expires_at, shown as "cache warm 3m" to tell whether resuming an idle session is still cheap
pr.number and pr.review_state
Snapshot them in devdesk-statusline and show compact meters. Verify the field names against the current statusLine docs first.
_Source: comparable-tools research, 2026-10-07._
The statusLine JSON also carries:
- `rate_limits.five_hour` / `seven_day` (`used_percentage`, `resets_at`)
- `prompt_cache.expires_at`, shown as "cache warm 3m" to tell whether resuming an idle session is still cheap
- `pr.number` and `pr.review_state`
Snapshot them in `devdesk-statusline` and show compact meters. Verify the field names against the current statusLine docs first.
jared
added this to the backlog milestone 2026-10-07 20:04:32 -04:00
Shipped in v0.9.0: plan-usage meters (5-hour and weekly, from the statusLine rate_limits) in the footer and ⋯ menu, with a warning at 90 % of the 5-hour window, and a PR chip on session rows (from pr, with the review state).
The prompt-cache countdown was dropped: the statusLine payload has no cache-expiry field, and guessing it from timestamps would show a number that may be wrong.
Shipped in v0.9.0: plan-usage meters (5-hour and weekly, from the statusLine `rate_limits`) in the footer and ⋯ menu, with a warning at 90 % of the 5-hour window, and a PR chip on session rows (from `pr`, with the review state).
The prompt-cache countdown was dropped: the statusLine payload has no cache-expiry field, and guessing it from timestamps would show a number that may be wrong.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Source: comparable-tools research, 2026-10-07.
The statusLine JSON also carries:
rate_limits.five_hour/seven_day(used_percentage,resets_at)prompt_cache.expires_at, shown as "cache warm 3m" to tell whether resuming an idle session is still cheappr.numberandpr.review_stateSnapshot them in
devdesk-statuslineand show compact meters. Verify the field names against the current statusLine docs first.Shipped in v0.9.0: plan-usage meters (5-hour and weekly, from the statusLine
rate_limits) in the footer and ⋯ menu, with a warning at 90 % of the 5-hour window, and a PR chip on session rows (frompr, with the review state).The prompt-cache countdown was dropped: the statusLine payload has no cache-expiry field, and guessing it from timestamps would show a number that may be wrong.