[eric-engberg]

What

Session Usage is now Block Usage:

• Label: 5h: 42.0%, was Session: 42.0%. It pairs with Weekly Usage's Weekly: 18.0%.
• Picker: listed as Block Usage, described as "Shows the current 5-hour block's usage percentage" (was "Shows daily/session API usage percentage").
• Type: stays session-usage, so saved configs keep working unchanged.

Anyone who prefers the old label can set it back with the label editor (e in the line editor), since label overrides are kept per widget.

Why

The label Session: meant two different things on the same line:

• Session Usage: the 5-hour usage window.
• Session Clock and Session Name: the Claude Code conversation.

So Session: 42.0% | Session: 1hr 5m reads as two facts about one session when they're about different things.

The 5-hour window already has a name here: Block Timer ("Shows current 5hr block elapsed time or progress") and Block Reset Timer ("…until current 5hr block reset window") call it the block. So the widget is named Block Usage, and the three 5-hour widgets now share a name in the picker. Session Clock, Session Cost and Session Name keep "session", which is the conversation.

Its label is 5h: rather than Block: , because Block Timer already prints Block: 3hr 45m for the block's elapsed time. A second Block: beside it would label two different numbers the same way. 5h: says which window the percent is of, as Weekly: does.

How

• usage-percent-widget.ts: the session kind's display name, label (5h: ) and description change. Internal names (sessionUsage, the session kind) stay, since they follow the usage data's field names.
• docs/USAGE.md: the widget's current descriptions and keys say Block Usage. The README's past release notes keep the name the widget shipped with.
• Not changed:
  • Session Clock, Session Cost and Session Name;
  • every other widget's label;
  • how a label override is stored.

A note for review: #183 proposes a separate block-usage widget (the cost of the current block). This rename keeps the session-usage type, so the two could never collide in a config. Only their display names would overlap if both landed.

Demo

Piped renders with the 5-hour window at 42% and a 1 hr 5 min conversation (made-up payload): Model, Block Usage, then Session Clock.

Powerline

Before (main)	After

Plain

Before (main)	After

In Add Widget, a search for "block" lists Block Usage next to Block Timer and Block Reset Timer, with its new description:

Powerline

Plain

Testing

• SessionUsage.test.ts:
  • The shared usage suite and the time-cursor tests now expect 5h: .
  • A new test checks the display name, the default 5h: 20.0%, and that a Session: label override still renders Session: 20.0%.
  • The existing label-override test is unchanged apart from the default label.
• bun test: 3113 pass, 0 fail. bun run lint passes. Under Node (Vitest), SessionUsage.test.ts passes 18 of 18.
• Built CLI (runtime-check.sh, Bun 1.4.2 and Node 26.10.0):
  • with the baseline plain and Powerline configs, which have no Session Usage, identical to main;
  • with the demo's configs and payload, both runtimes agree and differ from main only in the label;
  • the TUI opens and exits under both.