nomnomtokens 0.2.0 → 0.3.0

package/README.md

@@ -10,7 +10,9 @@ projects, and when you'll hit your limit.
 npx nomnomtokens
 ```
 
-![nomnomtokens dashboard — Timeline with spend chart and activity heatmap](docs/dashboard.png)
+![nomnomtokens Overview — eaten today, cache hit rate, and limit projections](docs/overview.png)
+
+![nomnomtokens Timeline — spend stacked by model and activity heatmap](docs/timeline.png)
 
 Claude Code, Cursor (when its local IDE database has token fields), and Codex
 CLI/IDE session rollouts. The event contract is deliberately not AI-shaped, so
@@ -31,7 +33,7 @@ without touching the core.
 - **Limits** — window-fill history with a burn-rate projection and markers for
   the moments you actually hit the cap.
 
-Filter state lives in the URL, `⌘K` jumps anywhere, dark by default.
+Filter state lives in the URL, `⌘K` jumps anywhere, light or dark theme.
 
 ## Install
 
@@ -65,6 +67,10 @@ The hook doubles as a real status line:
 | `nnt init [--force]` | wire up the status line hook |
 | `nnt statusline` | ingest a session payload and print a status line |
 | `nnt doctor` | why is it empty? checks sources, hook, and store |
+| `nnt import <file.csv>` | import a billing CSV into the local store |
+| `nnt export` | dump filtered events as CSV/JSON |
+| `nnt prices [show\|refresh]` | local model price table (`~/.nomnomtokens/prices.json`) |
+| `nnt alerts [show\|check]` | limit % / daily $ thresholds (`~/.nomnomtokens/alerts.json`) |
 
 ## Privacy
 
@@ -135,19 +141,18 @@ the core, the contract is wrong and that's a bug worth reporting.
 
 ## Roadmap
 
-Shipped: Claude Code adapter, Cursor adapter (local `state.vscdb`), Codex
-adapter (`~/.codex/sessions/**/rollout-*.jsonl`), all six screens, limits with
-forecasting, live updates. CSV helpers exist in `packages/adapters` but are not
-wired into `scan` / the UI yet.
+Shipped: Claude Code / Cursor / Codex adapters, CSV import & export, Projects
+grouped by name, local `prices.json` refresh, limit/daily alerts, all dashboard
+screens, limits with forecasting, live updates.
 
 Cursor caveat: the IDE often stores zero token counts in local bubbles. We only
 emit events when numbers are present (exact `tokenCount`, or
 `tokensUsed` + delta). We do not estimate from message text. Sessions without
-local counts will not appear until Cursor writes them — or until a future
-optional CSV enrich from the Cursor dashboard.
+local counts will not appear until Cursor writes them — or until you import a
+billing CSV.
 
-Next: wire up CSV import, OTLP receiver, export, alerts. Then cloud mode — a
-second sink for the same events, never a rewrite, and never in the critical path.
+Next: OTLP receiver, then cloud mode — a second sink for the same events, never
+a rewrite, and never in the critical path.
 
 ## License