Git for agents
(and humans).

Git tracks code.
Nobody tracks work.

AI agents now write significant portions of production code. They commit, push, open PRs, run pipelines. But the trail of how software gets built is fragmented and mostly lost.

The anchor.

Oobo's core primitive. It extends a git commit with AI context: which sessions contributed, token counts, code attribution (AI vs human lines), model used, session duration. Anchors sync via a git orphan branch that travels with your repo.

Git:   commit = diff(files)
Oobo:  anchor = commit + sessions + tokens + attribution

$ oobo commit -m "fix auth middleware"

# under the hood:
1. Execute real git commit
2. Detect write operation
3. Read AI sessions from local tool storage
4. Build anchor: commit + sessions + tokens + attribution
5. Write anchor to local DB + git orphan branch
6. Fire event to endpoint (if configured)
7. Return git's exit code unchanged

Read operations (status, log, diff) pass straight through to git with zero overhead.

Two memories.

Oobo captures two kinds of memory. Together they turn disposable local history into a durable, searchable work record.

Quick start.

Install, setup, use. Then explore what happened.

$ curl -fsSL https://oobo.ai/install.sh | bash
$ oobo setup                        # detects your tools, configures endpoint

$ oobo commit -m "fix auth middleware"
$ oobo push origin main
$ oobo status                       # reads pass through to git

$ oobo anchors                      # enriched commit history with AI context
$ oobo sessions                     # browse AI chat sessions (interactive TUI)
$ oobo sessions search "auth bug"   # search by keyword
$ oobo stats                        # token usage, attribution, analytics
$ oobo stats --tool cursor --since 7d

$ oobo alias install                # adds alias git=oobo to your shell rc
$ git commit -m "now this is oobo"  # transparent, you don't think about it
$ oobo card                         # shareable developer stats card

Built for agents.

Agents commit code constantly, across tools, often in parallel. Without oobo, there is no record of which agent wrote what, how many tokens it took, or which conversation produced a given function.

Every command supports --agent for structured JSON output. The installer has a silent mode. Agent lifecycle hooks track sessions in real time for Cursor, Claude Code, Gemini CLI, and OpenCode.

$ curl -fsSL https://oobo.ai/install.sh | bash -s -- --agent
{"status":"ok","version":"0.1.0","binary":"/home/agent/.oobo/bin/oobo","platform":"linux-x86_64"}

$ oobo sessions list --agent         # JSON array of sessions
$ oobo anchors --agent               # enriched commit history as JSON
$ oobo stats --agent                 # analytics as structured data
$ oobo inspect --agent               # diagnostics as JSON

$ oobo agent                         # prints skill file to stdout
# Installed at ~/.agents/skills/oobo/SKILL.md during setup.
# Cursor, Claude Code, Codex, Gemini CLI, OpenCode scan this path.

The bigger picture.

The CLI is the foundation. On top of it, Oobo builds a full engineering intelligence layer for teams where humans and agents build software together.

The more autonomous software creation becomes, the more valuable execution truth becomes.

10 tools. Zero plugins.

Oobo discovers and indexes AI sessions by reading existing local data. All access is read-only. No plugins, no browser extensions, no API keys required.

Private by default.

• Read-only. never writes to AI tool directories
• Local by default. everything stays in ~/.oobo/. Nothing leaves your machine unless you configure an endpoint
• Secret redaction. sessions are scrubbed with gitleaks patterns before any sharing
• No telemetry. oobo never collects or sends data unless you explicitly opt in
• Transparency is opt-in. anchor metadata always syncs via git. Transcripts stay local unless you turn transparency on

One product. Two memories.

Give every commit memory.