Create a test from a conversation

Conversation prefill converts real runtime evidence into an editable test draft. It is useful when a production or Test Chat turn reveals a regression that should become a permanent Next Reply, Tool Invocation, or Simulation check.

Choose the evidence boundary#

Open a conversation and select Create test from here on the relevant event. Operade derives the draft from the ordered, append-only event ledger and applies a boundary based on the selected message. Events from later turns are excluded, even if the conversation continued afterward.

Selecting a User message includes that message as the final history entry. Selecting an Agent response stops history at the preceding User message, so rerunning Next Reply generates that response again instead of seeding it as an answer. The selected Agent text is preserved only as original_agent_response metadata and as an editing reference. If no preceding User message exists, the draft becomes a Simulation and stops before the selected response.

Earlier User and Agent messages become structured history. Tool calls and Tool results stay associated with a separate Agent entry, including consecutive Tool evidence. The selected response itself is never duplicated into executable Next Reply history.

Review the prefilled draft#

Prefill returns data; it does not save a test automatically. Choose the test type, remove customer-specific text, write the success condition or expected Tool action, and give the test a reusable name. The metadata records the source conversation, event sequence, selected Agent response when relevant, conversation identifier, and UTC time.

System metadata helps trace the origin but should not be used as a secret store. Replace personal data, credentials, order identifiers, and unrestricted free-form content with synthetic values before saving.

Save and run deliberately#

The prefill endpoint accepts an API key or dashboard session and enforces workspace scope. It does not scrape rendered dashboard HTML and does not expose events from another workspace. Saving creates the first immutable test revision.

After review, follow Create, edit, and share tests, then Attach and run tests. For the raw event view, see Transcript and Activity.