OpenAI Introduces Pando: A Git Backend Rebuilt for AI Agent Traffic, Cutting Push Latency by ~80%
OpenAI released Pando, a new Git backend using causal consistency and packfile reuse to handle high-concurrency AI agent pushes, reporting an 80% drop in median latency and 1 PB daily throughput.
On November 2, 2026, OpenAI announced the launch of Pando, a new Git server backend now powering all development in its internal monorepo. The system was designed to address the infrastructure bottlenecks caused by the massive parallelization of work enabled by AI coding agents like Codex. According to OpenAI's engineering team, Pando has reduced median push latency by nearly 80% and currently delivers close to 1 petabyte of Git data per day.
Traditional Git servers typically enforce repository-wide consistency and generate unique packfiles for each client, which becomes a bottleneck under thousands of concurrent pushes. Pando abandons these assumptions: it employs 'causal consistency' instead of global snapshots, allowing unrelated branches to update independently and eliminating write contention across the repository. Additionally, it stores each pushed packfile as an immutable object and reuses these files for subsequent fetch requests, significantly reducing server-side computation.
To accommodate high-frequency interactions from AI agents, Pando also optimizes ref advertisement. In repositories with millions of branches, a full ref list can exceed 100 MiB. Pando advertises only the trunk branch as a base for new feature branches, enabling clients to reuse packs based on shared trunk history. While this approach causes repeat or stacked branch pushes to resend non-trunk history (with p99 pack sizes under 3 MiB), it substantially improves overall throughput.
Pando was designed by a single engineer and implemented by teams of Codex agents over 10 weeks, written in Rust. It has been serving production traffic since April 2026. Although Pando itself is not open source, OpenAI states that it has contributed several client-side improvements (such as parallel pack indexing and explicit haves support) back to the upstream Git project and is exploring ways to share the technology more broadly.