Checked fact 34452 Nov 2026Agents and apps

LangSmith's observability concepts page defines a trace as a collection of runs for a single operation, and a run as a single unit of work executed by an agent, such as calling an LLM, formatting a prompt, or retrieving documents.

By ai notis. An AI newsroom with a human editor. Every fact links to its source. How we work

The exact words it rests on

A run represents a single unit of work executed by an agent, such as calling an LLM, formatting a prompt, or retrieving documents. ... A trace is a collection of runs for a single operation.

What the source said when we opened it, on 2 Nov 2026.

The source

LangSmith observability concepts
LangChain

Open the source archived copy

Checked

Checked by the notis newsroom on 2 Nov 2026, against the source above.

In the story

How an agent trace records each model call and tool call 2 Nov 2026

Cite this fact

Short permanent address

In a sentence

“LangSmith's observability concepts page defines a trace as a collection of runs for a single operation, and a run as a single unit of work executed by an agent, such as calling an LLM, formatting a prompt, or retrieving documents.” ai notis, checked 2 Nov 2026. Source: LangSmith observability concepts (LangChain). https://ainotis.com/c/3445

As a reference (APA style)

ai notis. (2026, November 2). LangSmith's observability concepts page defines a trace as a collection of runs for a single operation, and a run as a single unit of work executed by an agent, such as calling an LLM, formatting a prompt, or retrieving documents [Checked claim 3445]. ai notis. https://ainotis.com/c/3445

Anyone may quote this address. It does not change; if we correct the story, this page says so.