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
{{ message }}
Repository navigation
Commit e7916b3
Browse filesBrowse the repository at this point in the historyBrowse files
Fix three demo bugs: browser beside apps, doubled tool calls, vendor names in steps (#824)
* Leave a computer tool the caller offers to the caller, beside headless plugin tools
In a conversation the browser offers the computer_* tools itself. When the Bot also held an app or research tool, the run was wrapped in HeadlessToolsMiddleware, which claimed every computer_* call and, holding no such tool, answered each one as unavailable for this headless turn. It now claims a computer_* call only when nobody else offered that tool, so an unattended turn still answers an unknown one with a refusal.
* Test that a caller's computer tool is not answered beside a plugin tool
* Note that a Bot with an app or web research can use its browser again
* Count a stored tool call the live turn already holds as that message
The stored conversation names a tool call's message differently from the live stream (assistant-call_1 where the stream said call_1), and mergeStoredMessages matched on message id only, so it inserted the stored copy as missing. Every tool call that came back from the store that way was drawn twice, which is most visible as two Connect cards for one refusal. A stored assistant message whose every call one live message already holds now anchors on that message instead of being added.
* Test merging a stored tool call the live turn already holds
* Note that an app a Bot could not use asks to be connected once
* Name a brokered app's action without the broker or the app's own prefix
Composio publishes every action as <APP>_<VERB>_<NOUN>, so a step read "Airtable list bases", and an Arcade app's key reached the screen as arcade-Gmail because only the composio- prefix was known. A brokered app's action now starts at the verb, "List bases", with the app named once beside it, and connectorName drops either broker's prefix.
* Summarise a brokered app's steps as the app, not as Composio Airtable
* Test naming brokered actions without any vendor prefix
* Test that a brokered app is summarised as the app
* Note that an app's steps are named for the app
* Name the message a step's tool calls belong to, as the store does
agent-langgraph sent TOOL_CALL_START with no parentMessageId, so the surface named each call's message after the call (call_1) while the conversation store kept the step as assistant-call_1. The surface then sent its copy back on the next turn and the store kept both, so every tool call of a finished turn was stored, and drawn, twice. Each step's calls now carry the store's name for their message, taken from the step's first call.
* Test that a step's tool calls name their stored message
* Say that a conversation no longer keeps a second copy of each tool call
0 commit comments