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_18ebd6e2 / 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_18ebd6e2failed1.5.0
13 steps · 22.3s · ≈$0.011

steps 11 → 13 · cost −76% · duration +67% · outcome failed

What changed between them

Agent version1.4.01.5.0
Prompt versionv7v8
Modelclaude-sonnet-4-5gpt-4.1-mini

Step by step

= same (1)≠ changed (7)+ only in B (4)− only in A (2)
A · run_8b4a65d4B · run_18ebd6e2
≠#2 claude-sonnet-4-5#2 gpt-4.1-minimodel changed
≠#3 sentry.getIssue#3 sentry.getIssueargs changed
≠#4 claude-sonnet-4-5#4 gpt-4.1-minimodel changed
≠#5 gitlab.searchCode#5 gitlab.searchCodeargs changed
+—#6 gpt-4.1-mini
+—#7 gitlab.searchCode
≠#6 gitlab.readFile#8 gitlab.readFileargs changed
≠#7 claude-sonnet-4-5#9 gpt-4.1-minimodel changed
≠#8 jira.createIssue429 Too Many Requests#10 jira.createIssueargs, outcome changed
−#9 jira.createIssue429 Too Many Requests—
−#10 jira.createIssue—
+—#11 gpt-4.1-mini
+—#12 gitlab.createMergeRequest422 Unprocessable Entity
=#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.