@xerg/cli 0.5.1 → 0.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # xerg
2
2
 
3
- Audit OpenClaw and Hermes workflows in dollars, compare fixes, and optionally connect hosted follow-up after the first local result.
3
+ Audit OpenClaw, Hermes, and Cursor spend in dollars, surface provenance-aware waste findings, compare fixes, and optionally connect hosted follow-up after the first local result.
4
4
 
5
5
  Xerg runs locally by default. Local audits and `--compare` are free. No account is required for local value, and no data leaves your machine unless you explicitly push results to Xerg Cloud.
6
6
 
@@ -16,7 +16,7 @@ npx @xerg/cli init
16
16
 
17
17
  - detects local OpenClaw or Hermes data
18
18
  - runs a first audit and stores the local snapshot
19
- - prints the standard terminal summary
19
+ - prints the provenance-aware terminal summary
20
20
  - offers optional hosted follow-up with `connect` and `mcp-setup`
21
21
 
22
22
  Prefer a global install?
@@ -34,6 +34,7 @@ If you already know what you want, skip `init` and use the direct flows:
34
34
  npx @xerg/cli doctor
35
35
  npx @xerg/cli audit
36
36
  npx @xerg/cli audit --compare
37
+ npx @xerg/cli audit --cursor-usage-csv ./cursor-usage.csv
37
38
  npx @xerg/cli audit --json
38
39
  npx @xerg/cli audit --markdown
39
40
  ```
@@ -109,7 +110,7 @@ xerg push
109
110
 
110
111
  ## Works where your agent data lives
111
112
 
112
- - Local machine: yes
113
+ - Local machine: OpenClaw, Hermes, and explicit Cursor usage CSV exports
113
114
  - VPS or remote server: OpenClaw only in this phase
114
115
  - If OpenClaw runs remotely, you can audit it from your local machine with `xerg audit --remote user@host`
115
116
  - Or point Xerg at exported files directly with flags
@@ -135,6 +136,7 @@ xerg audit --runtime openclaw --log-file /path/to/openclaw.log
135
136
  xerg audit --runtime openclaw --sessions-dir /path/to/sessions
136
137
  xerg audit --runtime hermes --log-file ~/.hermes/logs/agent.log
137
138
  xerg audit --runtime hermes --sessions-dir ~/.hermes/sessions
139
+ xerg audit --cursor-usage-csv ./cursor-usage.csv
138
140
  ```
139
141
 
140
142
  If only one supported local runtime is present, Xerg auto-selects it. If both OpenClaw and Hermes are present locally, rerun with `--runtime openclaw` or `--runtime hermes`.
@@ -191,10 +193,13 @@ Example `~/.xerg/config.json`:
191
193
  - Total spend by workflow and model, in dollars
192
194
  - Daily spend and confirmed waste rollups in UTC
193
195
  - Observed vs. estimated cost (always labeled)
194
- - Confirmed waste: retry, loop, cache carryover where applicable
196
+ - Confirmed waste: retry and loop findings when the required source structure is present
197
+ - Provenance-aware waste rollups by observed, inferred, declared, or unknown signal source
195
198
  - Savings opportunities: context bloat, downgrade candidates, idle, max mode concentration where applicable
196
199
  - Ranked recommendations with where-to-change guidance and compare validation steps
197
- - Before/after deltas on re-audit
200
+ - Before/after normalized rates on re-audit, including waste per run and waste per 1k calls
201
+
202
+ Local JSON findings may include `signalSource`, `ruleId`, and evidence references so agents can distinguish observed signals from inferred or legacy unknown provenance. These local provenance fields are not part of the pushed v2 wire payload.
198
203
 
199
204
  ## Privacy
200
205
 
@@ -209,7 +214,7 @@ Xerg v0 stores economic metadata and audit summaries locally. It does not store
209
214
 
210
215
  ## Troubleshooting
211
216
 
212
- - `better-sqlite3` is a native dependency. If install fails, retry on a supported Node version and make sure standard native build tooling is available for your platform.
217
+ - If install fails with an unsupported engine warning, retry with Node 22 or 24.
213
218
  - `xerg init` is interactive in v1. Use direct `doctor` / `audit` commands when you need non-interactive control.
214
219
  - `--verbose` prints progress updates to stderr for `xerg doctor` and `xerg audit`, which helps distinguish package install time from CLI runtime.
215
220
  - If `xerg audit --remote ...` fails before pulling files, verify that both `ssh` and `rsync` are installed and reachable on your `PATH`.
@@ -0,0 +1,3 @@
1
+ // src/browser.ts
2
+ throw new Error("@xerg/cli is a Node.js CLI and cannot run in browser bundles.");
3
+ //# sourceMappingURL=browser.js.map
@@ -0,0 +1 @@
1
+ {"version":3,"sources":["../src/browser.ts"],"sourcesContent":["throw new Error('@xerg/cli is a Node.js CLI and cannot run in browser bundles.');\n"],"mappings":";AAAA,MAAM,IAAI,MAAM,+DAA+D;","names":[]}