Skip to main content

​
What is oobo?

Oobo is a developer memory tool. It sits beside git and gives every commit context about which AI wrote what, how many tokens it took, and what the agent was thinking. It is not a git wrapper. You run git for git things. You run oobo for memory things.

​
The Problem

Your team uses AI coding tools every day - Cursor, Claude Code, Copilot, Codex, Gemini - but once the code is committed, all context is lost. Six months later, nobody knows:
  • Which lines were AI-generated
  • What conversation produced them
  • How much it cost
  • Who approved it

​
The Solution: Anchors

An anchor is oobo’s core primitive. It extends a git commit with AI context: 
Git commit  =  diff + message + author + timestamp
Anchor      =  commit + sessions + tokens + attribution
Each anchor records:
  • Which AI sessions contributed to the commit
  • Token counts (input, output, cache)
  • Code attribution (AI vs human lines, per-file and per-line)
  • Model used and session duration
  • Tool calls, subagent activity, and thinking time
Anchors live on a git orphan branch (oobo/anchors/v1) that travels with the repo. No external dependencies, no cloud required.

​
How It Works

You commit normally:  git commit -m "fix auth middleware"

  1. Post-commit hook fires automatically
  2. Oobo reads active AI sessions from local tool storage
  3. Builds an anchor: commit + sessions + tokens + attribution
  4. Writes anchor to the git orphan branch
  5. On push, anchor data travels with your code
Git operations work exactly as before. Oobo captures context via hooks, never by wrapping git.

​
What You Can Do With It

oobo                            # scrollable feed of enriched commits
oobo blame src/main.rs          # git blame + who (AI/human) wrote each line
oobo search "auth bug"          # semantic code search
oobo recall "auth bug"          # search sessions and memory
oobo delta                      # what changed since the last anchor
oobo goto <turn>                # time-travel to any point in a session

​
What It Is (and Isn’t)

oobo isoobo is not
A standalone binary alongside gitA git wrapper or alias
A git-native metadata store (orphan branch)A cloud-first SaaS
A 15-tool observer (passive, read-only)A plugin for any specific editor
Zero-config (auto-detects tools on commit)Something that requires scanning or indexing

​
Supported Tools

ToolSessionsTranscriptsTokensHooks
Cursor✓✓estimated✓
Claude Code✓✓native✓
Gemini CLI✓✓native✓
OpenCode✓✓native✓
Codex CLI✓✓native-
Aider✓✓native*-
GitHub Copilot✓✓estimated-
Zed✓✓native-
Continue✓✓estimated✓
Factory Droid✓✓estimated✓
Windsurf✓---
Trae✓---
Amp✓✓estimated-
Junie✓✓estimated-
Kiro✓✓estimated✓
All integrations are read-only for session data - oobo never modifies any tool’s conversation history. During setup, it writes hook configs to tool settings files. Native = tool stores exact token counts. Estimated = oobo calculates via tiktoken (marked with is_estimated: true). *Aider native tokens require user configuration (see Tool Integrations).

​
Architecture

  • Local-first: Config in ~/.oobo/, anchors on the orphan branch. Metadata travels only where your code already goes (your git remote).
  • Read-only data access: Never modifies AI tool conversation history. Writes hook configs during setup.
  • Zero-config: Tool detection is automatic on every commit.
  • Three output modes: Pretty (TUI), --agent (token-efficient text), --json (structured).