Good question, at first I only called the fully autonomous agents as agents, as to me that's what having agency is. I didn't like when other projects had "multi-agent" when it's just a bunch of llm calls.
Initially the coding and software dev agents were called workflows, but to make it more agenty I was ok with it being called an agent if the result of an llm call affected the control flow
No, a chat bot using tools (e.g. GPTs) is an "assistant."
An LLM agent is not a chat bot, unlike an assistant. It is a primarily or fully autonomous LLM driven application which "chats" primarily with itself and/or other agents.
In other words, assistants primarily interact with humans while agents primarily interact with themselves and other agents.
I'm going to make the availability of requestFeedback function a boolean flag, so when running benchmark suites etc it can be disabled. Whether its an assistant or agent by that definition is just really a parameter value.
Initially the coding and software dev agents were called workflows, but to make it more agenty I was ok with it being called an agent if the result of an llm call affected the control flow