Chat Input (CHAT_INPUT)
The start of a chat pipeline. It passes the user’s chat message to the next module.
Category: Input & Output · Deployed: yes · Tool-capable: no
Ports
| Port | Kind | Purpose |
|---|---|---|
Prompt ( |
Output |
The user’s chat message |
No input port — a chat run starts here.
What happens at run time
-
A chat run starts at Chat Input. Only modules that are wired to it, directly or through other modules, run in a chat. A module that is not on such a path does not run, even if it is on the canvas.
-
Without Chat Input, a chat runs every module that has at least one wire.
-
Attached files: when the user attaches files, the message also names them. The agent can read a file only with an Attachment Tool.
Notes
-
A scheduled pipeline starts at a Scheduler instead. The Scheduler carries its own message.
-
A module without an input port, for example Data Faker as a step, can never be wired from Chat Input. So it does not run in a pipeline that has a Chat Input.