More agents, more background agents, and improved team prompt sharing

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.