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
As of now, it seems that SetNextNode can be after ToolCalls, but not after Call.
It would be nice to make it consistent and allow SetNextNode after Call as well.
The text was updated successfully, but these errors were encountered:
Can you please create a short example illustrating what happens now when we generate SetNextNode after the Call and what the intended behavior looks like?
I've changed the computation of the next node in #73, and I have some doubts that these changes could already solve the problem, but I need a concrete example to check.
I was looking at the Financial Analyst example at the end of the intro notebook. Particularly inside the generate_steps function of the ActNode. I was wondering if we can change the order of SetNextNode() and AssistantStep(). Just tried it again and it seems to be working regardless of the order...
As of now, it seems that
SetNextNode
can be afterToolCalls
, but not afterCall
.It would be nice to make it consistent and allow
SetNextNode
afterCall
as well.The text was updated successfully, but these errors were encountered: