wip: refactor query pipeline agent to use stateful function components #14263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this should be a cleaner UX than the old guide which made users use
AgentInputComponent
andAgentFnComponent
to define an agentic query pipeline.Here you can define a query pipeline through a single abstraction
StatefulFnComponent
:When you wrap a query pipeline with an agent worker, the
task
andstep.step_state
are injected in the state dictionary of every stateful component.This also makes it easier to test the query pipeline used for an agent in isolation. Just initialize the state dictionary of the query pipeline with
task
andstep.step_state
, and dopipeline.run()