Looks like omp supports ACP, so all you have to do is specify a Custom Agent in Zed and it should just work.
Is it available now? Still seems to be a waitlist?
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?
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.
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)
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.
For me, its a massive improvement over IntelliJ for my daily workflow.
Terrible Linux support.
I have never used snippets so unsure about that too, going from command bar seemed to work.
I think it might be bad, but could also be it's not correctly configured maybe try asking codex/claude or something to check if it can fix/fine tune the config, if that doesn't work file issues?
I do suspect it might be working for me cause I got lucky I do see an open issue[1], but given Zed is used a bunch the lack of comments does suggest maybe it's not that wide spread either way not a good look.
[1]: https://github.com/zed-industries/zed/issues/47004
Maybe I got lucky?? Does it not auto update on linux maybe I am on an old build... Very suspicious.
Having said that, I love the idea of correlating the agent sessions to the changes. I'm glad someone is working on it.
See https://zed.dev/blog/introducing-deltadb but also https://zed.dev/blog/crdts from years ago.
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.
Shit, as someone who uses Zed everyday, I didn't realize what I am using is unusable.
I can't use an editor where the file contents I'm being shown don't match the reality of the file. I guess this issue doesn't affect most people somehow, but in the age of CLI agents I'm not sure how more people aren't running into it.
I was really enjoying Zed for a short while before I ran into this fundamental issue.
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.
For example, a lot of disable buttons do not actually disable stuff. They just hide it from the UI.
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.
it is a code editor after all. how about integrating the LSP so that it doesn't have to resort to rg/grep/sed/scripts to edit code?
Be among the first to try DeltaDB, a version control system that records the work as it unfolds and keeps every change connected to the conversation that shaped it.
Rewind to any edit
DeltaDB captures every operation in between commits and gives each one a stable identity, so you can point to the code at any moment in its evolution.
Trace code to conversation
Every change is linked to the agent conversation that produced it. From any line of code, find the conversation. From any message, jump to the code it touched.
Branch at any moment
DeltaDB virtualizes the worktree, so spinning up a new agent branch is effectively free. Any point in history is a valid branch point, including mid-run.
Share the thread, not the PR
A teammate can join while the work is still happening, talk to the agent that did the work, and annotate as they go, without waiting for you to commit and push first.