Investigate whether sending whole State object to a Tool automatically if State is in the tool's function signature would be beneficial.
A pro of this would be that it would be easier for developers creating tools from scratch to read/write from State without having to worry about using the inputs_from_state and outputs_to_state tool params which can at times be clunky.
However, this runs the risk of being able to do the same thing in too many different ways which could lead to user confusion about what's best-practice or the recommended route to use.
This idea has popped up a few times when talking with @deep-rloebbert, @sebastianh-deepset and @kacperlukawski as a way to make manipulating the Agent's State behavior easier when working directly with code.
👋 Hello there! This issue will be handled internally and isn't open for external contributions. If you'd like to contribute, please take a look at issues labeled contributions welcome or good first issue. We'd really appreciate it!
Investigate whether sending whole
Stateobject to aToolautomatically ifStateis in the tool's function signature would be beneficial.A pro of this would be that it would be easier for developers creating tools from scratch to read/write from
Statewithout having to worry about using theinputs_from_stateandoutputs_to_statetool params which can at times be clunky.However, this runs the risk of being able to do the same thing in too many different ways which could lead to user confusion about what's best-practice or the recommended route to use.
This idea has popped up a few times when talking with @deep-rloebbert, @sebastianh-deepset and @kacperlukawski as a way to make manipulating the Agent's State behavior easier when working directly with code.
👋 Hello there! This issue will be handled internally and isn't open for external contributions. If you'd like to contribute, please take a look at issues labeled contributions welcome or good first issue. We'd really appreciate it!