1.9.0 - Limit Hero banner, activity calendar improvements, cross-platform clarity

Dashboard: Limit Hero banner

The empirical session, daily-pacing, and weekly limit estimates now get a prominent banner at the very top of the dashboard, above the KPI cards -- instead of one being buried in a single KPI card and the other in a data table further down. Three panels: your current 5h session against its estimated limit, today's usage against a fair daily share of your estimated weekly limit, and this billing week's usage so far against its estimated limit. Each panel is honest when there isn't enough data yet instead of guessing.

Sidebar: Limit Pulse (NextGen)

The same Today-vs-fair-daily-share and this-week-vs-estimated-weekly-limit numbers now sit at the very top of the sidebar's Today page too -- visible the moment you open the sidebar, no dashboard needed. Same underlying calculation as the Dashboard's Limit Hero, so the two can never show different numbers.

Activity calendar: easier to use

The tooltip and click target now live on the whole day cell, not just the small colored dot -- much easier to hit with the mouse. Click any day to add a short personal note about that day's usage (e.g. "big refactor, expected spike"). Notes are purely local, stored in plugin settings, and shown as a small marker on the day plus in its tooltip.

Cross-platform clarity

Token Usage already worked fully on macOS and Linux: the core session reading has always been platform-neutral (~/.claude/projects/ via Node's os.homedir()), no code change was needed there.

Agent Mode discovery correctly scoped to Windows

The Claude Desktop Agent Mode session finder added in v1.8.0 turned out to be a Windows-only necessity: only the Windows app runs its embedded Claude Code inside an MSIX sandbox that virtualises the filesystem, which is why Agent Mode sessions physically land somewhere other than the ordinary ~/.claude/projects/ there. macOS and Linux have no equivalent sandboxing layer, and per available documentation, Claude Code -- CLI, editor integrations, and the desktop app alike -- writes to the same ~/.claude/projects/ on every platform. So on macOS/Linux, Agent Mode sessions (where the feature exists) are expected to already land in the same standard location the plugin already reads -- no extra path guessing needed.

A briefly-added, unverified Windows-Store-style path guess for macOS was removed and replaced with a documented, evidence-based platform boundary in the code.

Documentation

The full documentation page now has an explicit platform breakdown under Data Sources & Transparency, plus a Getting Started note and an FAQ entry, so macOS and Linux users can see exactly what's platform-neutral and what (if anything) is Windows-specific.

If you use Claude Desktop's Agent Mode on macOS or Linux and notice usage that doesn't show up in the plugin, please open a GitHub issue -- the platform assumption above is based on available documentation, not a confirmed test on real hardware.

---

Full documentation, glossary, and manual: https://www.langeatn.de/media/token-usage/