vibe-coding-tracker 2.4.0__tar.gz → 2.5.0__tar.gz

{vibe_coding_tracker-2.4.0 → vibe_coding_tracker-2.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: vibe-coding-tracker
-Version: 2.4.0
+Version: 2.5.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
@@ -345,7 +345,7 @@ For noninteractive `usage` and `analysis` scans, vct exits with an error when ev
 ```
 
 - **Claude** — plan tier, 5-hour, weekly, and per-model weekly usage from the official OAuth usage API (`GET /api/oauth/usage`), read from `~/.claude/.credentials.json`, plus your credit balance. Polled about once a minute to stay under the endpoint's rate limit; a red `LIMIT` flag appears in the title when a cap is hit. The per-model weekly row is best-effort and simply hides when that scope is not returned.
-- **Codex** — plan tier, 5-hour and weekly usage, credit balance, and the earliest fetched available earned-reset expiry from the ChatGPT backend (`wham/usage` + `wham/rate-limit-reset-credits`) using `~/.codex/auth.json` (with approximate remaining messages / spend cap when applicable); falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
+- **Codex** — plan tier, available 5-hour and weekly usage windows, credit balance, and the earliest fetched available earned-reset expiry from the ChatGPT backend (`wham/usage` + `wham/rate-limit-reset-credits`) using `~/.codex/auth.json` (with approximate remaining messages / spend cap when applicable); falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
 - **Copilot** — plan tier plus your premium-request quota, shown as two gauges: percent used and the used / total request count (e.g. `45/1500`), from GitHub's Copilot API (`GET /copilot_internal/user`), read from `~/.copilot/config.json`. The request impersonates the Copilot CLI. The token is long-lived, so there is no refresh; a `401` / `403` shows a `run: copilot login` hint.
 - **Cursor** — plan tier, total / auto / API percent **used**, and on-demand spend from cursor.com (`GET /api/usage-summary`), using the session token in `~/.config/cursor/auth.json`. Refresh is reactive: vct re-reads the file each poll and uses the token while it is valid, since the official Cursor client keeps it fresh.
 - **Grok** — plan tier plus your included-allowance usage for the current weekly or monthly period, from the Grok CLI's own billing endpoint (`GET /v1/billing?format=credits`), read from `~/.grok/auth.json`. A prepaid balance is shown only once it is non-zero, and pay-as-you-go spend once you have either spent something or set a cap. The request impersonates the Grok CLI; a `401` / `403` shows a `run: grok login` hint.
@@ -487,9 +487,13 @@ Codex code-mode sessions expose a completed JavaScript `exec` cell but no struct
 
 ## Update Command
 
-**Keep your installation up-to-date automatically.**
+**Keep supported direct installations up to date automatically.**
 
-The update command works for **all installation methods** (npm/pip/cargo/manual) by directly downloading and replacing the binary from GitHub releases.
+At startup, vct silently checks for a newer release at most once per UTC day. A newer release is downloaded and applied only when the current binary was installed by the official `scripts/install.sh` or `scripts/install.ps1` installer and carries its `.vct-managed` marker. The check, download, and replacement never print to stdout or stderr. A network failure, rate limit, read-only directory, or another running vct process only leaves the current command running; the reason is recorded in the diagnostic log. `VCT_OFFLINE=1` skips the check completely.
+
+After a Unix update, vct re-executes the current command with the new binary. On Windows, the current command finishes and a helper applies the replacement afterwards. The automatic path never modifies installs from cargo, npm, PyPI, a distro package, or an unmarked manual or development build. Update those through their package manager instead. To add automatic updates to an existing direct install, run the current official installer once more so it creates the marker.
+
+Set `general.auto_update = false` in `~/.vct/config.toml` to disable startup checks and automatic updates. The explicit `vct update` command retains its existing manual behavior.
 
 ### Basic Usage
 
@@ -586,9 +590,12 @@ vct keeps its user settings in `~/.vct/config.toml`. The file is **created with
 # Default time range when no --daily/--weekly/--monthly/--all flag is given.
 # One of: "daily" | "weekly" | "monthly" | "all".
 default_time_range = "all"
+# Check for a newer release at startup and automatically update supported direct installs.
+# Set to false to disable this behavior.
+auto_update = true
 # Layout version of this file, stamped by vct. Only the upgrade pass reads it;
 # leave it alone unless you want a past upgrade to run again.
-version = 2
+version = 3
 
 [usage]
 # Start the usage dashboard with models merged across provider prefixes.
@@ -636,6 +643,7 @@ retention_days = 7
 | Setting                        | Effect                                                                                                                          |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
 | `general.default_time_range`   | Period used when you pass no `--daily/--weekly/--monthly/--all`. An explicit flag always wins.                                  |
+| `general.auto_update`          | Check once per UTC day at startup and automatically update only official-installer direct installs. Set to `false` to disable.  |
 | `general.version`              | Layout version vct stamps on the file, so a panel added by a later release is offered to you exactly once.                      |
 | `usage.merge_models`           | Seeds the dashboard merged; the `m` toggle saves your last choice back here. `--merge-providers` forces on.                     |
 | `usage.refresh_interval`       | Redraw cadence of the `usage` dashboard (seconds).                                                                              |

{vibe_coding_tracker-2.4.0 → vibe_coding_tracker-2.5.0}/README.md

@@ -319,7 +319,7 @@ For noninteractive `usage` and `analysis` scans, vct exits with an error when ev
 ```
 
 - **Claude** — plan tier, 5-hour, weekly, and per-model weekly usage from the official OAuth usage API (`GET /api/oauth/usage`), read from `~/.claude/.credentials.json`, plus your credit balance. Polled about once a minute to stay under the endpoint's rate limit; a red `LIMIT` flag appears in the title when a cap is hit. The per-model weekly row is best-effort and simply hides when that scope is not returned.
-- **Codex** — plan tier, 5-hour and weekly usage, credit balance, and the earliest fetched available earned-reset expiry from the ChatGPT backend (`wham/usage` + `wham/rate-limit-reset-credits`) using `~/.codex/auth.json` (with approximate remaining messages / spend cap when applicable); falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
+- **Codex** — plan tier, available 5-hour and weekly usage windows, credit balance, and the earliest fetched available earned-reset expiry from the ChatGPT backend (`wham/usage` + `wham/rate-limit-reset-credits`) using `~/.codex/auth.json` (with approximate remaining messages / spend cap when applicable); falls back to the newest `rate_limits` in your Codex session logs when the API is unavailable (the title shows `Codex` vs `Codex (session)`).
 - **Copilot** — plan tier plus your premium-request quota, shown as two gauges: percent used and the used / total request count (e.g. `45/1500`), from GitHub's Copilot API (`GET /copilot_internal/user`), read from `~/.copilot/config.json`. The request impersonates the Copilot CLI. The token is long-lived, so there is no refresh; a `401` / `403` shows a `run: copilot login` hint.
 - **Cursor** — plan tier, total / auto / API percent **used**, and on-demand spend from cursor.com (`GET /api/usage-summary`), using the session token in `~/.config/cursor/auth.json`. Refresh is reactive: vct re-reads the file each poll and uses the token while it is valid, since the official Cursor client keeps it fresh.
 - **Grok** — plan tier plus your included-allowance usage for the current weekly or monthly period, from the Grok CLI's own billing endpoint (`GET /v1/billing?format=credits`), read from `~/.grok/auth.json`. A prepaid balance is shown only once it is non-zero, and pay-as-you-go spend once you have either spent something or set a cap. The request impersonates the Grok CLI; a `401` / `403` shows a `run: grok login` hint.
@@ -461,9 +461,13 @@ Codex code-mode sessions expose a completed JavaScript `exec` cell but no struct
 
 ## Update Command
 
-**Keep your installation up-to-date automatically.**
+**Keep supported direct installations up to date automatically.**
 
-The update command works for **all installation methods** (npm/pip/cargo/manual) by directly downloading and replacing the binary from GitHub releases.
+At startup, vct silently checks for a newer release at most once per UTC day. A newer release is downloaded and applied only when the current binary was installed by the official `scripts/install.sh` or `scripts/install.ps1` installer and carries its `.vct-managed` marker. The check, download, and replacement never print to stdout or stderr. A network failure, rate limit, read-only directory, or another running vct process only leaves the current command running; the reason is recorded in the diagnostic log. `VCT_OFFLINE=1` skips the check completely.
+
+After a Unix update, vct re-executes the current command with the new binary. On Windows, the current command finishes and a helper applies the replacement afterwards. The automatic path never modifies installs from cargo, npm, PyPI, a distro package, or an unmarked manual or development build. Update those through their package manager instead. To add automatic updates to an existing direct install, run the current official installer once more so it creates the marker.
+
+Set `general.auto_update = false` in `~/.vct/config.toml` to disable startup checks and automatic updates. The explicit `vct update` command retains its existing manual behavior.
 
 ### Basic Usage
 
@@ -560,9 +564,12 @@ vct keeps its user settings in `~/.vct/config.toml`. The file is **created with
 # Default time range when no --daily/--weekly/--monthly/--all flag is given.
 # One of: "daily" | "weekly" | "monthly" | "all".
 default_time_range = "all"
+# Check for a newer release at startup and automatically update supported direct installs.
+# Set to false to disable this behavior.
+auto_update = true
 # Layout version of this file, stamped by vct. Only the upgrade pass reads it;
 # leave it alone unless you want a past upgrade to run again.
-version = 2
+version = 3
 
 [usage]
 # Start the usage dashboard with models merged across provider prefixes.
@@ -610,6 +617,7 @@ retention_days = 7
 | Setting                        | Effect                                                                                                                          |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
 | `general.default_time_range`   | Period used when you pass no `--daily/--weekly/--monthly/--all`. An explicit flag always wins.                                  |
+| `general.auto_update`          | Check once per UTC day at startup and automatically update only official-installer direct installs. Set to `false` to disable.  |
 | `general.version`              | Layout version vct stamps on the file, so a panel added by a later release is offered to you exactly once.                      |
 | `usage.merge_models`           | Seeds the dashboard merged; the `m` toggle saves your last choice back here. `--merge-providers` forces on.                     |
 | `usage.refresh_interval`       | Redraw cadence of the `usage` dashboard (seconds).                                                                              |

{vibe_coding_tracker-2.4.0 → vibe_coding_tracker-2.5.0}/pyproject.toml

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