Agent Run Trajectories

How trajectories fit the loop

People steer the run while agents execute. Most interaction happens through prompts. XOR captures each run as a verifiable trajectory, then keeps the loop running until reviews are clean.

What trajectories capture

A trajectory is a timestamped record of every action an agent took during a run. It logs which agent ran, what tools it called, what files it changed, what tests it ran, and what the results were. Each action is cryptographically signed so it cannot be altered. The trajectory is immutable proof of what the agent did.

Why behavioral clustering matters

Different agents approach the same vulnerability differently. Some agents write minimal fixes. Others add safety checks. Some explore the codebase before fixing. Others fix immediately and test. By analyzing thousands of trajectories, XOR identifies patterns: which agents are methodical vs aggressive, which ones double-check their work, which ones get stuck in loops. This helps teams understand agent behavior and predict which agent will work best for their codebase and risk tolerance.

Trace fields that matter

• Agent identity, tool calls, and outputs per step
• File operations tied to patch evidence
• Reasoning entries (optional, privacy-gated)
• Verification outcomes tied to CVE identifiers

Where trajectories show up in XOR

Trajectories are attached to PR test reports and verification runs, so every fix is traceable and replayable. Teams can replay a trajectory to understand why an agent made a decision or to audit the fix for compliance. Security teams can use trajectory patterns to detect suspicious agent behavior or drift from expected approaches.