vibe-log-cli

<div align="center"> <img width="280" height="257" alt="og-image" src="https://github.com/user-attachments/assets/ff8a996f-6292-44eb-b6f4-a07737db7d6d" /> <p></p> <h3>Open-source CLI for analyzing Claude Code and Codex sessions locally and generating productivity reports</h3> <p></p>

<a href="https://vibe-log.dev"><img src="https://img.shields.io/badge/by-vibe--log.dev-16A34A" alt="by vibe-log.dev"></a> <a href="https://www.npmjs.com/package/vibe-log-cli"><img src="https://img.shields.io/npm/v/vibe-log-cli.svg" alt="npm version"></a> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a> <a href="https://nodejs.org"><img src="https://img.shields.io/node/v/vibe-log-cli.svg" alt="Node.js Version"></a>

<a href="https://github.com/vibe-log/vibe-log-cli/actions/workflows/tests.yml"><img src="https://github.com/vibe-log/vibe-log-cli/actions/workflows/tests.yml/badge.svg" alt="Tests"></a> <a href="https://github.com/vibe-log/vibe-log-cli/actions/workflows/npm-publish.yml"><img src="https://github.com/vibe-log/vibe-log-cli/actions/workflows/npm-publish.yml/badge.svg" alt="NPM Publish"></a> <a href="https://github.com/vibe-log/vibe-log-cli/actions/workflows/build-verification.yml"><img src="https://github.com/vibe-log/vibe-log-cli/actions/workflows/build-verification.yml/badge.svg" alt="Build Verification"></a> <img src="./coverage/badges.svg" alt="Coverage">

<a href="SECURITY.md"><img src="https://img.shields.io/badge/Security-Policy-blue.svg" alt="Security Policy"></a> <a href="https://github.com/vibe-log/vibe-log-cli?tab=readme-ov-file#-privacy--security"><img src="https://img.shields.io/badge/build-transparent-blue" alt="Transparent Build"></a>

<a href="CONTRIBUTING.md"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs Welcome"></a> <a href="https://x.com/Vibe_Log/"><img alt="X Follow" src="https://img.shields.io/twitter/follow/Vibe_Log"></a> <a href="https://github.com/vibe-log/vibe-log-cli"><img src="https://img.shields.io/badge/⭐_Star-this_repo-22C55E?labelColor=000000" alt="Star this repo"></a>

</p> </p>

Website • Report Bug • Request Feature

</div>

What is Vibe-Log?

Vibe-log-cli is an open-source command-line tool that analyzes your Claude Code and Codex sessions to extract productivity insights and generate reports. All analyses can run completely locally on your machine using your local AI coding tool through ACP. It also includes a Claude Code statusline that helps you get more from your sessions.

Getting Started fast

Just run:

npx vibe-log-cli@latest

Main features

1. 📋 Today's standup

New: Be prepared in 2-3 minutes for your daily standup meeting! <img width="1270" height="512" alt="Screenshot 2025-10-02 163102" src="https://github.com/user-attachments/assets/b0e2bd55-618e-4b9e-b1c0-f2d7069e76aa" />

2. 📊 Claude Code and Codex Productivity Report Generation (Local)

Generate comprehensive productivity reports from Claude Code and Codex sessions using your local AI coding setup. No data leaves your machine. See example of locally generated report here: https://vibe-log.dev/example-daily-report <img width="869" height="968" alt="image" src="https://github.com/user-attachments/assets/8712e0ed-101d-4ba4-a243-8790ea409a5c" />

3. 🧠 Claude Code Co-pilot Statusline

Strategic product advisor in Claude Code. Your prompts are analyzed locally (via CC) to provide actionable guidance that pushes you to ship faster. Feedback appears in your Claude Code status line with concrete next steps. <img width="612" height="227" alt="image" src="https://github.com/user-attachments/assets/b2f7f10b-8a29-429b-921a-d0fc0bc45183" />

Updates

What's New in v0.7.x

Today's Standup ✨

