Updated: October 6, 2026 · Source-first reference130 documented agents & platforms · No paid rankings

AgentenCode Knowledge

What is an AI agent?

AI agents go beyond one-shot text generation: they can interpret a goal, gather context, plan, use tools, observe results and decide what to do next within the permissions they have been given.

Direct answer

An AI agent combines a model with goals, context, tools and an execution loop so it can work through multiple steps and act on external systems.

The core characteristics of an AI agent

An AI agent is best understood as a software system that uses an AI model inside an execution loop. The model is important, but it is only one component. The system also needs context, instructions, access to tools or data, and logic for deciding what should happen after each result.

The most important difference from a simple response generator is continuity. An agent can move from one step to the next, keep state, react to tool output and pursue a goal until it reaches a stopping condition. The amount of autonomy varies widely: some agents merely prepare a draft, while others can execute approved actions in business systems.

How an AI agent works

A typical loop starts with a goal. The agent interprets that goal, decides what information is missing, chooses a next step and may call a tool such as search, code execution, a CRM connector or a browser. It then observes the result, updates its working state and continues.

This loop can be short and deterministic or long and adaptive. A coding agent may inspect a repository, modify files, run tests and revise its approach. A research agent may search multiple sources, compare evidence and produce a cited synthesis. An enterprise agent may read a ticket, query internal systems and request approval before changing a record.

The main building blocks

The model provides reasoning and language capability. Instructions define the role and boundaries. Tools connect the agent to external systems. Memory or persistent state can carry information across steps or sessions. Retrieval can bring in documents or structured knowledge. Orchestration determines how tasks, subagents and approvals are coordinated.

Identity and permissions are equally important. An agent that can only read a public webpage has a very different risk profile from one that can send email, modify cloud infrastructure or initiate a payment. The deployed system—not the model name alone—determines what the agent can actually do.

Agent, assistant, chatbot or workflow?

A chatbot is optimized for conversation. An assistant can combine conversation with tools but may still rely on the user to drive every step. A workflow follows predefined logic. An agent is typically more flexible in choosing intermediate steps, but real products often combine all four patterns.

The label itself is therefore less useful than concrete questions: Can the system choose tools? Can it take multiple steps without a new user message? Can it change external state? Does it keep memory? Which actions require approval? Those answers reveal the actual level of agency.

Autonomy is a spectrum

Autonomy is not a binary property. One agent may only read and analyze; another may propose actions for approval; another may execute low-risk actions automatically while pausing on sensitive ones. The right design depends on the use case and the cost of error.

For high-impact actions, human approval, least-privilege permissions, logging and rollback can be more important than making the agent maximally autonomous. A useful agent is not necessarily the agent with the fewest human checkpoints.

Risks and evaluation

Agents can amplify both capability and mistakes because they can repeatedly use tools and act on external systems. Prompt injection, excessive permissions, incorrect tool selection, stale memory, hidden assumptions and weak auditability can all become operational risks.

Evaluation should therefore include task success, reliability, cost, latency, security boundaries, source quality, observability and the ability to recover from failure. AgentenCode separates these dimensions instead of compressing them into a single “best agent” score.

Where to continue

Use the AgentenCode directory to compare actual products, the Trust & EU layer to inspect documented governance controls, and the methodology page to see how evidence is verified. For a specific product, the Agent Profile remains the place where current capabilities, sources and history are tied together.

Sources and further reading

Frequently asked questions

Is ChatGPT an AI agent?

Some ChatGPT experiences can behave agentically when they use tools, run multi-step tasks or act through connected systems. The product name alone is not enough; the specific feature and execution mode matter.

Does an AI agent need memory?

No. Memory can improve continuity, but an agent can still be agentic with only temporary working state.

Are AI agents autonomous?

They can be, but autonomy exists on a spectrum. Many production systems deliberately require human approval for consequential actions.

Primary sources and further reading

These sources support the technical patterns described above and should be preferred over secondary summaries when implementation details change.

  1. Google Cloud – Choose agentic AI architecture components
  2. OpenAI – Developer quickstart: tools and agents
  3. NIST – Identity and authority of software agents