Tab · Build

Causal trail

Your alerts point at the line of code that caused them. Imports, callgraph, schema/route reads + writes (K4.B) joined to Sentry, Vercel, PostHog, and DB slow queries (K4.C) — a cross-signal correlator (K4.C.5) wires each alert to the change that likely triggered it.

Where to find it

  • Localhost: Build → Causal trail · the top item every time prod alerts
  • API: GET /api/causal-trail?signal=<sentry-incident-id>
  • MCP tool: causal_trail — pass a signal, get back a ranked list of suspect commits
  • Keyboard: ⌘ K then trail

What it does for you

One graph, four signals.Sentry crashes, Vercel deploy fails, PostHog event regressions, and DB slow queries all flow into the same causal graph, joined to the file or schema column they touch.
Each alert names its likely cause.The correlator scores recent commits by edge-distance to the affected code path and the time delta between deploy and signal — the top suspect lands on your dashboard with the diff one click away.
Opt-in per source, off by default.Sentry, Vercel, PostHog, and DB-slow-query ingest are each opt-in per repo with redaction at ingest — nothing leaves your machine until you turn it on.

Read more