Get a personalized standup summary of your recent Claude Code and Codex activity right from your terminal. Runs 100% locally using your own AI coding setup. The standup feature analyzes your recent sessions and generates a concise summary of:

• What you worked on
• Key accomplishments
• Next steps

Improved Onboarding Experience 🚀

Getting started with vibe-log is now smoother than ever: Better first-run setup flow Helpful prompts to guide you through configuration Improved error messages when things go wrong

Improved Time Calculation ⏱️

More accurate session duration tracking with better handling of: Massive sessions: Sessions with 10,000+ messages no longer cause performance issues Smart truncation: Large sessions are intelligently truncated while preserving time data Consistent timestamps: Better parsing and validation of session timing information Edge case handling: Fixed issues with sessions that had missing or invalid timestamps

💬 More about Claude Status Line - Strategic Co-pilot / Advisor (Local)

🔒 Installation Safety: Automatically backs up your existing status line configuration. Uninstalling instantly restores your original setup - zero risk to your Claude Code configuration.

Why Use Status Line?

• 🚀 Ship Faster: Get pushed to deliver
• 🎯 Stay Focused: Remembers your original mission and keeps you on track and forward ⏩︎
• ⚡ Concrete Actions: Specific next steps like:
• 📈 Strategic Thinking: Considers edge cases, user experience, and scaling at the right time
• 📊 Token Usage Display: Integrates with ccusage to show real-time token metrics
• ↩️ Easy Restore: Your original status line is backed up and can be restored anytime

Architecture

How Status Line Works

1. Intercepts prompts submitted in Claude Code
2. Analyzes via the local Claude Code latest prompt with relevant session context.
3. Provides strategic guidance and pushes you to ship
4. Displays actionable feedback in the Claude Code status line

In more details:

flowchart LR
    subgraph Input ["✳️ In Claude Code"]
        User([👤 You type a<br/>prompt]) --> Submit[Press Enter to<br/>submit prompt]
        Submit --> Hook[🪝 UserPromptSubmit<br/>hook triggers]
    end

    subgraph Analysis ["🧠 Local Prompt Analysis via Claude Code SDK"]
        Hook --> CLI[Vibe-log CLI<br/>receives prompt]
        CLI --> Check{Is new chat?}
        Check -->|No| Context[📝 Include previous<br/>conversation]
        Check -->|Yes| Direct[💭 Analyze prompt<br/>standalone]
        
        subgraph Personality ["🎭 Infuse Coach Personality"]
            Gordon[🧑‍🍳 Gordon<br/>Tough love]
            Vibe[💜 Vibe-log<br/>Encouraging]
            Custom[✨ Custom<br/>Your style]
        end
        
        Context --> SDK[Claude SDK<br/>analyzes prompt quality]
        Direct --> SDK
        Personality -.-> SDK
        SDK --> Score[📊 Generate score<br/>& suggestion]
    end

    subgraph Display ["💬 Status Line Feedback"]
        Score --> Save[💾 Save to<br/>~/.vibe-log/analysis]
        Save --> Status[Status bar<br/>reads result]
        Status --> Show[🟢 85/100<br/>✨ Gordon says:<br/>Add more context chef!]
    end

    Show --> Improve([📈 Better prompts<br/>Better results])

Coach Personalities

• Gordon - Sharp, pushy, business-focused. Creates urgency: "Ship by FRIDAY or you're fired!"
• Vibe-Log - Supportive but pushy senior dev. Helps you ship: "MVP checklist: Auth works ✓ | Ship it!"
• Custom - User-defined personality with strategic focus

Example Output

Setup

1. Run npx vibe-log-cli
2. Select "Configure prompt coach status line"
3. Choose coach personality
4. (Optional) Enable ccusage token metrics display
5. Prompts will be analyzed locally in Claude Code

Note: Installation automatically backs up your current status line (if any). When you uninstall vibe-log, your original configuration is instantly restored.

Local Report Generation Works

Generate comprehensive productivity reports from Claude Code and Codex sessions. No data leaves your machine.

• Select timeframe
• Select projects

