Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

An workflow is a collection of steps defined by someone, where the steps can be performed by an LLM call. (i.e. propose a topic -> search -> summarise each link -> gather the summaries -> produce a report)

The "agency" in this example is on the coder that came up with the workflow. It's murky because we used to call these "agents" in the previous gen frameworks.

An agent is a collection of steps defined by the LLM itself, where the steps can be performed by LLM calls (i.e. research topic x for me -> first I need to search (this is the LLM deciding the steps) -> then I need to xxx -> here's the report)

The difference is that sometimes you'll get a report resulting from search, or sometimes the LLM can hallucinate the whole thing without a single "tool call". It's more open ended, but also more chaotic from a programming perspective.

The gist is that the "agency" is now with the LLM driving the "main thread". It decides (based on training data, etc) what tools to use, what steps to take in order to "solve" the prompt it receives.



I think it's interesting that the industry decided that this is the milestone to which the term "agentic" should be attached to, because it requires this kind of explanation even for tech-minded people.

I think for the average consumer, AI will be "agentic" once it can appreciably minimize the amount of interaction needed to negotiate with the real world in areas where the provider of the desired services intentionally require negotiation - getting a refund, cancelling your newspaper subscription, scheduling the cable guy visit, fighting your parking ticket, securing a job interview. That's what an agent does.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: