llm-usage-metrics 0.10.0 → 0.10.2

package/README.md

@@ -5,7 +5,7 @@
 <h1 align="center">llm-usage-metrics</h1>
 
 <p align="center">
-  Local usage reports for AI coding tools.
+  Usage reports for AI coding tools, across all your machines.
 </p>
 
 <p align="center">
@@ -23,10 +23,12 @@
   <a href="./CONTRIBUTING.md">Contributing</a>
 </p>
 
-`llm-usage-metrics` reads local session data from 17 AI coding tools and converts it into one normalized usage history. Use it to review tokens and estimated cost, compare periods, find expensive sessions, correlate usage with local Git activity, or export the result.
+`llm-usage-metrics` reads local session data from 17 AI coding tools, on this machine and on others you reach over ssh, and converts it into one normalized usage history. Use it to review tokens and estimated cost, compare periods, find expensive sessions, correlate usage with local Git activity, or export the result.
 
 The CLI parses session content on your machine. It discovers standard source locations and includes a bundled pricing snapshot, so the first report can run without configuration or network access.
 
+See [Privacy](https://ayagmar.github.io/llm-usage-metrics/privacy/) for what it reads, stores, and sends over the network.
+
 ## Quick start
 
 Requires Node.js 22.16+ or 24+ (Node 23 lacks the SQLite busy timeout the ledger uses), or Bun 1.4+.
@@ -193,6 +195,7 @@ Reports can include your other machines' usage over ssh. Install llm-usage-metri
 llm-usage machine add laptop         # syncs over ssh laptop; see the docs for other destinations
 llm-usage monthly                    # this machine and the laptop, fetched when due
 llm-usage monthly --machine laptop   # only the laptop
+llm-usage                            # the summary splits this month's cost by machine
 ```
 
 A session that reached both machines (a copied or synced `~/.claude`) is counted once. See [Multiple machines](https://ayagmar.github.io/llm-usage-metrics/machines/).
@@ -204,9 +207,10 @@ llm-usage daily --all --json
 llm-usage daily --markdown
 llm-usage daily --compact
 llm-usage monthly --share
+llm-usage weekly --last 1 --no-cost
 ```
 
-Terminal tables fit the terminal width: on a narrow terminal, token counts are abbreviated and less-used columns are hidden, with a `stderr` note saying what was left out. `--compact` asks for the short table directly.
+Terminal tables fit the terminal width: on a narrow terminal, token counts are abbreviated and less-used columns are hidden, with a `stderr` note saying what was left out. `--compact` asks for the short table directly. `--last N` covers the last N days, weeks, or months, counting the current one, and `--no-cost` leaves spend out of tables and share cards.
 
 Report data goes to `stdout`. Diagnostics go to `stderr` as one summary line plus any warnings, which keeps JSON and Markdown safe to redirect; `--quiet` keeps only warnings and `--verbose` adds per-source and skipped-row detail. JSON output is wrapped in a versioned envelope: `{ "schemaVersion": 1, "report": "usage", "data": ... }`. Scripts written against pre-0.8.0 JSON should follow the [migration guide](https://ayagmar.github.io/llm-usage-metrics/migrating-to-0-8/).
 
@@ -231,6 +235,8 @@ pnpm run build
 
 The website has a [docs overview](https://ayagmar.github.io/llm-usage-metrics/docs/) and a [report chooser](https://ayagmar.github.io/llm-usage-metrics/reports/) for finding the right command. Its landing page and source navigation use the CLI source registry; regenerate CLI and security references after behavior changes.
 
+For LLMs and agents, the docs are also published as [llms.txt](https://ayagmar.github.io/llm-usage-metrics/llms.txt) (plus `llms-full.txt` with every page inlined).
+
 Site commands:
 
 ```bash