@samuellhuber.eth
Zed's goal is to make your codebase a living, navigable history of how your software evolved, where discussions with humans and AI agents are durably linked to the code they reference and always up-to-date. It's an evolution beyond version control that incorporates not just the code itself, but also the background information of how and why the code got into a particular state—context that AI agents can query to make more informed edits, understanding the assumptions, constraints, and decisions that shaped the existing code.
Picture a new engineer facing a production stack trace in Zed. They highlight a problematic line, like an unwrap that caused a crash, and see every related discussion: why the function was written or what an AI agent assumed about an invariant. They ping the responsible human, sparking a quick chat that turns into an audio call, all indexed to the exact code spot, creating a shared, revisitable record without leaving the codebase.
https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-operation-level-version-control
0 reply
0 recast
0 reaction