Agentic workflows (the loop)
Goal → plan → tools → observe → loop — vs a single chat reply.
Most chat use is single-shot: you ask, you get a reply, you’re done (or you ask again yourself). Agentic systems try to chase a goal by planning, calling tools, reading results, and looping until they finish — or until a limit stops them.
Single-shot first
That’s enough for many beginner tasks. Your personal AI workflow sits on top: you still research, verify, and cite.
The agentic loop
Solid arrows = forward steps (numbered). Dashed teal arrow = “loop if not done,” also labeled in the diagram.
In plain words:
- Goal — What should be true when we’re done?
- Plan — Break the goal into steps (the system may rewrite the plan as it goes).
- Act — Call tools: search, code, calendar, files, APIs.
- Observe — Read what the tool returned; notice errors.
- Loop or finish — Update the plan and act again, or stop when the goal looks met.
See also: Glossary — Agent, Agentic workflow.
Why beginners go slow here
- More steps means more ways to spend money, leak data, or take a wrong action.
- A fluent loop is not the same as a correct loop — you still verify outcomes.
- Prefer supervised / sandboxed agents before anything that can email, buy, or delete.
From the tool landscape: start with chat; treat agents as “powerful; start supervised.” For how apps reach cloud-hosted models in that loop, see how clouds serve frontier models.
Takeaway
Single-shot = one generation. Agentic = goal-driven loop with tools. Same models often power both — the workflow shape is what changes.
Pick a task (e.g. “find three reputable sources on X and draft a paragraph”). Sketch it once as single-shot chat, once as the five-step loop. Which steps would you insist on doing yourself?