Which projects actually
drive your AI usage?
Some codebases generate far more AI activity than others. Vibenalytics breaks down sessions, usage, tool calls, and API-equivalent value per project so attribution is finally visible.
Projects
5 activevibenalytics-app
42 sessions
marketing-web
28 sessions
rust-cli
19 sessions
design-system
14 sessions
api-gateway
8 sessions
What you get.
All projects, one screen
Stop switching between tabs. Every project's sessions, usage, and tool patterns in a single sortable view.
See which projects drive usage
Side-by-side comparison makes it obvious which projects generate the most activity and which ones stay quiet.
Per-project timelines
Drill into any project to see usage over time. Track how token consumption evolves as your codebase grows.
Language breakdown per project
See which programming languages Claude works with most in each project - lines added and removed by file extension.
Tool usage per project
Different projects use different tools. See Read, Edit, Bash, and MCP tool distribution for each codebase.
Custom project names
Rename projects to meaningful labels. Path hashes stay private - you control what appears in your dashboard.
Explore other use cases
One dashboard. Every project.
Projects are auto-detected from your workspace paths, then tracked as separate streams of usage.
curl -fsSL https://vibenalytics.dev/install.sh | bash