Quick Start

Install

curl (recommended)
Homebrew
Build from source
GitHub Releases

curl -fsSL https://oobo.ai/install.sh | bash

Downloads the binary, adds it to PATH, and runs oobo setup automatically.

brew install ooboai/tap/oobo
oobo setup

git clone https://github.com/ooboai/oobo.git && cd oobo
cargo build --release
# binary at target/release/oobo

Platforms: macOS (Apple Silicon, Intel) - Linux (x86_64, ARM64, glibc, musl) - Windows (x86_64) For AI agents and CI (silent, JSON output):

curl -fsSL https://oobo.ai/install.sh | bash -s -- --agent

What Setup Does

oobo setup runs automatically after install. It:

Scans your machine for git projects with AI tool activity
Auto-enables projects where it finds existing sessions
Installs agent lifecycle hooks for supported tools (Cursor, Claude Code, Gemini, etc.)
Installs git hooks (post-commit, pre-push, post-merge, post-rewrite) in enabled projects
Installs a skill file so AI agents can discover oobo

You can re-run it anytime: oobo setup For CI/non-interactive: oobo setup --non-interactive

Enable a Project

Oobo tracks on a per-project basis. During oobo setup, projects with existing AI sessions are auto-enabled. For any new repo (or one that wasn’t picked up by setup), enable it explicitly:

cd ~/my-project
oobo enable

This creates a .oobo/config in the project root and installs git hooks. Without this step, oobo won’t capture anything for that repo.

oobo enable is idempotent - running it again just refreshes hooks.

Drop Your First Anchor

Once a project is enabled, use git normally. Oobo hooks capture AI context automatically:

git commit -m "fix auth middleware"

That’s it. The post-commit hook read your active AI sessions from local tool storage and wrote an anchor - a commit enriched with AI context - to the orphan branch.

See What Happened

oobo                            # scrollable TUI feed of your anchors
oobo anchor show <sha>          # drill into one commit's AI context
oobo blame src/main.rs          # git blame + per-line AI attribution
oobo search "auth bug"          # semantic code search
oobo recall "auth bug"          # search sessions and anchors
oobo sessions                   # list your AI coding sessions
oobo session <id>               # session details, turns, tokens
oobo delta                      # what changed since the last anchor

All commands support --agent (compact text) and --json (full structured):

oobo --agent                    # compact anchor list
oobo anchor show <sha> --json   # full structured anchor data

Time Travel

Navigate through your coding history:

oobo goto <turn-or-sha>         # jump to a turn or commit (auto-stashes)
oobo back                       # return to where you were

Optional: API Key

Add an API key for recall (semantic memory search) and delta (anchor comparison):

oobo settings set key <your_key>

Anchor metadata still syncs through Git - the API key is only for recall and delta features.

Disable a Repo

To stop tracking without deleting existing anchors:

oobo disable

Re-enable anytime with oobo enable.

Repair

If hooks or metadata look stale:

oobo setup --repair             # re-install hooks, re-detect tools
oobo setup --reindex            # force full rescan

Get Started

Usage

Deep Dives

Quick Start

Install

What Setup Does

Enable a Project

Drop Your First Anchor

See What Happened

Time Travel

Optional: API Key

Disable a Repo

Repair

​Install

​What Setup Does

​Enable a Project

​Drop Your First Anchor

​See What Happened

​Time Travel

​Optional: API Key

​Disable a Repo

​Repair

Install

What Setup Does

Enable a Project

Drop Your First Anchor

See What Happened

Time Travel

Optional: API Key

Disable a Repo

Repair