You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running a LangGraph flow with tool calls and have a response node that generates a response based on the tool calls/responses. When I run LangSmith Playground on this response node, which sees message history, including tool call and tool response message info, I get the following error in a popup on the bottom right of the LangSmith page:
tool_call() got an unexpected keyword argument 'artifact'
The artifact it refers to is likely my use of tool artifacts to retrieve from the tool not just what I want the response node LLM to see but also an artifact with more comprehensive data that I use for various logic outside of the response node. Here's documentation on artifacts: https://python.langchain.com/docs/how_to/tool_artifacts/.
It seems like there's just a bug in LangSmith Playground that doesn't handle artifacts well, but please let me know if I should do something differently.
Suggestion:
No response
The text was updated successfully, but these errors were encountered:
Issue you'd like to raise.
I'm running a LangGraph flow with tool calls and have a response node that generates a response based on the tool calls/responses. When I run LangSmith Playground on this response node, which sees message history, including tool call and tool response message info, I get the following error in a popup on the bottom right of the LangSmith page:
tool_call() got an unexpected keyword argument 'artifact'
The artifact it refers to is likely my use of tool artifacts to retrieve from the tool not just what I want the response node LLM to see but also an artifact with more comprehensive data that I use for various logic outside of the response node. Here's documentation on artifacts: https://python.langchain.com/docs/how_to/tool_artifacts/.
It seems like there's just a bug in LangSmith Playground that doesn't handle artifacts well, but please let me know if I should do something differently.
Suggestion:
No response
The text was updated successfully, but these errors were encountered: