Skip to main content
This is the same kind of question as anything else you ask Langy, aimed at a wider read: instead of one trace, it looks across your project’s history at once.
Also check: Ask Langy (the panel you ask from), Scenario tests and evals (what an investigation can produce).

​
Ask what changed

Point Langy at a window and it reads across your traces to find what moved, instead of making you page through them:
  • “Did my agent get worse this week?”
  • “What changed in my errors since the last deploy?”
  • “Where is my cost going, and how does it compare to last week?”
  • “Why is p50 latency 12s on the checkout agent?”
Langy runs the langwatch CLI (trace search, analytics query, and more) over the origin you named, compares this week to previous weeks, and comes back with the cost, latency, or quality change that stands out and the traces behind it. From there you can ask it to write a test or open a PR on the same finding.

​
Ask it to watch for you

When something is worth watching past a single question, ask Langy to set up an alert or an automation and it creates the monitor or trigger for you:
  • “Alert me if p95 latency on the checkout agent goes above 8s.”
  • “Create a trigger that flags any trace where the answer-correctness eval fails.”
  • “Watch my daily token spend and tell me if it jumps.”
Langy sets these up with langwatch monitor create and langwatch trigger create, so the alert or automation lives in your project like any other, not inside the chat. You change or remove it the same way you would one you made yourself.
These are things you ask Langy to do, on the window and metric you name. Langy analyzes your traces and sets up monitors when you ask; it does not watch and act on its own.