- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
RE-Designer builds a communication graph while agents are running, rather than fixing the whole graph beforehand. It selects agent roles, chooses which previous messages to pass on, and decides when to stop. Training combines supervised examples with RL and a semantic-similarity-based feedback signal. Experiments cover six reasoning and code-generation benchmarks.
Critical strengths
-
The main idea is practically useful. Letting actual intermediate outputs influence later communication is more flexible than deciding every connection before seeing any results. The method also considers when to stop, rather than only which edges to add.
-
The message-conditioning ablation directly tests the central idea. Starting from the same checkpoint, the authors compare policies with and without access to runtime messages. The additional improvement supports the claim that these messages help the controller make better decisions.
Critical weaknesses
-
The distinction from the closest related method is not fully established. Section 2 describes AnyMAC as selecting the next agent and relevant previous outputs during execution, but it is absent from the main comparison. It remains unclear how much additional capability or benefit comes from explicitly representing this process as graph generation.
-
The information-based feedback has a weak justification. I understand that it is only inspired by the information bottleneck. Still, similarity to the final answer does not necessarily mean that a message helped produce that answer, and similarity to the question does not necessarily mean redundancy. The ablation supports its usefulness, but not the claimed interpretation of what it measures.
Questions for authors
-
What does the explicit graph representation add beyond AnyMAC’s next-agent and context selection? Is there a comparison using the same backbone and a comparable token budget?
-
Do messages receiving higher information weights actually contribute more to final correctness? For example, does removing them hurt performance more than removing low-weight messages?