Skip to main content
An agent is the artifact you build and deploy. Its conversation logic is a flow, which you edit in the builder. A deployment is the agent’s live operating setup, and a channel is the surface where end users talk to it. Tars ships two channels: Web and WhatsApp.

​
Agent states

The Draft, Published, and Unpublished changes states with publish and edit arrows, plus a duplication branch that creates a new agent with its own deployment
The agent library shows each agent’s state on its card:

​
Versions and drafts

Publishing takes a snapshot of the flow and numbers it: v1, v2, and so on. The version end users currently get carries the Live badge. After a rollback, that is not the newest version. Editing the builder never touches the live version, which is why the amber dot can exist. Beyond the working copy, you can create named drafts to experiment in while the live agent keeps running untouched. The builder toolbar shows which environment you are editing: Live, Draft · followed by the draft name, or Not published. Selecting Make live on a draft publishes it as the next version. The Rollback action returns an earlier version to live, and Clone to draft copies the live version into a new draft. See Drafts and publishing for the full workflow.

​
Test and live environments

Conversations belong to one of two environments. Test conversations come from the builder’s test panel and from draft preview links. Live conversations come from end users on a channel. The split is visible in two places. The Activity section of an agent has one source picker. It offers Live, Test · Published flow, and each named draft under Draft previews. The conversation inbox has a test and live toggle in its left rail. The split also matters for billing, because test and draft conversations are never billed. See Watch conversations and Conversation usage.

​
Duplication

Duplicating an agent creates a separate agent, not another version. You choose the source: the current draft, including unpublished changes, or the last published version. The copy receives its own deployment and does not depend on the source agent.

​
From build to live

The four steps from building the flow to connecting knowledge and tools, publishing the agent, and deploying it to the Web and WhatsApp channels
The path from an empty flow to a live agent runs through four stages. First you build the flow in the builder, one gambit at a time. Then you connect knowledge bases and tools so the agent can answer from your content and act on it. Finally you publish the agent and deploy it to channels.

Quickstart

Build, test, publish, and share your first agent in about 15 minutes.

Organizations and members

How organizations, members, roles, and plans fit together.

Deployments explained

How a deployment connects a published agent to its channels.

Builder basics

Add gambits from the palette and connect branches.