Agent Client Protocol (ACP)
agentclientprotocol.com
Agent Client Protocol (ACP)
1–10 of 104 posts
Re: Agent Client Protocol (ACP)
#2Re: Agent Client Protocol (ACP)
#3Re: Agent Client Protocol (ACP)
#4Curious to see how adoption among cli agents will go (it’s nice to see Gemini cli already in).
The level of competition in the LLM and coding assistant market is always nice to see, and this only helps to make costs of switching between offerings even smaller.
Re: Agent Client Protocol (ACP)
#5Re: Agent Client Protocol (ACP)
#6You need to define an interface for Ai to click buttons? Or to create keyboard macros that simulate clicking buttons? We are all doomed!
Re: Agent Client Protocol (ACP)
#7I’m going to be hungry all day, everyday if this catches on and we call it ACP
Re: Agent Client Protocol (ACP)
#8Fingers crossed for this - it seems like Zed is kinda “going back to the roots” (of working on collaboration) and leaving this in place to disrupt the agentic IDE category (and make themselves not have to spend time on competing in it). Curious to see how adoption among cli agents will go (it’s nice to see Gemini cli already in). The level of competition in the LLM and coding assistant market is always nice to see, a…
I welcome them openly collaborating.
Re: Agent Client Protocol (ACP)
#9Re: Agent Client Protocol (ACP)
#10I ask AI to write a feature (or fix a bug, or do a refactoring) and then I read the commit. If the commit is not to my liking, I "git reset --hard", improve my prompt and ask the AI to do the task again.
I call this "prompt coding":
https://www.gibney.org/prompt_coding
This way, there is no interaction between my coding environment and the AI at all. Just like working with a human developer does not involve them doing anything in my editor.