developer tools
The Training Trace Had to Match the Harness That Made It
CoTrace routed verified terminal-agent trajectories by runtime provenance instead of pooling every successful replay.
Summary
CoTrace routed verified terminal-agent trajectories by runtime provenance instead of pooling every successful replay.
Terminal agents learn inside a harness that formats prompts, binds tools and recovers from errors, making a trajectory's value conditional on the runtime that produced it. CoTrace alternates harness search and policy training while matching supervised rollouts to the adopted harness and using fresh interactions for reinforcement learning. On the Tmax promotion split, the authors report Qwen3.5-9B advancing from 78 to 88 solved tasks under supervised fine-tuning and to 90 with online reinforcement learning. A compact harness-matched corpus outperformed much larger pools from sibling harnesses, and out-of-distribution tests showed failures when training and evaluation scaffolds diverged. The result treats harness provenance as training data, not incidental metadata.
Why it matters
CoTrace routed verified terminal-agent trajectories by runtime provenance instead of pooling every successful replay.
Limits and context
- The result treats harness provenance as training data, not incidental metadata.
Key claims
CoTrace routed verified terminal-agent trajectories by runtime provenance instead of pooling every successful replay.
Qualification: The result treats harness provenance as training data, not incidental metadata.
Evidence: source-2026-10-08-015
Sources
- arXiv preprint 2610.10426arXiv · primary research
Corrections
No corrections have been recorded for this story.