Repository navigation
fix(langchain): don't record tool call output if not include_prompt / should_send_default_pii - #4836
Conversation
… should_send_default_pii
|
✅ All tests passed in 2567.23s |
|
My one concern is that I have not heard tool arguments referred to as "prompts". Would users be confused if setting We could consider more granular setting, especially since I am unsure how intuitive it is for tool call input and outputs to fall under the "prompt" umbrella. But if that's more niche than we want to cater for, this looks good to go. |
@alexander-alderman-webb My thought on this is that a tool call may include raw user input, and that raw user input is a prompt, no? And in terms of behaviour, if a user specifies that they do not want to record that type of user input in general, we should stick to it throughout the SDK. Just to be clear: we still record 1. that tool calls happen and 2. which tool is being called - just not the user input associated with it. |
alexander-alderman-webb
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks for answering my questions!
Not sure if someone with more experience on the AI integrations should also approve.
antonpirker
left a comment
There was a problem hiding this comment.
Yes, looks good. The name include_prompts is not the best, you are right @alexander-alderman-webb but this is the name we have in other integrations. The functionality of it evolved over time. We probably should think of changing it but as this is a library we need to be careful with this to not break users code.
gen_ai.chatspans in langchain when users deselect the option to include prompts / send piiCloses TET-1181