Changelog

Since the big release of 1.2 we've shipped a lot of smaller fixes to make sure attribution survives across some of the latest ways agents like using worktrees and hardened subagent support.

Bash

Thanks to a big efforts from @jwiegley code that ends up in the repo as the result of Agents running bash commands is properly attributed. For instance - if an agent ran a command to generated a database migration, that sql file would be attributed to that Agent session and the exact bash command that it appeared in. There's some amazing code here, heavilly tested, and highly optimized to work in the background. Great work!

Agent Support

• Pi - the unix-principles inspired agent of choice for everyone's Claws. Now supported. @siarhei-belavus
• Firebender — checkpoint preset and tool-call filtering for Firebender — by @kevo1ution
• Cursor moved to JSONL — Cursor checkpoint storage migrated from sqlite to JSONL

Bug Fixes

• Respect CLAUDE_CONFIG_DIR — install-hooks and skills now honor the env var
• Fix stats for renamed files — git ai stats no longer double-counts renames
• Worktree checkpoint routing — checkpoints route to the correct linked worktree when CWD is the main repo

Git AI 1.2 is here. Read the full story in Git AI Everywhere — the short version: Git AI no longer requires wrapping Git or setting up hooks. Attribution runs asynchronously in the background, surviving cherry-picks, rebases, squashes, and stash/pops without slowing down your Git commands.

Run git ai upgrade or install fresh from GitHub.

Performance & Bug Fixes

• Improved worktree support - some complex workflows began losing attribution after a recent Claude Code update.
• Codex daemon post-commit CAS uploads fixed — Codex Cloud users were missing some attribution data
• Checkpoint routing fixed for nested subrepos — checkpoints now route to the correct nested subrepo instead of the parent
• Detect running agents after hook updates — Git AI now warns you if agents need a restart after hook configuration changes
• Propagate cwd from hook input — fixes repo_working_dir resolution for all agent presets when invoked from hooks
• Recognize negated pathspec globals — --no-literal-pathspecs and similar flags are now handled correctly

Windows

• Guard git ai upgrade wrapper path — fixes an edge case in the Windows upgrade flow
• PowerShell progress bar disabled during download — was causing extreme slowness for some users
• Backslash path handling in clone target resolution — Windows paths with backslashes are now handled correctly

The last week we shipped broader agent and IDE coverage, a few improvements for background agents, and a couple of fixes that had been causing problems during enterprise rollouts.

Agent & IDE Support

• Cursor preToolUse hook migration — Cursor now supports pre-tool hooks; Git AI migrates from beforeSubmitPrompt to preToolUse for more accurate attribution.
• Windsurf in IntelliJ plugin — shipped for teams using Windsurf inside JetBrains IDEs. Hooks are now registered in both required locations to match Windsurf Cascade's hook discovery behavior.
• Devin, Cursor Agent, and Claude Web and Codex Cloud - commits are not attributed to AI.
• Custom Background Agent support override — teams building custom background agents can now add metadata and run Git AI in background agent mode. Used by several companies in NYC - docs and will be launched to everyone soon.

There's a lot in-flight from OSS contributors we're working to get closed and merged.

• Kilo Code agent support (#762) — Checkpoint preset and agent detection for Kilo Code.
• Kimi Code (Moonshot AI) support (#751) — Agent detection via noreply@moonshot.cn / noreply@kimi.ai and kimi-code[bot] GitHub username, plus a KimiCodePreset checkpoint preset.
• git-ai blame in JetBrains plugin (#741) — AI blame annotations in IntelliJ matching the VS Code extension: gutter color stripes, inline model-name inlays, a status bar widget, and a Cmd+Shift+G toggle. Calls git-ai blame --json under the hood with a 300ms debounced refresh.
• Roo Code - the Roo code team is working with us to build a direct Git AI integration.

For Team and Enterprise users

• Persist install API base in config — shipped a bug fix for self-hosted and enterprise installs. git-ai install-hooks now writes API_BASE into ~/.git-ai/config.json so subsequent commands always hit the right endpoint without needing the env var set. This worked for brand new Git AI installs, but was not setting properly if a developer had installed Git AI before their company fully adopted it.
• Local Prompt analysis was broken if you logged into your enterprise org — shipped for Cloud and Enterprise users who share prompts with their team. Prompt analysis was overwriting local transcripts with the empty [] from git notes, causing most recent prompts to appear blank. Analysis now correctly falls back to the locally stored transcript.

This week was split between two priorities: broadening agent support to support the enterprises using Git AI, and tightening the new core hooks system so it's reliable in more deployment configurations. Several teams had asked for finer-grained control over hook behavior — now they have it.

Agent Support

• Windsurf agent support — shipped for the enterprises who love Windsurf. Full integration including hook installer, checkpoint preset parsing for Windsurf's nested JSON + JSONL transcript format, sync-prompts, show-transcript support, and end-to-end test coverage.
• OpenCode plugin tools — shipped for OpenCode users on newer models. Adds detection for patch and multiedit tools in the OpenCode plugin.
• First steps towards supporting Background Agents — shipped for teams where AI agents commit directly under their own git identity. A new agent detection module maps known agent author emails and GitHub usernames to tool names, synthesizing attribution across all blame output formats when no authorship note exists.

What Shipped

• Hook feature flags — shipped for platform teams managing Git AI across many repos. Two new flags: git_hooks_enabled (auto-ensure hooks on checkpoint) and git_hooks_externally_managed (write hook scripts without touching core.hooksPath). Both support env var overrides and CLI config.
• Fix blame-deletions for renamed files — shipped for teams tracking attribution on refactored codebases. Corrected attribution when --blame-deletions is enabled on files that were renamed.
• CI: auto-bump flake.nix on release — shipped for Nix users. The release workflow now keeps flake.nix version in sync with Cargo.toml automatically.

Two big themes this week. First, we shipped full git worktree support — something teams with complex branching workflows have been asking for. Second, we put serious effort into Windows reliability and accuracy — a lot of footguns around canonical paths got addressed properly.

Agent support

• Amp CLI agent support — shipped for teams using Amp as their AI coding agent. New Amp preset with transcript parsing, plugin installer and template, and integration coverage.
• GitHub Copilot hooks — for more accurate AI attribution in enterprises (Copilot is still used everywhere).

Crazy stuff for the crazy times.

• Comprehensive worktree support — shipped for teams using git worktrees for parallel branch development. Worktree-aware repository resolution with --git-common-dir handling, isolated per-worktree storage, aligned blame behavior, and new integration tests.
• External git diff tool support — shipped for a healthcare company that uses custom external diff tools. Internal git execution profiles now enforce the standard diff.
• Support checkpoints from one agent session in multiple repos — a big infra company was refactoring a bunch of code across many locally checked out repos. This fix lets one Agent edit files in n repos, grouping them by repository, and running separate checkpoints for each.

Stability now!

• Graphite CLI test suite — 25 tests verifying attribution survives Graphite operations, catching edge cases in rebase-heavy workflows.
• Windows fixes — shipped for developers on Windows across Git Bash, Fork, Sublime Merge, Cursor, and Claude Code. Fixes include PATH shadowing in Git Bash, forward-slash path handling in Fork, BOM stripping in Cursor hook input, and git-bash-style path conversion for Claude hooks.