Lesson 10 · Foundations · ~7 min

Chatbot vs. Agent: What's Really Different?

Maybe this has happened to you. You asked an AI to do something real — "sort these files and email me a summary" — and it took off, did five things in a row, and got one of them wrong. Impressive and a little alarming at the same time. What is that, exactly? It isn't the chatbot you're used to.

Way back in the first lesson, we said an agent is an LLM that's been given hands — it can act, not just talk. And then we left it there. Time to open it up, because the whole difference comes down to a single picture.

A chatbot moves in a straight line

Start with the thing you already know. When you type into a chatbot, here's the entire trip. Behind the chat window, it reads your whole conversation fresh — every message, top to bottom — improvises a reply, sends it back, and then goes quiet. One question, one answer. A single round trip, and it's done until you type again.

That's worth sitting with, because it kills a common myth: there's no little person in there between your messages, waiting and remembering. Nothing is happening at all until you hit send. Each time, it wakes up, re-reads the whole thread, answers, and goes idle again.

And the "thinking"? Same as before — it isn't pondering your question the way a person would. It's the well-read improviser, building the next likely words from everything it has taken in. Hold onto that, because it's about to explain the agent too.

An agent moves in a loop — with hands

Now the other shape. You don't hand an agent a single question; you hand it a goal. "Plan a week of dinners and put the shopping list in my notes." And instead of one round trip, it starts circling:

  • It thinks: what's the first step?
  • It reaches for a tool to do that step.
  • It looks at what came back.
  • It thinks again: okay, what now?
  • …and around once more, step after step, until the goal is met — then it reports back to you.

Picture a capable assistant working down a to-do list, checking each result before moving to the next. That loop — think, act, look, think again — is the whole difference. A chatbot talks. An agent works.

Chatbot
it talks
You ask
Behind the chat window: reads the whole chat, improvises a reply
Reply — then it goes idle
Agent
it acts
Your goal
repeat until done
Think: what's next?
Use a tool
Look at the result
tools it can reach for
webappcalendarcode
Report back
A chatbot runs in a straight line; an agent runs in a loop, reaching for tools each time around.

So what's a "tool"?

That word is doing a lot of work, so let's pin it down. A tool is just an ability the agent is allowed to reach for: searching the web, opening an app, running something, checking your calendar or your email.

Here's the part that surprises people. The AI doesn't suddenly grow new powers. It's handed access to abilities that already exist out in the world. On its own it can only produce words — but if those words are allowed to press the buttons (run the search, send the email), it can start getting real things done. The hands aren't magic. They're permissions.

How does it know which tool to grab?

The same way it does everything else — and this is the satisfying part. It's still the well-read improviser. Just as it predicts the next likely word, it predicts the next sensible action: "given this goal and what just happened, reaching for the calendar is probably what comes next." Pattern, not understanding.

Which is exactly why it sometimes gets it wrong. A bad guess about the next word gives you an awkward sentence. A bad guess about the next action — grabbing the wrong tool, or doing the right thing to the wrong file — actually does something. That's the flip side of handing it hands.

A peek through the builder's door

Ever wonder how people build these things? Quick peek, then we move on. Builders lean on ready-made toolkits (this is the one spot the word framework belongs) to wire an agent up to its tools. LangChain is a general-purpose one — a kind of Swiss Army knife for connecting an AI to tools, data, and memory. CrewAI is for setting up several agents that each play a role and work together like a small team.

You don't need either of these. They're where the builder's path begins — a different course entirely. It's just good to know the names aren't magic spells; they're workshops.

Why this matters when you're the one using it

So: an assistant with hands. What does that change for you, in practice?

It's more powerful, and more worth watching. Because an agent acts on its own, a wrong step early can quietly snowball — that's the "it went off and botched one of five things" feeling from a minute ago. It's also slower and pricier: every trip around the loop is another call to the AI, and (thinking back to what we said about cost) more calls means more cost.

And that's the mystery gone. An agent was never a different creature — it's the same language brain from before, the same improviser, set loose in a loop and handed a few tools. Talker becomes doer; that's the whole trick.

Which leaves exactly one thing — and it's the most useful skill of all. Whether it's an agent acting on its own or a chatbot just answering you, every bit of this runs on an improviser that can be calmly, confidently wrong. So how do you catch it before it costs you? That's where we finish.

← PREVIOUS
AI Isn't Just for Writing: Images, Audio, Video & Code