eugene feedback

Author: sydney-runkle

src/oss/langgraph/graph-api.mdx

@@ -1052,7 +1052,7 @@ graph.addConditionalEdges("nodeA", (state) => {
 
 - **[Return from nodes](#return-from-nodes)**: Use `update`, `goto`, and `graph` to combine state updates with control flow.
 - **[Input to `invoke`/`stream`](#input-to-invokestream)**: Use `resume` to continue execution after an interrupt.
-- **[Return from tools](#return-from-tools)**: Use `update` to modify graph state from inside a tool.
+- **[Return from tools](#return-from-tools)**: Similar to return from nodes, combine state updates and control flow from inside a tool.
 
 ### Return from nodes
 
@@ -1086,8 +1086,6 @@ Use @[`Command`] when you need to **both** update state **and** route to a diffe
 
 When returning @[`Command`] in your node functions, you must add return type annotations with the list of node names the node is routing to, e.g. `Command[Literal["my_other_node"]]`. This is necessary for the graph rendering and tells LangGraph that `my_node` can navigate to `my_other_node`.
 
-@[`Command`] only adds dynamic edges — static edges defined with `add_edge` still execute. For example, if `node_a` returns `Command(goto="my_other_node")` and you also have `graph.add_edge("node_a", "node_b")`, both `node_b` and `my_other_node` will run.
-
 </Note>
 
 :::
@@ -1130,13 +1128,13 @@ builder.addNode("myNode", myNode, {
 });
 ```
 
-<Note>
+:::
 
-@[`Command`] only adds dynamic edges — static edges defined with `addEdge` still execute. For example, if `nodeA` returns `new Command({ goto: "myOtherNode" })` and you also have `graph.addEdge("nodeA", "nodeB")`, both `nodeB` and `myOtherNode` will run.
+<Warning>
 
-</Note>
+@[`Command`] only adds dynamic edges — static edges defined with `add_edge` / `addEdge` still execute. For example, if `node_a` returns `Command(goto="my_other_node")` and you also have `graph.add_edge("node_a", "node_b")`, both `node_b` and `my_other_node` will run.
 
-:::
+</Warning>
 
 Check out this [how-to guide](/oss/langgraph/use-graph-api#combine-control-flow-and-state-updates-with-command) for an end-to-end example of how to use @[`Command`].
 
@@ -1197,10 +1195,11 @@ This is particularly useful when implementing [multi-agent handoffs](/oss/langch
 
 <Warning>
 
-`Command(resume=...)` is the **only** `Command` pattern intended as input to `invoke()`/`stream()`. Do not use `Command(update=...)` as input to continue multi-turn conversations — because passing any `Command` as input resumes from the last checkpoint position (skipping `__start__`), the graph will appear stuck. To continue a conversation on an existing thread, pass a plain input dict:
+`Command(resume=...)` is the **only** `Command` pattern intended as input to `invoke()`/`stream()`. Do not use `Command(update=...)` as input to continue multi-turn conversations — because passing any `Command` as input resumes from the latest checkpoint (i.e. the last step that ran, not `__start__`), the graph will appear stuck if it already finished. To continue a conversation on an existing thread, pass a plain input dict:
 
 ```python
-# WRONG — graph resumes from end state, appears stuck
+# WRONG — graph resumes from the latest checkpoint
+# (last step that ran), appears stuck
 graph.invoke(Command(update={  # [!code --]
     "messages": [{"role": "user", "content": "follow up"}]  # [!code --]
 }), config)  # [!code --]
@@ -1219,10 +1218,11 @@ graph.invoke( {  # [!code ++]
 
 <Warning>
 
-`new Command({ resume: ... })` is the **only** `Command` pattern intended as input to `invoke()`/`stream()`. Do not use `new Command({ update: ... })` as input to continue multi-turn conversations — because passing any `Command` as input resumes from the last checkpoint position (skipping `__start__`), the graph will appear stuck. To continue a conversation on an existing thread, pass a plain input object:
+`new Command({ resume: ... })` is the **only** `Command` pattern intended as input to `invoke()`/`stream()`. Do not use `new Command({ update: ... })` as input to continue multi-turn conversations — because passing any `Command` as input resumes from the latest checkpoint (i.e. the last step that ran, not `__start__`), the graph will appear stuck if it already finished. To continue a conversation on an existing thread, pass a plain input object:
 
 ```typescript
-// WRONG — graph resumes from end state, appears stuck
+// WRONG — graph resumes from the latest checkpoint
+// (last step that ran), appears stuck
 await graph.invoke(new Command({ update: { messages: [{ role: "user", content: "follow up" }] } }), config);  // [!code --]
 
 // CORRECT — plain object restarts from __start__
@@ -1284,7 +1284,13 @@ Check out the [interrupts conceptual guide](/oss/langgraph/interrupts) for full
 
 ### Return from tools
 
-A common use case is updating graph state from inside a tool. For example, in a customer support application you might want to look up customer information based on their account number or ID in the beginning of the conversation.
+You can return @[`Command`] from tools to update graph state and control flow. Use `update` to modify state (e.g., saving customer information looked up during a conversation) and `goto` to route to a specific node after the tool completes.
+
+<Warning>
+
+When used inside tools, `goto` adds a dynamic edge — any static edges already defined on the node that called the tool will still execute.
+
+</Warning>
 
 Refer to [this guide](/oss/langgraph/use-graph-api#use-inside-tools) for detail.