We don't publish
your competitive advantage.

IFWhen using LangGraph's built-in ToolNode with tools that require ToolRuntime for runtime context injection, an error occurs because the runtime is not passed.

THENAs a temporary workaround, either use LangChain's internal ToolNode (with leading underscore) or implement a custom tool node that manually passes the 'runtime' parameter to tool.invoke(). The LangGraph maintainers have acknowledged the issue and plan to add support in an upcoming release, so after updating, the official ToolNode will handle ToolRuntime natively.

IFWhen using LangGraph's built-in ToolNode with tools that require `ToolRuntime`, the runtime context is not passed, causing an error.

THENUse LangChain's internal `_ToolNode` as a temporary workaround, or switch to LangChain's `create_agent` which natively supports `ToolRuntime`. Alternatively, implement a custom ToolNode that injects the runtime. The LangGraph team plans to add official support soon.

IFWhen using LangGraph's built-in ToolNode with tools that declare a `ToolRuntime` parameter, an error occurs because the runtime context is not automatically injected.

THENImplement a custom ToolNode that manually passes the runtime context (e.g., `ToolRuntime` or `Runtime`) to each tool's `invoke` method. Inside the custom node, iterate over the tool calls from the state, look up the tool by name, and call `tool.invoke(tool_call['args'], runtime=runtime)`. This bypasses the missing support in the official ToolNode until the LangGraph team ports it over.