Skip to main content

​
What is oobo?

oobo is a transparent git decorator that enriches every commit with AI context: sessions, tokens, and code attribution. It bridges the gap between your AI coding conversations and your git history. AI coding tools generate conversations, token usage, and context that disappear the moment you close the tab. Meanwhile, git log only shows diffs — it has no idea that Claude wrote that function or that you spent 14k tokens debugging a race condition. oobo solves this problem. On every write operation (commit, push, merge), oobo captures the AI sessions that contributed to the change and writes structured metadata called an anchor.

No workflow changes

Use oobo exactly like git. All commands pass through transparently.

No plugins required

Works with your existing AI tools — no integrations to install.

No cloud required

Everything stays local unless you configure an endpoint.

Read-only access

Never writes to AI tool directories. Privacy-first by design.

​
How it works

Oobo sits between you and git, intercepting write operations to capture AI context:
1

Execute real git command

Oobo runs the actual git commit command unchanged
2

Detect write operation

Intercepts commits, pushes, and merges
3

Read AI sessions

Pulls session data from local tool storage directories
4

Build anchor metadata

Creates structured record: commit + sessions + tokens + attribution
5

Write anchor

Stores in local SQLite DB and git orphan branch oobo/anchors/v1
6

Fire event (optional)

Sends to configured endpoint if transparency mode is enabled
7

Return unchanged

Returns git’s exit code — transparent to your workflow
Read operations (status, log, diff, etc.) pass straight through to git with zero overhead.

​
The anchor concept

An anchor is oobo’s core primitive — it extends a git commit with AI context: 
Git:   commit = diff(files)
Oobo:  anchor = commit + sessions + tokens + attribution
Each anchor records:
  • Which AI sessions contributed
  • Token counts (input/output per model)
  • Code attribution (AI vs human lines)
  • Model used and session duration
  • Session transcripts (local only by default)
Anchors live in:
  1. Local SQLite database (~/.oobo/oobo.db) for fast queries
  2. Git orphan branch (oobo/anchors/v1) that syncs with your repo
The orphan branch is created automatically on your first intercepted commit — metadata travels with your code.

​
Supported AI tools

Oobo integrates with the tools you already use:
ToolSessionsTranscriptsToken StatsAgent Hooks
Cursor✓✓✓✓
Claude Code✓✓✓✓
Gemini CLI✓✓✓✓
OpenCode✓✓✓✓
Codex CLI✓✓✓—
Aider✓✓✓—
GitHub Copilot Chat✓✓✓—
Windsurf✓✓partial—
Zed✓✓✓—
Trae✓✓partial—
All tools are read-only — oobo never writes to AI tool data directories.

​
Agent hooks

For tools that support it (Cursor, Claude Code, Gemini CLI, OpenCode), oobo installs lifecycle hooks that track when agent sessions start and end. This enables real-time session linking during commits, rather than relying on time-window correlation.

​
Why oobo?

For developers

Track which AI sessions contributed to each commit. Understand your AI-assisted coding patterns and productivity.

For teams

See code attribution across your team. Know which changes came from AI assistance vs manual coding.

For agents

Built for autonomous agents that commit constantly. Use --agent flag for structured JSON output on every command.

For compliance

Audit trail of AI involvement. Token usage tracking. Secret redaction with gitleaks patterns.

​
Key features

​
Session browsing

oobo sessions              # Interactive TUI
oobo sessions --all        # Sessions across all projects
oobo sessions search "auth bug"  # Keyword search
The TUI shows source, model, tokens, duration, and title for each session. Select one to scroll through the full conversation.

​
Analytics

oobo stats                 # Tokens, attribution, productivity
oobo stats --project myapp # Per-project
oobo stats --tool cursor   # Per-tool
oobo stats --since 30d     # Time-filtered

​
Enriched commit history

oobo anchors               # Recent commits with AI context
oobo anchors --agent       # JSON output
See which AI sessions contributed to each commit, with token counts and attribution.

​
Developer card

oobo card                  # Generate AI-first developer stats
oobo card --out dev.md     # Save to custom path
Generates a shareable overview of your AI tool usage — sessions, tokens, models, AI code percentage. No project names or private data included.

​
Privacy & security

Local by default

Everything stays in ~/.oobo/. Nothing leaves your machine unless you configure an endpoint.

Read-only

Never writes to AI tool directories. Only reads session metadata.

Secret redaction

Sessions scrubbed with gitleaks patterns before any sharing.

No telemetry

Oobo does not phone home. Your data is yours.
Config files containing API keys are automatically protected with chmod 0600.

​
Next steps

Installation

Get oobo installed on your system

Quick Start

From zero to first commit with AI context

Configuration

Configure endpoints, tools, and transparency mode

For AI Agents

Using oobo from autonomous agents

Build docs developers (and LLMs) love

Get started for freeTalk to us