When to use a guided flow instead of free-form chat
Choose a bounded task
Publishing triage often has a finite path: ask a question, capture an issue, branch and finish or queue an operator. Flow Studio models this as a deterministic graph. Use it where the next step should be explicit. It does not need a model to decide the path and does not automatically retrieve knowledge from Evidence Studio.
Start small and include a fallback
Create the support starter and follow each outgoing path. Capture only what is needed for triage. Do not ask for passwords or stream keys: a capture field does not make those safe to collect. Make the unknown-answer branch useful and honest about operator availability. A short complete journey is preferable to an elaborate ideal-path demonstration.
Validate structure and behavior
Validation rejects missing targets, duplicate IDs and malformed interpolation. Cycles produce warnings and runtime step budgets limit execution. These checks cannot establish that wording is understandable. Simulate ordinary branches, empty and oversized answers, and a previously completed journey. Read the resulting text as a customer would before relying on structural validity.
Publish from scenario evidence
Saved scenarios can assert outcomes, text, fields and operator queues. Node and branch coverage expose untested paths but do not prove advice quality. Run the suite, review coverage and confirm publication from a fresh signed preview. Flow and evidence modes cannot share a new session in v0.10. Scope any required combination as separate integration work.
Product and guides
Explore creekX Agents · Quick start · Documentation. Written for v0.10 early access, 23 October 2026.
Frequently asked questions
Where should I start?
Read the separate Agents quick start and evaluate v0.10 in a private local workspace before a customer pilot.