Cadence CLI stores AI coding agent session logs in dedicated Git refs:
refs/cadence/sessions/datarefs/cadence/sessions/index/branchrefs/cadence/sessions/index/committerIt adds provenance for AI-assisted development without altering your commit history.
Prerequisites:
- Git
macOS and Linux:
curl -sSf https://raw.githubusercontent.com/TeamCadenceAI/cadence-cli/main/install.sh | shWindows (PowerShell):
iwr -useb https://raw.githubusercontent.com/TeamCadenceAI/cadence-cli/main/install.ps1 | iexIf ~/.local/bin is not on your PATH, add it:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrcBuild from source:
cargo build --release- Install hooks:
cadence install-
Make commits as usual.
-
Inspect session refs:
git show-ref refs/cadence/sessions/data- Diagnose install issues (hooks, rewrite safety):
cadence doctorCadence installs global Git hooks that scan for recent AI session logs, then stores canonical session objects and indexes after each commit. It also configures Git note rewrite settings so notes follow rewritten commits during rebase/amend. Notes can be synced alongside commits without modifying commit history.
If a repository still has the legacy ref refs/notes/ai-sessions, Cadence will migrate it to
refs/cadence/sessions/data when new session data is ingested.
- Claude Code
- Codex
- Cursor
- GitHub Copilot
- Antigravity
- Warp
Note: Warp stores sessions in a local SQLite database. In some local-only cases the assistant output may be missing, so Cadence stores prompts/context without responses.
To encrypt session logs before attaching (local + API recipients):
cadence keys setupCadence uses built-in OpenPGP (Rust) and stores an encrypted private key in ~/.cadence/cli/.
The passphrase is stored in your OS keychain.
- Remove hooks:
git config --global --unset core.hooksPath
rm -rf ~/.git-hooks- Remove the binary from your PATH (for example
~/.local/bin/cadence).
See LICENSE.md.