Set build target to js add translations for 4th and 5th parts of the tutorial

2026-09-07 02:07:52 +02:00 · 2025-07-28 14:44:50 -07:00
parent 54e64640de
commit 9f12c142e5
3 changed files with 656 additions and 10 deletions
@@ -2,7 +2,15 @@

 Agents can be unreliable and may need human input to successfully accomplish tasks. Similarly, for some actions, you may want to require human approval before running to ensure that everything is running as intended.

-LangGraph's [persistence](../../concepts/persistence.md) layer supports **human-in-the-loop** workflows, allowing execution to pause and resume based on user feedback. The primary interface to this functionality is the [`interrupt`](../../how-tos/human_in_the_loop/add-human-in-the-loop.md) function. Calling `interrupt` inside a node will pause execution. Execution can be resumed, together with new input from a human, by passing in a [Command](../../concepts/low_level.md#command). `interrupt` is ergonomically similar to Python's built-in `input()`, [with some caveats](../../how-tos/human_in_the_loop/add-human-in-the-loop.md).
+LangGraph's [persistence](../../concepts/persistence.md) layer supports **human-in-the-loop** workflows, allowing execution to pause and resume based on user feedback. The primary interface to this functionality is the [`interrupt`](../../how-tos/human_in_the_loop/add-human-in-the-loop.md) function. Calling `interrupt` inside a node will pause execution. Execution can be resumed, together with new input from a human, by passing in a [Command](../../concepts/low_level.md#command).
+
+:::python
+`interrupt` is ergonomically similar to Python's built-in `input()`, [with some caveats](../../how-tos/human_in_the_loop/add-human-in-the-loop.md).
+:::
+
+:::js
+`interrupt` is ergonomically similar to Node.js's built-in `prompt()` function, [with some caveats](../../how-tos/human_in_the_loop/add-human-in-the-loop.md).
+:::

 !!! note

@@ -14,6 +22,7 @@ Starting with the existing code from the [Add memory to the chatbot](./3-add-mem

 Let's first select a chat model:

+:::python
 {% include-markdown "../../../snippets/chat_model_tabs.md" %}

 <!---
@@ -24,9 +33,22 @@ llm = init_chat_model("anthropic:claude-3-5-sonnet-latest")
 ```
 -->

+:::
+
+:::js
+
+```typescript
+// Add your API key here
+process.env.ANTHROPIC_API_KEY = "YOUR_API_KEY";
+```
+
+:::
+
 We can now incorporate it into our `StateGraph` with an additional tool:

-``` python hl_lines="12 19 20 21 22 23"
+:::python
+
+```python hl_lines="12 19 20 21 22 23"
 from typing import Annotated

 from langchain_tavily import TavilySearch
@@ -76,6 +98,82 @@ graph_builder.add_edge("tools", "chatbot")
 graph_builder.add_edge(START, "chatbot")
 ```

+:::
+
+:::js
+
+```typescript hl_lines="12 19 20 21 22 23"
+import { TavilySearchResults } from "@langchain/community/tools/tavily_search";
+import { tool } from "@langchain/core/tools";
+import { z } from "zod";
+
+import { MemorySaver } from "@langchain/langgraph";
+import {
+  StateGraph,
+  START,
+  END,
+  MessagesAnnotation,
+} from "@langchain/langgraph";
+import { ToolNode } from "@langchain/langgraph/prebuilt";
+import { ChatAnthropic } from "@langchain/anthropic";
+
+import { Command, interrupt } from "@langchain/langgraph";
+
+const humanAssistance = tool(
+  async ({ query }) => {
+    const humanResponse = interrupt({ query });
+    return humanResponse.data;
+  },
+  {
+    name: "humanAssistance",
+    description: "Request assistance from a human.",
+    schema: z.object({
+      query: z.string().describe("Human readable question for the human"),
+    }),
+  }
+);
+
+const searchTool = new TavilySearchResults({ maxResults: 2 });
+const tools = [searchTool, humanAssistance];
+
+const model = new ChatAnthropic({ model: "claude-3-5-sonnet-latest" });
+const llmWithTools = model.bindTools(tools);
+
+const chatbot = async (state: typeof MessagesAnnotation.State) => {
+  const message = await llmWithTools.invoke(state.messages);
+  // Because we will be interrupting during tool execution,
+  // we disable parallel tool calling to avoid repeating any
+  // tool invocations when we resume.
+  if (message.tool_calls && message.tool_calls.length > 1) {
+    throw new Error("Multiple tool calls not supported with interrupts");
+  }
+  return { messages: [message] };
+};
+
+const graphBuilder = new StateGraph(MessagesAnnotation).addNode(
+  "chatbot",
+  chatbot
+);
+
+const toolNode = new ToolNode(tools);
+graphBuilder.addNode("tools", toolNode);
+
+const shouldContinue = (state: typeof MessagesAnnotation.State) => {
+  const messages = state.messages;
+  const lastMessage = messages[messages.length - 1];
+  if ("tool_calls" in lastMessage && lastMessage.tool_calls?.length) {
+    return "tools";
+  }
+  return END;
+};
+
+graphBuilder.addConditionalEdges("chatbot", shouldContinue);
+graphBuilder.addEdge("tools", "chatbot");
+graphBuilder.addEdge(START, "chatbot");
+```
+
+:::
+
 !!! tip

    For more information and examples of human-in-the-loop workflows, see [Human-in-the-loop](../../concepts/human_in_the_loop.md).
@@ -84,17 +182,33 @@ graph_builder.add_edge(START, "chatbot")

 We compile the graph with a checkpointer, as before:

+:::python
+
 ```python
 memory = InMemorySaver()

 graph = graph_builder.compile(checkpointer=memory)
 ```

+:::
+
+:::js
+
+```typescript
+const memory = new MemorySaver();
+
+const graph = graphBuilder.compile({ checkpointer: memory });
+```
+
+:::
+
 ## 3. Visualize the graph (optional)

 Visualizing the graph, you get the same layout as before – just with the added tool!

-``` python
+:::python
+
+```python
 from IPython.display import Image, display

 try:
@@ -104,12 +218,30 @@ except Exception:
    pass
 ```

+:::
+
+:::js
+
+```typescript
+import * as tslab from "tslab";
+
+const drawableGraph = graph.getGraph();
+const image = await drawableGraph.drawMermaidPng();
+const arrayBuffer = await image.arrayBuffer();
+
+await tslab.display.png(new Uint8Array(arrayBuffer));
+```
+
+:::
+
 ![chatbot-with-tools-diagram](chatbot-with-tools.png)

 ## 4. Prompt the chatbot

 Now, prompt the chatbot with a question that will engage the new `human_assistance` tool:

+:::python
+
 ```python
 user_input = "I need some expert guidance for building an AI agent. Could you request assistance for me?"
 config = {"configurable": {"thread_id": "1"}}
@@ -138,8 +270,54 @@ Tool Calls:
    query: A user is requesting expert guidance for building an AI agent. Could you please provide some expert advice or resources on this topic?
 ```

+:::
+
+:::js
+
+```typescript
+const userInput =
+  "I need some expert guidance for building an AI agent. Could you request assistance for me?";
+const config = {
+  configurable: { thread_id: "1" },
+  streamMode: "values" as const,
+};
+
+const events = await graph.stream(
+  { messages: [{ role: "user", content: userInput }] },
+  config
+);
+
+for await (const event of events) {
+  if ("messages" in event) {
+    const lastMessage = event.messages[event.messages.length - 1];
+    console.log(`[${lastMessage._getType()}]: ${lastMessage.content}`);
+    if ("tool_calls" in lastMessage && lastMessage.tool_calls?.length) {
+      console.log("Tool calls:", lastMessage.tool_calls);
+    }
+  }
+}
+```
+
+```
+[human]: I need some expert guidance for building an AI agent. Could you request assistance for me?
+[ai]: Certainly! I'd be happy to request expert assistance for you regarding building an AI agent. To do this, I'll use the human_assistance function to relay your request. Let me do that for you now.
+Tool calls: [
+  {
+    name: 'humanAssistance',
+    args: {
+      query: 'A user is requesting expert guidance for building an AI agent. Could you please provide some expert advice or resources on this topic?'
+    },
+    id: 'toolu_01ABUqneqnuHNuo1vhfDFQCW'
+  }
+]
+```
+
+:::
+
 The chatbot generated a tool call, but then execution has been interrupted. If you inspect the graph state, you see that it stopped at the tools node:

+:::python
+
 ```python
 snapshot = graph.get_state(config)
 snapshot.next
@@ -149,10 +327,26 @@ snapshot.next
 ('tools',)
 ```

+:::
+
+:::js
+
+```typescript
+const snapshot = await graph.getState(config);
+console.log(snapshot.next);
+```
+
+```
+['tools']
+```
+
+:::
+
 !!! info Additional information

    Take a closer look at the `human_assistance` tool:

+    :::python
    ```python
    @tool
    def human_assistance(query: str) -> str:
@@ -162,12 +356,33 @@ snapshot.next
    ```

    Similar to Python's built-in `input()` function, calling `interrupt` inside the tool will pause execution. Progress is persisted based on the [checkpointer](../../concepts/persistence.md#checkpointer-libraries); so if it is persisting with Postgres, it can resume at any time as long as the database is alive. In this example, it is persisting with the in-memory checkpointer and can resume any time if the Python kernel is running.
+    :::
+
+    :::js
+    ```typescript
+    const humanAssistance = tool(async ({ query }) => {
+      const humanResponse = interrupt({ query });
+      return humanResponse.data;
+    }, {
+      name: "humanAssistance",
+      description: "Request assistance from a human.",
+      schema: z.object({
+        query: z.string().describe("Human readable question for the human")
+      })
+    });
+    ```
+
+    Similar to JavaScript's built-in `prompt()` function, calling `interrupt` inside the tool will pause execution. Progress is persisted based on the [checkpointer](../../concepts/persistence.md#checkpointer-libraries); so if it is persisting with Postgres, it can resume at any time as long as the database is alive. In this example, it is persisting with the in-memory checkpointer and can resume any time if the JavaScript runtime is running.
+    :::

 ## 5. Resume execution

-To resume execution, pass a [`Command`](../../concepts/low_level.md#command) object containing data expected by the tool. The format of this data can be customized based on needs. For this example, use a dict with a key `"data"`:
+To resume execution, pass a [`Command`](../../concepts/low_level.md#command) object containing data expected by the tool. The format of this data can be customized based on needs.

-``` python
+:::python
+For this example, use a dict with a key `"data"`:
+
+```python
 human_response = (
    "We, the experts are here to help! We'd recommend you check out LangGraph to build your agent."
    " It's much more reliable and extensible than simple autonomous agents."
@@ -215,12 +430,54 @@ If you'd like more specific information about LangGraph or have any questions ab
 Output is truncated. View as a scrollable element or open in a text editor. Adjust cell output settings...
 ```

+:::
+
+:::js
+For this example, use an object with a key `"data"`:
+
+```typescript
+const humanResponse =
+  "We, the experts are here to help! We'd recommend you check out LangGraph to build your agent." +
+  " It's much more reliable and extensible than simple autonomous agents.";
+
+const humanCommand = new Command({ resume: { data: humanResponse } });
+
+const resumeEvents = await graph.stream(humanCommand, config);
+
+for await (const event of resumeEvents) {
+  if ("messages" in event) {
+    const lastMessage = event.messages[event.messages.length - 1];
+    console.log(`[${lastMessage._getType()}]: ${lastMessage.content}`);
+  }
+}
+```
+
+```
+[tool]: We, the experts are here to help! We'd recommend you check out LangGraph to build your agent. It's much more reliable and extensible than simple autonomous agents.
+[ai]: Thank you for your patience. I've received some expert advice regarding your request for guidance on building an AI agent. Here's what the experts have suggested:
+
+The experts recommend that you look into LangGraph for building your AI agent. They mention that LangGraph is a more reliable and extensible option compared to simple autonomous agents.
+
+LangGraph is likely a framework or library designed specifically for creating AI agents with advanced capabilities. Here are a few points to consider based on this recommendation:
+
+1. Reliability: The experts emphasize that LangGraph is more reliable than simpler autonomous agent approaches. This could mean it has better stability, error handling, or consistent performance.
+
+2. Extensibility: LangGraph is described as more extensible, which suggests that it probably offers a flexible architecture that allows you to easily add new features or modify existing ones as your agent's requirements evolve.
+
+3. Advanced capabilities: Given that it's recommended over "simple autonomous agents," LangGraph likely provides more sophisticated tools and techniques for building complex AI agents.
+
+...
+```
+
+:::
+
 The input has been received and processed as a tool message. Review this call's [LangSmith trace](https://smith.langchain.com/public/9f0f87e3-56a7-4dde-9c76-b71675624e91/r) to see the exact work that was done in the above call. Notice that the state is loaded in the first step so that our chatbot can continue where it left off.

 **Congratulations!** You've used an `interrupt` to add human-in-the-loop execution to your chatbot, allowing for human oversight and intervention when needed. This opens up the potential UIs you can create with your AI systems. Since you have already added a **checkpointer**, as long as the underlying persistence layer is running, the graph can be paused **indefinitely** and resumed at any time as if nothing had happened.

 Check out the code snippet below to review the graph from this tutorial:

+:::python
 {% include-markdown "../../../snippets/chat_model_tabs.md" %}

 ```python
@@ -272,6 +529,81 @@ memory = InMemorySaver()
 graph = graph_builder.compile(checkpointer=memory)
 ```

+:::
+
+:::js
+
+```typescript
+import { TavilySearchResults } from "@langchain/community/tools/tavily_search";
+import { tool } from "@langchain/core/tools";
+import { z } from "zod";
+
+import { MemorySaver } from "@langchain/langgraph";
+import {
+  StateGraph,
+  START,
+  END,
+  MessagesAnnotation,
+} from "@langchain/langgraph";
+import { ToolNode } from "@langchain/langgraph/prebuilt";
+import { ChatAnthropic } from "@langchain/anthropic";
+import { Command, interrupt } from "@langchain/langgraph";
+
+const humanAssistance = tool(
+  async ({ query }) => {
+    const humanResponse = interrupt({ query });
+    return humanResponse.data;
+  },
+  {
+    name: "humanAssistance",
+    description: "Request assistance from a human.",
+    schema: z.object({
+      query: z.string().describe("Human readable question for the human"),
+    }),
+  }
+);
+
+const searchTool = new TavilySearchResults({ maxResults: 2 });
+const tools = [searchTool, humanAssistance];
+
+const model = new ChatAnthropic({ model: "claude-3-5-sonnet-latest" });
+const llmWithTools = model.bindTools(tools);
+
+const chatbot = async (state: typeof MessagesAnnotation.State) => {
+  const message = await llmWithTools.invoke(state.messages);
+  if (message.tool_calls && message.tool_calls.length > 1) {
+    throw new Error("Multiple tool calls not supported with interrupts");
+  }
+  return { messages: [message] };
+};
+
+const graphBuilder = new StateGraph(MessagesAnnotation).addNode(
+  "chatbot",
+  chatbot
+);
+
+const toolNode = new ToolNode(tools);
+graphBuilder.addNode("tools", toolNode);
+
+const shouldContinue = (state: typeof MessagesAnnotation.State) => {
+  const messages = state.messages;
+  const lastMessage = messages[messages.length - 1];
+  if ("tool_calls" in lastMessage && lastMessage.tool_calls?.length) {
+    return "tools";
+  }
+  return END;
+};
+
+graphBuilder.addConditionalEdges("chatbot", shouldContinue);
+graphBuilder.addEdge("tools", "chatbot");
+graphBuilder.addEdge(START, "chatbot");
+
+const memory = new MemorySaver();
+const graph = graphBuilder.compile({ checkpointer: memory });
+```
+
+:::
+
 ## Next steps

-So far, the tutorial examples have relied on a simple state with one entry: a list of messages. You can go far with this simple state, but if you want to define complex behavior without relying on the message list, you can [add additional fields to the state](./5-customize-state.md).
+So far, the tutorial examples have relied on a simple state with one entry: a list of messages. You can go far with this simple state, but if you want to define complex behavior without relying on the message list, you can [add additional fields to the state](./5-customize-state.md).