- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper addresses asynchronous reasoning/tool-calling problem in full-duplex interaction scenarios. They build MoshiAgent and ToolRaceBench for the target task.
Critical strengths
This manuscript addresses realistic and speech-oriented constraints where users may easily change their intents while background tool calling starts with outdated information.
Critical weaknesses
I consider the writing incomplete in its current form for the following reasons:
-
Figure 1 is not referenced in the text.
-
Figure 2 is not fully explained in the main text. The manuscript discusses only the streaming speaker, leaving the other components unexplained. All terms and components shown in the figure should be described in the main text, with clear connections to the figure.
-
Confusing terms are being used, such as "semantic" in sec 3.2, and they did not mention about its deterministic rules and actual models. Basic formulations, like dialogue states, are not explained how it looks like.
-
Although ToolRaceBench is an important contribution of the manuscript, all details are sent to the appendix. Essential information should be included in the main text to make the manuscript self-contained.
Overall, I suggest significantly revising the writing by removing redundant components and clearly highlighting contributions.
Questions for authors
N/A
Response to Reviewer XNJJ
We thank the reviewer for the specific comments on the presentation.
W1. Fig. 1 is not referenced
Thank you for catching this. Sec. 1 described the alarm example of Fig. 1 but did not cite the figure. It now cites Fig. 1(a) for the failure case and Fig. 1(b) for our handling.
W2. Fig. 2 is not fully explained
We agree. Sec. 3.1 previously described only the Streaming Speaker and the grounding interface as a whole. A new paragraph in Sec. 3.1 ("System Components") follows the layout of the figure and explains every labeled component and arrow. It covers speech (Streaming Speaker, Request, Respond), reasoning (Reasoning Coordinator, Fast Reasoner, Deliberative Explorer, Launch, Exploration Goal, State), and execution (Action, the "Side-effecting action?" branch, Tool Executor, Write Control, User Confirmation, Results, Findings, Evidence Admission, Authoritative Session State).
W3. The term "semantic", the deterministic rules, and the models
Sec. 3.2 stated that deterministic rules handle unambiguous acceptance and rejection and that a semantic classifier handles modifications and mixed intent, but it did not explain "semantic", give an example of the rules, or name the classifier. It now adds all three. Supersession is semantic because it depends on what the new speech means for the pending work, not only on the revision counter. For example, a backchannel ("mm-hmm") advances the revision but leaves earlier work valid, whereas "actually, make it 10" supersedes it. The rules decide clear consent or refusal (e.g., a bare "yes" or "no"). The classifier is the reasoning backend itself (Gemma-4-31B-it by default). It is invoked only for speech with a modification cue or mixed affirmative and negative words, and all other speech (e.g., a question) is
unclear. Appendix A.2 gives the decision table and pseudocode.W4. The dialogue state is not explained
We agree that a concrete description was missing. Sec. 3.2 introduced the dialogue state only as the user-side transcript with a revision counter. Sec. 3.1 now describes all three parts of St=(Dt,At,Wt). Dt is the user transcript with the revision counter r, At records each proposal, authorization, and tool invocation with its status and outcome, and Wt holds the observations and verified effects returned by tools. For example, in Fig. 3(a), "Actually, make it 10 a.m." advances r and marks
set_alarm(9)as superseded in At, while Wt still records 8 a.m. Appendix A.1 gives the full schema.W5. ToolRaceBench details are only in the appendix
Sec. 5.1 described the construction, the scenario format, and what is evaluated, but not the size, categories, pass criterion, or scoring. It now reports the size (298 scenarios), the number of primary categories (nine, distributed as in Table 20 of Appendix E), the pass criterion, and the scoring.
W6. Redundancy and contributions
We removed a repeated set of result numbers from the introduction and several sentences in Sec. 5 that only restated table values. The first contribution now names what is new, namely the authoritative session state, proposal-relative semantic supersession, and the properties P1 to P4 with the runtime procedure that enforces them.
We hope the revision addresses the reviewer's concerns about the presentation. Since the missing details may also have made the method hard to assess, we note that Appendix A now gives the runtime specification. We would be glad to address any remaining concern about soundness and would appreciate it if the reviewer could take another look at the revised version.