Overview
Theanchors command shows enriched commit history with AI context. Each anchor extends a git commit with:
- Linked AI sessions
- Token counts
- AI vs human code attribution
- Model information
- Contributors (humans + agents)
anchors has a short alias: aWhat is an Anchor?
An anchor is oobo’s core primitive — it extends a git commit with AI context:- Which AI sessions contributed
- Token counts per session
- Code attribution (AI vs human lines)
- Model used
- Session duration
- Files changed
oobo/anchors/v1) that travels with the repo.
Command Syntax
Number of commits to show.
Output as JSON.
Examples
Show recent anchors
Show more commits
JSON output for agents
Output Fields
Human Output
Each anchor shows:- Indicator - ◆ (AI-assisted) or ● (human-only)
- Commit hash - First 7 characters (yellow)
- Message - Commit message
- Contributors - Humans + agents with models
- Diff stats - Lines added/deleted, files changed, AI percentage
- Attribution - AI vs human line counts
- Sessions - Linked sessions with tokens
- Summary - AI-generated summary (if available)
JSON Output
| Field | Type | Description |
|---|---|---|
commit_hash | string | Full commit SHA |
message | string | Commit message |
author | string | Git author |
author_type | string | human, assisted, or autonomous |
contributors | array | Humans and agents who contributed |
branch | string | Branch name |
committed_at | number | Unix timestamp |
files_changed | array | List of changed file paths |
lines_added | number | Total lines added |
lines_deleted | number | Total lines deleted |
file_changes | array | Per-file attribution |
ai_lines_added | number | Lines added by AI |
ai_lines_deleted | number | Lines deleted by AI |
human_lines_added | number | Lines added by human |
human_lines_deleted | number | Lines deleted by human |
ai_percentage | number | Percentage of code written by AI (0-100) |
sessions | array | Linked AI sessions |
summary | string | AI-generated summary |
intent | string | Commit intent (fix, feat, refactor, etc.) |
Contributor Object
| Field | Type | Description |
|---|---|---|
name | string | Contributor name (human or tool name) |
role | string | human or agent |
model | string | AI model (for agents only) |
Session Object
| Field | Type | Description |
|---|---|---|
session_id | string | Full session UUID |
agent | string | Tool name (cursor, claude, etc.) |
model | string | AI model used |
link_type | string | explicit or correlation |
input_tokens | number | Input tokens consumed |
output_tokens | number | Output tokens generated |
files_touched | array | Files modified in session |
Author Types
- human - No AI involvement detected
- assisted - Collaboration between human and AI
- autonomous - Fully AI-generated (e.g., agent commit)
How Anchors Are Created
Anchors are recorded automatically when you commit through oobo:Anchors are created after the commit succeeds, so they never interfere with your git workflow.
Syncing Anchors
Anchors sync automatically via theoobo/anchors/v1 orphan branch:
- First commit - Creates orphan branch
- Every push - Pushes anchors
- Clone/pull - Import with
oobo sync
Use Cases
Review AI contributions
Export commit history with AI context
Find commits by AI percentage
See which sessions contributed to a commit
Next Steps
Sessions
View the AI sessions linked to your commits
Stats
See code attribution and AI percentage across your project
