GitHub - re-cinq/claudit: Save coding agents' conversations in Git Notes, automatically

claudit

Save AI coding conversations as Git Notes. Claude. Audit. See what we did there? 🥁

Install

curl -fsSL https://raw.githubusercontent.com/re-cinq/claudit/master/scripts/install.sh | bash
# ...In a Git repo
claudit init --agent=<agent>

Where <agent> is claude (default), codex, copilot, gemini, or opencode.

Now work with your coding agent as you would normally. Whenever you or the agent commit, the conversation since the last commit will be attached to that commit as a Git Note.

Supported Agents

Usage

See what conversations you have:

Search through past conversations:

claudit search "authentication"          # Text search
claudit search --agent claude --branch main  # Filter by metadata
claudit search "jwt" --regex --context 2     # Regex with context lines

Get a quick summary of a conversation:

claudit summarise        # Summarise HEAD conversation
claudit tldr HEAD~1      # Alias, works the same way
claudit tldr --focus="security"  # Prioritise security-related changes

Resume a past session:

claudit resume abc123    # By commit SHA
claudit resume HEAD~3    # By git ref

View in your browser:

Pull down conversations from a repo you cloned:

claudit vs Entire

Why?

In order to understand how and why a commit was made, we need to see the conversation that led to it.

How It Works

Claudit uses Git Notes to attach conversations to commits, stored under refs/notes/claude-conversations to keep git log clean. When you run claudit init, it sets up hooks so:

1. When the coding agent makes a commit, the conversation is saved automatically
2. When you make a commit during an agent session, it's saved too
3. When you push/pull, conversations sync with the remote

No extra steps needed during your normal workflow.

To view notes directly with git: git log --notes=claude-conversations

Commands

Requirements

• Git
• One of the supported coding agents (Claude Code, Codex CLI, Copilot CLI, Gemini CLI, or OpenCode)

Multi-Developer Sync

When multiple developers use claudit on the same repository, each person's conversation notes are synced automatically via git push/pull hooks. Notes from different developers are merged seamlessly because they typically annotate different commits.

If the remote notes ref has diverged (e.g. two developers pushed notes without pulling first), claudit sync push will reject the push and advise you to pull first:

claudit sync pull   # Fetches and merges remote notes
claudit sync push   # Now succeeds

In the rare case where two developers annotate the exact same commit SHA, both notes are preserved by concatenation — no data is lost.

Git Worktrees

Claudit is worktree-safe. If you use git worktree to work on multiple branches simultaneously, each worktree sees only the conversations for commits on its own branch. Hooks are shared across worktrees (as git requires), but claudit list and claudit show are scoped to the current HEAD.

Local Rebase

Conversation notes automatically follow commits when you rebase. During claudit init, the notes.rewriteRef git config is set to refs/notes/claude-conversations, which tells git to remap notes to the new commit SHAs during rebase. No manual steps are needed.

If you initialized before this config was added, run claudit init again or set it manually:

git config notes.rewriteRef refs/notes/claude-conversations

You can verify the config is set with claudit doctor.

GitHub Rebase Merge

When a PR is merged via GitHub's "Rebase and merge" strategy, the commits get new SHAs on the target branch. Since this happens server-side, git's notes.rewriteRef does not apply and notes remain keyed to the original (now-orphaned) commit SHAs.

Claudit handles this automatically. After you pull a rebase-merged PR, the post-merge hook runs claudit remap, which:

1. Finds notes on commits that are no longer on any branch (orphaned)
2. Uses git patch-id to match each orphaned commit to its rebased counterpart by diff content
3. Copies the note to the new commit SHA (the original note is also kept)

For this to work, the local feature branch must be deleted or pruned so the old commits become orphaned. If your GitHub repo is configured to auto-delete branches after merge, this happens naturally when you git pull with fetch.prune=true (or git fetch --prune). Otherwise, delete the branch manually first:

git branch -D feature-branch
claudit remap

You can also run claudit remap at any time — it reports how many notes were remapped and how many remain unmatched. Unmatched notes are left in place, not deleted.

Note: Remap works with GitHub's "Rebase and merge" strategy. It does not support "Squash and merge", which combines all commits into one new commit with no 1:1 mapping to copy notes from.

License

AI Native Application License (AINAL) — see LICENSE.