flowchart TD
    Start([📝 Claude Code and Codex Sessions]) --> Select[vibe-log-cli select time frame and projects]
    Select --> Extract[Extracts & prepares session data]
    Extract --> Launch[Launches local ACP analysis]
    Launch --> Parallel{Session analysis}
    Parallel --> Gather[Gathers results &<br/>Generates report]
    Gather --> Output[📊 HTML Report in current folder]    
    style Start fill:#e1f5fe
    style Output fill:#d4edda

Example of Local Report Output

<img width="1920" height="4048" alt="screencapture-file-C-vibelog-vibe-log-cli-vibe-log-report-2025-09-05-2-html-2025-09-05-15_54_16" src="https://github.com/user-attachments/assets/545c0515-7649-4561-9e19-86b69a2e7103" />

☁️ Cloud Sync (Optional)

Optionally sync your sanitized session data to the vibe-log dashboard for advanced analytics and tracking over time.

Features

• 🎁 Free Forever: Up to 1,000 session analyses per month
• 📈 Track Over Time: Monitor your prompt quality and productivity trends
• 🔄 Auto-sync: Configure hooks for automatic background sync
• 🔒 Privacy First: All code removed before upload, only patterns synced
• 📊 Web Dashboard: Learn and improve your AI coding sessions.

How It Works

flowchart TD
    subgraph Local ["🏠 Your Machine"]
        Sessions[Claude Code and Codex Sessions] --> Select[Select sessions]
        Select --> Privacy[🔒 Privacy Layer<br/>Removes code & secrets<br/>Keeps only patterns]
    end
    
    subgraph Cloud ["☁️ Vibe-Log Cloud"]
        Privacy --> Upload[Upload patterns]
        Upload --> Verify[Server verification]
        Verify --> Analysis[AI analysis]
        Analysis --> Dashboard[📊 Web Dashboard]
    end
    
    subgraph Features ["Dashboard Features"]
        Dashboard --> Track[📈 Track prompt improvement over time]
        Dashboard --> Metrics[⚡ Deeper productivity insights]  
        Dashboard --> Streaks[🔥 Peak times/Low times]
        Dashboard --> Prompt[💬 User Prompt Analysis]
    end
    
    style Local fill:#e1f5fe
    style Cloud fill:#f3e5f5
    style Features fill:#d4edda

Auto-Sync

What is Auto-Sync

Claude Code hooks and Codex hooks allow Vibe-Log to automatically sync local sessions in the background. Claude Code auto-sync is stable. Codex auto-sync is experimental and sync-only.

What are hooks?

• Small commands that run at specific moments in Claude Code or Codex

• They work silently in the background (you won't notice them)

Which Claude Code hooks do we use?

📍 SessionStart - Syncs previous sessions when you start/resume work (Triggers: startup, resume, clear commands)

📦 PreCompact - Syncs full session before context compression (Triggers: manual or automatic context cleanup)

Why we recommend both:

✓ SessionStart ensures nothing is lost between sessions

✓ PreCompact syncs everything before Claude compresses context

Which Codex hooks do we use?

📍 SessionStart - Syncs recent Codex sessions when work starts

🔚 Stop - Syncs after Codex finishes responding

Codex hooks write Vibe-Log commands to Codex hooks.json and enable [features].codex_hooks = true in Codex config.toml. Vibe-Log does not install Codex prompt coach or statusline hooks.

Setup Auto-sync

1. Run npx vibe-log-cli
2. Authenticate with your Github account
3. Enable auto-sync via CLI menu

Supported Coding Engines

Currently supported:

• ✅ Claude Code
• ✅ Codex (manual cloud sync, experimental auto-sync hooks, local standups, local reports)

Future:

• 🔜 Cursor
• 🔜 VS Code

🌍 Cross-Platform - Runs on macOS, Windows, Linux, and any environment with Node.js

🔒 Privacy & Security

<div align="center"> <a href="https://github.com/vibe-log/vibe-log-cli/actions/workflows/npm-publish.yml"><img src="https://img.shields.io/badge/Automated-Releases-success?logo=githubactions" a