Assistant node, and the Control tab as one conversation (openpanel V5)
run_turn takes its tools, system prompt and tool caller; the chat passes the MCP tools as before. The assistant node offers one tool per wired target, reads its other inputs as context, streams its reply a sentence at a time, warms the provider on `listening` and says so when the provider is not there. Completions share the per-server HTTP client. wren replies when nothing reads `unhandled`, stt shows a note when nothing was heard. /ai/control lists one conversation per entry node with the messages to watch.
This commit is contained in:
@@ -84,10 +84,13 @@ export class AiService {
|
||||
|
||||
/**
|
||||
* Read Control Nodes
|
||||
* The wren nodes of the running live flows, for the chat's Control tab.
|
||||
* The conversations of the running live flows, for the chat's Control tab.
|
||||
*
|
||||
* Only those with both ends wired: the chat publishes the command on the
|
||||
* prompt's message and reads the answer off the actions'.
|
||||
* One per wren or assistant node a command reaches first. A node whose
|
||||
* prompt is another's ``unhandled`` answers in that one's conversation,
|
||||
* after it. The conversation shows the prompt, the words heard so far (the
|
||||
* ``partial`` of a ``stt`` node writing the prompt), and each node's
|
||||
* ``reply`` and ``actions``, so typed and spoken commands are one.
|
||||
* @returns ControlNode Successful Response
|
||||
* @throws ApiError
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user