[agrippanux]

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).

[dewey]

The Agent Model came out very recently, I’ve been following the GitHub issue over the past days and you can see it was rushed out. But I don’t see anything wrong with that, many AI topics are being rushed out and adding slash commands and other small things are very small things to add once the foundation is there.

[manmal]

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.

[beefsack]

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 /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.

[furyofantares]

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.

[mi_lk]

Seems like those issues are largely limited by SDK so urging Anthropic to adopt is the only realistic move

[cmrdporcupine]

Yeah I was initially excited here, but it feels more like a demonstration of what's possible rather than a working tool.

I found the interface very nice but quickly ran up against limitations on prompt length (it wasn't that long) for example. I am used to being able to give detailed instructions, or even paste in errors/tracebacks.

I'll check back in in a few months.