From 624247a51f07b596e7a085caf449f6718c9b9c8e Mon Sep 17 00:00:00 2001 From: Sydney Runkle <54324534+sydney-runkle@users.noreply.github.com> Date: Mon, 28 Jul 2025 15:31:36 -0400 Subject: [PATCH] Update docs/docs/agents/context.md Co-authored-by: Eugene Yurtsev --- docs/docs/agents/context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/agents/context.md b/docs/docs/agents/context.md index b246b6dce..c571fffda 100644 --- a/docs/docs/agents/context.md +++ b/docs/docs/agents/context.md @@ -37,7 +37,7 @@ LangGraph provides **three** primary ways to manage context: The field of "context engineering" refers to the practice of optimizing the content of the context window to improve the LLM's performance. The context discussed in this section is the local context. As a developer, you might use the local context to eventually optimize - the LLM context (ex: use a user_id to fetch a user's name and information from a database to populate the context window with relevant memories). + the LLM context. For example, use a user_id to fetch a user's name and information from a database to populate the context window with relevant memories. Runtime context is for immutable data like user metadata, tools, db connections, etc. Use this when you have values that don't change mid-run.