Replies: 2 comments 2 replies
-
|
Thanks for sharing! Do you have a minimum repro example for us to reproduce? |
Beta Was this translation helpful? Give feedback.
-
The trace for the tool call looks like this: I worked my way around it by having my own decorator that basically wraps the function and sets the trace inputs to everything besides runtime, so for me this is a non issue now. But you still might want to think about this, or give recommendations in the docs. Its a lot of unnecessary data sent your way. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature or potential improvement
Langchain now recommends the runtime to pass parameters into tools through the runtime context. The problem is, that when I add support for the runtime parameter into my tools, my trace shows the full runtime. Here a simplified input of a tool call in langfuse:
I know we can manually reconfigure the input in a trace, but I think we could handle this out of the box. I see little value of having the full conversation history inside an Agent trace for every tool call the agent calls. Its also tedious to always having to filter out parameters for every tool just for langfuse. In the best case the runtime context should be saved on an agent level and the runtime is removed from agent tool calls automatically.
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions