- Rating
- 3
- Confidence
- 2
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper presents ClueFlow, a training framework for long-horizon search agents. Instead of treating every turn equally, it keeps evidence and candidate records, then after each trajectory it checks which state changes really support the answer and traces them back to the browser actions that provided the evidence. These Source–State–Final chains decide which turns are trained in their original context and how Turn-PPO assigns credit; validated partial progress from wrong final answers is also reused. With Qwen3.5-35B-A3B, ClueFlow reaches 59.1% on BrowseComp and 72.0% on BrowseComp-Plus.
Critical strengths
-
The core idea is easy to buy: instead of treating every turn equally, the method asks which state changes actually moved the research forward and which browser actions supplied the evidence.
-
ClueFlow gives a concrete learning signal for both SFT and PPO, and the failure-recovery angle is particularly practical because long search trajectories often contain useful intermediate work even when the final answer is wrong.
-
The appendices are very detailed, and the qualitative traces help the reader clearly see what an attribution chain actually looks like.
Critical weaknesses
-
The source-tracing step is heuristic, yet we do not see its precision and recall or how often valid evidence transitions are dropped because no reliable browser source is found. This matters because a wrong source link or a wrong validation label directly changes which turns get supervised or credited.
-
The comparisons also have several confounds: different teacher trajectories, different checkpoints for fixed-corpus and live-web settings, different context management, etc. The controlled ablations are better, but they do not fully isolate attribution from serialization format and data volume.
-
The PPO attribution budget hypeparameters are hand-tuned and there is no analysis or comparison with other turn-level credit-assignment methods.
Questions for authors
-
As mentioned in weakness-1, what is the precision and recall of deterministic source tracing, and what fraction of validated Evidence transitions are dropped for lack of a reliable source?
-
How much of the gain comes from the persistent state itself versus the clue tools, readiness rules, and prompting?
-
Can failure recovery reinforce evidence that is correct but followed by a wrong conclusion? More qualitative cases would help.
2 comments
We sincerely thank the reviewer for taking the time to revisit our responses and additional experiments. We are glad that these additions have addressed your main concerns and strengthened the paper. We greatly appreciate your constructive feedback throughout the review process.
Thank you for the detailed response and additional experiments. They address my main concerns and strengthen the paper. I think I will maintain my rating.