Skip to main content

Command Categories

Oobo provides three categories of commands:
  1. Project commands - Run inside a git repository
  2. Global commands - Work from anywhere
  3. Git passthrough - Any git command, with AI context capture on write operations

Sessions

Browse and search AI chat sessions

Anchors

View enriched commit history with AI context

Stats

Token usage analytics and code attribution

Projects

Manage all tracked projects

Setup

First-time configuration wizard

Scan

Discover projects and sessions

Share

Share a redacted session

Agent

Print AI agent skill file

The —agent Flag

Every command supports --agent for structured JSON output. This is the primary interface for AI agents and scripting.
oobo sessions --agent            # JSON list of sessions
oobo stats --agent               # Analytics as structured data
oobo anchors --agent             # Enriched commit history as JSON
--agent is a global flag - it works with any command at any position in the argument list.

How —agent Works

oobo sessions
Launches an interactive TUI with arrow key navigation, session preview, and full conversation view.

Git Passthrough

Oobo is a transparent git decorator. Any command not recognized as an oobo subcommand passes straight through to git:
oobo status              # → git status
oobo log --oneline       # → git log --oneline
oobo diff HEAD~1         # → git diff HEAD~1

Write Operations

Write operations (commit, push, merge) execute the git command and capture AI context:
oobo commit -m "fix auth middleware"
# 1. Execute: git commit -m "fix auth middleware"
# 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. Return git's exit code unchanged
Read operations have zero overhead - they pass straight through to git with no interception.

Project Commands

These commands run inside a git repository and operate on the current project:
CommandAliasDescription
sessions-Browse AI chat sessions for this project
anchorsaShow enriched commit history with AI context
share-Share a redacted session
ship-Send AI context to dashboard now
sync-Import anchors from orphan branch
ignore-Stop tracking this repo
unignore-Re-enable tracking

Global Commands

These work from anywhere and manage oobo’s global state:
CommandDescription
setupFirst-time configuration wizard
projectsBrowse and manage all projects
statsToken usage analytics and attribution
cardDeveloper stats card (shareable)
scanDiscover projects and sessions across all tools
indexCompute token analytics for sessions
sourcesData source status and coverage
dashConfiguration overview
authConfigure API keys and remote server
aliasManage git→oobo shell alias
agentPrint AI agent skill file
inspectDiagnose and auto-repair issues
updateCheck for updates or self-update
versionShow version info

Common Patterns

Alias git to oobo

For seamless integration, alias git itself:
oobo alias install      # adds alias git=oobo to your shell rc
Now you can use git commands as normal, and oobo will transparently capture AI context on commits.

Session ID Prefixes

Many commands accept session IDs. You can use short prefixes instead of full UUIDs:
oobo sessions show abc12def      # matches abc12def-3456-7890-...
oobo share abc12                 # prefix match

Filtering and Scoping

oobo sessions --all              # all projects (default: current project)
oobo stats --project myapp       # per-project stats
oobo stats --tool cursor         # per-tool stats
oobo stats --since 30d           # time-filtered

JSON Everywhere

Add --agent to any command for machine-readable output:
oobo sessions list --agent
oobo sessions show <id> --agent
oobo sessions search <q> --agent
oobo projects --agent
oobo stats --agent
oobo card --agent
oobo sources --agent
oobo dash --agent
oobo version --agent
oobo inspect --agent

Next Steps

Sessions

Learn how to browse and export AI chat sessions

Stats

Explore token usage analytics and code attribution

Build docs developers (and LLMs) love