What is an agent step?

An agent step is one individual unit of work performed by an AI agent during task execution.

A step usually starts with the agent's current state, produces a decision or action, receives a result, and updates the state before the next step begins.

A simplified view is:

Current state → Decide or act → Receive result → Update state

What happens in one agent step?

Depending on the agent design, a step may include:

• reading the current goal and state
• deciding what to do next
• calling a tool
• processing the tool result
• updating task state
• determining whether another step is needed

Not every step must contain a tool call.

For example, one step might decide that the agent already has enough information to return a final answer.

Example

Suppose an agent is investigating why an order has not shipped.

The current state says:

• order exists
• payment completed
• shipping status unknown

One agent step might be:

Decision: Check inventory availability. Action: Query inventory system. Result: Item is out of stock. State update: Record that inventory is the likely cause of the delay.

The next agent step can now use this updated state.

Steps build on previous steps

Agent execution is usually sequential in the sense that each step can use information produced by earlier steps.

For example:

Step 1: Check payment status. Step 2: Check inventory. Step 3: Check expected restock date. Step 4: Return the explanation to the user.

The exact number of steps depends on the task and what happens during execution.

A step is not the entire task

A single agent step is only one part of the overall execution.

For a simple task, one step may be enough.

For a complex task, the agent may need many steps before the goal is complete.

The broader repeated process is covered in “What is an agent execution cycle?”

Step boundaries depend on the framework

Different agent systems define a step differently.

In one framework, a step may mean:

• one model decision

In another, it may include:

• one model decision plus one tool execution

In a graph-based agent system, a step may correspond to:

• execution of one node or transition

The important idea is that a step represents a bounded unit of progress inside the larger agent run.

Why agent steps matter

Tracking work as steps helps developers:

• monitor agent progress
• debug failures
• record tool usage
• enforce execution limits
• measure cost and latency
• prevent uncontrolled loops

For example, an agent may be configured to stop after a maximum number of steps if it has not completed the task.

That concept is covered separately in “What is a maximum-step limit in an agent?”

In short

An agent step is one bounded unit of execution inside an AI agent's larger task-processing cycle.

Each step uses the current state to make progress, produces new information or an action, updates the state, and prepares the agent for the next step.