vibe-coding-tracker 0.12.0__tar.gz → 0.13.0__tar.gz

{vibe_coding_tracker-0.12.0 → vibe_coding_tracker-0.13.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: vibe-coding-tracker
-Version: 0.12.0
+Version: 0.13.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
@@ -106,7 +106,7 @@ Automatically detects and processes logs from Claude Code, Codex, Copilot, Gemin
 
 Choose the installation method that works best for you:
 
-> **Developers**: If you want to build from source or contribute to development, please see [CONTRIBUTING.md](CONTRIBUTING.md).
+> **Developers**: If you want to build from source or contribute to development, please see [CONTRIBUTING.md](.github/CONTRIBUTING.md).
 
 #### Method 1: Install from npm
 
@@ -169,6 +169,7 @@ 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)
@@ -260,6 +261,24 @@ The tool automatically scans these directories:
 - `~/.gemini/tmp/<project_hash>/chats/*.jsonl` (Gemini CLI)
 - `~/.local/share/opencode/opencode.db` (OpenCode — SQLite database; honors `$XDG_DATA_HOME`)
 
+### 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:
+
+```
+┌ Provider/Tokens/Cost/Days ┬ Claude ────────┬ Codex (API) ────┐
+│ Claude    1.2M  $3.00  4d │ 5h ▰▰▱▱▱  16%   │ Plan: plus      │
+│ Codex      800K $0.00  6d │    ↻ 4h13m      │ 5h ▰▰▱▱▱  27%   │
+│ ...                       │ 7d ▰▰▰▱▱  28%   │ 7d ▱▱▱▱▱   4%   │
+│                           │ updated 2m ago  │ Credits: 0  +2  │
+└───────────────────────────┴────────────────┴─────────────────┘
+```
+
+- **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)`).
+
+Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
+
 ---
 
 ## Analysis Command
@@ -337,6 +356,35 @@ 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.12.0 → vibe_coding_tracker-0.13.0}/README.md

@@ -80,7 +80,7 @@ Automatically detects and processes logs from Claude Code, Codex, Copilot, Gemin
 
 Choose the installation method that works best for you:
 
-> **Developers**: If you want to build from source or contribute to development, please see [CONTRIBUTING.md](CONTRIBUTING.md).
+> **Developers**: If you want to build from source or contribute to development, please see [CONTRIBUTING.md](.github/CONTRIBUTING.md).
 
 #### Method 1: Install from npm
 
@@ -143,6 +143,7 @@ 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)
@@ -234,6 +235,24 @@ The tool automatically scans these directories:
 - `~/.gemini/tmp/<project_hash>/chats/*.jsonl` (Gemini CLI)
 - `~/.local/share/opencode/opencode.db` (OpenCode — SQLite database; honors `$XDG_DATA_HOME`)
 
+### 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:
+
+```
+┌ Provider/Tokens/Cost/Days ┬ Claude ────────┬ Codex (API) ────┐
+│ Claude    1.2M  $3.00  4d │ 5h ▰▰▱▱▱  16%   │ Plan: plus      │
+│ Codex      800K $0.00  6d │    ↻ 4h13m      │ 5h ▰▰▱▱▱  27%   │
+│ ...                       │ 7d ▰▰▰▱▱  28%   │ 7d ▱▱▱▱▱   4%   │
+│                           │ updated 2m ago  │ Credits: 0  +2  │
+└───────────────────────────┴────────────────┴─────────────────┘
+```
+
+- **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)`).
+
+Quota panels appear only in the interactive TUI; `--table`, `--text`, and `--json` are unchanged.
+
 ---
 
 ## Analysis Command
@@ -311,6 +330,35 @@ 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.12.0 → vibe_coding_tracker-0.13.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "vibe_coding_tracker"
-version = "0.12.0"
+version = "0.13.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" }