Usage 0.20.0: Status line nudges when context is too heavy and teaches you

Release notes

FEATURE

Status line nudges when context is too heavy and teaches you how to clear it

When a Claude Code conversation packs its context window (context — the range of previous messages the AI remembers) past the 80% red zone, the status line now appends a one-line reminder. Past this point, every turn resends a heavy log, making each turn more expensive and causing your quota to burn faster; typing /clear lets you drop the baggage and reset. The nudge also shows the context percentage and your session cost. It's like having a system tap you on the shoulder when your backpack is nearly full, suggesting you empty out what you don't need before hiking further.

BUGFIX

Long Codex sessions no longer show stale 5-hour quotas

Previously, if a Codex session (session — one continuous stretch of a conversation) went on for too long, the system fetching the 5-hour quota could overlook the file that was actually modified most recently, causing the menu bar to show stale numbers. Now, the system sorts all visible files by their last modified time, ensuring the menu bar always reflects the latest snapshot. It's like checking a planner: you used to sort entries only by when they were created and missed ones updated later, but now you sort straight by last updated, ensuring you always see the freshest progress.

Original changelog

Original changelogStatus line nudges when context is too heavy and teaches you how to clear it

**Status line nudges `/clear` when the context window goes heavy (≥80%)**: once a Claude Code conversation fills its context window past the red zone, the status line appends a one-line reminder. Past that point every turn resends a heavy context — pricier turns and a faster rate-limit burn, both of which `/clear` resets. The nudge shows the context % and, when available, the session cost, in all five languages.

Original changelogLong Codex sessions no longer show stale 5-hour quotas

**Codex 5h quota no longer goes stale on long-lived sessions**: the rate-limit reader scanned Codex session files newest-date-directory first and stopped at a scan limit, which could skip the file that was *actually* modified most recently when a long session keeps appending to an older creation-date directory. It now sorts all visible session files by modification time, so the menu bar always reflects the newest snapshot. (#37, by @ericweichun)