←back to thread

Agent Client Protocol (ACP)

(agentclientprotocol.com)
272 points vinhnx | 1 comments | 30 Aug 25 12:42 UTC | HN request time: 0.277s | source
Show context
mg ◴[30 Aug 25 14:02 UTC] No.45074786[source]▶
I'm fine with treating AI like a human developer:

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

replies(2): >>45074878 #>>45076374 #
Disposal8433 ◴[30 Aug 25 14:16 UTC] No.45074878[source]▶
> Nowadays, it is better to write prompts

Very big doubt. AI can help for a few very specific tasks, but the hallucinations still happen, and making things up (especially APIs) is unacceptable.

replies(6): >>45074958 #>>45074999 #>>45075081 #>>45075111 #>>45079473 #>>45081297 #
1. tomjen3 ◴[31 Aug 25 07:51 UTC] No.45081297[source]▶
Its surprisingly fine, as long as you allow the AI to iterate on its work. It will discover that it doesn't compile, and then maybe lookup the API and then it will most often fix it and move on.

AI is no more capable of reliably one shotting solutions that you are.