From 14949c81c822acbb1eff63c33f45d2a45ebfaed9 Mon Sep 17 00:00:00 2001 From: Sydney Runkle <54324534+sydney-runkle@users.noreply.github.com> Date: Mon, 28 Jul 2025 16:22:16 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Lauren Hirata Singh --- docs/docs/agents/context.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/agents/context.md b/docs/docs/agents/context.md index 5b39b4090..9c8403a6a 100644 --- a/docs/docs/agents/context.md +++ b/docs/docs/agents/context.md @@ -24,14 +24,14 @@ Runtime context is for immutable data like user metadata, tools, db connections, The `Runtime` object is recommended to access static context and runtime-specific information like the store and stream writer. -!!! note "'Context' is an overloaded term" +!!! note Runtime context refers to local context: data and dependencies your code needs to run. It does not refer to: * The LLM context, which is the data passed into the LLM's prompt. * The "context window", which is the maximum number of tokens that can be passed to the LLM. - You likely want to use the local context to optimize the llm's context window. For example, you + You likely want to use the local context to optimize the LLM's context window. For example, you could use a user_id to fetch a user's name and information from a database to populate the context window with relevant memories. Specify static context via the `context` argument to `invoke` / `stream`, which is reserved for this purpose: