East River Source Control is developing a new version control backend that speaks the Git protocol but replaces Git's storage layer to handle the demands of agentic development and massive monorepos. They're designing it to work with Jujutsu as a client, allowing teams to gradually migrate beyond Git's 2005-era constraints without abandoning existing tooling.

• Agentic AI development is creating problems at scale that previously only large companies faced: massive repositories, frequent branching, merge contention, and the need for fast cloud-based clones.
• Git was designed for the Linux kernel in 2005, not for billion-line monorepos or private enterprise features that modern organizations need, yet switching is risky because Git is embedded throughout the entire development ecosystem.
• ERSC's strategy is to keep the Git protocol as the client interface while replacing the backend storage engine, and eventually support Jujutsu as a client that can speak different protocols to enable a gradual migration path to future version control systems.

Lore is a centralized version control system that represents repository state with Merkle trees and an immutable revision chain. It’s optimized for binary-first storage, deduplication, and on-demand data hydration at scale. You can explore its repositories on the Epic Games GitHub.

• Lore uses a centralized server model with Merkle trees and content-addressed, immutable revision chains instead of distributed history.
• It's built for binary-heavy projects (game assets, media), storing blobs and trees separately and hydrating data on demand rather than requiring full clones.
• Deduplication at the storage layer means identical file chunks are written only once, cutting disk usage and speeding backups.
• Epic Games hosts public sample repos on GitHub demonstrating asset pipelines, builds, and backup workflows.

Zed is building DeltaDB, a version control system that records every edit as a discrete, addressable delta instead of relying on commits. By linking each operation to its generating conversation, it lets humans and agents collaborate in real time on a shared worktree without waiting for snapshots or pull requests. Early beta access opens in a few weeks.

• DeltaDB replaces Git commits with a continuous stream of individually addressable edit operations, each with a stable ID.
• Messages and the edits they spawn are stored together, so comments anchor to deltas rather than line numbers and never drift when code changes.
• Conflict-free replicated worktrees let multiple humans and AI agents edit the same real on-disk files simultaneously, skipping pull-request workflows.
• Agents can trace why code exists by pulling up past conversations and even pinging other agents that previously touched the code.