89c3428d85
Goal here is 2 fold
1. Improved devx for injecting args into tools
2. Support runtime injection for Python 3.10 async
One consequence of this PR is that `ToolNode` now expects `config`
available with `runtime`, which only happens in LangGraph execution
contexts. Hence the config patch for tests.
Are we ok reserving `tool_runtime`?
before, eek:
```py
from langchain.agents import create_agent
from langchain.tools import tool, InjectedState, InjectedStore
from langgraph.runtime import get_runtime
from typing_extensions import Annotated
from langgraph.store.base import BaseStore
@tool
def do_something(
arg: int,
state: Annotated[dict, InjectedState],
store: Annotated[BaseStore, InjectedStore],
) -> None:
"""does something."""
print(state)
print(store)
print(get_runtime().context)
...
```
after, woo!
```py
from langchain.agents import create_agent
from langchain.tools import tool, ToolRuntime
@tool
def do_something_better(
arg: int,
tool_runtime: ToolRuntime,
) -> None:
"""does something better."""
print(tool_runtime.state)
print(tool_runtime.store)
print(tool_runtime.context)
...
```
```python
@dataclass
class ToolRuntime(InjectedToolArg, Generic[StateT, ContextT]):
state: StateT
context: ContextT
config: RunnableConfig
tool_call_id: str
stream_writer: StreamWriter
context: ContextT
store: BaseStore | None
Packages
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.