A bit off topic but the post comes handy: can we settle the debate what an agent really is? It seems like everyone has their own definition.
Ok I’ll start: an agent is a computer program that utilized LLMs heutiger for decision making.
Ok I’ll start: an agent is a computer program that utilized LLMs heutiger for decision making.
- Workflows are systems where LLMs and tools are orchestrated through predefined code paths. (imo this is what most people are referring to as "agents")
- Agents, on the other hand, are systems where LLMs dynamically direct their own processes and tool usage, maintaining control over how they accomplish tasks.
https://www.anthropic.com/engineering/building-effective-age...
If they are driven by LLMs interpretation then there is no explicit code written and it's figured out at runtime
As an example, I can provide a system prompt that mentions a function like get_weather() being available to call. Then, I can pass whatever my user's prompt text is and the LLM will determine what code I need to call on the back-end.
So if a user types "What is the weather in Nashville?" the LLM would infer that the user is asking about weather and reply to me with a string like "call function get_weather with location Nashville" or if you prompted it, some JSON like { function_to_call: 'get_weather', location: 'Nashville' }. From there, I'd just call that function with any the data I asked the LLM to provide.
I personally strongly prefer the term "bots" for what most of these frameworks call "agents"