vibe-coding-tracker 0.7.2__tar.gz → 0.9.0__tar.gz

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.
Files changed (10) hide show
  1. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/PKG-INFO +18 -16
  2. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/README.md +17 -15
  3. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/pyproject.toml +1 -1
  4. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/linux-arm64-gnu/vibe_coding_tracker +0 -0
  5. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/linux-x64-gnu/vibe_coding_tracker +0 -0
  6. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/macos-arm64/vibe_coding_tracker +0 -0
  7. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/macos-x64/vibe_coding_tracker +0 -0
  8. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/windows-arm64/vibe_coding_tracker.exe +0 -0
  9. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/binaries/windows-x64/vibe_coding_tracker.exe +0 -0
  10. {vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/src/vibe_coding_tracker/__init__.py +0 -0
{vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.3
2
2
  Name: vibe-coding-tracker
3
- Version: 0.7.2
3
+ Version: 0.9.0
4
4
  Summary: Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results
5
5
  Keywords: cli,ai,coding-assistant,telemetry,claude,codex,gemini,usage-tracker,analytics
6
6
  Author: Wei Lee
@@ -265,14 +265,15 @@ The tool automatically scans these directories:
265
265
 
266
266
  ### Flags
267
267
 
268
- | Flag | Purpose |
269
- | ---------------------------------------------- | ------------------------------------------------------------------ |
270
- | *(none)* | Interactive TUI dashboard over all sessions |
271
- | `--path <FILE>` | Analyze a single JSONL/JSON conversation file (prints JSON) |
272
- | `--table` | Static table with per-provider daily averages |
273
- | `--output <FILE>` | Save results as pretty-printed JSON |
274
- | `--by-provider` | Group rows by provider (claude / codex / copilot / gemini) as JSON |
275
- | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
268
+ | Flag | Purpose |
269
+ | ---------------------------------------------- | ----------------------------------------------------------- |
270
+ | *(none)* | Interactive TUI dashboard over all sessions |
271
+ | `--path <FILE>` | Analyze a single JSONL/JSON conversation file (prints JSON) |
272
+ | `--table` | Static table with per-provider daily averages |
273
+ | `--text` | Plain text, script-friendly |
274
+ | `--json` | JSON array of aggregated rows printed to stdout |
275
+ | `--output <FILE>` | Save results as pretty-printed JSON |
276
+ | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
276
277
 
277
278
  See [`examples/`](examples/) for sample inputs and matching JSON outputs for all four providers.
278
279
 
@@ -285,22 +286,23 @@ vct analysis
285
286
  # Static table output with daily averages
286
287
  vct analysis --table
287
288
 
289
+ # Plain text for scripts
290
+ vct analysis --text
291
+
292
+ # JSON of aggregated rows for data processing
293
+ vct analysis --json
294
+
288
295
  # Analyze a single conversation file → stdout JSON
289
296
  vct analysis --path ~/.claude/projects/session.jsonl
290
297
 
291
298
  # Save results to JSON
292
299
  vct analysis --output report.json
293
300
 
294
- # Group results by provider
295
- vct analysis --by-provider
296
-
297
- # Save grouped results
298
- vct analysis --by-provider --output grouped_report.json
299
-
300
301
  # Combine time range with output format
301
302
  vct analysis --weekly
302
303
  vct analysis --table --monthly
303
- vct analysis --by-provider --daily --output today.json
304
+ vct analysis --json --daily
305
+ vct analysis --output today.json --daily
304
306
  ```
305
307
 
306
308
  ### Preview: Interactive Dashboard (`vct analysis`)
{vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/README.md RENAMED
@@ -239,14 +239,15 @@ The tool automatically scans these directories:
239
239
 
240
240
  ### Flags
241
241
 
242
- | Flag | Purpose |
243
- | ---------------------------------------------- | ------------------------------------------------------------------ |
244
- | *(none)* | Interactive TUI dashboard over all sessions |
245
- | `--path <FILE>` | Analyze a single JSONL/JSON conversation file (prints JSON) |
246
- | `--table` | Static table with per-provider daily averages |
247
- | `--output <FILE>` | Save results as pretty-printed JSON |
248
- | `--by-provider` | Group rows by provider (claude / codex / copilot / gemini) as JSON |
249
- | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
242
+ | Flag | Purpose |
243
+ | ---------------------------------------------- | ----------------------------------------------------------- |
244
+ | *(none)* | Interactive TUI dashboard over all sessions |
245
+ | `--path <FILE>` | Analyze a single JSONL/JSON conversation file (prints JSON) |
246
+ | `--table` | Static table with per-provider daily averages |
247
+ | `--text` | Plain text, script-friendly |
248
+ | `--json` | JSON array of aggregated rows printed to stdout |
249
+ | `--output <FILE>` | Save results as pretty-printed JSON |
250
+ | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
250
251
 
251
252
  See [`examples/`](examples/) for sample inputs and matching JSON outputs for all four providers.
252
253
 
@@ -259,22 +260,23 @@ vct analysis
259
260
  # Static table output with daily averages
260
261
  vct analysis --table
261
262
 
263
+ # Plain text for scripts
264
+ vct analysis --text
265
+
266
+ # JSON of aggregated rows for data processing
267
+ vct analysis --json
268
+
262
269
  # Analyze a single conversation file → stdout JSON
263
270
  vct analysis --path ~/.claude/projects/session.jsonl
264
271
 
265
272
  # Save results to JSON
266
273
  vct analysis --output report.json
267
274
 
268
- # Group results by provider
269
- vct analysis --by-provider
270
-
271
- # Save grouped results
272
- vct analysis --by-provider --output grouped_report.json
273
-
274
275
  # Combine time range with output format
275
276
  vct analysis --weekly
276
277
  vct analysis --table --monthly
277
- vct analysis --by-provider --daily --output today.json
278
+ vct analysis --json --daily
279
+ vct analysis --output today.json --daily
278
280
  ```
279
281
 
280
282
  ### Preview: Interactive Dashboard (`vct analysis`)
{vibe_coding_tracker-0.7.2 → vibe_coding_tracker-0.9.0}/pyproject.toml RENAMED
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "vibe_coding_tracker"
3
- version = "0.7.2"
3
+ version = "0.9.0"
4
4
  description = "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results"
5
5
  authors = [
6
6
  { name = "Wei Lee", email = "mai@mai0313.com" }