←back to thread

Building Effective AI Agents

(www.anthropic.com)
543 points Anon84 | 1 comments | | HN request time: 0.997s | source
Show context
AvAn12 ◴[] No.44303213[source]
How do agents deal with task queueing, race conditions, and other issues arising from concurrency? I see lots of cool articles about building workflows of multiple agents - plus what feels like hand-waving around declaring an orchestrator agent to oversee the whole thing. And my mind goes to whether there needs to be some serious design considerations and clever glue code. Or does it all work automagically?
replies(7): >>44303413 #>>44303510 #>>44303611 #>>44303637 #>>44303642 #>>44304027 #>>44304092 #
daxfohl ◴[] No.44303637[source]
Nothing works automagically. You still have to build in all the operational characteristics that you would for any traditional system. It's deceptively easy to look at some AI agent demos and think "oh, I can replace my team's huge mess of spaghetti code with a few clever AI prompts!" And it may even work for the first couple use cases. But all that code is there for a reason, and eventually it'll have to be reckoned with. Once you get to the point where you're translating all that code directly into the AI prompt and hoping for no hallucinations, you know you've lost the plot.
replies(1): >>44306135 #
whattheheckheck ◴[] No.44306135[source]
Then wtf is the point of this?
replies(3): >>44309003 #>>44311070 #>>44313336 #
1. daxfohl ◴[] No.44313336[source]
If you're a big software company, not much. If you're a small non-tech business, it could be an easy way to automate some things without hiring a software engineer.