llm-usage-metrics 0.9.0 → 0.10.0

package/README.md

@@ -29,7 +29,7 @@ The CLI parses session content on your machine. It discovers standard source loc
 
 ## Quick start
 
-Requires Node.js 22.16+ or 24+ (Node 23 lacks the SQLite busy timeout the ledger uses).
+Requires Node.js 22.16+ or 24+ (Node 23 lacks the SQLite busy timeout the ledger uses), or Bun 1.4+.
 
 ```bash
 # Run without installing
@@ -39,6 +39,9 @@ npx --yes llm-usage-metrics@latest
 npm install -g llm-usage-metrics
 llm-usage
 
+# Or with Bun (--bun runs the CLI on Bun instead of Node)
+bunx --bun llm-usage-metrics@latest
+
 # Optional: tab completion (bash shown; zsh and fish work the same way)
 echo 'source <(llm-usage completion bash)' >> ~/.bashrc
 ```
@@ -182,6 +185,18 @@ llm-usage prune --departed-before 2026-01-01 --apply
 
 Deleting the ledger also deletes retained history. Read [Caching](https://ayagmar.github.io/llm-usage-metrics/caching/) before clearing it as a troubleshooting step.
 
+## Multiple machines
+
+Reports can include your other machines' usage over ssh. Install llm-usage-metrics there, make sure ssh logs in without a prompt, then:
+
+```bash
+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
+```
+
+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/).
+
 ## Output
 
 ```bash

package/dist/bin.js

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+
+// src/cli/bin.ts
+import module from "module";
+module.enableCompileCache();
+await import(new URL("./index.js", import.meta.url).href);
+//# sourceMappingURL=bin.js.map