The git-native flight recorder for AI coding agents
Which prompt wrote this line? Did the agent exceed its brief? dkod blame and dkod drift answer both — from session records stored in your own repo. Transcripts are never stored outside your git host.
Your team ships code with AI agents every day, but nobody knows what they did or why. Agent transcripts vanish when the session ends. When something breaks, you’re left reverse-engineering diffs.
dkod captures every agent session — Claude Code, Codex, Copilot CLI, Cursor, Factory droid, Gemini CLI, opencode — the full transcript, the diff, the files touched, with secrets redacted at capture time, on by default. Everything is stored as a git ref inside your repo and rides on git push, so there’s nothing new to deploy.
Then ask the questions git can’t answer: dkod blame traces any line back to the agent session and prompt that produced it. dkod drift flags sessions where the agent did materially more — or other — than it was asked.
Every AI coding agent — Claude Code, Codex, Copilot CLI, Cursor, Factory droid, Gemini CLI, opencode — now leaves a permanent record in your repo. dkod captures the full transcript, the diff, the files touched, and stores everything as a git ref. No external database, no cloud dependency. Sessions ride on git push and git fetch.
Then interrogate that record: dkod blame traces any line back to the agent session and prompt that produced it, and dkod drift flags sessions where the agent did more than it was asked. For teams, the hosted dashboard searches sessions across every repo in your org. The indexer persists metadata only — transcripts are fetched on demand under your token and never stored outside your git host.
Which prompt wrote this line?
Capture every agent session, then interrogate it. Per-line provenance with blame, scope auditing with drift — all from records that stay in your git host.
dkod blame
For any line in your codebase: which agent session produced it, and which prompt asked for it. git blame tells you who committed — dkod blame tells you why it exists.
dkod drift
Flags sessions where the agent did materially more — or other — than it was asked. Catch scope creep before review, not after the incident.
Capture from 7 agents
Claude Code, Codex, Copilot CLI, Cursor, Factory droid, Gemini CLI, opencode. Sessions live in refs/dkod/sessions/ inside your repo — no external database.
Privacy by Architecture
Transcripts are never stored outside your git host. Secrets are redacted at capture time, on by default. Zero third-party data-at-rest.
How it works
Init
Run dkod init in any repo. Hooks are installed, config is created.
Capture
Wrap your agent with dkod capture <agent>. The transcript and diff are stored as a git ref.
Push
Push your branch. Sessions ride along — standard git, no special protocol.
Interrogate
Run dkod blame to trace any line back to the session and prompt that wrote it, and dkod drift to flag sessions that exceeded their brief.
Init
Run dkod init in any repo. Hooks are installed, config is created.
Capture
Wrap your agent with dkod capture <agent>. The transcript and diff are stored as a git ref.
Push
Push your branch. Sessions ride along — standard git, no special protocol.
Interrogate
Run dkod blame to trace any line back to the session and prompt that wrote it, and dkod drift to flag sessions that exceeded their brief.
Get started
One binary, 30 seconds to install. Capture your first session in under a minute.
Install the CLI
30 secondscurl -fsSL https://raw.githubusercontent.com/dkod-io/dkod-cli/main/install.sh | shOne binary. Captures sessions from 7 agents. Also available via brew install dkod-io/tap/dkod or cargo install dkod-cli.
Quickstart guideFrequently Asked Questions
dkod captures AI agent sessions into git refs so your team has full visibility into what every agent did and why. dkod blame traces any line to its session and prompt; dkod drift flags sessions that exceeded their brief. The CLI is free and MIT-licensed. The hosted team layer adds org-wide cross-repo session search.
Claude Code, Codex, Copilot CLI, Cursor, Factory droid, Gemini CLI, and opencode. Each agent has a dedicated adapter that captures its transcript format.
Inside your git repo as custom refs (refs/dkod/sessions/). The indexer persists metadata only — transcripts are fetched on demand under your token and never stored outside your git host.
The dkod CLI is fully open source under the MIT license, and the Free plan includes hosted team features for up to 5 seats. The Team plan ($15/seat/month, in beta) adds unlimited repos and org-wide search.
Redaction is on by default. Built-in patterns strip AWS access keys, GitHub tokens, OpenAI keys, Stripe keys, and environment variable assignments before anything is stored. You can add custom patterns in .dkod/config.toml.
No. The CLI works with zero account — capture and blame run fully local. Only the team dashboard requires GitHub OAuth sign-in.
See what your agents are building
Install in 30 seconds — free, no account required.