Skip to main content

​
Install

If you have not installed oobo yet, see Installation. The short version: 
# Humans
curl -fsSL https://oobo.ai/install.sh | bash

# Agents (silent, JSON output)
curl -fsSL https://oobo.ai/install.sh | bash -s -- --agent

​
Setup wizard

Run the interactive setup to detect your AI tools and configure oobo: 
oobo setup
The wizard will:
  1. Detect installed AI tools (Cursor, Claude Code, Gemini CLI, etc.)
  2. Let you enable or disable individual tools
  3. Configure transparency mode (metadata only, or metadata + redacted transcripts)
  4. Optionally configure a remote endpoint
  5. Install agent hooks for supported tools (Cursor, Claude Code, Gemini CLI, OpenCode)
  6. Install the skill file at ~/.agents/skills/oobo/SKILL.md
For agents that skip the wizard, see AI Agent Integration for non-interactive setup.

​
Alias git (optional)

For zero-friction usage, alias git to oobo: 
oobo alias install
This adds alias git=oobo to your shell RC file (.zshrc, .bashrc, or config.fish). After reloading your shell, every git commit automatically becomes an enriched commit with anchor metadata. All regular git commands pass straight through. To remove the alias: 
oobo alias uninstall

​
First enriched commit

Use oobo wherever you would use git: 
oobo commit -m "fix auth middleware"
oobo push origin main
Behind the scenes, oobo executed the real git commit, detected the write operation, read any active AI sessions from local tool storage, and wrote an anchor linking the commit to those sessions.

​
See what happened

# Enriched commit history with AI context
oobo anchors

# Browse your AI chat sessions (interactive TUI)
oobo sessions

# Token usage, attribution
oobo stats
All of the above also support --agent for structured JSON output: 
oobo anchors --agent
oobo sessions --agent
oobo stats --agent

​
Discover existing sessions

If you have been using AI tools before installing oobo, scan for existing sessions: 
oobo scan              # discover projects and sessions
oobo index             # compute token counts and analytics
These commands are incremental. They only process new or changed sessions on subsequent runs.

​
Pull billing data from provider APIs (optional)

If you want exact token numbers from your AI provider accounts, configure API keys: 
oobo auth anthropic <sk-ant-admin-key>    # Anthropic Admin API
oobo auth openai <sk-key>                 # OpenAI Admin API
oobo auth google <key>                    # Google AI Studio
This pulls organization-level usage data (per-day, per-model tokens) for the last 30 days and stores it locally. See Tool Integrations for details.

​
Check your setup

Run diagnostics to verify everything is configured correctly: 
oobo inspect           # colored pass/warn/fail output
oobo inspect --fix     # auto-repair common issues
oobo inspect --agent   # machine-readable JSON output
This checks: config file, database, git alias, git hooks, agent hooks, stale sessions, and tool availability.

​
Generate your developer card

After using oobo for a while, generate a shareable stats card: 
oobo card
This prints an overview of your AI tool usage and saves oobo-card.md, a markdown file you can add to your GitHub profile README or share with teams.