Zed

We've shipped more than a thousand versions of Zed, but all of them began with zero. Today, that changes. zed.dev/blog/zed-1-0

@ja3k_ Yes and

I've been thinking agent transcripts should be committed along with code changes in a way that makes it easy to chat with the agent that made a change

@swyx Happy Friday x.com/zeddotdev/stat…

## The Future Codebase After the PR dies, after the Code Review dies, i am seriously wondering if Git needs to die next. roughly 20-40% of code spend is just managing and updating merge conflicts. necessary evil? or legacy "horseless carriage"? cargo culting the past? we don't do line by line merge conflicts when we collaborate with human colleagues - instead we chat, suggest edits, do side comments, and an owner ships it. btw we also don't do CI/CD even collaborating on documents with serious legal/financial implications. maybe the future codebase looks more like a Notion or Linear database than .git objects. It will be less efficient, but more scalable. exactly the Salty Lesson.

@notagodzilla zed.dev/blog/chatgpt-s…

I love using @zeddotdev it's so fast, clean and actually works. Used to whip out Cursor for caveman work but it got too bloated and just deadweight, moved to Zed and everything is so clean, fast and outright works. Missing some extensions but I'll just create em with Codex. Yet to try out the agentic experience but don't want to pay for ANOTHER coding agent.

One week out: Open Source + AI meetup in Paris, Thursday, June 18 at 7pm CEST, hosted by @neon_noir_paris with @commitvc. Tom Houlé from Zed is giving a talk. Come hang with the Paris open source crowd! luma.com/gx64jwdn

@MightyChungus @ryanvogel Because it solves so many problems, Chungus

@zeddotdev @ryanvogel Fucking hell. zed is spamming the same shit everywhere

you guys aren't understanding this this isn't memory this should be a internal stackoverflow, where once an agent figures out a bug it posts a little "question/answer" into the folder that way future agents can refer to that if they run into the same issue

@ryanvogel x.com/zeddotdev/stat…

okay yes, if agents had INFINITE CONTEXT then I would want this added to memory sure whatever, but my niche expo sheet causes a reload of the IVS stream is not something I need in 99.99999999% of conversations its for me next month when something gets fucked and I need to remember how and why I did something so I don't spend another 50 minutes finding whats wrong

@garybernhardt x.com/zeddotdev/stat… Good morning Gary

The #1 thing I want right now isn't a smarter model; it's better tools for understanding what an agent just did.

@sridca We'll have a lot to share very soon! 😉

@zeddotdev Could you post a demo? I read the blog post but don’t see yet what it actually does.

Great software always took shape in conversation, not the commit. With agents, the conversation that generates the code is becoming the true source of our software. And Git can't keep up. So we built something that can. Meet DeltaDB: zed.dev/blog/introduci…

@aboodman x.com/zeddotdev/stat…’m

cosign. I don't find the "create giant spec and let it loose overnight" very productive. I need to be in the loop to even know what I want. The majority of the finished product is in the iteration, not v1.

@lmendelowski on the list for sure

@zeddotdev thanks for making `add selection to thread` to work with terminal threads! Any plans to make terminal a default agent thread with option to specify default command (claude / codex)?

@mgyarmathy_ It is Git-compatible by design. Git's discretized snapshots are a subset of DeltaDB's continuous history.

@zeddotdev Most of CI/CD technology is built on top of git versioning. How will DeltaDB interop with traditional version control for outer loop SDLC workflows?

The beta opens in a few weeks. If you'd like to be among the first to try it, sign up here: zed.dev/deltadb

Never forget to commit or push again and skip the PR ceremony. Jump into a teammate's thread while the work is still live, talk to the agent that wrote it, and comment or branch from there.

Source code and the conversation that produced it live in the same place. Jump from any line of code to the prompt that created it. Or from a past conversation to that code as it stands now, or the moment the agent wrote it.

DeltaDB is a new kind of version control. Where Git captures a snapshot at each commit, DeltaDB captures every keystroke and operation in between as a fine-grained delta, each with its own stable identity.

@johnbarker @artooro @angel_d_munoz @Apple @jetbrains This is not actually correct. zed.dev/blog/chatgpt-s…

@artooro @angel_d_munoz @zeddotdev @Apple @jetbrains ACP enables you to use the harness of your choice, thus also subscription. For example, you can’t use your Codex subscription with Zed unless you use ACP (but that also means you’re not using the Zed agent; you’re just using the Codex harness).

Xcode (@Apple), @jetbrains IDEs, Zed, and dozens of other tools (CLIs, desktop, web, and mobile apps) all use ACP to talk to agents. Open source, no lock-in. What's preventing you from adopting?

@fuolpit @Apple @jetbrains 😢

@zeddotdev @Apple @jetbrains white on transparent background strikes again lol