Terrible Linux support.
Shit, as someone who uses Zed everyday, I didn't realize what I am using is unusable.
https://github.com/zed-industries/zed/discussions/54150 failing to show newly created files and declining to provide a refresh button, instead adding a polling backend, breaks Zed on WSL.
Why a new version control system? Why not git, jj, or another existing system?
Having said that, I love the idea of correlating the agent sessions to the changes. I'm glad someone is working on it.
And the workflow they are describing in the post sounds amazing, I‘ve been wishing for that. It‘s orthogonal to CVS, no? You can still make PRs. But, crucially, you can loop people in early on, when it matters the most.
you must not use it much. try pasting in an image, quitting zed and restarting (ie: upgrading the app). it shows you the base64 encoded data instead of just showing the image. heck, it doesn't even show you the image when you paste it in. it just shows the filename.
Maybe I’m pessimistic, but I think this just gives micro-managers the data they need to micro-manage you. It invites people to scrutinize the process, instead of the results.
Not once have I wished to review a colleague’s conversation with an AI. I want to review finished work.
I look at this and I can only imagine layoffs being justified with “bad prompt quality”. An incident retrospective broadcasting your agent conversations to the entire company, with people speculating where you should have put the “make no mistakes”.
It’s a shame, really, because I like Zed as an editor, but I can’t bring myself to support them if this is the direction they’re choosing.
As anyone who's ever tried to split a days worth of work apart with `git add -p` is well aware.
It may be feasible with a million agents, but they could remember what they typed three hours ago anyhow.
Looks like omp supports ACP, so all you have to do is specify a Custom Agent in Zed and it should just work.
See https://zed.dev/blog/introducing-deltadb but also https://zed.dev/blog/crdts from years ago.
Jujutsu already does this. I had agent screwing up changeset over couple hour long session and it took one shell command to split on pieces with longer pause.
The only downside is that because of Jujutsu snapshots it can't be used inside sandbox (since all jj commands are mutating)
I have not gone to the Zed repository and created an issue telling them to stop developing DeltaDB because it takes away the maintainers’ time.