Flow Studio guide

Agents v0.10 · Early access · Updated 23 October 2026

Use Flow Studio for bounded prompts, field capture, branching, completion and operator queuing.

Create a small complete journey

Create the support starter and inspect its publishing, playback and fallback branches. Name the journey for its job. Capture only required issue information. Stable field names make interpolation maintainable. Do not request passwords, stream keys or tokens. Trace masking does not make secret collection appropriate.

Validate and simulate

Missing destinations, duplicate identifiers and malformed interpolation are rejected. Duplicate capture keys cannot overwrite earlier fields. Empty or oversized captured values receive retries. Cycles produce warnings and runtime step budgets limit execution. Simulations are isolated from live sessions. Try each route, an unknown response, invalid input and an already completed journey.

Review scenarios and coverage

Saved cases define turns and expected terminal outcome. Assertions can check response text, captured fields and operator queue. Node and branch coverage reveal untested paths. Visiting every node does not establish good advice; read each output. Draft or case changes invalidate old passing evidence. Compare compatible scenarios rather than unrelated suites.

Publish a version

Save the graph and scenarios.
Run the suite and inspect failures and coverage.
Request a fresh signed publication preview.
Confirm the unchanged preview.
Start a new runtime session and complete every important path manually.

Published versions and existing sessions remain fixed after draft edits. Rollback restores a draft for testing rather than silently changing active conversations.

Handoff and mode boundaries

A handoff queues a local operator request, not a carrier transfer or joined audio room. Assign staff to waiting conversations and verify text replies reach the original session. Closing the playground does not end it. Flow Studio and Evidence Studio are separate new-session modes; sending both identifiers is rejected. Cross-mode retrieval or an external help-desk integration must be scoped and validated separately.