Start and End gambits - Tars Docs

Start is where a conversation the end user opens enters the flow. Reaching End marks the conversation complete.

The gambits in the builder

Here both bounding gambits of the demo flow are highlighted, and the rest of the screen is dimmed. Both render as rounded pills rather than the card shape the configurable gambits use. Neither takes any settings.

Start

Property	Behavior
Count	One per flow. Start is not in the palette, so you cannot add a second.
Deletion	Cannot be deleted.
Handles	One outgoing handle.
Settings	None.

A conversation started by a Trigger gambit enters at that gambit instead. To open the conversation with a message, wire Start to a Text or No Input gambit and put the message there.

End

Property	Behavior
Count	As many as the flow needs. Add more from the Flow Control group of the palette.
Deletion	The default End gambit cannot be deleted. End gambits you add can.
Handles	One incoming handle. Nothing leaves an End gambit.
Settings	None.

A flow can also stop by running out of connected gambits. That conversation is not marked complete. Wire an End gambit on every path you consider finished.

Verify

Select Validate in the toolbar to open the Problems panel. A flow with no End gambit is an error, and a gambit with no outgoing connection that is not an End gambit is a warning. See Test your agent.