Git AI

the open standard for tracking AI-generated code

[Git AI @usegitai]

Real-time Coding Agent o11y. Now you can see real-time telemetry on cost, tool calls, and the journey of all the AI-code in your repos from prompt out to production.

[Aidan Cunniffe @aidandcunniffe]

"We only have the bills" - how a lot of engineering leaders we work with feel about measuring ROI before Git AI.

It's difficult to do this right because of long spanning sessions contributing code to different commits, brainstorming sessions that don't lead to code, stacking..

[Git AI @usegitai]

1.4 shipped huge improvements to how Git AI connects LoC to Agent Sessions.

- Tool-call level granularity. Connect each AI-line to the tool that generated it
- Support for non-linear sessions (subagents, interruptions, rewinds)

something is coming

https://t.co/wE81bLlNPD

[Git AI @usegitai]

Git AI now tracks and attributes changes that result from Agents running shell commands.

super cool to see the community take on something this big and useful 🚀

[Git AI @usegitai]

Not the biggest Pi news of the last week but definitely the biggest Pi * Git AI news of the week 😍

Community built. Now in 1.3.0

[Git AI @usegitai]

Full post here https://t.co/OFhZ6Ep8ml

[Git AI @usegitai]

Retroactively calling this a launch week because v1.2 is full of so much good stuff:

🫡 Maximum compatibility — no more Git hooks or git wrapping. It just works.
🚀 No overhead — attribution calculated off Git hot path
🛸 Support for Background Agents

[Aidan Cunniffe @aidandcunniffe]

Exactly what Git AI was built for https://t.co/PCqfkadGI1

I think the signal we want in RL extends way further than sessions…
- what human overrides were made
- was the AI code approved
- what got changed in code review
- is the generated code still in prod a month later?
- did AI code cause a bug or incident?

It’s about 100x harder to do track AI code through the SDLC - but that’s where the real reward signal is

[Git AI @usegitai]

Super cool to see @cubic_dev_ include AI attributions powered by Git AI. The team is cracked and pushing the frontier of code review.

[cubic @cubic_dev_]

Your team uses 4 different coding agents, and you're starting to spend a fortune on them.

Which one produces the best code? Which do devs actually use?

cubic now tracks which lines of code AI wrote, and which model and harness produced them - partnering with Git AI.

[Git AI @usegitai]

Over the last few weeks companies have begun running Git AI in their custom background agents. Turns out you can't build an autonomous software factory without observability and attribution for code and decisions.

Super cool to be listed here by our friends at @ona_hq

[Lou @loujaybee]

Want to build your own background agents platform like Ramp Inspect or Stripe Minions?

Now you can:
https://t.co/gTuCVk2Obs

[Git AI @usegitai]

Community has been cooking this week 🚀

New contributors added support for @kilocode and @Kimi_Moonshot as well as porting the AI-blame extension to the @jetbrains ecosystem.

[Aidan Cunniffe @aidandcunniffe]

Seeing this trend a lot of this across teams that use Git AI: enterprises are investing in their own background agents. I was skeptical at first, but I get it now.

Building and optimizing the factory will be the work of platform teams for the next 5 years.

[Aidan Cunniffe @aidandcunniffe]

Semi-serious proposal if you're having Amazon-style problems with Coding Agents.

[Git AI @usegitai]

The spec is what you built and why.

[Git AI @usegitai]

The spec is what you built and why.

[yenkel @yenkel]

I mean, I've rarely seen such a detailed PRD that mixed product requirements with technical specification, was kept up to date over time, etc.

you still have some spec, or you can iterate on the feature with the agent directly and the spec lives in prompt history and you can use @usegitai to keep around as future context

but you get the gist about the high level, BDUF PRD being dead

[Git AI @usegitai]

Also huge Shot to the @AmpCode team. Their new plugin system takes a very different approach than most Agents, but we think they have the right model.

Excited to build more with this team!

[Git AI @usegitai]

Looks like @AmpCode was here 🚀.

The Git AI <> Amp integration is now live. Track all the code written by Amp — along with the prompt that generated them.

[Git AI @usegitai]

Git AI now lets you use past prompts as context — across agents. Whenever you're building on top of AI-code the original prompts help inform what the agent writes next.

Claude knows and adheres to the requirements you gave Cursor. Codex knows about an architecture decision you made in OpenCode. All your agents remember your intent and why they wrote code the way they did.

Get more of your team on Git AI and all your team's agents get smarter.