vibe-coding-tracker 0.5.11

Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results

Vibe Coding Tracker — AI Coding Assistant Usage Tracker

Track your AI coding costs in real-time. Vibe Coding Tracker is a powerful CLI tool that helps you monitor and analyze your Claude Code, Codex, Copilot, and Gemini usage, providing detailed cost breakdowns, token statistics, and code operation insights.

English | 繁體中文 | 简体中文

Note: CLI examples use the short alias vct. If you installed via npm/pip/cargo, the binary might be named vibe_coding_tracker or vct. Create an alias or replace vct with the full name when running commands if needed.

---

🎯 Why Vibe Coding Tracker?

💰 Know Your Costs

Stop wondering how much your AI coding sessions cost. Get real-time cost tracking with automatic pricing updates from LiteLLM.

📊 Beautiful Visualizations

Choose your preferred view:

• Interactive Dashboard: Auto-refreshing terminal UI with live updates
• Static Reports: Professional tables for documentation
• Script-Friendly: Plain text and JSON for automation
• Full Precision: Export exact costs for accounting

🚀 Zero Configuration

Automatically detects and processes logs from Claude Code, Codex, Copilot, and Gemini. No setup required—just run and analyze.

🎨 Rich Insights

• Token usage by model and date
• Cost breakdown by cache types
• File operations tracking
• Command execution history
• Git repository information

---

✨ Key Features

Feature	Description
🤖 Auto-Detection	Intelligently identifies Claude Code, Codex, Copilot, or Gemini logs
💵 Smart Pricing	Fuzzy model matching + daily cache for speed
🎨 4 Display Modes	Interactive, Table, Text, and JSON outputs
📈 Comprehensive Stats	Tokens, costs, file ops, and tool calls
⚡ High Performance	Built with Rust for speed and reliability
🔄 Live Updates	Real-time dashboard refreshes every second
💾 Efficient Caching	Smart daily cache reduces API calls

---

🚀 Quick Start

Installation

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.

Method 1: Install from npm

Prerequisites: Node.js v22 or higher

Choose one of the following package names (they are identical):

# Main package
npm install -g vibe-coding-tracker

# Short alias with scope
npm install -g @mai0313/vct

# Full name with scope
npm install -g @mai0313/vibe-coding-tracker

Method 2: Install from PyPI

Prerequisites: Python 3.8 or higher

pip install vibe_coding_tracker
# Or with uv
uv pip install vibe_coding_tracker

Method 3: Install from crates.io

Install using Cargo from the official Rust package registry:

cargo install vibe_coding_tracker

First Run

# View your usage with the short alias (if available)
vct usage

# Or run the binary built by Cargo/pip
vibe_coding_tracker usage

# Analyze a specific conversation
vibe_coding_tracker analysis --path ~/.claude/projects/session.jsonl

---

📖 Command Guide

🔍 Quick Reference

vct <COMMAND> [OPTIONS]
# Replace with `vibe_coding_tracker` if you are using the full binary name

Commands:
analysis    Analyze JSONL conversation files (single file or all sessions)
usage       Display token usage statistics
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)

---

💰 Usage Command

Track your spending across all AI coding sessions.

Basic Usage

# Interactive dashboard (recommended)
vct usage

# Static table for reports
vct usage --table

# Plain text for scripts
vct usage --text

# JSON for data processing
vct usage --json

What You Get

The tool scans these directories automatically:

• ~/.claude/projects/*.jsonl (Claude Code)
• ~/.codex/sessions/*.jsonl (Codex)
• ~/.copilot/history-session-state/*.json (Copilot)
• ~/.gemini/tmp/<project_hash>/chats/*.json (Gemini)

---

📊 Analysis Command

Deep dive into conversation files - single file or batch analysis.

Basic Usage

# Single file: Analyze and display
vct analysis --path ~/.claude/projects/session.jsonl

# Single file: Save to file
vct analysis --path ~/.claude/projects/session.jsonl --output report.json

# Batch: Analyze all sessions with interactive table (default)
vct analysis

# Batch: Static table output with daily averages
vct analysis --table

# Batch: Save aggregated results to JSON
vct analysis --output batch_report.json

# Batch with provider grouping: Output complete records grouped by provider (JSON format)
vct analysis --all

# Save the grouped results to a file
vct analysis --all --output grouped_report.json

---

🔄 Update Command

Keep your installation 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.

Basic Usage

# Check for updates
vct update --check

# Interactive update with confirmation
vct update

# Force update - always downloads latest version (even if already up-to-date)
vct update --force

---

💡 Smart Pricing System

How It Works

1. Automatic Updates: Fetches pricing from LiteLLM daily
2. Smart Caching: Stores pricing in ~/.vibe_coding_tracker/ for 24 hours
3. Fuzzy Matching: Finds best match even for custom model names
4. Always Accurate: Ensures you get the latest pricing

Model Matching

Priority Order:

1. ✅ Exact Match: claude-sonnet-4 → claude-sonnet-4
2. 🔄 Normalized: claude-sonnet-4-20250514 → claude-sonnet-4
3. 🔍 Substring: custom-gpt-4 → gpt-4
4. 🎯 Fuzzy (AI-powered): Uses Jaro-Winkler similarity (70% threshold)
5. 💵 Fallback: Shows $0.00 if no match found

---

🐳 Docker Support

# Build image
docker build -f docker/Dockerfile --target prod -t vibe_coding_tracker:latest .

# Run with your sessions
docker run --rm \
    -v ~/.claude:/root/.claude \
    -v ~/.codex:/root/.codex \
    -v ~/.copilot:/root/.copilot \
    -v ~/.gemini:/root/.gemini \
    vibe_coding_tracker:latest usage