setup

​

Overview

1. Scans for AI tools - Detects installed tools (Cursor, Claude, Gemini, etc.)
2. Discovers sessions - Finds existing projects and sessions
3. Configures tools - Enables/disables tools individually
4. Sets up remote server - Optionally configures API endpoint and key
5. Installs skill file - Writes ~/.agents/skills/oobo/SKILL.md for agent discovery
6. Configures git alias - Optionally installs alias git=oobo in your shell
7. Installs hooks - Sets up git hooks and agent lifecycle hooks

oobo setup

​

What It Detects

​

Supported AI Tools

​

What Gets Configured

[server]
url = "https://your-endpoint.example.com"
api_key = "sk_..."

[transparency]
mode = "off"           # off | on

[cursor]
enabled = true

[claude]
enabled = true

[gemini]
enabled = false

# ... other tools

​

Setup Flow

​

1. Tool Detection

• Session directories - Tool-specific storage locations
• Configuration files - Tool config in home directory
• Running processes - Active tool instances

  scanning for AI tools...
  found: Cursor (42), Claude (18), Gemini CLI (5)
  3 project(s), 65 session(s)

​

2. Interactive Configuration

• Tool selection - Enable/disable each detected tool
• Remote server - Optional API endpoint URL
• API key - Authentication for remote server
• Transparency mode - Share transcripts or metadata only
• Git alias - Install alias git=oobo

​

3. Installation

• Tells AI agents how to use oobo
• Includes install command, JSON schemas, usage examples

alias git=oobo

• post-commit - Captures AI context after commits
• pre-push - Syncs anchors to remote

• Session start/end tracking
• Real-time session correlation

  Configuration saved to /Users/dev/.oobo/config.toml
  Git alias installed (git = oobo)
  Agent skill installed at ~/.agents/skills/oobo/

  Agent lifecycle hooks installed:
    cursor
    claude
    gemini

  Git hooks installed for this project:
    post-commit
    pre-push

  You're all set! Try:
    oobo sessions   -- view your AI chat sessions
    oobo scan       -- discover projects and sessions
    oobo dash       -- interactive dashboard

​

Configuration Options

​

Server Configuration

[server]
url = "https://oobo.example.com"
api_key = "sk_your_api_key"

​

Transparency Mode

• Off (default) - Only metadata syncs (sessions, tokens, file paths). Transcripts stay local.
• On - Full transcripts included in anchors and events.

[transparency]
mode = "off"           # off | on

​

Tool Configuration

[cursor]
enabled = true

[claude]
enabled = false

​

Re-running Setup

• Add new tools - Enable tools you installed after initial setup
• Update server - Change API endpoint or key
• Toggle transparency - Switch between metadata-only and full transcripts
• Reinstall hooks - Fix broken or missing hooks

oobo setup

​

Manual Configuration

# Edit config
vim ~/.oobo/config.toml

# Verify changes
oobo dash

​

Skipping Interactive Prompts

# Use defaults (no prompts)
oobo scan
oobo index

• Custom server configuration
• Enabling/disabling specific tools
• Installing git alias and hooks

​

What Gets Created

​

Files

~/.oobo/
  config.toml              # Main configuration
  oobo.db                  # SQLite database
  skills/oobo/SKILL.md     # Agent skill file

~/.agents/skills/oobo/     # Symlink to ~/.oobo/skills/oobo/

.git/hooks/                # Per-project hooks
  post-commit
  pre-push

​

Hooks

• Created in .git/hooks/ for the current repo
• post-commit captures AI context
• pre-push syncs anchors to remote

• Cursor: ~/.cursor/hooks/
• Claude: ~/.config/claude/hooks/
• Gemini CLI: ~/.gemini/hooks/
• OpenCode: ~/.config/opencode/hooks/

​

Uninstalling

# Remove git alias
oobo alias uninstall

# Remove config and database
rm -rf ~/.oobo

# Remove agent skill symlink
rm -rf ~/.agents/skills/oobo

# Remove per-project git hooks (run in each project)
rm .git/hooks/post-commit .git/hooks/pre-push

​

Troubleshooting

​

No tools detected

1. Check tool installation - Ensure AI tools are installed
2. Run the tool once - Create at least one session
3. Check paths - Tools must be in standard locations

# Force a scan
oobo scan

​

Hooks not installed

# Re-run setup from inside the repo
cd /path/to/repo
oobo setup

​

Skill file not found

# Verify it exists
ls -la ~/.agents/skills/oobo/SKILL.md

# Print it
oobo agent

# Re-run setup to recreate
oobo setup

​

Next Steps