$ join clog
// get set up in a few simple steps and start tracking your claude code journey
// prerequisites
// setup
One command does everything — sets up your GitHub repo, runs your first sync, and optionally configures automatic background syncing.
npx @jaobrown/clog initYour profile appears on the leaderboard immediately. If you enabled automatic syncing, your stats stay up to date in the background — no manual work needed.
// faq
Where does the data come from?
clog reads your local Claude Code session data from ~/.claude/projects/. Sync includes summary/activity metadata plus project names and session titles/timestamps/durations for your public profile. No conversation content is ever accessed.
Is my data private?
Your clog repo is public on GitHub so others can see your stats. No conversation content or code is included. clog also excludes local project paths, per-session git branches, and per-session model IDs from synced data.
How are streaks calculated?
A streak is consecutive days with at least one Claude Code session. Your current streak resets if you miss a day. The streak continues if your last session was yesterday or today.
How often should I sync?
Set up automatic syncing with 'clog schedule' and never think about it again — choose anywhere from 1x to 12x per day. Or run 'clog sync' manually whenever you want.
What if I have sensitive data in my Claude Code sessions?
You can redact project names and session titles using the `clog redact` command, or set up redactions during init. Redacted projects still count toward your totals, but names are hidden everywhere clog syncs data.