- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper proposes DC-Flow, a target-conditioned cyclic peptide design framework based on delayed-coupling flow matching. The method first generates a receptor-conditioned backbone and progressively activates sequence and side-chain generation while allowing the backbone and sequence to continuously co-adapt. It further incorporates a frozen ProteinMPNN as a structural sequence prior and introduces cascaded test-time scaling to improve candidate exploration and allocate computational resources to promising designs.
Critical strengths
- The proposed delayed-coupling strategy is intuitive. Delaying sequence and side-chain generation until the backbone has developed, while still allowing the modalities to co-evolve afterward, is a reasonable approach to cyclic peptide design.
- The paper is generally well written and organized, with clear explanations and high-quality figures that help illustrate the motivation and overall framework.
Critical weaknesses
- The performance gains of DC-Flow on the cofolding benchmark appear to depend heavily on predictor guidance. Without generation-time guidance, DC-Flow achieves the lowest strict-hit rate among the compared methods after AfCycDesign optimization (24.2%, compared with 33.3% for HFGuidedDesign and 29.2% for RFPeptides). Its advantage only emerges when guidance is enabled, raising concerns about how much of the improvement can actually be attributed to the proposed delayed-coupling mechanism. Moreover, since generation-time guidance and final evaluation rely on the same AlphaFold-Multimer model family, it is difficult to rule out predictor-specific optimization or reward hacking. Although HFGuidedDesign provides a relevant guided baseline, the comparisons remain limited, and it is unclear whether the methods use comparable computational budgets. The authors should demonstrate that DC-Flow outperforms existing approaches under matched structure-predictor inference budgets and provide stronger evidence isolating the contribution of delayed coupling.
- DC-Flow involves substantial computational overhead, requiring repeated structure-predictor evaluations during generation-time guidance, followed by expensive AfCycDesign optimization and potentially additional cascaded search. However, the paper does not provide a comprehensive comparison of inference costs, such as the number of predictor calls, GPU-hours, or wall-clock time. Another major concern is that the final evaluation still relies on AlphaFold-Multimer, the same model family used for guidance and optimization. Evaluating the generated candidates with an independent predictor, such as AlphaFold 3, would provide more convincing evidence that the improvements generalize beyond the optimization oracle. Additionally, the motivation for generating the backbone before the sequence is not fully convincing. The authors should further justify this design choice and investigate alternatives, such as generating the sequence first and then refining the backbone, to establish whether the proposed generation order is indeed preferable.
Questions for authors
- Could the authors report the number of structure-predictor evaluations, optimization steps, and total inference costs (e.g., GPU-hours) for DC-Flow and the baselines? Although HFGuidedDesign also uses predictor guidance, it is unclear whether the methods receive comparable amounts of guidance and optimization compute.
- Since generation-time guidance, post-generation optimization, and final evaluation all rely on the AlphaFold-Multimer model family, could the authors evaluate the generated candidates using an independent structure predictor, such as AlphaFold 3 or another suitable model?