BUG: ToolResponse doesn't show up in onMessage, messages, as well as toolStatusStore

[digital-Chairman]

Hi,

Recently I discovered that ToolResponse message is not received with hume-react-sdk.

SDK version: v0.2.8

Expected behaviour:
When tool calling happens, onMessage event will trigger with ToolResponse, useVoice().messages will include ToolResponse, and toolStatusStore[toolID].resolved will not be null.

Actual behaviour:
Hume React will receive the toolCall message, but not the toolResponse message. In the dashboard, however, I can see the ToolResponse in Chat History, and based on my conversation with EVI, EVI did receive the message in the backend. This indicates that the socket in Hume React didn't process the ToolResponse message.

[zgreathouse]

@digital-Chairman For a tool use flow, you should only expect to see tool response messages for built in tools (e.g., websearch).

For function tools you can expect to receive a tool call message which contains the arguments for your tool. You then invoke your tool with the provided arguments and send the returned value back to EVI in a tool response message.

For more on orchestrating tool call flows in your application, see our documentation.

In case I am misunderstanding your post, I tried reproducing with our Next.js function calling example and tool call flows were working as expected with the latest version of the React SDK (0.2.9). When you run the same example with your credentials, do you still experience the same behavior?

[digital-Chairman]

@zgreathouse I see, I didn't know that the tool response message was for built-in only. Just ran a test in the example, it worked as you described: the built-in tools received a tool response, whereas the get_weather tool did not.

Can the client also receive tool responses from custom tools from onMessage()? I have a background agent that needs to track the chat history between the user and EVI. I do have a jank workaround right now, where I upload the tool response message to my own chat history before I call send.success() or send.error().