Skip to main content
Agents support both synchronous and asynchronous execution using either .invoke() / await .ainvoke() for full responses, or .stream() / .astream() for incremental streaming output. This section explains how to provide input, interpret output, enable streaming, and control execution limits.

​
Basic usage

Agents can be executed in two primary modes:
  • Synchronous using .invoke() or .stream()
  • Asynchronous using await .invoke() or for await with .stream()
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const agent = createReactAgent(...);
// highlight-next-line
const response = await agent.invoke({
    "messages": [
        { "role": "user", "content": "what is the weather in sf" }
    ]
});

​
Inputs and outputs

Agents use a language model that expects a list of messages as an input. Therefore, agent inputs and outputs are stored as a list of messages under the messages key in the agent state.

​
Input format

Agent input must be a dictionary with a messages key. Supported formats are:
FormatExample
String{"messages": "Hello"} — Interpreted as a HumanMessage
Message dictionary{"messages": {"role": "user", "content": "Hello"}}
List of messages{"messages": [{"role": "user", "content": "Hello"}]}
With custom state{"messages": [{"role": "user", "content": "Hello"}], "user_name": "Alice"} — If using a custom state definition
Messages are automatically converted into LangChain’s internal message format. You can read more about LangChain messages in the LangChain documentation.
Using custom agent stateYou can provide additional fields defined in your agent’s state directly in the state definition. This allows dynamic behavior based on runtime data or prior tool outputs. See the context guide for full details.
A string input for messages is converted to a HumanMessage. This behavior differs from the prompt parameter in createReactAgent, which is interpreted as a SystemMessage when passed as a string.

​
Output format

Agent output is a dictionary containing:
  • messages: A list of all messages exchanged during execution (user input, assistant replies, tool invocations).
  • Optionally, structuredResponse if structured output is configured.
  • If using a custom state definition, additional keys corresponding to your defined fields may also be present in the output. These can hold updated state values from tool execution or prompt logic.
See the context guide for more details on working with custom state schemas and accessing context.

​
Streaming output

Agents support streaming responses for more responsive applications. This includes:
  • Progress updates after each step
  • LLM tokens as they’re generated
  • Custom tool messages during execution
Streaming is available in both sync and async modes: 
for await (const chunk of agent.stream(
  { messages: [{ role: "user", content: "what is the weather in sf" }] },
  { streamMode: "updates" }
)) {
  console.log(chunk);
}
For full details, see the streaming guide.

​
Max iterations

To control agent execution and avoid infinite loops, set a recursion limit. This defines the maximum number of steps the agent can take before raising a GraphRecursionError. You can configure recursionLimit at runtime or when defining agent via .withConfig():
  • Runtime
  • .withConfig()
import { GraphRecursionError } from "@langchain/langgraph";
import { ChatAnthropic } from "@langchain/langgraph/prebuilt";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const maxIterations = 3;
// highlight-next-line
const recursionLimit = 2 * maxIterations + 1;
const agent = createReactAgent({
    llm: new ChatAnthropic({ model: "claude-3-5-haiku-latest" }),
    tools: [getWeather]
});

try {
    const response = await agent.invoke(
        {"messages": [{"role": "user", "content": "what's the weather in sf"}]},
        // highlight-next-line
        { recursionLimit }
    );
} catch (error) {
    if (error instanceof GraphRecursionError) {
        console.log("Agent stopped due to max iterations.");
    }
}
⌘I