Skip to content

What an agent actually is

How an Agent Differs From a Chatbot

The difference between a chatbot and an agent is not intelligence. It is usually the same model underneath. What changes is who does the work between steps, and that single change moves several things at once: speed, visibility, and how mistakes reach you.

The same task, done twice

Say you need to compare three project management tools for a small team and write up a recommendation.

With a chat assistant, you do the moving. You ask what to compare on. You paste in pricing pages. You ask it to draft a comparison. You spot that it has the wrong plan tier, correct it, and ask again. You read each answer as it arrives, so a mistake surfaces immediately and costs you one message.

With an agent, you state the goal and it runs. It searches, opens pages, extracts details, builds the table, writes the recommendation, and hands you a finished document. You did nothing in between. If it misread a pricing page in step two, that error is now baked into the recommendation in step nine, and nothing flagged it along the way.

Both used the same underlying model. The output quality differs mostly because of where you were standing.

What you gain

Time on multi-step work. Anything that involves fetching, transforming, and assembling from several sources is where agents earn their keep. You are not the bottleneck between steps.

Reach. An agent can act on systems a chat window cannot: files, databases, calendars, code repositories, browsers.

Persistence. It can retry, work around a failure, and keep going. A chat assistant simply stops and waits for you.

What you give up

Visibility. In chat, every intermediate answer passes through your eyes. In an agent run, most steps happen unobserved. You see a result, not the reasoning that produced it.

Early correction. A wrong assumption in chat costs one message. In an agent run it can silently shape everything after it. See where agents fail for how this compounds.

Predictability of cost. A chat turn is one request. An agent run may make dozens, and a loop that fails to notice it is stuck can make hundreds.

How to choose

Use chat when the thinking is the point, when you need to steer, when the material is sensitive, or when you would want to catch a mistake at the moment it appears. Drafting, explaining, deciding, and anything where you are still working out what you actually want.

Use an agent when the goal is clear, the steps are mechanical, the actions are reversible, and you can verify the result at the end. Gathering, converting, reformatting, filling in a structured document from sources.

A useful middle path is an agent that plans out loud and pauses for approval before anything irreversible. You keep most of the speed and get back most of the visibility. Our plan before you act prompt is built for exactly that.

The honest summary

Agents are not an upgrade that makes chat obsolete. They trade your attention for autonomy. That is a good trade when the task is well-defined and the failure modes are cheap, and a bad one when the task is ambiguous or the mistakes are expensive.

Key takeaway: the model is the same. What changes is whether a human sits between the steps, and that determines when you find out something went wrong.

Progress is saved in your browser only — no account, nothing sent anywhere.