381–390 of 431 posts
Note: if you use SSH-based remote development, this doesn't work. https://x.com/sridca/status/1963271904384401886
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 now plain hate Cursor's auto complete, it's too aggressive I cannot write any code anymore, it seems to have hijacked CMD too, not just tab.
Give the agent as much context as possible and let it go, review and correct the implementation, let it go again, finish it off…
The I just find the autocomplete a little annoying in my workflow, especially with the local self-hosted models I need to use at work.
Claude Code on corporate approved AWS Bedrock account.
I think it's just a TAD annoying that this stupid thing uses API key based cost when it has a perfectly good x20 subscription to work with. I just burned through my entire API budget.
Am I reading this wrong, they added support for Claude Code, which should work with your Anthropic sub. The Claude via API that has always been there is not what they're talking about in this anoucement
Which I didn’t notice until my whole balance ran out.
Earlier quoted context omitted.
I now plain hate Cursor's auto complete, it's too aggressive I cannot write any code anymore, it seems to have hijacked CMD too, not just tab.
This is why I’m not a fan of auto complete in my editor. Much rather pair program with an agent. Give the agent as much context as possible and let it go, review and correct the implementation, let it go again, finish it off… The I just find the autocomplete a little annoying in my workflow, especially with the local self-hosted models I need to use at work. Claude Code on corporate approved AWS Bedrock account.
Right now it's borderline impossible to write code, the autocompletion results are loaded ultra fast and Cursor maps different buttons to autocompleting functionality.
It's no longer usable for me.
I'm fine getting autocompletes, but I decide when to trigger it, ideally after reading it, like this I can't even type.
Earlier quoted context omitted.
VSCode is actually not slow. The problem is to make it useful you need to add quite a few extensions, and those can be slow. That itself wouldn't be too bad but VSCode doesn't expose any information about what is causing the slowness. You end up with "VSCode is slow and it could be due to any one of the dozen extensions I have installed", which effectively means that VSCode is slow. It remains to be seen if Zed can a…
VSCode (and all Electron based editors) have undeniable input latency. Zed is built by the same team that developed Atom and Electron and one of their stated goals is to make up for the shortcomings of these technologies. If you don't feel that VSCode is slow, it's because you are used to it.
Start up time, sure. But VSCode was lauded as the first performant Electron based editor. I just tested VSCode, Zed, and vim and I can't see any difference from when I press a key to when a character shows up on the screen (appears instantly). I'd be curious to see the results of a blind test, and wonder if people's biases against Electron are showing up.
Earlier quoted context omitted.
Out of curiosity, why not just stick to Cursor instead?
For me, the editor is still the most important component of my tooling. The AI features are secondary to my needs/wants when it comes to an editor. Zed is hitting all the checkboxes when it comes to performance and user experience (yeah, I care about that in my editor). I'm not a hardcore user of AI, but I do make use of Zed's inline suggestions and occasional use of Opus 4.1 through my Zed subscription.
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.
I genuinely don't understand why one would want to AI autocomplete. Deterministic autocomplete is amazing but AI autocomplete completely breaks my flow. Even just the few seconds of lag absolutely drive me nuts and then it often it is close to what I wanted but not exactly what I wanted. Either I am in control or the generative AI but mixing both feels so wrong.
I am happy people find use for the autocomplete but ugh I really don't get how they can stomach it. Maybe it is for people that are not good at typing or something.
I love Zed but this has all the hallmarks of something being totally rushed out the door. It works off the Claude Code SDK, which mean it doesn't support many of the built in slash commands - it doesn't support /compact, which is 100% necessary because when you use this implementation enough, you'll eventually get a "Prompt too long" error message with no ability to do anything about it. Since you can't see how far y…
Tbf I never use /compact but clear instead, and load in the relevant context anew. I just haven’t seen compacted context to be very useful, so far.
I set up my directives to maintain a work log for all work that I do. I instruct Claude Code to maintain a full log of the conversation, all commands executed including results, all failures as well as successes, all learnings and discoveries, as well as a plan/task list including details of what's next. When context is getting full, I do a /clear and start the new session by re-reading the work log and it is able to jump right back into action without confusion.
Work logs are great because the context becomes portable - you can share it between different tools or engineers and can persist the context for reuse later if needed.
Earlier quoted context omitted.
You may not notice because macOS fonts look terrible (blurry) on any monitor that is not hidpi. Zed is just par for the course here. Meanwhile on Linux and Windows, they still implement subpixel rendering so fonts look great on 1440p.
As I said, I do notice when it is blurry, and in such a case it is a problem with anything that is rendered on that monitor not just zed. As I said, this does not happen "on any monitor" that is not hidpi. I use multiple operating systems on my day to day work, so I am not as brainwashed by apple as to not notice when such rendering issues arise. I know some people have bad experiences with 1440p and macos for some r…
Earlier quoted context omitted.
Tbf I never use /compact but clear instead, and load in the relevant context anew. I just haven’t seen compacted context to be very useful, so far.
The model is usually so confused after a /compact I also prefer a /clear. I set up my directives to maintain a work log for all work that I do. I instruct Claude Code to maintain a full log of the conversation, all commands executed including results, all failures as well as successes, all learnings and discoveries, as well as a plan/task list including details of what's next. When context is getting full, I do a /cl…