Oobo is Git for agents (and humans). It enriches your repo with additional context about AI usage, helping agents and teams understand why something was built, how decisions were made, and what happened around the code, not just in the final diff.
We built Oobo because AI is writing more and more of the code, but almost none of the context around that work is preserved in a useful way.
You see the final diff, maybe a commit message, but not what the agent was trying to do, why a decision was made, what changed during the process, or how a human and one or more agents got to that result.
That started feeling like a real gap.
The idea evolved into a Git decorator because we didn’t want to replace Git or force people into a brand new system. Git already owns the code history. What was missing was the extra layer of context around AI usage and build decisions.
So Oobo became a way to enrich normal Git workflows with that missing context, making it easier for both agents and humans to understand what happened around the code, not just the code itself.
Congrats on the launch - definitely something that I'll need for our swarm of agents 😅
Really nice product! I can imagine this being huge for handoffs, especially when one person or agent starts something and another one has to continue it. Are you already seeing that use case?
Congrats on the launch! Is the end user for a finance team looking at token spend measurement or developer productivity (à la DORA)?
Congrats on the launch Teddy!
Is there a way to search for something across chats?
For example, I'm using Cursor and Claude Code for different chats, and sometimes I change something but forget which chat I asked in. So I'd love to be able to find when I changed something.
Really nice product, btw.
How does Oobo capture and structure AI decision context without significantly increasing repository size or slowing down existing Git workflows?
Teddy