Context¶

Context engineering is the practice of building dynamic systems that provide the right information and tools, in the right format, so that a language model can plausibly accomplish a task.

Context includes any data outside the message list that can shape behavior. This can be:

Information passed at runtime, like a user_id or API credentials.
Internal state updated during a multi-step reasoning process.
Persistent memory or facts from previous interactions.

LangGraph provides three primary ways to supply context:

Type	Description	Mutable?	Lifetime
Runtime Context	data passed at the start of a run	❌	per run
Short-term memory (State)	dynamic data that can change during execution	✅	per run or conversation
Long-term memory (Store)	data that can be shared between conversations	✅	across conversations

Runtime Context¶

config['configurable'] -> runtime.context

In LangGraph < v1.0, static runtime context was passed via the config['configurable'] key, paired with a config_schema argument to StateGraph or Pregel. This is now deprecated and will be removed in v2.0.

As of LangGraph v1.0, the Runtime object is recommended to access static context and runtime-specific information like the store and stream writer.

Runtime context is for immutable data like user metadata or API keys. Use this when you have values that don't change mid-run.

Specify static context via the context argument to invoke / stream, which is reserved for this purpose:

@dataclass
class ContextSchema:
    user_name: str

graph.invoke( # (1)!
    {"messages": [{"role": "user", "content": "hi!"}]}, # (2)!
    context={"user_name": "John Smith"} # (3)!
)

This is the invocation of the agent or graph. The invoke method runs the underlying graph with the provided input.
This example uses messages as an input, which is common, but your application may use different input structures.
This is where you pass the runtime data. The context parameter allows you to provide additional dependencies that the agent can use during its execution.

Agent promptWorkflow nodeIn a tool

from langchain_core.messages import AnyMessage
from langgraph.runtime import get_runtime
from langgraph.prebuilt.chat_agent_executor import AgentState
from langgraph.prebuilt import create_react_agent

def prompt(state: AgentState) -> list[AnyMessage]:
    runtime = get_runtime(ContextSchema)
    system_msg = f"You are a helpful assistant. Address the user as {runtime.context.user_name}."
    return [{"role": "system", "content": system_msg}] + state["messages"]

agent = create_react_agent(
    model="anthropic:claude-3-7-sonnet-latest",
    tools=[get_weather],
    prompt=prompt,
    context_schema=ContextSchema
)

agent.invoke(
    {"messages": [{"role": "user", "content": "what is the weather in sf"}]},
    context={"user_name": "John Smith"}
)

See Agents for details.

from langgraph.runtime import Runtime

def node(state: State, config: Runtime[ContextSchema]):
    user_name = runtime.context.user_name
    ...

See the Graph API for details.

from langgraph.runtime import get_runtime

@tool
def get_user_email() -> str:
    """Retrieve user information based on user ID."""
    # simulate fetching user info from a database
    runtime = get_runtime(ContextSchema)
    email = get_user_email_from_db(runtime.context.user_name)
    return email

See the tool calling guide for details.

Short-term memory (mutable context)¶

State acts as short-term memory during a run. It holds dynamic data that can evolve during execution, such as values derived from tools or LLM outputs.

In an agentIn a workflow

Example shows how to incorporate state into an agent prompt.

State can also be accessed by the agent's tools, which can read or update the state as needed. See tool calling guide for details.

from langchain_core.messages import AnyMessage
from langchain_core.runnables import RunnableConfig
from langgraph.prebuilt import create_react_agent
from langgraph.prebuilt.chat_agent_executor import AgentState

class CustomState(AgentState): # (1)!
    user_name: str

def prompt(
    state: CustomState
) -> list[AnyMessage]:
    user_name = state["user_name"]
    system_msg = f"You are a helpful assistant. User's name is {user_name}"
    return [{"role": "system", "content": system_msg}] + state["messages"]

agent = create_react_agent(
    model="anthropic:claude-3-7-sonnet-latest",
    tools=[...],
    state_schema=CustomState, # (2)!
    prompt=prompt
)

agent.invoke({
    "messages": "hi!",
    "user_name": "John Smith"
})

Define a custom state schema that extends AgentState or MessagesState.
Pass the custom state schema to the agent. This allows the agent to access and modify the state during execution.

from typing_extensions import TypedDict
from langchain_core.messages import AnyMessage
from langgraph.graph import StateGraph

class CustomState(TypedDict): # (1)!
    messages: list[AnyMessage]
    extra_field: int

def node(state: CustomState): # (2)!
    messages = state["messages"]
    ...
    return { # (3)!
        "extra_field": state["extra_field"] + 1
    }

builder = StateGraph(State)
builder.add_node(node)
builder.set_entry_point("node")
graph = builder.compile()

Define a custom state
Access the state in any node or tool
The Graph API is designed to work as easily as possible with state. The return value of a node represents a requested update to the state.

Turning on memory

Please see the memory guide for more details on how to enable memory. This is a powerful feature that allows you to persist the agent's state across multiple invocations. Otherwise, the state is scoped only to a single run.

Long-term memory (cross-conversation context)¶

For context that spans across conversations or sessions, LangGraph allows access to long-term memory via a store. This can be used to read or update persistent facts (e.g., user profiles, preferences, prior interactions).

For more information, see the Memory guide.