Key Moments

Stanford CME295 Transformers & LLMs | Autumn 2026 | Lecture 6 - AI Agents

Stanford OnlineStanford Online
Education6 min read101 min video
Nov 13, 2026|15,951 views|225|2
Save to Pod
TL;DR

AI agents can now perform complex tasks, but their reliance on specific prompts and the potential for over-reliance on tools like "grep" in programming raise concerns about robustness and security.

Key Insights

1

Retrieval-Augmented Generation (RAG) enhances LLMs by retrieving relevant information, addressing the knowledge cutoff and limited context window of base models.

2

Bi-encoders and cross-encoders are used in RAG for candidate retrieval and re-ranking, respectively, with BM25 offering a keyword-matching alternative.

3

Tool calling allows LLMs to execute actions beyond text generation by interfacing with external functions, categorized into three main types: information retrieval, computation, and code execution.

4

The ReAct framework combines reasoning and action, enabling agents to observe, plan, act, and observe again in a loop to achieve goals.

5

Agent frameworks like 'harness' provide the infrastructure around an LLM, including tools, orchestration, compression strategies, and memory management.

6

Multi-agent systems, including agent swarms, allow multiple AI agents to collaborate and communicate, presenting both opportunities for complex problem-solving and security risks.

Bridging LLM limitations with retrieval-augmented generation

Large Language Models (LLMs) have limitations, primarily their knowledge being restricted to their training data, leading to a 'knowledge cutoff' date. For instance, GPT-6 Astra's cutoff is April 30, 2026, making it unaware of events after that date. Furthermore, LLMs cannot perform actions; they can only respond to prompts. Retrieval-Augmented Generation (RAG) addresses these issues by enhancing prompts with relevant external information. The RAG process involves retrieving relevant documents, augmenting the prompt with this retrieved content, and then generating a response. This approach circumvents the limitations of a fixed context window (even a large one like GPT-6 Astra's million tokens) and the performance degradation seen with longer inputs (the 'needle in a haystack' problem). RAG is crucial for enabling LLMs to access and utilize up-to-date or specific information not present in their training data.

The mechanics of retrieval in RAG systems

Effective retrieval is the cornerstone of RAG. Documents are first processed into smaller 'chunks' and then represented as embedding vectors. The retrieval process typically involves two stages: candidate retrieval and re-ranking. Candidate retrieval aims to maximize recall by quickly scanning the knowledge base for potentially relevant documents, often using computationally inexpensive methods like bi-encoders (which encode query and document separately) or BM25 (for keyword matching). Bi-encoders calculate similarity scores between query and document embeddings, often leveraging approximate nearest neighbor algorithms for efficiency. The transcript highlights that semantic similarity from bi-encoders might not always be sufficient, leading to the consideration of keyword-based methods like BM25. Hybrid approaches combining both semantic and keyword search often yield better results. Candidate retrieval might return hundreds of potential documents.

Refining relevance through re-ranking and evaluation

Following candidate retrieval, a more sophisticated 're-ranking' stage refines the results to capture finer nuances. This stage is more computationally intensive but operates on a smaller set of documents (e.g., 100 candidates). Cross-encoders are often used here, processing the query and document together in a single model to better understand their relationship. Metrics like Normalized Discounted Cumulative Gain (NDCG), Mean Reciprocal Rank (MRR), precision, and recall are used to evaluate the effectiveness of the retrieval process, assessing how well the top-ranked documents align with actual relevance.

Enabling LLMs to take action with tool calling

Tool calling extends LLMs beyond text generation by allowing them to interact with external functionalities. Tools can be broadly categorized into information retrieval (e.g., searching databases, web browsing), computation (e.g., calculators for precise math), and code execution (e.g., generating plots, running scripts). When a user prompts an LLM with a request that requires an action, the LLM predicts which tool to use and what arguments to pass. This involves a three-stage process: 1) The LLM predicts the required action using available tools. 2) The predicted action is executed by the backend system. 3) The results from the backend are fed back to the LLM to formulate a final, natural language response. For instance, to find a teddy bear nearby, an LLM might first call a tool to get the user's location, then call another tool to query a backend system for nearby teddy bears, and finally, present the findings.

Standardizing tool integration with protocols like MCP

To manage the complexity of integrating numerous tools with various LLMs, standardization protocols like the Model Communication Protocol (MCP) are essential. MCP defines a 'server' that hosts tool implementations and a 'client' that interacts with these servers. It provides unified templates for defining tools, their arguments, and outputs. It also defines 'prompts' for specific workflows and 'resources' that applications can provide to tools. This standardization simplifies tool development and integration, allowing a tool to be used across different LLM providers that support the protocol. Prompt caching is a crucial cost-saving mechanism, especially when tool definitions are included in the prompt, reducing costs significantly.

Orchestrating LLM behavior with the ReAct framework

The ReAct (Reasoning and Acting) framework provides a structured approach for LLMs to interact with tools and achieve goals. It involves a loop of observing the current state, planning actions, executing those actions ('act'), and then observing the outcome again. This iterative process allows the LLM to dynamically adjust its strategy based on the feedback from tool execution. For example, if a teddy bear is cold, the LLM might observe this, plan to check the temperature, act by calling a temperature-sensing tool, observe the current temperature, and then plan to adjust the thermostat if necessary. This framework is often learned through supervised fine-tuning.

Managing context and memory for long-term agent interaction

LLMs have a finite context window, which poses a challenge for maintaining long conversations or complex workflows. 'Compression strategies' are employed to reduce the amount of information in the context window, such as summarizing previous turns or removing information no longer relevant in a sliding window approach. Beyond short-term memory (the context window), 'long-term memory' allows agents to recall information over extended periods. This can be achieved through RAG on past conversations or by using dedicated memory tools to store and retrieve specific facts or user preferences. Proper memory management is crucial for agents to retain context and user intent over time.

The rise of programming agents and multi-agent systems

Programming agents, a prominent application of AI agents, leverage tools like 'grep' for efficient code retrieval due to its precision over semantic similarity. They operate within execution environments and often employ automated approval mechanisms for actions. Concepts like 'agents.md' provide configuration rules, while 'skills' encapsulate repeatable workflows. The broader ecosystem includes frameworks like 'Pi' for streamlined agent development. Furthermore, multi-agent systems, including agent swarms, enable collaboration among multiple agents. While powerful for complex tasks, they introduce challenges like conflicting tool scopes ('benign' vs. 'malicious' conflicts) and potential security vulnerabilities, as demonstrated by the Hugging Face incident. Tool selection mechanisms help mitigate conflicts by choosing the most relevant subset of tools for a given query. The complexity of these systems is growing, with ongoing research into areas like computer control and more sophisticated multi-agent coordination.

OpenAI Prompt Caching Cost Savings

Data extracted from this episode

TypeCost per Million TokensRelative Saving Factor
Regular Input10 USD1x
Cached Input1 USD10x

Common Questions

Traditional LLMs are limited by their training data knowledge cutoff, meaning they cannot access real-time information. Additionally, they can only answer questions and cannot perform actions or execute procedures.

Topics

Mentioned in this video

More from Stanford Online

View all 177 summaries

Ask anything from this episode.

Save it, chat with it, and connect it to Claude or ChatGPT. Get cited answers from the actual content — and build your own knowledge base of every podcast and video you care about.

Get Started Free