Usage 0.22.14: History reads are faster, stabler, and tell you honestly

Release notes

FEATURE

History reads are faster, stabler, and tell you honestly when they break

You'll notice that reading your history is now faster, more stable, and more honest when things break. The engine that crunches your history in the background has been completely overhauled. It now scans your directories just once to both calculate the numbers and spot any changes, rather than making multiple redundant trips; also, if you archive your Codex chats, the system now tracks those edits instantly instead of showing stale data. Additionally, if the system fails to read your chat logs, it used to quietly fall back to the last known data, making you think you simply hadn't typed anything; now, it hangs a small warning badge on the card, honestly confessing that it can't read the data. And if the background updater program (the hook) breaks, it will no longer frantically rescan your entire folder tree over and over. It's like a broken stadium scoreboard that used to freeze at zero and make you think no one was scoring, but now it hangs a "Broken" sign — and the repair crew no longer rips up the entire field trying to find the problem.

Original changelog

Original changelogHistory reads are faster, stabler, and tell you honestly when they break

**Archived Codex sessions could show stale data**: usage counted `~/.codex/archived_sessions/` when computing totals but didn't watch it for changes, so edits there might not refresh the menu bar until an unrelated refresh happened; the archived folder is now included in the same change-detection that drives live updates.
**A broken usage-data hook no longer causes constant background rescanning**: when Claude Code's status hook goes stale, usage now caches the "is there recent activity" check briefly instead of rescanning your entire `~/.claude/projects` tree on every poll.
**A small warning badge appears if local usage history can't be read**: previously, a failed read silently fell back to the last known data with no visible sign anything was wrong; the Project Usage card now shows a brief note (hover for detail) so you can tell "no new data" apart from "something broke."
**Faster per-refresh history scans**: each refresh previously walked the Claude/Codex session directories multiple times (once to detect changes, again per data source); it's now scanned once and reused.