- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces chunk level coordination for multi-agent LLM reasoning. While one agent generates a reasoning chunk, other agents provide probability-based assessments. A trained MLP gate decides whether to invoke an arbitrator, which can retain the speaker or discard the chunk and transfer control. RhyCo-Base uses a prompted arbitrator; RhyCo-RL additionally trains it with GRPO. Experiments on six math, code, and multi-hop QA benchmarks report improved trade offs between accuracy and cost.
Critical strengths
--- Meaningful coordination problem. Separating routine monitoring from selective arbitration is a reasonable way to regulate intervention while keeping the reasoning backbones fixed.
--- Useful empirical coverage. The evaluation involved six benchmarks and includes adaptive methods such as AFlow and MaAS. The ablations and trajectory examples provide useful evidence about the risks of excessive intervention.
Critical weaknesses
--- The contribution appears incremental, and its distinctive value is insufficiently isolated. Learned coordination has precedents in Puppeteer and ECON, while intermediate checking and rollback are explored in GA-Rollback; Meta-R1 also studies selective monitoring during generation. RhyCo’s contribution appears to lie primarily in combining listener signals, learned gating, arbitration, and speaker handoff. However, the “w/o metrics” ablation also removes the gate and invokes the arbitrator at every chunk. Its degradation therefore does not establish the specific benefit of listener-driven timing over simpler selective intervention.
--- The benefit attributed to training is confounded with additional computation. RhyCo-RL receives three times the chunk budget of RhyCo-Base, while their performance difference is attributed to GRPO. Figure 3 provides useful cost comparisons but does not isolate the training effect at matched budgets. Moreover, Appendix A.1 excludes listener prefill from the training cost penalty, and whether Figure 3 fully accounts for this monitoring overhead is unclear.
Questions for authors
--- What is the specific advance over learned orchestration and online intervention methods, including HANDRAISER? I think the setting is very simlart with Rhyco. Can its benefit be isolated against a simpler controller with comparable intervention frequency and inference cost?
--- How much of the RL improvement remains when both policies use identical chunk budgets?
--- Does Figure 3 include all listener prefill, discarded chunks, whisper generation, and arbitrator computation? Does the reported efficiency advantage persist under this complete accounting?
5 comments
Response to Reviewer jufL (2/2)
Q1: Beat a simpler controller at matched frequency and cost?
Simpler controllers (Q1). We compare RhyCo with three simpler controllers: the gate-free arbitrator above, which decides at every chunk and is compared with RhyCo-Base; a random-timing control, which keeps the number of escalations that RhyCo-RL's learned gate makes on each problem but places them at random chunks; and Table 2's rule gate, which replaces RhyCo-Base's learned gate with hand-crafted rules over the same rhythm state. All three fall clearly below the corresponding learned gate, the first two at a comparable number of interventions, so RhyCo's advantage comes from the gate's choice of when to intervene.
On MATH-L5, the gate-free arbitrator interrupts about 1.8 times per query at 4B and 8B, close to RhyCo-Base's roughly 1.6, but on the same 100 problems it reaches only 60% and 64% against 69% for RhyCo-Base with a 1.7B arbitrator, and it costs more because it consults the arbitrator at every chunk. The random-timing control, with the arbitrator still receiving the listener metrics and whispers, lowers RhyCo-RL's accuracy from 74.1% to 68.1%; because the trained arbitrator can still keep the current speaker on an unneeded escalation, this 6.0-point gap is a conservative estimate of what learned timing adds at the same cost. The rule gate falls 5.8 to 8.9 points below RhyCo-Base across MATH-L5, BigCodeBench and HotpotQA. In every comparison the learned gate leads by 5 to 9 points, which is the benefit of listener-driven timing that the reviewer asked us to isolate.
3: RL at matched budgets (W2, Q2)
W2, Q2: RL gain at identical chunk budgets?
Matched budgets. We run the control in both directions: RhyCo-Base with RL's 90-chunk budget, and RhyCo-RL trained and evaluated with Base's 30 chunks. Gains are relative to RhyCo-Base at 30 chunks:
| Config | Budget | MATH-L5 (%) | HotpotQA (EM, %) |
|---|---|---|---|
| RhyCo-Base | 30 | 66.87 | 62.00 |
| RhyCo-Base | 90 | 68.52 (+1.65) | 62.00 (+0.00) |
| RhyCo-RL | 30 | 67.28 (+0.41) | 62.60 (+0.60) |
| RhyCo-RL | 90 | 74.07 (+7.20) | 64.00 (+2.00) |
Most of the RL improvement remains under matched inference budgets. On MATH-L5, 5.6 of the original 7.2 points (78%) remain when RhyCo-Base and RhyCo-RL are both evaluated with 90 chunks; on HotpotQA, the matched-budget gain is 2.0 points. At the tighter 30-chunk budget, the corresponding gains are 0.4 and 0.6 points, respectively. The smaller gains at 30 chunks reflect the limited room for the trained arbitrator to act before trajectories reach the budget: it often continues checking an answer, after which truncated trajectories fall back to an answer aggregated from the committed history. RhyCo-Base itself benefits little from increasing the budget from 30 to 90 chunks on MATH-L5, only 8 of 486 problems change, all of which were truncated at 30 chunks, yielding a 1.6-point gain; on HotpotQA, no trajectory reaches 30 chunks, so accuracy is unchanged.
4: Cost accounting (W2, Q3)
W2, Q3: A.1 excludes prefill; is all monitoring cost in Figure 3?
We thank the reviewer for this question. Figure 3 already includes all listener prefill, discarded speaker chunks, whisper generation, and arbitrator computation in the reported inference cost. Appendix A.1 describes a different quantity, the token-cost term of the GRPO training reward, which excludes listener prefill and affects only RL training; we will state this distinction explicitly in the revision.
Complete inference accounting. Figure 3(left) counts output tokens only, as labeled, and Figure 3(right) converts output and input tokens into output-token equivalents at 1:8. The table itemizes the per-query cost behind Figure 3(right) on MATH-L5; speaker decoding includes chunks later discarded by a switch.
| MATH-L5, per query | RhyCo-Base | RhyCo-RL |
|---|---|---|
| Speaker decoding | 840 out | 1,985 out |
| Whisper decoding | 96 out | 274 out |
| Arbitrator output | 240 out | 1,100 out |
| Listener prefill (3 × 64 per chunk) | 2,520 in | 5,955 in |
| Arbitrator input | 1,176 in | 3,359 in |
| History at handoff | 1,252 in | 3,610 in |
| Initial prompts | 5,100 in | 5,100 in |
| Total | 1,176 out / 10,048 in → 2,432 | 3,359 out / 18,024 in → 5,612 |
Efficiency under complete accounting. At every input/output price ratio from 1:4 to 1:100, RhyCo-Base costs less than every multi-agent baseline; at the 1:8 ratio of Figure 3, it uses 2,432 output-token units against 5,221 to 9,490 for AFlow, SC, MaAS and MAD. RhyCo-RL, the most accurate method at 74.1%, uses 5,612 units at 1:8, below SC, MaAS and MAD. The efficiency advantage therefore persists under complete accounting, and the revision will make the training-vs.-inference distinction explicit and add the component breakdown and price-ratio sensitivity.
We hope these analyses address the reviewer's concerns, and we would be glad to clarify any remaining questions.
Thank you for the detailed rebuttal and additional experiments. The token breakdown and gate-timing ablations address my questions regarding cost accounting and the role of the MLP gate. For me, the main takeaway from the paper is that separating continuous listener assessment from selective judgement can turn multi agent feedback into better reasoning.
However, I am still unsure whether they establish a sufficiently substantial contribution beyond existing learned methods such as HANDRAISER. In addition, under the original 30 chunk budget, RhyCo-RL yields only marginal gains over RhyCo-Base (+0.41% on MATH-L5 and +0.60% on HotpotQA), which means that the RL improvement relies largely on the expanded 90 chunk horizon rather than a clear gain in coordination efficiency at tight budget.
Although likely beyond the scope of this rebuttal, establishing a broader contribution would require a study across tasks that systematically varies listener count and disagreement, comparing trained centralized and decentralized controllers under matched budgets to show when and why central judge helps.
Response to Reviewer jufL (1/2)
We thank Reviewer jufL for a constructive review, whose questions on HANDRAISER, simpler controllers, and matched budgets led us to add direct comparisons. We answer in four parts.
We appreciate why the reviewer sees connections between RhyCo and the cited works. Recent work has made substantial progress in adaptive orchestration, online monitoring, interruption, recovery, and efficient coordination, opening a broader question: can multi-agent systems communicate with the flexibility of a human team? Human coordination is not rigid turn-taking: people listen while others speak, usually remain silent, intervene when useful, and flexibly hand control to whoever is best positioned to contribute. Our goal is the same adaptive freedom with bounded coordination cost. We call this balance communication rhythm.
The cited works also reveal why this broader communication problem requires joint system design. Puppeteer places dynamic agent selection in a centralized orchestrator, while HANDRAISER gives listeners learned control over when to interrupt; Meta-R1 introduces explicit online meta-level regulation, whereas ECON reduces costly direct exchanges through belief-driven coordination; and GA-Rollback responds to detected errors by rewinding the trajectory. These are effective choices in their respective settings, but they give different answers to three coupled questions: where control resides, how information is exposed during reasoning, and what happens once intervention is triggered. Once these choices operate within the same communication process, changing one also changes the state, cost, and decision context faced by the others. The problem is therefore one of joint system design: these coupled choices must be resolved under a common quality–cost objective.
RhyCo addresses these coupled choices through a system-level design of communication rhythm that jointly structures information flow, intervention timing, and floor control. Listeners can raise concerns and recommend intervention, but they cannot directly take over the reasoning floor; the system decides whether a handoff is needed and which specialist should take over.
Our ablations already show that each part of RhyCo matters, since rule-based gating, removing whispers, or an untrained arbitrator all lower performance. We test each cited mechanism that maps onto a RhyCo decision inside RhyCo. Puppeteer's centralized selection maps onto an every-chunk controller, which performs poorly: Table 2's Unrestricted Intervention averages 19.2 against 61.3 for RhyCo-Base, and the gate-free arbitrator below collapses at small sizes. ECON, GA-Rollback and Meta-R1 act on other decisions, described above, with no direct counterpart in RhyCo.
HANDRAISER and RhyCo share the premise that intervention timing should be learned from rollout outcomes; they differ in who decides. In HANDRAISER, a listener decides on its own to cut off a message in conversation, and in its main experiments only one agent per task may interrupt. In RhyCo, several listeners monitor one reasoning chain and may want to take the floor at once.
To test whether a central decision matters, we remove the gate and arbitrator and let each listener, prompted after every chunk, interrupt and take the floor on its own. It collapses to 17.9% on MATH-L5 because nearly every listener finds a problem and interrupts, as HANDRAISER also found for untrained listeners; Table 2's Unrestricted Intervention, which also intervenes at every chunk but centrally, reaches 31.1%, so central control does less damage. A trigger trained on rollout payoffs would instead fall silent, since competing interruptions mostly lower the payoff, reducing it to the single-agent baseline: 60.9% against 66.9% for RhyCo-Base. Decentralized listeners thus either interrupt too often or fall silent; RhyCo avoids both by separating reporting from deciding.
Gate vs. metrics (W1). Removing only the gate, a prompted arbitrator reads the metrics but decides at every chunk:
On BigCodeBench, the metrics carry the gate-free arbitrator, which beats SC by 8–10 points from 1.7B up, whereas the same 1.7B arbitrator without the metrics switches constantly and scores 0.0% (Table 2, 570 problems). On MATH-L5, the metrics overwhelm the 1.7B arbitrator, which interrupts 8 or more times per query and falls to 20%; only the 8B arbitrator regulates itself, at 64%. The gate is what lets a small arbitrator interrupt with discipline.