Agent Builder sessions

Agent Builder maintains conversational context across multiple turns so you can refine configuration without repeating background information.

Session lifecycle

Phase	Behavior
Start	New session on first message or after explicit “new session”
Active	Context includes prior messages, pending plans, and resource IDs
Idle timeout	30 minutes without input closes the session
End	Close manually or on timeout; undo window expires with session

Multi-turn context

Agent Builder remembers within a session:

Assistant, KB, tool, and deployment names you referenced
Pending unconfirmed plans (until confirmed or cancelled)
Results of read-only queries and tool tests

Example follow-up:

You: Attach Help Center KB to Website Support
Agent Builder: [preview — waiting for confirm]
You: Also add the Returns Policy KB
Agent Builder: [updated preview with both attachments]

Cancel in progress

Stop a running plan or apply operation:

Method	When to use
Cancel button	During plan generation or preview
Type `cancel` / `stop`	Anytime before confirm
Close browser tab	Aborts in-flight requests; unconfirmed plans are discarded

Cancellation does not undo already-confirmed writes — use Undo for that.

Session vs. confirmed changes

State	Persists after session ends?
Chat history	No — session-scoped
Confirmed configuration writes	Yes — saved to your organization
Unconfirmed plans	No — discarded on session end
Undo availability	Expires with session (~30 min after confirm)

Starting a fresh session

Start a new session

Use this when switching to a unrelated assistant or project to avoid stale context.

Concurrent sessions

Only one active Agent Builder session per admin user is recommended. A second browser tab may show stale pending plans.