FRSelf-host it
Live demo — simulated traces from two agents. sentry-triage regressed when agent 1.5.0 and prompt v8 shipped; support-bot is healthy. Read-only.
Agents / sentry-triage / run_04839b8e / compare

Compare runs

B is compared with the latest successful run of the previous version.

Arun_8b4a65d4ok1.4.0
11 steps · 13.4s · ≈$0.048
Brun_04839b8eok1.5.0
13 steps · 18.5s · ≈$0.084

steps 11 → 13 · cost +76% · duration +38% · outcome succeeded

What changed between them

Agent version1.4.01.5.0
Prompt versionv7v8

Step by step

= same (4)≠ changed (4)+ only in B (4)− only in A (2)
A · run_8b4a65d4B · run_04839b8e
=#2 claude-sonnet-4-5#2 claude-sonnet-4-5
≠#3 sentry.getIssue#3 sentry.getIssueargs changed
=#4 claude-sonnet-4-5#4 claude-sonnet-4-5
≠#5 gitlab.searchCode#5 gitlab.searchCodeargs changed
+—#6 claude-sonnet-4-5
+—#7 gitlab.searchCode
+—#8 claude-sonnet-4-5
+—#9 gitlab.searchCode
≠#6 gitlab.readFile#10 gitlab.readFileargs changed
=#7 claude-sonnet-4-5#11 claude-sonnet-4-5
≠#8 jira.createIssue429 Too Many Requests#12 jira.createIssueargs, outcome changed
−#9 jira.createIssue429 Too Many Requests—
−#10 jira.createIssue—
=#11 slack.postMessage#13 slack.postMessage

System spans are left out; steps are aligned on the tool called (or LLM call), then compared on arguments and outcome.