agenthub · output.chat
Chat Output
The original chat reply node. Deprecated — Outcome does the same thing plus every other channel.
Why the node earns its place
It is kept only so existing graphs keep running. Outcome with its channel set to mirror reproduces this behaviour exactly, and the envelope it emits was made deliberately back-compatible so the swap needs no change anywhere downstream.
For anything new, use Outcome. Migrating an existing graph is a leisurely job, not an urgent one.
How it works at run time
- 1Take the text or message from its wired input.
- 2Emit it as the run's reply on the incoming channel.
What you wire
Inputs
- textstring
- messageobject
Outputs
Nothing handed onward.
Configuration
| Key | Type | Default & options | What it does |
|---|---|---|---|
| role | string | default "assistant" assistant · system | — |
What usually goes wrong
Watch for this
If you are reading this because it is in the palette, that is the point of confusion — it appears alongside Outcome and looks like the simpler choice. It is the older one.
Behaviour & provenance