- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces TEA, which links an Agent Interaction Graph, a Task Activity Graph, and a shared environment to record interactions, task evolution, and supporting evidence. It also introduces Infuse, which derives collaboration guidance from execution traces. The experiments include examples of structural representation and recovery, as well as performance evaluations on code refactoring and Silo-Bench.
Critical strengths
-
Linking task progress to agent interactions has practical value for understanding and debugging open-ended collaboration.
-
Persistent task identities, version histories, and evidence links provide concrete mechanisms for inspecting past tasks and tracing how work was carried out.
Critical weaknesses
-
The motivation and distinct technical contribution of TAG are not clearly established. Section 1 lacks clear criteria for "emergent collaboration" and does not adequately distinguish dynamic behavior at runtime from the emergence of new coordination patterns. AgentOrchestra's TEA protocol [1] already addresses unified resource organization, while TalkHier [2] studies structured communication and hierarchical refinement. The paper therefore needs to clarify what TAG uniquely enables. Section 3 defines task versions and associated operations without sufficiently explaining why they are needed. Topology recovery in §4.1 relies primarily on AIG and does not establish a key role for TAG. As the paper moves from representation and recovery to policy improvement, the central insight and the connections between these contributions remain unclear.
-
The experiments do not directly validate the main contributions. Section 6.1 demonstrates representation, recovery, and traceability, but does not clearly show what TAG adds to identifying or explaining emergent collaboration. In §6.2.1, removing TAG also removes task tools, evidence access, and task observations, so the ablation cannot distinguish the benefits of the graph structure from those of shared task information. The performance gains in §6.2.2 likewise do not establish a link between TAG analysis and effective policy changes. The experiments therefore provide insufficient evidence for the importance of the paper's central design choices.
[1] Zhang, W., et al. (2025). AgentOrchestra: Orchestrating Hierarchical Multi-Agent Intelligence with the Tool-Environment-Agent (TEA) Protocol. arXiv:2506.12508v4.
[2] Wang, Z., Moriyama, S., Wang, W.-Y., Gangopadhyay, B., & Takamatsu, S. (2025). Talk Structurally, Act Hierarchically: A Collaborative Framework for LLM Multi-Agent Systems. arXiv:2502.11098.
Questions for authors
-
What criteria define "emergent collaboration", and how do the experiments test whether these criteria are met?
-
Which existing result best demonstrates TAG's distinct value, and how can the benefits of its structure be separated from those of shared task information?
4 comments
Response (Part 2 of 2)
W1: What does TAG add beyond AIG?
We see TEA as a starting point for studying agent collaboration, with further potential to explore. The recovery and relationship analysis in Section 4, together with Infuse in Section 5, illustrate one concrete way to use TEA to understand and improve collaboration.
Topology recovery and candidate rule inference indeed rely primarily on AIG. However, the power of TEA lies in linking AIG, TAG, and the environment to make the collaboration process interpretable and tie it to task success. We have clarified the roles of AIG and TAG in Section 4 (changes in blue). The new experiments below also provide empirical evidence for the value of this structure in collaboration and policy refinement.
W2/Q2: Separating TAG’s structure from shared information
To isolate TAG’s structural contribution, we compare TEA (TAG + communication) with Structural ablation, which hides TAG edges from agents and Infuse. In addition, we compare TEA with Blackboard, which replaces TAG with a shared read/write workspace. The new Section 6.3 and Tables 8-9 report five runs on shop and all 30 Silo-Bench tasks.
TEA with Infuse achieves the strongest overall results. After Infuse, it leads both LoC reduction metrics on shop and all three Silo-Bench metrics.
TAG’s structure makes compact collaboration history useful. In Raw runs, TEA’s TAG record is about one fifth Blackboard’s size at step 100 on shop (5.2k versus 25.2k characters) and less than half its average size on Silo-Bench (2.6k versus 6.3k). TEA and Structural ablation maintain similarly sized records, yet TEA achieves higher performance in all cases, suggesting that explicit task relationships make compact context useful for understanding collaboration.
Long, unfiltered history may make collaboration harder to improve. Blackboard interestingly achieves the highest Raw code reductions, but both reduction metrics decline after Infuse. However, on Silo-Bench, it matches TEA’s Raw success and benefits from Infuse. Blackboard’s record size turns out to be much smaller on Silo-Bench than on shop (6.3k versus 25k characters). Longer, unfiltered histories may make it harder for Infuse to interpret collaborative behavior.
TEA keeps history compact, and its explicit task relationships help agents and Infuse use that history to understand and improve collaboration.
We are happy to provide further clarification and discussion, and we hope you will consider raising your score if your concerns have been addressed.
Thank you for the detailed response and additional experiments. The clarifications and new ablation studies help address my main concerns, particularly regarding TAG's structural contribution beyond shared task information. I recommend that the authors further clarify the connection between TAG structure, emergent collaboration analysis, and policy improvement in the revised paper. I am then willing to raise my score from 2 to 3.
Thank you for recognizing our work and for your positive feedback. We are glad that the additional experiments helped address your main concerns. We have further revised Sections 4.2 and 5 of the manuscript (changes in orange) to make our contributions to analyzing and improving emergent collaboration more explicit. We appreciate your constructive suggestions!
Response (Part 1 of 2)
We thank the reviewer for recognizing the value of linking task progress to agent interactions and for the suggestions on TAG’s structural contribution. Below, we clarify the setting and present new experiments separating the structural effect from TAG.
W1/Q1: Emergent collaboration
LLM agents can collaborate under different degrees of policy specification. For example, a workflow could prescribe how agents work together, specifying their roles and interaction order. An orchestrator-subagent system may prescribe delegation relationships while letting the orchestrator decide what to delegate. More explicit specifications often require greater domain knowledge and design effort and can limit flexibility across tasks. We use emergent collaboration to describe work organization and coordination arising from agents’ decisions where the initial collaboration policy leaves them unspecified, such as how to divide work, whom to ask for help, when to share intermediate results. Section 3.1 now clarifies these settings (changes in blue).
We view emergent collaboration as a potentially more powerful setting. We believe it is often overlooked partly because it is difficult to study: there is no explicit collaboration procedure to vary and optimize. Our question is: how can we understand collaboration from agents’ actual interactions? TEA represents collaboration under any degree of policy specification. Section 5 explains how agents use TEA’s collaboration interface to organize collaboration themselves.
W1: Prior work (AgentOrchestra, TalkHier)
Both works give agents a collaboration structure to work within.
AgentOrchestra’s Tool-Environment-Agent protocol provides a standard way to use tools, access environments, and invoke agents. Its protocol could complement our Task-Environment-Agents (TEA) by supporting tool calls during AIG activations, where these calls and their results are recorded. AgentOrchestra builds on this protocol with a central planner that divides tasks and delegates work to specialized subagents. Our TEA is a representation framework for understanding collaborative behavior: which agent acted and when (AIG), what it did in the environment (Z), and why, using task goals and progress as context (TAG). Linking these layers makes emergent collaboration analyzable.
TalkHier uses an explicit collaboration structure to improve task outputs. It defines a graph with roles for generating, evaluating, and revising outputs, coordinated by supervisors. Our TEA enables analysis of agents’ collaboration without requiring a structure to be known in advance, while Infuse offers a mechanism for improving collaboration structure towards more effective task completion.