Hey HN! I built VibeTime because I wanted to know how much I was spending on Claude Code and how my usage compared to other developers.
It started when I realized I had no idea how much I was actually spending on AI coding assistants. The ccusage tool by @ryoppippi was great for local tracking, but I wanted to:
- See my usage trends over time with charts
- Compare my usage with the community
- Access my data from anywhere
- Track usage across multiple machines
Technical details:
- CLI: TypeScript wrapper around ccusage with cloud sync
- Web: SvelteKit on Cloudflare Workers with D1 database
- Auth: Lucia Auth with OAuth (Google/GitHub/Facebook)
- Privacy: All ccusage features work offline, sync is optional
Quick start:
npm install -g vibetime
vibetime daily # Works immediately, no setup
It started when I realized I had no idea how much I was actually spending on AI coding assistants. The ccusage tool by @ryoppippi was great for local tracking, but I wanted to:
- See my usage trends over time with charts - Compare my usage with the community - Access my data from anywhere - Track usage across multiple machines
Technical details: - CLI: TypeScript wrapper around ccusage with cloud sync - Web: SvelteKit on Cloudflare Workers with D1 database - Auth: Lucia Auth with OAuth (Google/GitHub/Facebook) - Privacy: All ccusage features work offline, sync is optional
Quick start: npm install -g vibetime vibetime daily # Works immediately, no setup
The web dashboard is at https://vibetime.ekusiadadus.workers.dev
I'd love feedback on: - The onboarding experience - What other metrics would be useful to track - Ideas for the ranking/gamification aspects
Happy to answer any questions!