Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2025-06-26 | 10.4 kB | |
v2.15.0 source code.tar.gz | 2025-06-26 | 7.3 MB | |
v2.15.0 source code.zip | 2025-06-26 | 8.0 MB | |
Totals: 3 Items | 15.3 MB | 0 |
⭐️ Highlights
Parallel Tool Calling for Faster Agents
ToolInvoker
now processes all tool calls passed torun
orrun_async
in parallel using an internalThreadPoolExecutor
. This improves performance by reducing the time spent on sequential tool invocations.- This parallel execution capability enables
ToolInvoker
to batch and process multiple tool calls concurrently, allowing Agents to run complex pipelines efficiently with decreased latency. - You no longer need to pass an
async_executor
.ToolInvoker
manages its own executor, configurable via themax_workers
parameter ininit
.
Introducing LLMMessagesRouter
A new component that classifies and routes incoming ChatMessage
objects to different connections using a generative LLM. This component can be used with general-purpose LLMs and with specialized LLMs for moderation like Llama Guard.
Usage example:
:::python
from haystack.components.generators.chat import HuggingFaceAPIChatGenerator
from haystack.components.routers.llm_messages_router import LLMMessagesRouter
from haystack.dataclasses import ChatMessage
# initialize a Chat Generator with a generative model for moderation
chat_generator = HuggingFaceAPIChatGenerator(api_type="serverless_inference_api", api_params={"model": "meta-llama/Llama-Guard-4-12B", "provider": "groq"}, )
router = LLMMessagesRouter(chat_generator=chat_generator, output_names=["unsafe", "safe"], output_patterns=["unsafe", "safe"])
print(router.run([ChatMessage.from_user("How to rob a bank?")]))
New HuggingFaceTEIRanker Component
Enables end-to-end reranking via the Text Embeddings Inference (TEI) API. Supports both self-hosted TEI services and Hugging Face Inference Endpoints, giving you flexible, high-quality reranking out of the box.
🚀 New Features
- Added a
ComponentInfo
dataclass to haystack to store information about the component. We pass it toStreamingChunk
so we can tell from which component a stream is coming. -
Pass the
component_info
to theStreamingChunk
in theOpenAIChatGenerator
,AzureOpenAIChatGenerator
,HuggingFaceAPIChatGenerator
,HuggingFaceGenerator
,HugginFaceLocalGenerator
andHuggingFaceLocalChatGenerator
. -
Added the
enable_streaming_callback_passthrough
to theinit
,run
andrun_async
methods ofToolInvoker
. If set toTrue
theToolInvoker
will try and pass thestreaming_callback
function to a tool's invoke method only if the tool's invoke method hasstreaming_callback
in its signature. -
Added dedicated
finish_reason
field toStreamingChunk
class to improve type safety and enable sophisticated streaming UI logic. The field uses aFinishReason
type alias with standard values: "stop", "length", "tool_calls", "content_filter", plus Haystack-specific value "tool_call_results" (used by ToolInvoker to indicate tool execution completion). -
Updated
ToolInvoker
component to use the newfinish_reason
field when streaming tool results. The component now setsfinish_reason="tool_call_results"
in the final streaming chunk to indicate that tool execution has completed, while maintaining backward compatibility by also setting the value inmeta["finish_reason"]
. -
Added a
raise_on_failure
boolean parameter toOpenAIDocumentEmbedder
andAzureOpenAIDocumentEmbedder
. If set toTrue
then the component will raise an exception when there is an error with the API request. It is set toFalse
by default so the previous behavior of logging an exception and continuing is still the default. -
Add
AsyncHFTokenStreamingHandler
for async streaming support inHuggingFaceLocalChatGenerator
-
For
HuggingFaceAPIGenerator
andHuggingFaceAPIChatGenerator
all additional key, value pairs passed inapi_params
are now passed to the initializations of the underlying Inference Clients. This allows passing of additional parameters to the clients liketimeout
,headers
,provider
, etc. This means we now can easily specify a different inference provider by passing theprovider
key inapi_params
. -
Updated StreamingChunk to add the fields
tool_calls
,tool_call_result
,index
, andstart
to make it easier to format the stream in a streaming callback.- Added new dataclass
ToolCallDelta
for theStreamingChunk.tool_calls
field to reflect that the arguments can be a string delta. - Updated
print_streaming_chunk
and_convert_streaming_chunks_to_chat_message
utility methods to use these new fields. This especially improves the formatting when usingprint_streaming_chunk
with Agent. - Updated
OpenAIGenerator
,OpenAIChatGenerator
,HuggingFaceAPIGenerator
,HuggingFaceAPIChatGenerator
,HuggingFaceLocalGenerator
andHuggingFaceLocalChatGenerator
to follow the new dataclasses. - Updated
ToolInvoker
to follow the StreamingChunk dataclass.
- Added new dataclass
⚡️ Enhancement Notes
- Added a new
deserialize_component_inplace
function to handle generic component deserialization that works with any component type. - Made doc-parser a core dependency since
ComponentTool
that uses it is one of the coreTool
components. - Make the
PipelineBase().validate_input
method public so users can use it with the confidence that it won't receive breaking changes without warning. This method is useful for checking that all required connections in a pipeline have a connection and is automatically called in the run method of Pipeline. It is being exposed as public for users who would like to call this method before runtime to validate the pipeline. - For component run Datadog tracing, set the span resource name to the component name instead of the operation name.
- Added a
trust_remote_code
parameter to theSentenceTransformersSimilarityRanker
component. When set to True, this enables execution of custom models and scripts hosted on the Hugging Face Hub. - Add a new parameter
require_tool_call_ids
toChatMessage.to_openai_dict_format
. The default isTrue
, for compatibility with OpenAI's Chat API: if theid
field is missing in a Tool Call, an error is raised. UsingFalse
is useful for shallow OpenAI-compatible APIs, where theid
field is not required. - Haystack's core modules are now "type complete", meaning that all function parameters and return types are explicitly annotated. This increases the usefulness of the newly added
py.typed
marker and sidesteps differences in type inference between the various type checker implementations. -
HuggingFaceAPIChatGenerator
now uses the util method_convert_streaming_chunks_to_chat_message
. This is to help with being consistent for how we convertStreamingChunks
into a finalChatMessage
.- If only system messages are provided as input a warning will be logged to the user indicating that this likely not intended and that they should probably also provide user messages.
⚠️ Deprecation Notes
async_executor
parameter inToolInvoker
is deprecated in favor ofmax_workers
parameter and will be removed in Haystack 2.16.0. You can usemax_workers
parameter to control the number of threads used for parallel tool calling.
🐛 Bug Fixes
- Fixed the
to_dict
andfrom_dict
ofToolInvoker
to properly serialize thestreaming_callback
init parameter. - Fix bug where if
raise_on_failure=False
and an error occurs mid-batch that the following embeddings would be paired with the wrong documents. - Fix component_invoker used by
ComponentTool
to work when a dataclass likeChatMessage
is directly passed tocomponent_tool.invoke(...)
. Previously this would either cause an error or silently skip your input. - Fixed a bug in the
LLMMetadataExtractor
that occurred when processingDocument
objects withNone
or empty string content. The component now gracefully handles these cases by marking such documents as failed and providing an appropriate error message in their metadata, without attempting an LLM call. - RecursiveDocumentSplitter now generates a unique
Document.id
for every chunk. The meta fields (split_id
,parent_id
, etc.) are populated beforeDocument
creation, so the hash used forid
generation is always unique. - In
ConditionalRouter
fixed theto_dict
andfrom_dict
methods to properly handle the case whenoutput_type
is aList
of types or aList
of strings. This occurs when a user specifies a route inConditionalRouter
to have multiple outputs. - Fix serialization of
GeneratedAnswer
whenChatMessage
objects are nested inmeta
. - Fix the serialization of
ComponentTool
andTool
when specifyingoutputs_to_string
. Previously an error occurred on deserialization right after serializing if outputs_to_string is not None. - When calling
set_output_types
we now also check that the decorator@component.output_types
is not present on therun_async
method of aComponent
. Previously we only checked that the Component.run method did not possess the decorator. - Fix type comparison in schema validation by replacing
is not
with!=
when checking the typeList[ChatMessage]
. This prevents false mismatches due to Python'sis
operator comparing object identity instead of equality. - Re-export symbols in
__init__.py
files. This ensures that short imports likefrom haystack.components.builders import ChatPromptBuilder
work equivalently tofrom haystack.components.builders.chat_prompt_builder import ChatPromptBuilder
, without causing errors or warnings in mypy/Pylance. - The
SuperComponent
class can now correctly serialize and deserialize aSuperComponent
based on an async pipeline. Previously, theSuperComponent
class always assumed the underlying pipeline was synchronous. - Fixed a bug in
OpenAIDocumentEmbedder
andAzureOpenAIDocumentEmbedder
where if an OpenAI API error occurred mid-batch then the following embeddings would be paired with the wrong documents.
💙 Big thank you to everyone who contributed to this release!
- @Amnah199 @Seth-Peters @anakin87 @atopx @davidsbatista @denisw @gulbaki @julian-risch @lan666as @mdrazak2001 @mpangrazzi @sjrl @srini047 @vblagoje