How confirmations work
Agent Builder never applies configuration changes silently. Every write operation requires explicit confirmation.
Confirmation flow
Section titled “Confirmation flow”| Step | What happens |
|---|---|
| 1. Request | You describe the desired change in natural language |
| 2. Plan | Agent Builder analyzes current state and drafts a change plan |
| 3. Preview | You see a diff: before/after values, affected resources, warnings |
| 4. Confirm or reject | You approve, edit the request, or cancel |
| 5. Apply | Only after approval, changes are written via the API |
Until step 5, no assistant, KB, tool, or deployment settings are modified.
Preview contents
Section titled “Preview contents”A typical preview includes:
| Section | Example |
|---|---|
| Summary | ”Update master prompt on Website Support” |
| Diff | Added/removed lines in prompt text |
| Affected resources | asst_7xK9mN2p |
| Warnings | ”This removes the Returns FAQ KB attachment” |
| Plan limits | ”Attaching this tool uses 4/5 tool slots on Starter” |
How to confirm
Section titled “How to confirm”| Action | Effect |
|---|---|
| Confirm / Apply button | Executes the planned writes |
| Edit request | Revises the plan without applying |
| Cancel | Discards the plan; no changes made |
You can also type “yes, apply it” or “confirm” in the chat after reviewing the preview.
Destructive changes
Section titled “Destructive changes”Operations that delete, archive, or detach resources show an additional confirmation:
⚠ This will detach "Legacy FAQ" from 2 assistants. Confirm?Destructive previews require a second explicit confirmation.
What does not need confirmation
Section titled “What does not need confirmation”Read-only operations execute immediately:
- Listing assistants, KBs, tools, deployments
- Showing current configuration
- Running tool test invocations (no config change)
- Explaining docs or suggesting prompts
Audit trail
Section titled “Audit trail”Confirmed writes appear in the audit feed with actor, timestamp, and change summary.