What is an LLM agent?
The short answer
An LLM agent is a system that uses a large language model as its reasoning engine to plan, call external tools, and act in a loop until a goal is reached. Unlike a plain chatbot, an agent observes the environment, decides the next action, executes it (web search, code, API call, file edit), reads the result, and iterates. The pattern was formalized in the ReAct paper (Yao et al., arXiv:2210.03629, ICLR 2023) and is now implemented in OpenAI's Agents SDK, Anthropic's Claude Agent SDK, Google's Agent Development Kit, and Microsoft AutoGen.
The longer answer
The phrase "LLM agent" describes a control loop, not a model. The model — Claude, GPT, Gemini, Llama — is the reasoning core, but the agent is the surrounding software that decides what to do with that reasoning. The canonical loop is: receive a goal, generate a thought, choose a tool, execute the tool, observe the output, repeat. When the agent decides the goal is complete, it stops and returns a final answer.
The intellectual origin is the ReAct ("Reasoning and Acting") paper by Shunyu Yao and collaborators at Princeton and Google Research (arXiv:2210.03629), which showed that interleaving chain-of-thought reasoning with tool calls outperformed either alone on HotpotQA and ALFWorld benchmarks. A second key primitive is tool use: the model emits a structured function call (JSON arguments matching a declared schema), the runtime executes it, and the result is appended to the context. OpenAI shipped function calling in June 2023; Anthropic's tool use went GA in May 2024; both converged on JSON-schema-typed tool definitions.
Modern agents extend this loop with memory (short-term scratchpad plus long-term vector recall), planning (decomposition into subgoals, as in Plan-and-Solve, arXiv:2305.04091), and self-reflection (Reflexion, arXiv:2303.11366). Multi-agent systems compose several LLM agents with distinct roles — researcher, coder, critic — coordinated by an orchestrator. Microsoft's AutoGen framework (arXiv:2308.08155) and the open-source CrewAI library popularized this pattern in 2024.
Production deployments are real but narrow. GitHub Copilot Workspace, Cursor, Devin (Cognition Labs), Claude Code, and OpenAI's Operator are agent products shipped to paying customers. Benchmarks show the technology is improving fast but is still error-prone: on SWE-bench Verified — a curated set of 500 real GitHub issues from popular Python repos — top agents hit roughly 65-72% resolution rate as of late 2024, up from under 5% eighteen months earlier (per the SWE-bench leaderboard maintained by Princeton's NLP group). On the GAIA benchmark for general assistant tasks (arXiv:2311.12983), top agents score around 65% versus 92% for humans.
Security is the unsolved problem. The OWASP Top 10 for LLM Applications (2025 edition) lists prompt injection (LLM01), insecure output handling (LLM02), and excessive agency (LLM06) as the leading risks for agentic systems. NIST AI 600-1 (the Generative AI Profile of the AI Risk Management Framework, published July 2024) names confabulation, data poisoning, and CBRN-uplift among the twelve categories of GAI-specific risk. The agent's ability to take real-world actions — send email, transfer money, modify files, browse — multiplies the blast radius of any prompt injection.
The terminology is still settling. Anthropic's published taxonomy (Schluntz and Zhang, "Building effective AI agents," December 2024) distinguishes workflows (predetermined LLM-plus-tool chains) from agents (systems where the LLM dynamically directs its own process). Most production systems labeled "agents" today are closer to workflows; true open-ended agents remain a research frontier.
Key facts
- The ReAct paradigm — interleaved reasoning and tool calls — was introduced by Yao et al. in October 2022 (arXiv:2210.03629) and published at ICLR 2023.
- OpenAI shipped function calling in
gpt-3.5-turbo-0613andgpt-4-0613on June 13, 2023, establishing JSON-schema tool definitions as an industry standard. - Anthropic's tool use went generally available across the Claude 3 family on May 30, 2024 (Anthropic news post).
- SWE-bench Verified is a 500-task subset of SWE-bench (arXiv:2310.06770) human-validated by OpenAI in August 2024 to filter out underspecified tasks.
- The GAIA benchmark (arXiv:2311.12983) by Mialon et al. tests assistants on 466 real-world questions requiring web browsing, code, and multimodal reasoning.
- AutoGen, Microsoft Research's multi-agent framework, was introduced in arXiv:2308.08155 (August 2023) and is now part of the .NET Foundation.
- NIST AI 600-1 (July 2024) is the official Generative AI Profile of the AI RMF and enumerates twelve GAI-specific risks.
- OWASP Top 10 for LLM Applications v2025 lists Excessive Agency (LLM06:2025) as a top-tier risk for agent deployments.
- Reflexion (arXiv:2303.11366) demonstrated that verbal self-reflection on failures could lift a GPT-4 agent's HumanEval pass@1 from 80% to 91%.
- The Model Context Protocol (MCP), open-sourced by Anthropic on November 25, 2024, standardizes how agents connect to external tools and data sources.
Related questions
Sources
- Yao, S. et al. "ReAct: Synergizing Reasoning and Acting in Language Models." arXiv:2210.03629. arxiv.org/abs/2210.03629
- Schluntz, E. and Zhang, B. "Building effective agents." Anthropic, December 19, 2024. anthropic.com/research/building-effective-agents
- Mialon, G. et al. "GAIA: a benchmark for General AI Assistants." arXiv:2311.12983. arxiv.org/abs/2311.12983
- Jimenez, C. et al. "SWE-bench: Can Language Models Resolve Real-World GitHub Issues?" arXiv:2310.06770. arxiv.org/abs/2310.06770
- NIST. "AI 600-1: Artificial Intelligence Risk Management Framework: Generative AI Profile." July 2024. nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf
- OWASP. "Top 10 for LLM Applications 2025." genai.owasp.org/llm-top-10
- Wu, Q. et al. "AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversation." arXiv:2308.08155. arxiv.org/abs/2308.08155
- Anthropic. "Introducing the Model Context Protocol." November 25, 2024. anthropic.com/news/model-context-protocol