←back to thread

Agent Client Protocol (ACP)

(agentclientprotocol.com)
270 points vinhnx | 1 comments | 30 Aug 25 12:42 UTC | HN request time: 0.001s | 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 #
NitpickLawyer ◴[30 Aug 25 14:26 UTC] No.45074958[source]▶
> but the hallucinations still happen, and making things up (especially APIs) is unacceptable.

The new models are much better at reading the codebase first, and sticking to "use the APIs / libraries already included". Also, for new libraries there's context7 that brings in up-to-date docs. Again, newer models know how to use it (even gpt5-mini works fine with it).

replies(1): >>45075292 #
1. sigseg1v ◴[30 Aug 25 15:06 UTC] No.45075292[source]▶
What size of codebases are we talking here? I've had a lot of issues trying to do pretty much anything across a 1.7 million LOC codebase and generally found it faster to use traditional IDE functionalities.

I've had much more success with things under 20k LOC but that isn't the stuff that I really need any assistance with.