←back to thread

677 points meetpateltech | 1 comments | | HN request time: 0.318s | source
Show context
agrippanux ◴[] No.45123632[source]
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 you are in the context window, it's a deal breaker, since you have to start a fresh chat and might run out of room before you can ask it to create a summary prompt for continuing.

There is no way to switch models that I can tell - I think it just picks up on your default model - and there is no way to switch to Plan mode, which has become absolutely crucial to my workflow.

I didn't see Zed picking up on problems reported in the IDE, it was defaulting to running 'tsc -b' in my directories.

At this point it's better to run a terminal inside Zed and work from there. The official response in the Zed Discord has been "talk to your local Anthropic rep" to get them to support Zed's Agent Client Protocol (ACP).

replies(4): >>45124327 #>>45124411 #>>45124759 #>>45127228 #
manmal ◴[] No.45124327[source]
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.
replies(2): >>45125167 #>>45130323 #
1. furyofantares ◴[] No.45130323[source]
I notice when I'm getting close and I tell it how to document current state into an .md file. Then I hit /clear and @ the new file.

This is probably very similar to /compact except I have a lot of control over the resulting context and can edit it and /clear again and retry if I run into an issue.