FileChange

Overview

The FileChange struct provides detailed attribution for individual files modified in a commit. It tracks how many lines were added/deleted and whether those changes were made by AI, human, or both.

FileChange Fields

path

string

required

The file path relative to the repository root.

lines_added

integer

required

Number of lines added to this file.

lines_deleted

integer

required

Number of lines deleted from this file.

attribution

FileAttribution

How this file’s changes were authored.See FileAttribution enum for possible values.

agent

string

Which agent touched this file (if attribution is ai or mixed).Examples: "cursor", "claude", "windsurf"

FileAttribution Enum

Describes how a file’s changes were authored.

Value	Description
`ai`	AI agent wrote/edited this file (file appears in tool’s `files_touched`)
`human`	Human wrote this file (no AI session touched it)
`mixed`	Both AI and human contributed (AI session active but file not in `files_touched`)

The mixed attribution occurs when an AI session was active during the commit, but the specific file wasn’t explicitly tracked in the session’s files_touched list. This often happens with:

Manual edits during an AI session
Files the AI suggested changes for but the human implemented
Configuration or metadata files modified by the developer

Example JSON

{
  "path": "src/main.rs",
  "lines_added": 10,
  "lines_deleted": 3,
  "attribution": "ai",
  "agent": "cursor"
}

Optional fields attribution and agent are omitted from JSON when not available or when no AI session was active.

Attribution Logic

Show How oobo determines attribution

Check for active sessions: If no AI sessions were linked to the commit, all files are human
Look at files_touched: Each session reports which files it modified
- If a file appears in files_touched → ai
- If not in files_touched but session was active → mixed
- If no session was active → human
Multiple sessions: If multiple AI agents worked on the same commit, oobo uses the most recent session that touched each file
Fallback: When tool doesn’t report files_touched (e.g., Aider, Claude CLI), attribution may be omitted or use heuristics

Show Example: Assisted commit workflow

Imagine a commit where Cursor AI made changes to src/lib.rs and src/utils.rs, but you manually edited Cargo.toml while the session was active:

[
  {
    "path": "src/lib.rs",
    "lines_added": 15,
    "lines_deleted": 2,
    "attribution": "ai",
    "agent": "cursor"
  },
  {
    "path": "src/utils.rs",
    "lines_added": 8,
    "lines_deleted": 0,
    "attribution": "ai",
    "agent": "cursor"
  },
  {
    "path": "Cargo.toml",
    "lines_added": 1,
    "lines_deleted": 0,
    "attribution": "mixed",
    "agent": "cursor"
  }
]

The commit’s author_type would be assisted because you collaborated with AI.

Anchor - The parent commit structure that contains file changes
SessionLink - Session metadata that provides files_touched data
Contributor - High-level contributor attribution

Data Structures

Overview

FileChange Fields

FileAttribution Enum

Example JSON

Attribution Logic

Build docs developers (and LLMs) love

Data Structures

​Overview

​FileChange Fields

​FileAttribution Enum

​Example JSON

​Attribution Logic

​Related Types

Build docs developers (and LLMs) love

Overview

FileChange Fields

FileAttribution Enum

Example JSON

Attribution Logic

Related Types