Configuration versions

An agent's configuration lives in versions. A version selects an ordered set of instruction blocks (reusable, site-wide instruction content) plus the engine it runs on, which connectors and chat tools it can use, its conversation starters, and its shopper-facing public identity (name and avatar). Versions let you change how an agent behaves while keeping every earlier configuration as history.

Where versions liveCopy Anchor Link

Open an agent and you land on its Overview tab: a status card (live or no champion yet, when the agent was last modified, and a Playground shortcut once there's a champion), quick-link cards into the editing surface that each show that section's live facts, and activity cards for recent conversations and the latest Evaluations run. The agent's name and type sit above the tabs themselves, in the page header, not on Overview. Editing and version history are split across the rest of the agent detail workspace:

• Identity, Capabilities, Instructions: the shared editing surface where you actually change a version's configuration. See Edit or create a version below.
• Versions: a table of every version with its status, engine, and last-updated date. Filter it by status or engine, sort any column (Version, Status, Engine, Updated), and click a row to open that version. Per-row actions live in a ⋯ menu: View, Playground, Duplicate (editors only), Promote to champion (hidden once it's champion), and Archive (hidden once it's archived).

Versions are immutableCopy Anchor Link

You don't edit a version. To change anything (instruction blocks, engine, tools, or connectors), you create a new version; the old ones stay readable as history. There is no in-place edit and no way to overwrite a version.

Opening a version from the Versions table shows it on a read-only page: every field is filled in and disabled. To change it, use Duplicate, which opens the shared editing surface prefilled from that version.

A version created before public identity was versioned shows a note on this read-only page saying its name/avatar were copied in by a one-time migration, not actually configured by a merchant for that version. The rest of that version's configuration is unaffected.

EngineCopy Anchor Link

Each version runs on an engine you pick when you create it. For a shopping assistant you choose between AISA Extra Light 1.0, AISA Light 1.0, AISA Standard 1.0, and AISA Max 1.0: tiers that trade response speed against answer quality. AISA Standard 1.0 is the default. Custom agents run on Custom 1.0, their only engine, so the selector is fixed.

The engine is part of the version, so it's pinned once the version is created and never changes on its own. To move an agent onto a different engine, create a new version and pick the engine there.

StatusesCopy Anchor Link

Every version has a status:

Saving on the editing surface can create a Draft, Candidate, or Champion version; see Edit or create a version below for how the save bar maps to each. Archived isn't a target you pick when saving: a version reaches it by being archived, or by being the champion that a newly promoted champion replaces.

InstructionsCopy Anchor Link

Instead of one free-text field, a version's guidance comes from instruction blocks it selects, in order; see Instructions for how to write and manage them. Here's how they fit into a version:

• Every site has a mandatory Général block, always active and forced-included in every version: the direct replacement for "just type your instructions." Blocks beyond it are optional.
• Each block is either Always active (its text is always composed into the system prompt) or Conditional (the assistant loads it only when its condition matches the conversation).
• A version pins the exact revision of each selected block at the moment you create it, never "whatever the block currently says." If a block you've selected has picked up a newer revision since, the picker flags it and offers update to latest for that one block, in this draft only.
• Reorder selected blocks with the up/down arrows; order sets both how they compose into the prompt and how they render in the picker.
• You can write a block without leaving the editing surface: New instruction creates one in a side panel and adds it to the selection, and the pencil on a selected block's row edits that block and re-pins this draft to the revision you just wrote. See Author a block from the editing surface for what that does and doesn't touch.

Conversation startersCopy Anchor Link

A version carries a welcome message per language the site has enabled (see Languages), a single alignment setting, and a switch deciding whether the welcome screen shows starter questions.

• Welcome message: up to 200 characters, shown above the composer on an empty conversation. Optional per language.
• Alignment: Left (the default), Center, or Right. Starter-question chips always stack in a single column, one below another. Alignment positions that column horizontally, it doesn't lay chips out side by side. It affects only the chips: the welcome message and the agent identity shown above it are always centered, regardless of this setting. One value for the whole version, the same across every language; there's no per-language alignment.
• Show starter questions: on by default. With it on, the welcome screen shows up to three chips from the site's starter-question library; with it off, none, whatever the library holds. Manage questions next to the switch opens that library.

Configure these on the Identity tab of the editing surface, in the Conversation starters section: pick the alignment once, switch between language tabs to fill in each language's welcome message, then set the switch. A dot on a tab marks a language that already has a welcome message.

The welcome message, the alignment and the switch are immutable per version, like a version's instruction blocks: editing any of them mints a new version rather than changing the current one. They apply to the hosted public link and the embedded web tag, and you can preview the result per language from the Playground.

Edit or create a versionCopy Anchor Link

Because versions are immutable, "editing" means creating a new one, but there's no separate page dedicated to that. Identity, Capabilities, and Instructions are the editor: landing on any of the three means you're already editing the agent's current configuration, split across the three tabs:

• Identity: avatar, per-language display name (see Public identity), and conversation starters.
• Capabilities: the engine, chat tools, capabilities, and connectors.
• Instructions: the instruction block picker described above.

Switching between the three sub-tabs never loses what you've typed: they share one mounted form. You reach this surface from:

• Identity, Capabilities, or Instructions in the agent's tab bar, or a quick-link card on Overview: prefilled from the current champion (or, if there's none, the most recent version).
• New version on the Versions tab's toolbar: same prefill as above.
• Duplicate on a version's row menu or its read-only page: prefilled from that specific version.

A banner above the tabs names the version your draft is derived from (or that this is a fresh first draft) and reminds you that saving creates a new version; the source stays intact.

Save, save as candidate, or publishCopy Anchor Link

A sticky bar at the bottom of the editing surface replaces the old single "save as" field with three actions:

• Save: the default action, creates a draft. No visitor impact, whatever the agent's current champion is.
• The small menu next to it, Save as candidate: same as Save, but marks the version Candidate instead of Draft (see Statuses above for what that status does and doesn't do today).
• Publish: promotes straight to champion. The first click turns the button into "Confirm publish?"; a second click actually publishes. Any other edit cancels that confirmation state, so it never carries over to an unrelated click.

All three actions stay disabled until you've actually changed something, since every one mints a new version, clicking Save or Publish with nothing edited would otherwise just duplicate the version you started from.

Whichever action you use, a new version is minted with the next version number and the previous champion is archived automatically if you published.

Creating and editing versions requires the Agents: Edit permission. A viewer sees the read-only pages, and the Identity/Capabilities/Instructions tabs with every field disabled and no save bar.

Promote or archive a versionCopy Anchor Link

From a version's read-only page, or from its row's ⋯ menu in the Versions table:

• Promote to champion moves it to champion, archiving the current champion. Shown on any version that isn't already the champion.
• Archive moves it to archived. Shown on any version that isn't already archived.

The Playground button on a version's read-only page (and the Playground item in its row menu) opens the Playground pinned to that exact version.