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_81979b2b / 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_81979b2bfailed1.5.0
14 steps · 21.9s · ≈$0.093

steps 11 → 14 · cost +95% · duration +63% · outcome failed

What changed between them

Agent version1.4.01.5.0
Prompt versionv7v8

Step by step

= same (4)≠ changed (5)+ only in B (4)− only in A (1)
A · run_8b4a65d4B · run_81979b2b
=#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
≠#6 gitlab.readFile#8 gitlab.readFileargs changed
=#7 claude-sonnet-4-5#9 claude-sonnet-4-5
≠#8 jira.createIssue429 Too Many Requests#10 jira.createIssue429 Too Many Requestsargs changed
≠#9 jira.createIssue429 Too Many Requests#11 jira.createIssueargs, outcome changed
−#10 jira.createIssue—
+—#12 claude-sonnet-4-5
+—#13 gitlab.createMergeRequest422 Unprocessable Entity
=#11 slack.postMessage#14 slack.postMessage

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