Editor tour
By the end of this page you will know your way around the AI Agent Editor — where each setting lives and how saving and versioning work.
Prerequisites
- An AI Agent created (Create an AI Agent).
- Admin or Developer role.
The editor at a glance
The AI Agent Editor is a form-based screen (not a canvas). It has three regions: a header with actions, a row of tabs for configuration, and a live preview panel on the right.
The header
From left to right, the header shows:
- Back — returns to the Agents list.
- The agent name, an AI badge, and version badges: a Prod: badge showing the production version number (if one exists), and the current version with its status — for example
v2 • DRAFT(states are DRAFT, READY, or PRODUCTION). If a phone number is attached, a telephony badge appears. - Chat preview toggle — show or hide the preview panel.
- Versions — opens the versions panel (see Versioning).
- Save — saves your configuration.
- Publish — promotes a version to production (see Publish).
- Deploy — creates or updates a deployment (see Deploy).
- An overflow ⋮ menu with Version History, Duplicate as New Version, Discard Draft, and Delete.
The four tabs
All configuration lives under four tabs:
| Tab | What you set here |
|---|---|
| Agent Identity | Name, Administrative Summary, Persona, Skills, and the Fallback message. |
| LLM Settings | Reasoning mode, step and tool-call limits, UX settings, model, and LLM policy. |
| Memory | Profile, Episodic, and Semantic memory tiers. |
| Modes | Enable Conversation and Voice, and configure voice. |
The Agent Identity tab is selected by default, and it hosts the Skills editor — the surface where you spend most of your time.
The live preview panel
The panel on the right lets you chat with your agent (and talk to it, if Voice is enabled) without leaving the editor. It reflects the modes you’ve enabled. If the agent has no saved version yet, the panel shows “Chat Preview Unavailable” with a Save to Create Version button.
See Test the agent for the full testing workflow, including role impersonation.
Saving and versioning
Changes to persona, model, policy, skills, memory, and modes are staged locally. They are only persisted when you click Save.
Saving does two things: it validates your configuration (every skill needs a name and description, and each skill’s system prompt must be 16,000 characters or fewer), and it writes your changes into a draft version. If you were editing a production version, Save creates a new draft from it so production keeps running unchanged. On success you’ll see the toast “Agent configuration saved.”
Common issues
- Save does nothing / shows a validation error — A skill is missing a name or description, or a system prompt exceeds 16,000 characters. Fix the flagged skill and save again.
- Preview says “Chat Preview Unavailable” — The agent has no version yet. Click Save to Create Version.
- My change disappeared — Unsaved staged changes are discarded when you switch versions. Save before switching.