Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agent Client Protocol (ACP)

agentclientprotocol.com

Post reply on HN
Print view View original

51–60 of 104 posts

Re: Agent Client Protocol (ACP)

#52

Post by dingnuts »

Disposal8433 wrote: post #25
salomonk_mur wrote: post #18

Earlier quoted context omitted.

Hard disagree. LLMs are now incredibly good for any coding task (with popular languages).

You can't disagree with facts. Every time I try to give a chance to all those LLMs, they always use old APIs, APIs that don't exist, or mix things up. I'll still try that once a month to see how it evolves, but I have never been amazed by the capabilities of those things. > with popular languages Don't know, don't care. I write C++ code and that's all I need. JS and React can die a painful death for all I care as the…

If you want them to not make shit up, you have to load up the context with exactly the docs and code references that the request needs. This is not a trivial process and ime it can take just as long as doing stuff manually a lot of the time, but tools are improving to aid this process and if the immediate context contains everything the model needs it won't hallucinate any worse than I do when I manually enter code (but when I do it, I call it a typo)

there is a learning curve, it reminds me of learning to use Google a long time ago

Re: Agent Client Protocol (ACP)

#54

Post by kgthegreat »

bsimpson wrote: post #49
awestroke wrote: post #22

Claude, come up with a protocol for communicating between AI agents and IDEs/editors. Create node, python and rust libraries. Create a website with a landing page

Honestly, I'm tempted to see if Gemini can write a Sublime Text plugin that implements this protocol. Feels like a lot of mindshare has shifted towards VSCode, so that's where the tooling investment goes. I don't want to be forced off of subl because new tools stop supporting it - it's a great editor, and it's not sponsored by a massive company.

Shouldn’t be too hard. I wrote this emacs plugin to do similar things but without this protocol - https://github.com/kgthegreat/protagentic . Heavily used AI assisted coding for it.

Re: Agent Client Protocol (ACP)

#56

Post by pickledish »

bsimpson wrote: post #49
awestroke wrote: post #22

Claude, come up with a protocol for communicating between AI agents and IDEs/editors. Create node, python and rust libraries. Create a website with a landing page

Honestly, I'm tempted to see if Gemini can write a Sublime Text plugin that implements this protocol. Feels like a lot of mindshare has shifted towards VSCode, so that's where the tooling investment goes. I don't want to be forced off of subl because new tools stop supporting it - it's a great editor, and it's not sponsored by a massive company.

Yeah agreed!

As you suggest, I've had a moderately successful time trying to get AI to write its own Sublime Text plugins so our favorite editor doesn't get left behind, so might be cool to try with this too?

https://github.com/pickledish/llm-completion

Re: Agent Client Protocol (ACP)

#57

Post by djim1337 »

triyambakam wrote: post #42
hari-trata wrote: post #26

I don’t see why we need so many protocols. In such a greenfield tech, many are eager to define rules. There’s already a protocol called AG-UI that does the similar thing, but even its purpose isn’t entirely clear to me. Rather than rushing to create standards, I think the focus should be on building practical implementations, AI-centric UI components that actually help developers design more AI-friendly interfaces. O…

I do agree it seems like too many protocols. I wonder why this couldn't be mcp. But regarding ag-ui in its name it's for UI - streaming from a backend agent to a client frontend. I actually have been working a lot with it this week.

[dead]

Re: Agent Client Protocol (ACP)

#59

Post by lyu07282 »

jmull wrote: post #41
baggiponte wrote: post #11

Earlier quoted context omitted.

I’m afraid you missed a bit the mark :( This is the equivalent of LSP but for coding agents. So any editor does not have to rebuild an interface to support each and every new one.

The question is why… The purpose of an ide is to pull together the tools a developer needs to develop software… first, reading/navigating and writing code, next running and debugging code, then (potentially) a variety of other tools: profilers, doc browsers, etc… all into a unified UI. But coding agents seem to already be able to use the command line and mcp quite well to do this. So why mediate using these tools thr…

> So why mediate using these tools through an IDE (over a new protocol) rather than just using the tools directly through the command line or mcp

The IDE is in-between because it asks the user for confirmation before doing anything, if that's what you are asking. It's not adding any indirection or something, this is just how coding agents talk to the IDE already, all this does is standardize the language they speak which would be a win for everybody.

Post reply on HN