Use the experimental dashboard Chat tab, manage user-scoped threads, and understand Agent access and stop-generation behavior.
Experimental dashboard chat
Web Chat lets you talk to an Agent from its dashboard Chat tab without configuring an external messaging provider. The feature is experimental and may change.
Start a chat
Open the Agent and select Chat. The composer is available when the Agent is Running and its health is Working. Send a message to start a thread. Agent Barn creates the built-in Web Chat Connection when needed; reading an empty history or opening its stream does not create a Connection.
You do not add, edit, or retire the built-in Connection through the normal provider Connection form. It has no external provider credentials.
Threads and history
You can create, rename, and delete threads, and return to existing conversations. Thread history is scoped to the requesting user within the Agent's Web Chat Connection. It is not a shared provider channel transcript. The Chat tab owns this history; the Agent's provider Conversations view excludes the built-in Web Chat Connection.
Initial history is bounded to the newest 500 messages and displayed chronologically. Thread listing is bounded to the newest 100 threads. Do not treat the visible history as a complete export of all past messages, or thread deletion as erasing runtime memory and every retained record.
Access
Reading Web Chat history requires effective activity.read access to the Agent. Sending, stopping, renaming, and deleting threads require agent.update. An Organization membership alone does not make an otherwise inaccessible Agent available.
Stop generation
Stop records a cancellation request and suppresses a late reply. It does not promise immediate interruption of the runtime's computation. Waiting state follows the durable delivery state, so navigating away and returning does not itself cancel a turn.
Related documentation
See Agent lifecycle, Share Agent access, and Communication Connections.