281–290 of 431 posts
This might come off as a naive question so pardon me in advance for my ignorance. I got Claude Max just last week and I have been using it in the MacOS Terminal app. I also used it in Zed and VS Code terminals and faced no issues. So what is the advantage of using it natively like this?
You get a diff view of the edits CC is making to your project and there's a mode where you editor's focus follows where CC is editing in your project.
I love Zed and I'm glad you now have native support for Claude. I previously ran it using the instructions in this post: https://benswift.me/blog/2025/07/23/running-claude-code-with... One thing that still suffers is AI autocomplete. While I tried Zed's own solution and supermaven (now part of Cursor), I still find Cursor's AI autocomplete and predictions much more accurate (even pulling up a file via search is more…
I'll third this. AI autocomplete is THE most efficient and helpful feature of Cursor, not the agents.
If performance were equal, I’d strongly consider going back to GH Copilot just because I don’t love my main IDE being a fork. I occasionally encounter IDE-level bugs in Cursor that are unrelated to the AI features. Perhaps they’re in the upstream as well, but I always wonder if a. there will be a delay in merging fixes or b. whether the fork is introducing new bugs. Just an inherent tradeoff I guess of forking a complex codebase.
This might come off as a naive question so pardon me in advance for my ignorance. I got Claude Max just last week and I have been using it in the MacOS Terminal app. I also used it in Zed and VS Code terminals and faced no issues. So what is the advantage of using it natively like this?
If you're going to live in the terminal, please do yourself a favor and replace Terminal.app with iTerm2, and replace bash with zsh.
I highly recommend trying fish, I wish I’ve switched earlier
This might come off as a naive question so pardon me in advance for my ignorance. I got Claude Max just last week and I have been using it in the MacOS Terminal app. I also used it in Zed and VS Code terminals and faced no issues. So what is the advantage of using it natively like this?
You get a diff view of the edits CC is making to your project and there's a mode where you editor's focus follows where CC is editing in your project.
Earlier quoted context omitted.
This seems obviously untrue. https://zed.dev/extensions
VSCode has 60k+ extensions vs Zed's 744. I'm pretty sure there's a clear winner here.
Earlier quoted context omitted.
Weird, I tried it recently and found it actually a bit laggier than VSCode. The rendering is much worse quality too. Are you using Vim mode or something like that?
I begrudgingly gave up vim mode in vscode a few years ago, because that seemed to make it so much more sluggish.
Fortunately standard editing shortcuts like Ctrl-D, Ctrl-left/right, etc. replace 99% of Vim "magic" and are way easier to remember and use.
Earlier quoted context omitted.
Helix itself seems quite young - and first time I’m hearing of it.
It’s about 4 years old, twice as old as Zed!
commit b400449a58507cca1fa007197929c2cfd6beabbe
Author: Nathan Sobo
Date: Sat Feb 20 10:02:34 2021 -0700
Start rebuilding with a cleanly-separated UI frameworkEarlier quoted context omitted.
If you're going to live in the terminal, please do yourself a favor and replace Terminal.app with iTerm2, and replace bash with zsh.
> and replace bash with zsh I highly recommend trying fish, I wish I’ve switched earlier
I love Zed and I'm glad you now have native support for Claude. I previously ran it using the instructions in this post: https://benswift.me/blog/2025/07/23/running-claude-code-with... One thing that still suffers is AI autocomplete. While I tried Zed's own solution and supermaven (now part of Cursor), I still find Cursor's AI autocomplete and predictions much more accurate (even pulling up a file via search is more…
I'll third this. AI autocomplete is THE most efficient and helpful feature of Cursor, not the agents.
Earlier quoted context omitted.
While this is probably annoying, I have to imagine that non-hidpi displays are becoming rarer and rarer. It's probably not a great idea to spend a lot of work on a feature that will only ever see declining use.
It's not rare at all. It's more common than not for people developing on monitors.