Flow suggestions

Suggestions are flows Qassandra discovered but hasn't added to your test suite yet. They give you control over what becomes part of your regression suite.

Why suggestions exist

If discovery just dumped every flow it found straight into your suite, two things would go wrong:

You'd end up with hundreds of low-value flows (e.g. variations of the same login form) that bloat your runtime.
You'd lose the human review step that catches misnamed or duplicate flows.

Suggestions sit in the middle: discovery proposes, you decide. Approving a suggestion promotes it to a real flow that future checks will run.

Where suggestions appear

Every check that discovers new flows lists them on the check detail page under Suggestions. For each suggestion you can:

Approve — turn it into a real flow. It will run in subsequent checks.
Reject — dismiss it. Qassandra remembers rejected suggestions and won't propose the same flow again.

Bootstrap auto-approval

When an app has zero flows and you trigger your first check, Qassandra runs in bootstrap mode: every discovered flow is auto-approved so the check has something to execute right away. After that, the normal review-then-approve workflow applies.

Force a discovery pass

Sometimes you want suggestions on demand — for example after a major redesign or feature launch. Trigger a check with discover_flows: true in the body and Qassandra will run a dedicated discovery pass alongside the regular flow execution. See Trigger a check.

What the agent looks at

During discovery the explorer walks a breadth-first frontier of URLs and UI states. At each rendered state it:

Analyses the page structure (forms, buttons, inputs, modals).
Opens menus, tabs, accordions, and safe search/filter forms to reveal deeper states.
Identifies plausible user journeys and writes step-by-step instructions.
Generates assertions to verify successful completion.
Records a Browserbase session for the discovery run (viewable as a replay).