dkod

title: Introduction description: What dkod is, how it works, and why AI agent sessions belong in git.

Introduction

dkod captures every AI agent session — the full transcript, the diff, the files touched — and stores it as a git ref inside your repository.

Every agent session, every commit, every repo — searchable across your whole org, without the transcripts ever leaving your git host.

Four components

ComponentWhat it doesCost
dkod CLICaptures agent sessions into git refs. Rust binary, MIT licensed.Free forever
dkod AppDesktop viewer. Timeline, session replay, local search.Free forever
dkod IndexerGitHub App that indexes session refs across an org.Part of team plan
Team DashboardCross-repo session search at dkod.io.Part of team plan

Supported agents

dkod ships adapters for seven agents:

  • Claude Code
  • Codex (OpenAI CLI)
  • Copilot CLI
  • Gemini CLI
  • Cursor
  • OpenCode
  • Factory AI (Droid)

Each adapter knows how to capture the agent's transcript format and normalize it into a dkod session.

How it works

  1. Capture. dkod capture <agent> wraps the agent invocation. When the session ends, the CLI stores the transcript + diff as a git blob under refs/dkod/sessions/<id>.
  2. Push. git push sends the session refs along with your branch. Standard git, no special protocol.
  3. Browse locally. The dkod App reads session refs from the repo and renders a timeline + replay UI. Zero network.
  4. Search across repos. The dkod GitHub App indexes session refs across your org. The team dashboard searches metadata and fetches content live through your GitHub token.

Privacy model

  • Git is the source of truth. Sessions are git objects inside your repo.
  • Transcripts never leave your git host. The indexer stores metadata + embeddings only.
  • Content is fetched live through the user's GitHub OAuth token — same access model as git clone.
  • Redaction is on by default. Built-in patterns strip secrets before storage.

Next steps