Document the wren node and the chat's Control tab

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013GAeg4Jo6xjZzjwy9QDWMQ
2026-10-05 20:59:23 +02:00
parent 673061d9fb
commit e8536e7c1c
3 changed files with 100 additions and 0 deletions
@@ -114,6 +114,21 @@ configuration, and the bin in the panel's header starts it over. `MCP_ENABLED`
 is not needed for it: the endpoint is for agents outside, the chat for the
 one inside.

+## Control
+
+Where a live flow has a [`wren` node](../reference/node-types.md#wren) with
+its `prompt` and `actions` wired, the chat gains a **Control** tab, and Home a
+chat button at the top right of the brain graph (in the header, on a phone)
+that opens it. No provider is needed for this one: the model is the node.
+
+A command is published to the node's `prompt` message as a value from the
+chat, and the answer is the next value of its `actions`: each call, the
+message it went to, whether it was applied, and how sure the model was. A
+failing node answers with its error, and one that says nothing for fifteen
+seconds is reported as such. With several nodes, a picker in the header
+chooses. The conversation is kept in the browser only, and a reload clears
+it.
+
 ## A note on working this way

 The pattern that works is the same one that works with a person: let the agent