langwatch CLI, so what comes back lives in your project like any test or evaluator you wrote by hand. Which one it picks depends on what the question needs to prove; see the table below.
Also check: Ask Langy (how you request a test), Pull requests (the tests it wrote run in your CI), Agent Simulations and Evaluations (the product surfaces these land in).
Scenario simulation tests
A Scenario test is a multi-turn simulation. A simulated user drives your agent across a full conversation, probing it the way a real user would, and a judge scores the transcript against the criteria you set. This is how Langy catches behavior that a single-turn check misses: an agent that holds the line for one message but drifts by turn 15. Langy writes and runs these with:
The Simulations overview filtered to red-team runs. Each row is a scenario run with its outcome.

A scenario run detail: the judge verdict with the reasoning it used to reach it.

A failed-run detail with the bug log showing where the agent's behavior diverged from the criteria.
Evaluations
An evaluation scores a run against a criterion: answer correctness, a custom rule, an LLM judge, a pairwise comparison. Langy writes evaluators and runs experiments and monitors with the CLI:langwatch experiment runscores an offline or batch run, for comparing two models or two prompts. See Experiments and running evals in CI/CD.langwatch monitor createsets up an online evaluation that scores live production traffic. See Online evaluation.langwatch evaluator createdefines the evaluator both of the above use. See Evaluators.
Which one Langy picks
Langy picks based on what your question needs to prove:
You can also name the one you want in the chat: “write a Scenario test that…” or “set up an evaluator for…”.