Earlier quoted context omitted.
You can disable all AI features in Zed with a single setting: https://zed.dev/blog/disable-ai-features
It doesn’t mean the bulk of their effort isn’t going to AI slopshit.
Parallel agents in Zed
121–130 of 178 posts
Re: Parallel agents in Zed
#122I'm having a hard time adjusting to the Project Panel on the right (and, at least for me, hidden by default) - seems like they're trying to bury the concept of a 'file'? It's certainly interesting though, and I'll give it some time - the post says "It feels more natural once you've spent a little time with it"
Re: Parallel agents in Zed
#123The claim really falls flat the moment you open it up and it is "native but not as you know it" providing the same UX experience of any other electron junk.
Re: Parallel agents in Zed
#124Re: Parallel agents in Zed
#125It's pretty clear by this point that everyone is going towards parallel agents and worktrees, but TBH I am surprised to see an offering from Zed, seeing how heavy they lean into being editor-heavy and having AI features be strictly optional. The key advantages Zed has are being agent-agnostic (so not a first party UI like Claude/Codex/Cursor Desktop), supporting multiple repositories on the same agent via creating a…
yeah, but they don't support a lot of the features Claude does like MCP integration. we've booked this up to logfire (telemetry provider) and it's a game changer when doing optimisation or diagnosis of bugs. plugins and skills also missing. but it is nice to switch between provider easily
Re: Parallel agents in Zed
#126I'm buying into this workflow more the more I use it, but the real gamechanger is (a) parallel threads in worktrees, with (b) enough lifecycle hooks to treat them similarly to spinning up a VM. Specifically for me that means that after I create a worktree I get some local config files copied over and Postgres duplicating my local dev and test databases so I can test in isolation, and then when I close out a worktree…
Love to hear it! (Conductor founder here). This is helpful to know - we're working on adding more agents, Copilot and OpenCode harnesses are among the most popular requests. We also recently built an escape hatch. If you turn on Settings → Experimental → Big Terminal Mode you can create new terminals in the center panel (with ⌘⇧T) and use any agent you'd like (Copilot, OpenCode, etc). It isn't the best experience bec…
Re: Parallel agents in Zed
#127I tried Zed and was really convinced that I could use it full-time, but the lack of extensions (TODO highlight, TabOut) + other QoL (line number goto as easy as VSCode + tab filter like another comment said). I also thought it was odd that I can't configure the font size in the git commit message editor. On recent additions, the dev container integration was great. Rooting for you Zed!
Re: Parallel agents in Zed
#128I personally don't love the idea of the default layout pushing aside my code and filetree to make space for AI tools I really like Zed, I use it every day. But, if I'd seen this layout when I first installed, I never would have taken it seriously I imagine this will push some new users away
Of course, that's only the default layout. I'm not familiar enough with Zed, but there's probably a way to change it? In JetBrains IDEs, you can configure panels to sit at the top left/bottom left/left bottom/right bottom/bottom right/top right side and show/hide them with one click (if only one panel on the respective side is shown, it will take up the full space). So you could have files at the top left and the agent panel at the bottom left. And the code editor is of course still the "centerpiece" in the middle.