Overview
Oobo is designed to be used by AI agents, not just humans. Every command supports the--agent flag for structured JSON output, and oobo ships with a skill file that agents can read to discover its capabilities.
The —agent flag
Add--agent to any command for structured JSON output. It is a global flag that works on every command.
--agent instead of --json. The --agent flag is the single entry point for machine-readable output.
Skill file
Oobo installs a skill file at~/.agents/skills/oobo/SKILL.md during oobo setup. This file describes oobo’s capabilities in a format that AI coding agents (Cursor, Claude Code, Codex, Gemini CLI, OpenCode) can read and understand.
To print the skill file:
- Install check (
command -v oobo) and install command (curl -fsSL https://oobo.ai/install.sh | bash -s -- --agent) - All available commands with examples
- JSON response field descriptions for each command
- Agent configuration recommendations
- Architecture overview
How agents discover oobo
Most AI coding tools scan~/.agents/skills/ (or similar paths) for skill files. When an agent finds oobo’s skill, it learns:
- That
oobois available as a CLI tool - What commands it can run (sessions, anchors, stats, etc.)
- What JSON fields to expect in responses
- How to use
--agentfor machine-readable output
Recommended agent settings
| Setting | Value | Why |
|---|---|---|
transparency.mode | on | Metadata + redacted transcripts sync with repo for team visibility |
git.alias_enabled | true | Automatic enrichment on every commit |
server.sync | true | Auto-push anchor data to backend on every commit |
--agent flag | Always use | Structured JSON output for parsing |
Agent lifecycle hooks
Oobo installs lifecycle hooks into supported AI tools so it can track when sessions start and end. This enables real-time session linking during commits.Supported hook targets
| Tool | Hook mechanism |
|---|---|
| Cursor | MCP server config or Rules file |
| Claude Code | CLAUDE.md project file |
| Gemini CLI | GEMINI.md project file |
| OpenCode | AGENTS.md project file |
How hooks work
When an AI agent starts a session, the hook calls:.git/oobo-sessions/<id>.json. When oobo intercepts a commit, it reads these files to link active sessions to the anchor.
When the session ends:
Agent-first setup
Installation
The install script supports--agent for machine-friendly output:
--agent, the installer:
- Suppresses colors and progress messages
- Outputs a single JSON result on success:
{"status":"ok","version":"...","binary":"...","platform":"..."} - Outputs JSON errors on failure:
{"error":"..."} - Still adds oobo to PATH (both shell RC and current session)
