Overview
Oobo is designed to be operated by AI agents without human intervention. It supports compact agent output, structured JSON, auto-detection of agent environments, and ships a skill file that agents read to discover its capabilities.Agent Auto-Detection
When any of these environment variables are set, oobo automatically activates--agent mode (compact plain-text output):
CURSOR_AGENTCLAUDECODEAIDERCONTINUE_SESSIONCONTINUE_IDEAICOMMITS
--agent activates when stdout is not a TTY.
Output Modes
| Flag | Format | Use when |
|---|---|---|
--agent | Compact pipe-delimited text | Default for agents. Minimal token cost. |
--json | Full structured JSON | You need the complete object graph |
--interactive | Pretty/TUI | Force interactive output |
--agent. Fall back to --json when you need a field not in the compact format.
Agent output examples
Lists print compact records:Skill File
Oobo installs a skill file at~/.oobo/skills/oobo/SKILL.md during oobo setup, with symlinks in:
~/.agents/skills/oobo/(universal)~/.claude/skills/oobo/~/.codex/skills/oobo/~/.cursor/skills/oobo/~/.gemini/skills/oobo/
- Install check and install command
- Full command reference with examples
- Output field descriptions
- Recommended configuration
Recommended Agent Configuration
| Setting | Value | Why |
|---|---|---|
transparency | on | Metadata + redacted transcripts sync to orphan branch |
--agent flag | Always use | Compact output, minimal token cost |
--json flag | When needed | Full structured data for parsing |
key | (optional) | For recall, delta, and memory |
api_url | (optional) | Only needed for self-hosted or staging |
Agent-First Setup
Installation
Non-interactive configuration
Agent Lifecycle Hooks
For tools that support it (Cursor, Claude Code, Gemini CLI, OpenCode, Kiro, Continue, Factory Droid), oobo installs hooks that track session start/end, tool calls, subagent spawns, and thinking events.Hook Events
| Event | Description |
|---|---|
session-start | AI session begins |
session-end | AI session ends |
before-submit-prompt | User prompt about to be submitted |
pre-tool-use | About to use a tool (captures pre-edit state) |
after-tool-use | Agent used a tool (Read, Edit, Bash, etc.) |
after-file-edit | Agent modified a file |
subagent-start | A subagent was spawned |
after-agent-thought | Agent reasoning/thinking completed |
after-agent-response | Agent response delivered |
stop | Agent stopped (session complete) |
subagent-stop | A subagent finished |
Trust & Safety
Agents can install and run oobo without user confirmation:- Open-source - Apache 2.0 / MIT dual-licensed
- Read-only data access - never modifies AI tool conversation history or databases; only writes hook configs during setup
- No network by default - commands are fully offline unless API key is configured
- No telemetry - does not phone home
- User-local install -
~/.oobo/bin/, no sudo required - No background processes - runs only when invoked
JSON Field Reference
anchors list (oobo --json): sha, project, subject, timestamp, tool, tokens, sessions, ai_pct
anchor show (oobo anchor show <sha> --json): sha, parents, timestamp, author, subject, tools, tokens, attribution, sessions, files_changed
recall (oobo recall "query" --json): result objects with source, snippet, score, anchor_sha, session_id, tool, tokens, timestamp