- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces TraceBridge, an interaction-aware system for reusing coding-agent training trajectories across different agent frameworks. It translates supported operations into compatible target tool calls using tool contracts and recorded evidence, while preserving unmappable interactions as context excluded from direct training loss, retaining information needed for subsequent actions. Using the same 10,000 trajectories to fine-tune Qwen3-8B, TraceBridge outperforms direct source-trajectory training and Agent Data Protocol across OpenHands and SWE-agent on SWE-bench Verified, Pro, and Multilingual. Behavioral analysis further shows fewer rejected calls, failed edits, and empty patches, demonstrating how adapting actions while preserving interaction context can improve the training value of existing agent experience.
Critical strengths
- The result is better than ADP, which is another traj translation method.
Critical weaknesses
-
It's quite confusing how to deal with think/content; it seems that section 4.3 didn't deal with that. However, the thinking pattern in the traj is important for training. Also, how to deal with the tool name in think? For example, the model considers which parameter should be added in the tool call in think, and it is highly related to the tool format.
-
Such a method seems to work only when the data volume is small. The effectiveness of traj (sampled from different harnesses ) on different harnesses is orthogonal. (The generalization can only be from SWE-Agent to Openhands; other pairs are weak, as shown in Qwen3-Coder-Next Technical Report and later unpublished research). So it's more like having more SWE-Agent data. If we just scale up more SWE-Agent data, it can be better than this method. (And the open-source community already has.)
-
It will train some bad patterns (mismatches) in the model, which may harm the RL process later.
I think this is just a compromise method when the data is really lacking, but this is not real in SWE.
Questions for authors
- How to deal with the thinking part?