vibe-coding-tracker 0.16.0__tar.gz → 1.0.0__tar.gz

{vibe_coding_tracker-0.16.0 → vibe_coding_tracker-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: vibe-coding-tracker
-Version: 0.16.0
+Version: 1.0.0
 Summary: Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results
 Keywords: cli,ai,coding-assistant,telemetry,claude,codex,gemini,usage-tracker,analytics
 Author: Wei Lee
@@ -169,7 +169,6 @@ vct <COMMAND> [OPTIONS]
 Commands:
   analysis    Analyze JSONL conversation files (single file or all sessions)
   usage       Display token usage statistics
-  statusline  Cache Claude Code rate limits from a statusLine hook (stdin JSON)
   version     Display version information
   update      Update to the latest version from GitHub releases
   help        Print this message or the help of the given subcommand(s)
@@ -177,12 +176,12 @@ Commands:
 
 Time range flags (shared by `usage` and `analysis`, mutually exclusive, default `--all`):
 
-| Flag        | Window                            |
-| ----------- | --------------------------------- |
-| `--daily`   | Sessions modified today           |
-| `--weekly`  | Current ISO week (Monday → today) |
-| `--monthly` | Current calendar month            |
-| `--all`     | Every session on disk (default)   |
+| Flag          | Window                            |
+| ------------- | --------------------------------- |
+| `--daily`     | Sessions modified today           |
+| `--weekly`    | Current ISO week (Monday → today) |
+| `--monthly`   | Current calendar month            |
+| `-a`, `--all` | Every session on disk (default)   |
 
 ---
 
@@ -198,6 +197,7 @@ Time range flags (shared by `usage` and `analysis`, mutually exclusive, default
 | `--table`                                      | Static table, no TUI                |
 | `--text`                                       | Plain text, script-friendly         |
 | `--json`                                       | JSON with enriched pricing metadata |
+| `--output <FILE>`                              | Save enriched JSON to a file        |
 | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
 
 ### Basic Usage
@@ -215,6 +215,9 @@ vct usage --text
 # JSON for data processing (includes cost_usd and matched_model fields)
 vct usage --json
 
+# Save enriched JSON straight to a file
+vct usage --output report.json
+
 # Combine time range with output format
 vct usage --weekly
 vct usage --table --monthly
@@ -258,7 +261,7 @@ The tool automatically scans these directories:
 
 ### Live Quota Panels
 
-At the bottom of the interactive dashboard, the per-provider stats sit on the left and two live quota panels sit on the right:
+`vct usage` shows **live remaining quota for Claude Code and Codex right in the dashboard — with zero setup.** No status-line hook, no config file: vct reads each provider's own OAuth credentials, calls its usage API on a background thread, and keeps the panels current while you work.
 
 ```
 ┌ Provider/Tokens/Cost/Days ┬ Claude ────────┬ Codex ──────────┐
@@ -269,10 +272,14 @@ At the bottom of the interactive dashboard, the per-provider stats sit on the le
 └───────────────────────────┴────────────────┴─────────────────┘
 ```
 
-- **Claude** — 5-hour and weekly rate-limit usage. Claude Code only exposes these limits through its `statusLine` hook, so wire `vct statusline ingest` into your statusLine (see [Statusline Command](#statusline-command)) for this panel to populate.
-- **Codex** — plan tier, 5-hour and weekly usage, and credit balance. Pulled live from the ChatGPT backend (`wham/usage`) using the token in `~/.codex/auth.json` on a background thread; when unavailable it falls back to the newest `rate_limits` in your Codex session logs (the title shows `(API)` vs `(session)`).
+- **Claude** — 5-hour and weekly usage from the official OAuth usage API (`GET /api/oauth/usage`), read from `~/.claude/.credentials.json`.
+- **Codex** — plan tier, 5-hour and weekly usage, and credit balance from the ChatGPT backend (`wham/usage`) using `~/.codex/auth.json`; falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
+
+**Automatic token refresh.** For both providers, when a token is near expiry or rejected, vct refreshes it and writes the new token back to the provider's own credential file (in that CLI's exact format), so a token is reused across checks rather than refreshed every time. If a refresh cannot proceed, the panel shows a `run: <provider> auth login` hint instead of breaking.
+
+A panel appears only for a provider whose credentials are present. Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
 
-Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
+> **Platform note:** on macOS, Claude Code stores its OAuth credentials in the system Keychain rather than `~/.claude/.credentials.json`, so the Claude panel is not shown on macOS.
 
 ---
 
@@ -346,35 +353,6 @@ vct analysis --output today.json --daily
 
 ---
 
-## Statusline Command
-
-**Feed Claude Code rate limits into the `usage` dashboard.**
-
-Claude Code only exposes its 5-hour / weekly rate limits through the `statusLine` hook's stdin JSON, so `vct` captures them from there and caches them to `~/.vibe_coding_tracker/claude_rate_limits.json` for the Claude quota panel.
-
-### If you already have a statusLine
-
-Add one backgrounded line to your existing statusLine script. It has zero impact on your current display and is isolated, so a vct error can never disturb the statusLine:
-
-```bash
-printf '%s' "$input" | vct statusline ingest >/dev/null 2>&1 &
-```
-
-### If you do not have a statusLine yet
-
-Point Claude Code's `~/.claude/settings.json` straight at vct, which caches the limits and prints a compact one-line status:
-
-```json
-{
-  "statusLine": {
-    "type": "command",
-    "command": "vct statusline"
-  }
-}
-```
-
----
-
 ## Update Command
 
 **Keep your installation up-to-date automatically.**

{vibe_coding_tracker-0.16.0 → vibe_coding_tracker-1.0.0}/README.md

@@ -143,7 +143,6 @@ vct <COMMAND> [OPTIONS]
 Commands:
   analysis    Analyze JSONL conversation files (single file or all sessions)
   usage       Display token usage statistics
-  statusline  Cache Claude Code rate limits from a statusLine hook (stdin JSON)
   version     Display version information
   update      Update to the latest version from GitHub releases
   help        Print this message or the help of the given subcommand(s)
@@ -151,12 +150,12 @@ Commands:
 
 Time range flags (shared by `usage` and `analysis`, mutually exclusive, default `--all`):
 
-| Flag        | Window                            |
-| ----------- | --------------------------------- |
-| `--daily`   | Sessions modified today           |
-| `--weekly`  | Current ISO week (Monday → today) |
-| `--monthly` | Current calendar month            |
-| `--all`     | Every session on disk (default)   |
+| Flag          | Window                            |
+| ------------- | --------------------------------- |
+| `--daily`     | Sessions modified today           |
+| `--weekly`    | Current ISO week (Monday → today) |
+| `--monthly`   | Current calendar month            |
+| `-a`, `--all` | Every session on disk (default)   |
 
 ---
 
@@ -172,6 +171,7 @@ Time range flags (shared by `usage` and `analysis`, mutually exclusive, default
 | `--table`                                      | Static table, no TUI                |
 | `--text`                                       | Plain text, script-friendly         |
 | `--json`                                       | JSON with enriched pricing metadata |
+| `--output <FILE>`                              | Save enriched JSON to a file        |
 | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter (see table above) |
 
 ### Basic Usage
@@ -189,6 +189,9 @@ vct usage --text
 # JSON for data processing (includes cost_usd and matched_model fields)
 vct usage --json
 
+# Save enriched JSON straight to a file
+vct usage --output report.json
+
 # Combine time range with output format
 vct usage --weekly
 vct usage --table --monthly
@@ -232,7 +235,7 @@ The tool automatically scans these directories:
 
 ### Live Quota Panels
 
-At the bottom of the interactive dashboard, the per-provider stats sit on the left and two live quota panels sit on the right:
+`vct usage` shows **live remaining quota for Claude Code and Codex right in the dashboard — with zero setup.** No status-line hook, no config file: vct reads each provider's own OAuth credentials, calls its usage API on a background thread, and keeps the panels current while you work.
 
 ```
 ┌ Provider/Tokens/Cost/Days ┬ Claude ────────┬ Codex ──────────┐
@@ -243,10 +246,14 @@ At the bottom of the interactive dashboard, the per-provider stats sit on the le
 └───────────────────────────┴────────────────┴─────────────────┘
 ```
 
-- **Claude** — 5-hour and weekly rate-limit usage. Claude Code only exposes these limits through its `statusLine` hook, so wire `vct statusline ingest` into your statusLine (see [Statusline Command](#statusline-command)) for this panel to populate.
-- **Codex** — plan tier, 5-hour and weekly usage, and credit balance. Pulled live from the ChatGPT backend (`wham/usage`) using the token in `~/.codex/auth.json` on a background thread; when unavailable it falls back to the newest `rate_limits` in your Codex session logs (the title shows `(API)` vs `(session)`).
+- **Claude** — 5-hour and weekly usage from the official OAuth usage API (`GET /api/oauth/usage`), read from `~/.claude/.credentials.json`.
+- **Codex** — plan tier, 5-hour and weekly usage, and credit balance from the ChatGPT backend (`wham/usage`) using `~/.codex/auth.json`; falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
+
+**Automatic token refresh.** For both providers, when a token is near expiry or rejected, vct refreshes it and writes the new token back to the provider's own credential file (in that CLI's exact format), so a token is reused across checks rather than refreshed every time. If a refresh cannot proceed, the panel shows a `run: <provider> auth login` hint instead of breaking.
+
+A panel appears only for a provider whose credentials are present. Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
 
-Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
+> **Platform note:** on macOS, Claude Code stores its OAuth credentials in the system Keychain rather than `~/.claude/.credentials.json`, so the Claude panel is not shown on macOS.
 
 ---
 
@@ -320,35 +327,6 @@ vct analysis --output today.json --daily
 
 ---
 
-## Statusline Command
-
-**Feed Claude Code rate limits into the `usage` dashboard.**
-
-Claude Code only exposes its 5-hour / weekly rate limits through the `statusLine` hook's stdin JSON, so `vct` captures them from there and caches them to `~/.vibe_coding_tracker/claude_rate_limits.json` for the Claude quota panel.
-
-### If you already have a statusLine
-
-Add one backgrounded line to your existing statusLine script. It has zero impact on your current display and is isolated, so a vct error can never disturb the statusLine:
-
-```bash
-printf '%s' "$input" | vct statusline ingest >/dev/null 2>&1 &
-```
-
-### If you do not have a statusLine yet
-
-Point Claude Code's `~/.claude/settings.json` straight at vct, which caches the limits and prints a compact one-line status:
-
-```json
-{
-  "statusLine": {
-    "type": "command",
-    "command": "vct statusline"
-  }
-}
-```
-
----
-
 ## Update Command
 
 **Keep your installation up-to-date automatically.**

{vibe_coding_tracker-0.16.0 → vibe_coding_tracker-1.0.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "vibe_coding_tracker"
-version = "0.16.0"
+version = "1.0.0"
 description = "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results"
 authors = [
     { name = "Wei Lee", email = "mai@mai0313.com" }