x

docs/docs/concepts/human_in_the_loop.md

@@ -215,42 +215,4 @@ for event in graph.stream(None, thread, stream_mode="values"):
     print(event)
 ```
 
-See [the how to review tool calls guide](../how-tos/human_in_the_loop/review-tool-calls.ipynb) for a details.
-
-
-## Advanced
-
-### How does an `interrupt` work?
-
-Execution always resumes from the **beginning** of the **graph node**, not the exact point of the `interrupt`.
-
-Please note that this is **unlike** a traditional breakpoint or Python's `input()` function. As a result, you should structure your graph nodes to handle the `interrupt` and `resume` logic effectively.
-
-Keep the following considerations in mind when using the `interrupt` function:
-
-1. **Side effects**: Place side-effecting code, such as API calls, **after** the `interrupt` to avoid duplication, as these are re-triggered every time the node resumes.
-2. **Multiple interrupts**: Using multiple `interrupt` calls in a node can be very useful (e.g., for run-time validation), but the order and number of calls must remain consistent to prevent mismatched resume values.
-
-
-### Options for resuming execution
-
-After an `interrupt`, graph execution can be resumed using the [Command](../reference/types.md#langgraph.types.Command) primitive. The `Command` primitive provides several options to control and modify the graph's state during resumption:
-
-1. **Pass a value to the `interrupt`**: Provide data, such as a user's response, to the graph using `Command(resume=value)`. Execution resumes from the beginning of the node where the `interrupt` was used, however, this time the `interrupt(...)` call will return the value passed in the `Command(resume=value)` instead of pausing the graph.
-2. **Update the graph state**: Modify the graph state using `Command(update=update)`. Note that resumption starts from the beginning of the node where the `interrupt` was used. Execution resumes from the beginning of the node where the `interrupt` was used, but with the updated state.
-3. **Navigate to another node**: Direct the graph to continue execution at a different node using `Command(goto="node_name")`.
-
-```python
-# Resume graph execution with the user's input.
-graph.invoke(Command(resume={"age": "25"}), thread_config)
-```
-
-By leveraging `Command`, you can resume graph execution, handle user inputs, and dynamically adjust the graph's state or flow.
-
-??? note "Using other types of breakpoints"
-
-    The `interrupt` function was introduced to address difficulties with the older methods that necessitated updating the graph state when resuming execution. You can read more about these methods in the [low-level guide](./low_level.md#breakpoints). A [previous version of this guide](v0-human-in-the-loop.md) covers the older method of setting breakpoints using **static breakpoints** and the `NodeInterrupt` exception. 
-
-    See [this guide](../how-tos/human_in_the_loop/breakpoints.ipynb) for a full walkthrough of how to add breakpoints.
-
-
+See [the how to review tool calls guide](../how-tos/human_in_the_loop/review-tool-calls.ipynb) for a details.