LLM agents are increasingly applied to anomaly detection and root-cause analysis in time-series observations collected from real-world systems; however, their performance on these tasks has not been systematically evaluated under controlled conditions. We introduce TraceBench, a simulation-based framework for generating controlled root-cause attribution tasks. In each generated task, an agent receives time-series observations produced by simulating a physical dynamical system and must determine whether a system parameter was altered during the simulation and, if so, which one. Using TraceBench, we generate tasks from three interpretable mechanical systems and systematically evaluate four LLM agents across controlled experimental conditions, yielding new insights into how these agents analyze time-series observations from dynamical systems. Our results show that agents benefit substantially from domain context and explore data primarily through numerical console output rather than visualizations. We also find that agents generally perform worse when required to produce a Python script that maps each time-series sample to a predicted root-cause label than when they submit predictions directly. We release our datasets, agent trajectories, experimental results, and a leaderboard on our website, tracebench.github.io.
Figures & tables
Figure 1. Overview of the TraceBench framework using a bouncing-ball simulator. In this example, the black and orange segments show the position observation under the low-noise setting before and after an intervention at tint=4.0 . The intervention increases gravitational acceleration, and the dashed line marks the intervention time. At test time, the agent determines from the observed time-series channels whether an intervention occurred and, if so, which parameter changed. \name{} pipeline: a physical simulator produces multivariate time series before and after a parameter intervention; the low-noise BallDrop position observation is black before and orange after a dashed gravity-intervention marker; the agent identifies the changed root-cause parameter.
Figure 2. The four controllable axes in TraceBench. Four cards summarize the independently controlled \name{} task axes: domain context, observation noise, labeled examples, and direct or programmatic submission.
Figure 3. Representative noise-free signals from one observed channel for each simulator. Black and orange segments show the trajectory before and after the intervention time, respectively, which is marked by a dashed vertical line. The panels show position for BallDrop and BounceBall , and velocity for MassSlide . The interventions increase the coefficient of restitution in BallDrop and the inclination angle in BounceBall , and decrease the plane inclination in MassSlide . Additional examples with observation noise and all observed channels are provided in Appendix A . Three horizontally arranged time-series plots showing position for BallDrop and BounceBall and velocity for MassSlide. Each plot marks the intervention time with a dashed vertical line.
Low Noise
High Noise
Sdirect
Sprog
Sdirect
Sprog
Episode
Episode
Held-out
Episode
Episode
Held-out
Accuracy
gpt-5.5
0.933±0.056
0.853±0.143
0.671±0.096
0.833±0.194
0.733±0.227
0.547±0.138
gemini-3.1-pro
0.760±0.115
0.733±0.153
0.604±0.128
0.560±0.221
0.547±0.169
0.440±0.085
claude-opus-4.6
0.853±0.115
0.687±0.122
0.614±0.084
0.593±0.170
0.593±0.190
0.499±0.129
Table 1. Mean accuracy and exploration metrics per episode for the main experiment, aggregated across simulators. Accuracy values are reported as the mean ± within-simulator standard deviation; random-chance accuracy is 0.189. Python calls indicate the total number of Python interpreter invocations, while Python statements count statements across generated Python source versions. Plot counts report the number of generated ∣ inspected plots. Console-output entries report the number of numeric values printed ∣ the estimated percentage of tokens attributable to console output. See Appendix G for computation details.
Figure 4. Accuracy as a function of token usage, evaluation cost, episode time, and tool calls. Each point aggregates all episodes for one agent-system configuration across the four main-experiment conditions, three simulators, and five repetition seeds. Four scatter plots compare model accuracy with token usage, evaluation cost, episode time, and tool calls. Each point represents one agent-system configuration aggregated over all episodes, with error bars showing population standard deviations.
Sdirect
Sprog
Episode
Episode
Held-out
Accuracy
gpt-5.5 (No labeled examples)
0.887±0.125 ( +5.3 )
0.847±0.116 ( +11.3 )
0.506±0.070 ( -4.1 )
gemini-3.1-pro (No labeled examples)
0.647±0.159 ( +8.7 )
0.653±0.176 ( +10.7 )
0.444±0.113 ( +0.4 )
gpt-5.5 (No domain context)
0.513±0.202 ( -32.0 )
0.453±0.209 ( -28.0 )
0.316±0.092 ( -23.2 )
gemini-3.1-pro (No domain context)
0.313±0.135 ( -24.7 )
0.347±0.154 ( -20.0 )
0.328±0.043 ( -11.3 )
Table 2. Accuracy and token usage for the two high-noise ablation conditions, aggregated across simulators. Entries report the mean ± within-simulator standard deviation, followed in parentheses by the signed change relative to the corresponding non-ablated condition with three labeled examples per class and domain context. Accuracy changes are in percentage points; token values and changes are in millions.
Appendix figures & tables37 assets
Supplementary material from the paper’s appendix.
Appendix
Simulation End
10 s
Sampling Frequency
400 Hz
Number of Rows
3999
Appendix
Table 3. BallDrop simulation settings used by the released trajectories.
Applies to
Rule
All interventions
The first apex after the first detected divergence must exceed 0.1m in at least one of the intervention and baseline traces, and each trace must contain fewer than 25 qualifying rebounds.
Qualifying rebound
The ground-contact signal must exceed 1 , the incoming speed must exceed 0.5ms−1 , and the rebound speed must exceed 0.1ms−1 ; events separated by less than 0.03s are merged.
Drag, mass, and restitution
A qualifying rebound must occur both before and after the first detected divergence.
Drag
The normalized-DTW velocity distance over the following 0.2s must exceed 0.1 , or the terminal-velocity rule must hold.
Terminal-velocity rule
Accept a near-terminal descent after a rebound or one that ends above 0.1m before the trace ends.
Appendix
Table 4. Simulator-specific rejection rules for BallDrop.
Figure 5. Position, velocity, and ground-contact impulse (Ns) channels from BallDrop under (a) low and (b) high observation noise. Two side-by-side sets of three aligned BallDrop time-series panels showing position, velocity, and ground-contact impulse (Ns) before and after a gravity intervention. The left set uses low observation noise and the right set uses high observation noise.
Channel
Low Noise
High Noise
Impulse
21.07±2.55
9.03±2.55
Position
42.41±3.19
30.58±3.14
Velocity
36.58±2.60
24.54±2.60
Appendix
Table 7. BallDrop released-trajectory SNR in dB as the mean and sample standard deviation.
Simulation End
60 s
Sampling Frequency
50 Hz
Number of Rows
2999
Appendix
Table 8. BounceBall simulation settings used by the released trajectories.
Applies to
Rule
All interventions
Each usable intervention and baseline trace must contain fewer than 20 impacts. Impacts are counted from velocity reversals whose incoming speed exceeds 0.1ms−1 ; when velocity reversals cannot be computed, samples with absolute right-contact force above 10−9N are used.
Mass and viscous damping
In the intervention trace, a qualifying velocity reversal must occur both before and after the intervention time, and right-contact force must exceed 500N on both sides of that time.
Appendix
Table 9. Simulator-specific rejection rules for BounceBall.
Figure 6. Position, velocity, and right-wall force channels from BounceBall under (a) low and (b) high observation noise. Two side-by-side sets of three aligned BounceBall time-series panels showing position, velocity, and right-wall force before and after an inclination-angle intervention. The left set uses low observation noise and the right set uses high observation noise.
Channel
Low Noise
High Noise
Position
30.02±1.91
17.97±1.91
Velocity
40.98±2.46
28.94±2.46
Force
39.09±2.45
27.05±2.45
Appendix
Table 12. BounceBall released-trajectory SNR in dB as the mean and sample standard deviation.
Simulation End
10 s
Sampling Frequency
50 Hz
Number of Rows
499
Appendix
Table 13. MassSlide simulation settings used by the released trajectories.
Applies to
Rule
Breakaway friction
At least one common non-time channel must have symmetric relative difference 2∣y−y0∣/(∣y∣+∣y0∣+ϵSRD)>0.2 for five consecutive samples.
Gravity
At least one of the intervention and baseline traces must contain five finite, nonzero velocity samples before and five after the reference change time, taken as the intervention time or, if unavailable, the earliest detected divergence.
All remaining classes
No additional simulator-specific rule is applied.
Appendix
Table 14. Simulator-specific rejection rules for MassSlide.
Figure 7. Velocity, friction-force, and normal-force channels from MassSlide under (a) low and (b) high observation noise. Two side-by-side sets of three aligned MassSlide time-series panels showing velocity, friction force, and normal force before and after a Coulomb-friction-coefficient intervention. The left set uses low observation noise and the right set uses high observation noise.
Channel
Low Noise
High Noise
friction_force
42.03±9.75
29.99±9.75
mass_velocity
35.64±6.58
23.60±6.58
normal_force
59.90±0.40
47.86±0.40
Appendix
Table 17. MassSlide released-trajectory SNR in dB as the mean and sample standard deviation.
Table 18. Available platforms and their installation requirements.
Agent
Platform
Reasoning Effort
Img.
claude-opus-4.6
claude-code
high
Y
gemini-3.1-pro
gemini-cli
high
Y
gpt-5.5
codex
high
Y
minimax-m2.7
opencode
–
N
Appendix
Table 19. Agent profile catalog.
Package
Version
contourpy
1.3.3
cycler
0.12.1
fonttools
4.61.1
iniconfig
2.3.0
joblib
1.5.3
kiwisolver
1.4.9
Appendix
Table 20. Python packages installed in the agent runtime.
Agent
Input
Cached
Output
claude-opus-4.6
5
0.5
25
gemini-3.1-pro
2
0.2
12
gpt-5.5
5
0.5
30
minimax-m2.7
0.3
0.059
1.20
Appendix
Table 21. Agent prices used to compute evaluation costs, in USD per 1M tokens.
Figure 8. Episode top-1 accuracy versus mean evaluation cost for BallDrop under the four main-experiment conditions. Scatter plot of episode top-1 accuracy versus evaluation cost for BallDrop across models and experimental conditions.
Figure 9. Episode top-1 accuracy versus mean evaluation cost for BounceBall under the four main-experiment conditions. Scatter plot of episode top-1 accuracy versus evaluation cost for BounceBall across models and experimental conditions.
Figure 10. Episode top-1 accuracy versus mean evaluation cost for MassSlide under the four main-experiment conditions. Scatter plot of episode top-1 accuracy versus evaluation cost for MassSlide across models and experimental conditions.
Figure 11. BallDrop confusion matrices for Sdirect , reported separately for every agent under κlow and κhigh .
Figure 12. BounceBall confusion matrices for Sdirect , reported separately for every agent under κlow and κhigh . Eight BounceBall confusion matrices arranged in four agent rows and two noise-level columns. Rows within each matrix are ground-truth labels, columns are predicted labels, cells contain raw counts, and color encodes the row-normalized fraction.
Figure 13. MassSlide confusion matrices for Sdirect , reported separately for every agent under κlow and κhigh . Eight MassSlide confusion matrices arranged in four agent rows and two noise-level columns. Rows within each matrix are ground-truth labels, columns are predicted labels, cells contain raw counts, and color encodes the row-normalized fraction.
Contrast
Effect [95% CI]
W/T/L
Agent comparisons (low/high noise averaged)
gpt-5.5 - gemini-3.1-pro, Sdirect , episode
22.3 [10.7, 34.0]
12/0/3
gpt-5.5 - gemini-3.1-pro, Sprog , episode
15.3 [6.3, 24.3]
11/1/3
gpt-5.5 - gemini-3.1-pro, Sprog , held-out
8.7 [1.9, 15.5]
12/0/3
gpt-5.5 - claude-opus-4.6, Sdirect , episode
16.0 [6.7, 25.0]
12/0/3
gpt-5.5 - claude-opus-4.6, Sprog , episode
15.3 [6.9, 24.0]
13/1/1
Appendix
Table 23. Complete paired episode-level differences, reported in percentage points with confidence intervals obtained by exhaustive sign-flip inversion. For agent comparisons, differences are calculated within each simulator–seed pair and then averaged across the low- and high-noise conditions. For condition comparisons, differences are averaged across the three closed-weight agents; minimax-m2.7 is excluded. W/T/L (win/tie/loss) is determined from these paired differences.
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
1.000±0.000
0.840±0.089
0.960±0.055
gemini-3.1-pro
0.680±0.179
0.920±0.084
0.680±0.084
claude-opus-4.6
0.820±0.130
0.920±0.130
0.820±0.110
minimax-m2.7
0.160±0.114
0.180±0.164
0.540±0.152
Appendix
Table 24. Per- simulator results for the main experiment under κlow and submission mode Sdirect .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.820±0.239
0.860±0.089
0.880±0.084
gemini-3.1-pro
0.720±0.217
0.720±0.164
0.760±0.089
claude-opus-4.6
0.620±0.164
0.680±0.148
0.760±0.055
minimax-m2.7
0.180±0.130
0.180±0.084
0.480±0.179
Held-out Accuracy
Appendix
Table 25. Per- simulator results for the main experiment under κlow and submission mode Sprog .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.840±0.261
0.780±0.179
0.880±0.179
gemini-3.1-pro
0.440±0.230
0.500±0.324
0.740±0.114
claude-opus-4.6
0.500±0.187
0.440±0.219
0.840±0.134
minimax-m2.7
0.200±0.158
0.200±0.122
0.500±0.235
Appendix
Table 26. Per- simulator results for the main experiment under κhigh and submission mode Sdirect .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.760±0.207
0.640±0.321
0.800±0.187
gemini-3.1-pro
0.460±0.152
0.500±0.255
0.680±0.110
claude-opus-4.6
0.520±0.130
0.440±0.305
0.820±0.130
minimax-m2.7
0.340±0.167
0.200±0.071
0.520±0.249
Held-out Accuracy
Appendix
Table 27. Per- simulator results for the main experiment under κhigh and submission mode Sprog .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.900±0.122
0.820±0.148
0.940±0.134
gemini-3.1-pro
0.760±0.134
0.440±0.167
0.740±0.207
Appendix
Table 28. Per- simulator results for the ablation without labeled examples under κhigh and submission mode Sdirect .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.880±0.045
0.720±0.164
0.940±0.134
gemini-3.1-pro
0.640±0.114
0.680±0.228
0.640±0.207
Held-out Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.629±0.042
0.411±0.083
0.478±0.092
Appendix
Table 29. Per- simulator results for the ablation without labeled examples under κhigh and submission mode Sprog .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.600±0.235
0.400±0.187
0.540±0.230
gemini-3.1-pro
0.220±0.045
0.200±0.071
0.520±0.239
claude-opus-4.6
-
-
-
minimax-m2.7
-
-
-
Appendix
Table 30. Per- simulator results for the ablation without domain context under κhigh and submission mode Sdirect .
Episode Accuracy
BallDrop
BounceBall
MassSlide
gpt-5.5
0.340±0.230
0.440±0.241
0.580±0.205
gemini-3.1-pro
0.240±0.114
0.300±0.212
0.500±0.158
claude-opus-4.6
-
-
-
minimax-m2.7
-
-
-
Held-out Accuracy
Appendix
Table 31. Per- simulator results for the ablation without domain context under κhigh and submission mode Sprog .