Skip to main content
When your team codes with AI assistants, problems hide in hundreds of sessions. Signals shows you where to look: the overview for the last 30 days walks you from where issues concentrate, to who owns them, to the evidence sessions behind them.

​
Triage signals

1

Find where issues concentrate

Start on the Signals overview. The Projects × patterns matrix shows which projects keep hitting the same problem, such as long idle gaps in sessions.
2

Filter anomaly reports

In Anomaly reports, filter by status, severity, or detector. Filter to High severity to triage what matters first.
3

Look up an anomaly code

Open any code in What the anomaly codes mean (AD-001 to AD-012). Each explains what it looks like, what an admin should do, and the guardrail to set.
4

Open the evidence

Click a matrix cell to jump to the evidence sessions behind it.
5

Act on each finding

Acknowledge, Resolve, Dismiss, or Accept risk on each report.
Signals overview for the last 30 days with the three-step workflow, users table and Projects by patterns matrix, names blurred
Anomaly reports list with status, severity and detector filters and Acknowledge, Resolve, Dismiss and Accept risk actions
AD-003 Runaway or looping session code detail with examples, admin action and guardrail
Projects by patterns cell expanded to its evidence sessions with the Session idle gaps explanation

​
FAQ

AD-003 is a runaway or looping session. The code detail explains what it looks like, the admin action, and the guardrail to set.
Filter Anomaly reports to High severity, then work through them with Acknowledge, Resolve, Dismiss, or Accept risk.
Yes. Click any cell in the Projects × patterns matrix to open the evidence sessions behind it.