Execution mode and result visibility
Control how tools run and what the language model sees after execution — without changing your API.
Execution mode
Section titled “Execution mode”| Mode | Behavior | Best for |
|---|---|---|
| sync | Chat waits for the tool to finish before continuing | Fast lookups (< few seconds) |
| async | Tool runs in the background; visitor gets updates via status notifications | Slow APIs, batch jobs, multi-step backends |
Result visibility
Section titled “Result visibility”| Setting | Model receives | Best for |
|---|---|---|
| llm | Full tool JSON (subject to size limits) | Default — answers need API data |
| none | Success/failure only, no payload | Side-effect tools (create ticket, send email) where the model should summarize generically |
Use none when responses contain PII you do not want in the model context, or when the assistant should only confirm action completion.
Common combinations
Section titled “Common combinations”| Scenario | Execution | Visibility |
|---|---|---|
| Order status lookup | sync | llm |
| Hotel offer search + carousel | sync | llm (+ result_transform) |
| CRM note creation | sync | none |
| Report generation | async | llm |
Configure
Section titled “Configure”- Open tool → Execution.
- Set Execution mode and Result visibility.
- Pair async mode with on_start / on_delay notifications for better UX.
Rich content note
Section titled “Rich content note”Rich content cards are built server-side from successful tool JSON regardless of visibility — visitors see cards in the widget; none only limits what the LLM reads for follow-up turns.