Good AI agent examples share one property: a language model chooses the next action, reads the result and chooses again, until a check or a budget ends the run. Coding agents, research agents and incident investigators have it. A recommendation feed, an FAQ bot and a nightly summarize-and-post job, often listed beside them, do not.
Most pages that rank for this query are lists of products and industries. Several of them count a thermostat, a self-driving car and a streaming service’s recommendations as “AI agents”, which is true in an old textbook sense and useless when you have a ticket that says “build an agent”. You can’t learn what to build from a list that mixes the two.
So this guide sorts real-world AI agent examples by category and asks the same five questions of each: what does it loop on, which tools does it hold, how does the run end, what checks the result from outside the model, and what can a wrong action damage. The same five questions are then asked of the popular counter-examples. The definition comes from Chapter 1 of AI Agents, Engineered, which is free to read; the categories, the table and the worked example are this post’s own work.
What makes an AI agent example count as an agent?
An example counts when a language model, given a goal and a set of tools, decides the sequence of actions at runtime and code holds the limits. Chapter 1 puts it in one line: “An agent is a language model placed in a loop.” The rest of the definition is the motion of that loop.
“It looks at the state of the task, picks an action, sees the result, and goes again, until it judges the goal met or a stopping rule ends the run.”
A tool is an ordinary function your program runs when the model asks for it: search this, read that file, run the tests. A request to run one is a tool call. The practitioner shorthand the book adopts is Simon Willison’s: “An LLM agent runs tools in a loop to achieve a goal” (Willison, 2025).
The division of labor is what makes the five questions answerable. Chapter 3 states it this way: “the model supplies the judgment—which tool, with what arguments, and whether the job is done—and your code supplies everything else: the hands, the memory, and the stop button” (Chapter 3, The Agent Loop (in the full book)). Everything your code supplies is the harness, and four of the five questions are about the harness, which is the part you build and own.
Here are the five properties, defined once so the table can stay short:
- The loop: what the model does again after each result. No repeat, no agent.
- The tools: the functions it can ask for, which set the edge of what it can touch.
- How the run ends: the stop condition. Chapter 3 is blunt that “a loop whose only exit is the model’s judgment is a loop with no guaranteed exit at all”, so a real agent has a budget in code as well.
- The outside check: the signal, from outside the model, that tells you the result is right. Chapter 3 again: “The model’s “done” is testimony; a green test is evidence.”
- The blast radius: in Chapter 1’s words, “the damage a wrong action could do before anything stops it”. It is set by the tools and their permissions (blast radius).
If you want the formal test with verdicts, what an AI agent is runs five cumulative checks on a trace. This post applies the idea category by category.
Which AI agent examples hold up, side by side?
Eight categories of AI agent examples hold up under the five questions, and five common counter-examples do not. Pick a verdict in the filter to see only those rows; every row stays in the page. The product names are examples of the category, mostly open-source projects described from their own repositories. None is a recommendation, and I did not benchmark any of them.
| Example (labeled instances) | What it loops on | Tools it holds | How the run ends | What checks the result | Blast radius | Verdict |
|---|---|---|---|---|---|---|
| Coding agent (e.g. OpenHands, SWE-agent) | Read code, edit, run the tests, read the failure | File read and edit, a shell, the test runner | Suite green, or a step or cost budget | The test suite; a person reviewing the diff | The repository and whatever the shell can reach; contained by a sandbox and a pull request | agent |
| Research agent (e.g. GPT Researcher, the research feature Anthropic described in 2025) | Search, open sources, revise the sub-questions | Web or document search, a page reader | The model judges coverage sufficient; a budget on searches or time | Citations a person can open; a claim-checking pass | Words: a wrong claim that someone acts on | agent |
| Support agent with tools (mostly commercial; no product named) | Read the ticket, look up the account, act, reply | Order lookup, knowledge base, refund, ticket update | Resolved, or handed to a person; a turn cap | The customer’s confirmation; refund caps and an action log in code | Deeds: money moved, records changed, messages sent | agent |
| Data-analysis agent (e.g. PandasAI; whether a given setup loops shows in its trace) | Write a query or code, run it, read the result or the error, revise | SQL or code execution on the data | An answer; a step budget | Re-running the query; a number checked against a known figure | A wrong number in a report; the data itself, if it can write | agent |
| Browser or computer-use agent (e.g. Browser Use) | Look at the page, click or type, look again | Page snapshot or screenshot, click, type, navigate | Task done, or a step budget; a stop before submitting or paying | The page state after each action; a person confirming the submit | Anything the logged-in session can do | agent |
| Incident-investigation agent (e.g. HolmesGPT) | Query logs and metrics, form a hypothesis, query again | Read-only observability queries; sometimes runbook actions | A root-cause report; a time budget | The on-call engineer; whether the alert clears after the fix | Read-only: time lost on a wrong diagnosis. With remediation tools: production | agent |
| Personal assistant (e.g. OpenClaw) | Read the request, check mail or calendar, act, report back | Email, calendar, messaging, files, sometimes a shell | Request done, or a question back to the person; a budget | The person, who sees the outcome | The person’s accounts: sent mail, accepted invites, deleted files | agent |
| Multi-agent research pipeline (e.g. the same Anthropic research feature) | A lead agent plans, starts subagents, each loops; the lead merges | Subagents as tools; search | The lead judges it done; a budget per subagent | Citations; the lead’s merge; a person | Its workers’ blast radius, plus a larger bill | agent |
| Recommendation feed (listed as an “AI agent” on several list pages) | Nothing: a ranking model scores items | None the model asks for | Every request ends after one ranking | Click-through and A/B tests | A bad ranking | no language model |
| FAQ bot over help-center articles | Nothing: one model call per message | None; your code fetches the articles | After one reply | Sampled answers against the articles | A wrong answer, which your company has still said | chatbot |
| Chat assistant with one order lookup | Nothing: one tool call per turn | One read-only lookup | After one reply | The answer matches what the lookup returned | A wrong answer from a stale lookup | chatbot with tools |
| Nightly summarize-and-post job | Nothing: fixed steps in a fixed order | Your code calls them, the model fills in text | After the last step | Each step against its contract; a test set for the route | The same error in the same place on every run | workflow |
| Four-step ticket pipeline (classify, fetch policy, draft, check) | Nothing: the route was drawn in advance | Your code calls them | After the fourth step | Each step’s check; the human review queue | A bad draft that a reviewer should catch | workflow |
Two columns do most of the sorting of these AI agent examples. “What it loops on” separates the agents from everything else, and “Blast radius” separates the agents from each other. The last two rows are close to a line in Chapter 1, which uses the four-step ticket pipeline as its example of a workflow: “you could have drawn its flowchart before switching it on.”
What does each kind of AI agent loop on?
Each category of AI agent examples loops on a different kind of feedback, and the kind of feedback decides how trustworthy the category is. Chapter 3 opens with three of them, “the coding assistant rewriting a module, the research agent compiling a briefing, the triage system working a queue”, and says the core of every one of them “is a loop simple enough to write on an index card.” What differs is the harness around the loop.
Coding agents
A coding agent loops on test results: it edits, runs the suite, reads the failure and edits again. It is the cleanest of all AI agent examples because the check lives outside the model. Schluntz and Zhang list the reasons: “Code solutions are verifiable through automated tests” and “Agents can iterate on solutions using test results as feedback” (Schluntz and Zhang, 2024).
Chapter 1’s own example is this category: told that “the checkout tests are failing—fix them”, the agent “searches the codebase, reads three files, edits one, runs the tests, reads the new failure, edits again, and stops when the suite is green.” SWE-agent’s repository describes the same shape in one line: it “takes a GitHub issue and tries to automatically fix it”.
The blast radius is whatever the shell can reach. That is why coding agents usually run in a sandbox and hand back a branch or a pull request instead of merging.
Research agents
A research agent loops on what it reads: it searches, opens sources, and rewrites its own sub-questions as it learns the field’s vocabulary. The steps can’t be scripted, which is what makes it an agent. The team behind one production research system wrote that research involves “open-ended problems where it’s very difficult to predict the required steps in advance” (Anthropic, 2025).
Its weak point is the check. Chapter 23 puts the difference in one line: “A research agent’s product is words.” A business agent’s product, the same chapter says, is deeds (Chapter 23, Research and Business Agents (in the full book)). No compiler checks a paragraph, so the outside check has to be built: citations a person can open, a pass that checks claims against them, a person who spot-checks the claims that matter. The book calls the distance between a fluent report and a verified one the verification gap.
Support agents with tools
A support agent loops on the customer’s account: it reads the ticket, looks up the order, decides, acts and replies. Schluntz and Zhang describe the category as one that “combines familiar chatbot interfaces with enhanced capabilities through tool integration”, where “Actions such as issuing refunds or updating tickets can be handled programmatically.”
This category is where the chat window misleads. The same widget can be a chatbot with one lookup or an agent that chains a lookup, a refund and a ticket update, and from the outside they look alike. The difference is whether the model can choose another action after reading a result, which AI agent vs chatbot turns into six questions. Once it can issue a refund, the blast radius is money, and the harness owes a cap in code and an approval gate above the cap.
Data-analysis agents
A data-analysis agent loops on query results and errors: it writes SQL or code, runs it, reads what came back and revises. The one-shot version stops after one decision. If the model asks for one query in a chat turn and answers from the table, that is a chatbot with tools; if your code runs the model’s query on every request, or inside a reporting job, it is a workflow step.
The loop earns its cost when the first query usually fails or misleads: a column that doesn’t exist, a join that doubles the rows, a total that looks wrong. The outside check is weak unless you build one, so a good analysis agent reconciles at least one number against a figure someone already trusts. Read-only database credentials keep the blast radius at “a wrong number”.
Browser and computer-use agents
A browser agent loops on the screen: it looks at the page, clicks or types, and looks again to see what changed. Browser Use describes itself as an “Open-source Python library for AI browser agents”. The loop is the same one, and the tools are a page snapshot, a click and a keystroke.
Chapter 5 sets the ways an agent can reach software on a ladder: an API wherever one exists, then a structured browser tool that acts on named page elements, and pixel-level computer use last, “maximally general, slowest, most fragile” (Chapter 5, Tools and the Action Space (in the full book)). The blast radius is whatever the logged-in session can do, which can include buying, sending and deleting. The usual control is a hard stop before any submit or payment, enforced by the harness and not by the prompt.
Incident-investigation agents
An incident agent loops on evidence: it queries logs and metrics, forms a hypothesis, and queries again to confirm or drop it. HolmesGPT’s README calls it an “Open-source AI agent for investigating production incidents and finding root causes”, and it was a Cloud Native Computing Foundation sandbox project when I read it.
Kept read-only, this is one of the safer AI agent examples to start with: the worst case is a wrong diagnosis that costs the on-call engineer time. The check is the engineer, plus the plainest outside signal there is, whether the alert clears after the fix. Give it restart or rollback tools and the blast radius becomes production, which belongs behind the consequence tiers sized by the consequence tier classifier.
Personal assistants
A personal assistant loops on your accounts: it reads a request, checks the calendar or the inbox, acts and reports back. OpenClaw’s README calls it “an open-source AI assistant that runs on your own computer and meets you in the channels you already use”. It is an agent when it chains steps itself: find the thread, check three calendars, propose a slot, send the invite.
The check is you, after the fact, which is the weakest place for a check to sit. The blast radius is your identity: email sent in your name, invites accepted, files deleted. Assistants that can also read untrusted email combine private data, untrusted input and a way to send, the combination Chapter 17 calls the lethal trifecta, so the safest assistants draft and wait for you on anything outbound.
Multi-agent pipelines
A multi-agent pipeline is several loops, one of which starts and merges the others. In the research system described above, “a lead agent coordinates the process while delegating to specialized subagents that operate in parallel”, which is the orchestrator-worker pattern; each worker is a subagent with its own loop.
Every property of a single agent applies to each worker, and the bill grows. The same write-up reports that, “In our data”, agents “typically use about 4× more tokens than chat interactions, and multi-agent systems use about 15× more tokens than chats” (Anthropic, June 2025; their system, their measurement). Treat the multipliers as one team’s data. The direction is the part that carries over.
Which popular AI agent examples are not agents?
Five kinds of system are often listed as AI agents and fail the loop question: recommendation feeds, FAQ bots, chat assistants with one lookup, scheduled pipelines and vendor “agents” that are fixed flows. Each is useful, and each needs less harness than an agent. Calling them agents only hides what they are.
Recommendation feeds and thermostats. One ranking page says, “Platforms like YouTube and Netflix use AI agents to automatically recommend content to users” (Unito, 2025). In the textbook sense, where an agent is anything that perceives and acts, that is fair. In the engineering sense there is no language model choosing tool calls, so the honest name is automation, or a learned model of another kind.
FAQ bots over help articles. Your code fetches the articles, the model writes one answer, and the person reads it. That is a chatbot, and Chapter 1 says it plainly: “Chatbots are genuinely useful and often the right tool”.
A chat assistant with one lookup. One read-only call per message, then a reply, then it waits. The person still chooses every next step, so it is a chatbot with tools. A Hacker News commenter made the same call about voice assistants in January 2025: “it’s basically an LLM with function calling” (dimitri-vs, 2025).
Scheduled pipelines with a model step. A nightly job that pulls tickets, asks a model to summarize them and posts the summary runs unattended, and it is still a workflow: code fixed the steps. Running without a person describes the trigger. It says nothing about who chooses the path.
Vendor “agents” that are fixed flows. One commenter observed in March 2025 that what the essay above calls a workflow “is what most of the big enterprise software companies (Salesforce, ServiceNow, Workday, SAP, etc.) are building and calling AI Agents” (DebtDeflation, 2025). That is one person’s reading, and the practice it describes has a name, agent-washing. Ask for a trace of two different requests: if both followed the same steps, you are looking at a workflow.
None of this is a ranking. Chapter 1’s calibration pair makes the point: routing each email “to billing, technical, or sales” and drafting a reply “wants a workflow”, while making a failing test pass in an unfamiliar codebase “is a genuine agent problem.” The rule for choosing between them is in the agents vs workflows decision rule.
Worked example: one dependency bot, built two ways
The same product can be a workflow or an agent depending on one design choice, and the five properties show which you built. Take a bot that keeps a service’s dependencies current, a ticket many backend teams have seen.
Build A. A nightly job bumps one dependency, runs the test suite and, if it passes, opens a pull request whose description a model writes. If the tests fail, it opens an issue with the log attached. Run the five questions. Loop: none, since the model’s output never decides what runs next. Tools: none the model asks for. End: after the last step. Check: the test suite. Blast radius: one pull request that a person must merge. Verdict: a workflow with one model call, and a good one.
Build B. Same trigger, but when the tests fail the model reads the failure, opens the files it names, edits the call sites that broke, and reruns the tests. It repeats until the suite is green or it has used, say, fifteen passes (an illustrative cap; set yours from real traces). Two upgrades that break differently produce two different sequences of edits that nobody wrote in advance. Verdict: an agent, a small coding agent.
What changed is the harness Build B now owes. It needs a step and cost budget in code, a sandbox with no production credentials, a rule that it can only push to its own branch, and a reviewer who reads the diff. The check is still the test suite, which is why this agent is a reasonable first one: the domain grades its own work.
There is a middle build worth naming because it fools people. If the model only decides “try again or give up” while code applies the same scripted fix each time, the model is repeating one step your code wrote. That is a workflow with a loop. The test is whether the sequence of actions could differ between two runs in ways you could not have drawn beforehand.
How autonomous are real-world AI agents?
Most deployed AI agent examples run on a short leash: a few steps, then a person. In a study of production agents built from 20 case studies and a survey of 86 practitioners, “68% execute at most 10 steps before human intervention” (Pan et al., arXiv:2512.04123, v4, June 2026). That sample is of teams willing to be studied, so read it as a description of them.
It matches Chapter 1’s description of what ships: “Almost nothing that ships is a pure workflow or a pure agent. The dominant production shape is a workflow shell with one or two genuinely agentic steps inside it”. A practitioner on Reddit described the same shape in May 2026 (agent_trust_builder, 2026): the agent handles the fuzzy front end, and regular code handles “anything that actually makes a decision or touches money.”
So when you look for autonomous AI agents examples, expect agents placed on a dial. Chapter 1 locates much of production at the point where an agent “loops freely over its tools but pauses for human approval before anything consequential”. Coding agents that open pull requests and incident agents that report to a person both sit there.
How do you classify the next example you meet?
Ask for a trace, the step-by-step record of one run, of two different requests, and answer the five questions from it. If you can’t get a trace, the person who built the system can answer them in ten minutes. These are the questions, in the order that settles things fastest:
- Does the model choose an action, read its result and choose another action, with no person choosing in between? Writing the final reply after one lookup does not count. If not, it is a chatbot, a chatbot with tools, a workflow, or automation with no model in it; AI agent vs chatbot tells those four apart.
- Could two requests produce two different sequences that nobody wrote down? If not, it is a workflow, possibly with a loop.
- What ends the run, and is there a cap in code? No cap means an agent you shouldn’t run yet.
- What checks the result from outside the model? Tests, citations, a reconciled number, a person. If the only check is the model saying “done”, treat the result as a claim.
- What can its tools change? Read-only, drafts for a person, or deeds. That answer sets how much harness you owe.
Chapter 1 gives the shortest form of the first two questions as its litmus test: “If you can confidently draw the control-flow diagram before the request arrives, you are looking at a workflow. If the diagram can only be drawn in hindsight, once the model has reacted to what it found, you are looking at an agent.” If your own idea came out “agent”, the Should this be an agent? tool tests whether it should stay one.
Where does this classification stop working?
It stops working in three places. First, products change under their names: a chat assistant gains a second tool call in one release and becomes an agent with nobody announcing it, so classify the build you are running, not the product page.
Second, mixed systems are the norm. A workflow shell with one agentic step owes the workflow’s per-step checks and the agent’s budget and trace on that step, and the table’s single verdict per row hides that. Third, the labeled examples are open-source projects described from their own repositories on the day I read them. Their behavior depends on how they are configured, and I make no claim about how well any of them works.
The categories also say nothing about which business problem deserves an agent. For that, the AI agent use cases for startups sorts ideas into eight recurring shapes, each with its starting autonomy and usual failure.
The takeaway
The useful question about any AI agent example is what checks its result from outside the model. Coding agents lead because a test suite answers it; research agents need citations a person can open; agents that act need caps and gates before the first action. Chapter 1 asks the same question of every design: “what signal tells you it worked?”
Chapter 1, “What Is an Agent?” is free to read online and holds the definition, the litmus test and the dial quoted above. Chapter 3, The Agent Loop (in the full book) builds the loop and its stop conditions, and the agent loop explainer shows it in motion. The agent fundamentals guide collects the related posts and tools, and you can see the formats.
Questions readers ask
- What are some real-world examples of AI agents?
- Coding agents that edit code and rerun tests until they pass, research agents that search and revise their questions, support agents that look up an order and issue a refund, data-analysis agents that query and re-query, browser agents, incident investigators, personal assistants and multi-agent research pipelines. Each is an agent because a model chooses the next tool call in a loop.
- Is a chat assistant an AI agent?
- Not by default. A chat assistant that writes a reply and waits for your next message is a chatbot, and one that makes a single lookup per message is a chatbot with tools. It becomes an agent when the model reads a result and chooses another action itself, more than once, with nobody choosing in between.
- What is an example of an autonomous AI agent?
- A coding agent told to fix failing tests, which searches the code, edits a file, runs the suite, reads the new failure and stops when the suite is green, is the standard example. Autonomy is a dial, though: most deployed agents pause for a person before consequential actions and run a few steps between checks.
- Are recommendation systems and self-driving cars AI agents?
- In the textbook sense, where an agent is anything that perceives and acts, yes. In the engineering sense used for LLM agents, no: a recommendation feed has no language model choosing tool calls in a loop. Many list pages mix the two senses, which is why their examples are hard to learn from.
- Which kind of AI agent should a team build first?
- One whose result an outside signal can check and whose actions are contained: a coding agent working on a branch behind tests, or a read-only research or incident agent whose report a person reads. Agents whose actions move money or send messages come later, behind caps and approval gates.
Read the first part offline.
Get the free PDF sample, the preface and all of Part I, plus a two-page checklist: does this need an agent at all, and would you know if it failed? Then a few short emails on verifying agents. One-click unsubscribe.
Sources
- Erik Schluntz and Barry Zhang (Anthropic) (2024). Building effective agents
- Anthropic (2025). How we built our multi-agent research system
- Melissa Z. Pan et al. (2025; v4 2026). Measuring Agents in Production (arXiv:2512.04123, v4)
- Simon Willison (2025). I think “agent” may finally have a widely enough agreed upon definition to be useful jargon now
- Nicholas Bouchard (Unito) (2025, updated 2026). 10 Examples of AI Agents (And the 5 Types of Agents)
- DebtDeflation (Hacker News) (2025). Hacker News comment 43421630
- dimitri-vs (Hacker News) (2025). Hacker News comment 42670087, in “Ask HN: Are there any real examples of AI agents doing work?”
- agent_trust_builder (Reddit) (2026). Reddit comment in r/aiagents
- OpenHands contributors (retrieved 2026). OpenHands (repository)
- SWE-agent contributors (retrieved 2026). SWE-agent (repository)
- Assaf Elovic and contributors (retrieved 2026). GPT Researcher (repository)
- Browser Use contributors (retrieved 2026). Browser Use (repository)
- HolmesGPT contributors (CNCF sandbox) (retrieved 2026). HolmesGPT (repository)
- Sinaptik AI and contributors (retrieved 2026). PandasAI (repository)
- OpenClaw contributors (retrieved 2026). OpenClaw (repository)