Playground

The Playground is a standalone page for testing your agents against the live model, before you promote a version to champion. Open Playground in the dashboard sidebar. It's scoped to your active site, at /dashboard/sites/{siteId}/playground.

Open the PlaygroundCopy Anchor Link

• From the sidebar, Playground always opens on your active site's first agent and that agent's default version (its champion, or its newest version if there's no champion).
• From an agent's Versions table, a row's ⋯ → Playground action (or the Playground button on a version's read-only page) takes you straight to the Playground with that agent and version already preselected.

Test a versionCopy Anchor Link

• Pick the Agent and the Version to test from the configuration panel. The version selector is labeled with its number and status (e.g. "v3 · Champion").
• Type in the composer. The assistant answers using that version's instructions on top of its engine's base persona.
• New conversation starts a fresh thread. Switching to a different agent or version also starts a fresh thread: a conversation belongs to exactly one version, and switching agent resets the version selector to that agent's own default.

Playground conversations are saved like any other, on the Playground channel, so you can reopen them later under Conversations, where they show a Playground badge to set them apart from real shopper conversations. Once one has been quiet for a while, it's also labeled in the background by an AI judge.

Rate a responseCopy Anchor Link

Every assistant message has a thumbs-up/thumbs-down control. Rating one opens a dialog for an optional comment (and, for a thumbs-down, an optional issue category) rather than submitting instantly. See Rate a message for the full behavior, including how the rating still shows up when you reopen the conversation later under Conversations.

The configuration panelCopy Anchor Link

On desktop the configuration panel docks to the right of the chat, headed Configuration; collapse or restore it with the panel-toggle button in the top bar. On a narrower viewport it becomes a bottom sheet instead, opened with the settings (gear) button and closed by its close control, by tapping outside it, or with the Apply button at the bottom of the sheet. Applying is instant as you edit each field, so Apply is just a way to dismiss the sheet, not a separate commit step. Both presentations offer the same fields, grouped and separated by dividers:

• Agent and Version: described above (hidden while comparing; see below).

• User view: a two-option toggle, User and Technical:

  • Technical (the default): every tool call the assistant makes, and its reasoning, are visible as raw, collapsible detail. Each assistant message also gets a response-time badge (e.g. 164ms) next to the "more" menu; hover or focus it for a breakdown of first-token latency, total time, estimated speed, and chunk count. This badge is live-only: it's measured while a response streams in, so it doesn't appear when you reopen the conversation later under Conversations.
  • User: the same friendly display a shopper sees on the agent's public link: short status phrases like "Looking for the best products for you…" while a step is in progress, then just its result, with no tool names, no JSON, no reasoning text. This is the only view where a conditional instruction block's own indicator message shows, so it's where you preview one.

  Switching between the two only changes how the current conversation renders live. It doesn't affect what gets saved. Reopening the same conversation later under Conversations always shows the full technical detail, whichever view was active while you were chatting.

• Test language: previews, together, the chat panel's own on-screen text (the composer's placeholder, "Thinking…"-style status messages, and similar chrome) and the tested version's welcome screen (its welcome message, plus the starter questions carrying text in that language when the version has Show starter questions on; the Playground has no storefront page context, so a question scoped to specific page types still shows here), for one of the site's own enabled languages, or Auto to use the site's default language. This is unrelated to your own dashboard language: Auto resolves to the site's default, never to whatever locale your account happens to be in. Either way, it only affects this preview: it has no effect on the language the assistant replies in (still inferred from what you type, exactly as on the public link) and no effect on the rest of the dashboard.

• Test context: a freeform list of key/value pairs (e.g. product_id / SKU-1182) sent to the assistant as extra background for this test conversation only. Real shoppers never see it, and it never reaches the agent's public link. It's saved with the conversation it was set for, so reopening that conversation later still shows the context that produced it. Add a pair with Add a key/value pair, edit a key or value directly, or remove a pair with its × button.

  Test context is fixed for a conversation's whole lifetime: changing a pair after messages already exist starts a fresh, empty conversation with the updated context, exactly like changing the version does. Editing it before you've sent anything just updates what the first message will carry.

Compare two versionsCopy Anchor Link

Compare with another version, next to the version selector, splits the chat area into two panes on the same agent, each pane picking its own version. It's disabled when the agent has fewer than two non-archived versions, since there'd be nothing to compare against.

• Entering compare mode defaults the second pane to a different version than the first, preferring the champion if you started on a candidate or draft, or the newest remaining version otherwise. Change either pane's version from the selector in its own header.
• The Agent/Version fields in the side panel are replaced by both panes' version pickers while comparing; switching the agent exits compare mode and returns to a single pane on the new agent's default version.
• User view, Test language, and Test context stay shared fields in the configuration panel: they apply identically to both panes; there's no per-pane override.
• One shared composer sends your message to both panes at once. Each pane streams its own reply independently: one can finish before the other, and each pane's header keeps identifying which version it belongs to, so there's no ambiguity about which response is which.
• Each pane keeps its own conversation, so tool calls, replies, and history stay attributed to the right version. Nothing here merges the two into a single transcript.
• New conversation while comparing is a single control that resets both panes together, so they stay on the same turn count.
• Remove the second pane (its × button) to exit compare mode and go back to a single pane on the first pane's agent and version.

On a narrower viewport, the two panes become a tab switcher (one visible at a time), but the composer stays visible regardless of which tab is active, and a message you send still reaches the pane you're not currently looking at.