| Age | Commit message (Collapse) | Author |
|
In a tool_call_update, the content field must be a vector of
association lists, not just an association list.
|
|
It is enough to send the tool title, kind and rawInput the first time
when the tool call is created. There is no need to send these fields
repeatedly in subsequent updates. Subsequent updates need only mention
fields that have actually changed.
|
|
A sessionUpdate of "tool_call" must only be sent when the tool call is
created. Further updates must send a sessionUpdate of
"tool_call_update".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Report tool call parse failures immediately to the LLM without
bothering the client with permission requests; only notify the client.
|
|
We process tool calls one at a time using a new function
next-state-tool-call. We refactor next-state-llm-response to use
next-state-tool-call.
|
|
In doing so, we also change state->llm-request to state->llm-requests.
The new function now returns a list of <llm-request> objects rather
than a single one.
|
|
|
|
|