Pretty awesome blog describing how Cursor intends to deal with git at scale in their GitHub [for agents] competitor. tldr they store all pushed packfiles in a WAL in S3-like object storage which serves as the source of truth, build replicated caches on disk from the WAL, and attempt to push through a repo's primary cache to avoid conflicts (which is a performance policy rather than a correctness one).