The title seems like clickbait but also reflects an annoyance/frustration with overuse as marketing/sales tends to do. I ignore that and ask what exactly does your product do, then decide how to categorize it.
My hand-wavy definition is basically as a chatbot gives an AI multi-modal input and output to a user, an agent has 'hands' which can produce an effect on a system rather than reporting to the user directly via media. The method of integration isn't really important, it could be using a public network API or as part of a compiled static binary, whatever.
When “it becomes challenging to benchmark performance and ensure consistent outcomes,” should I worry that different products don’t fully comprehend client-server architecture?
Barely anyone will use this term in 2 years, just like nobody talks about copilots anymore. But for now: everything is labelled as agent.
The title seems like clickbait but also reflects an annoyance/frustration with overuse as marketing/sales tends to do. I ignore that and ask what exactly does your product do, then decide how to categorize it.
My hand-wavy definition is basically as a chatbot gives an AI multi-modal input and output to a user, an agent has 'hands' which can produce an effect on a system rather than reporting to the user directly via media. The method of integration isn't really important, it could be using a public network API or as part of a compiled static binary, whatever.
There is of course the "Agent Hospital: A Simulacrum of Hospital with Evolvable Medical Agents"[0] paper.
[0] https://arxiv.org/abs/2405.02957
Have we struggled with defining what a daemon is?
When “it becomes challenging to benchmark performance and ensure consistent outcomes,” should I worry that different products don’t fully comprehend client-server architecture?
A daemon or “non deterministic data pipeline” doesn’t command grandiose valuations. It must sound like magic.