- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper proposes ComAct, which lets computer-use agents act on an action space defined by the Component Object Model. It also introduces ComCADBench, which tests agents' task performance on mainstream CAD applications. Agents with ComAct showcase significantly better performance compared to agents with GUI interaction. It also proposes to train agents on COM with a 3-stage framework, which improves a 9B model's ability to act within the ComAct framework by a large margin, achieving better performance than frontier models.
Critical strengths
The potential of this proposed paradigm shift is huge (only from my point of view, but I am not very familiar with the current status and needs of CUAs). I see that COM is a better choice compared to GUI, especially in applications that are complex, require long-term interactions and need expertise. COM also seems to be better choice than API as it is more widely accepted in multiple software families. So I find the paper's motivation convincing.
The paper also proposes a three-stage training framework and trains a 9B model by optimizing (1) COM code generation, (2) code revision, and (3) task completion. The results demonstrate the potential of COMAct for training capable smaller-scale agents.
This paper is also well written and very easy to follow.
Critical weaknesses
I am not familiar with the field, but here are some concerns I think should be clarified.
First, I don't know how widely COM is used. For example, in WindowsAgentArena, I see that there are tasks that are not COM-compatible (the authors used only the "COM-compatible subsets").
Second, results are mainly focused on CAD tasks, with limited evaluation on other domains and applications that COM also applies to, as claimed in the paper. Moreover, the trained 9B model is not evaluated on WindowsAgentArena. Does the learned COM code generation ability transfer to other domains?
I also suggest including the backbone model name in Table 2, with a note that it is trained. The label "Ours" alone is confusing to readers.
Questions for authors
Since the authors reports strong performance on multi-task workflows, how does the success rate change as a function of the number of sequential operations / subtasks?
Also, please address my questions in the weaknesses section if you'd like to.
Dear Reviewer 3ZPa,
Thank you for your encouraging feedback and for recognizing our convincing motivation and paradigm potential. Below are our point-by-point responses.
Response to W1: Coverage of COM across software
COM is widely used in professional software. In WindowsAgentArena, the COM-incompatible applications are general-purpose browsers and lightweight utilities (e.g., Clock and Calculator), whereas most heavy professional applications support COM for cross-application communication and data exchange. For instance, in ScreenSpot-Pro (Li et al., 2025b), a visual grounding benchmark for professional software, all 16 covered professional applications support COM. We also list 34 COM-compatible professional applications across 6 domains in Appendix E.8 (Table 22).
Response to W2: Beyond-CAD evaluation & Cross-domain transfer
We focus on industrial CAD because it combines 3D spatial reasoning, strict numerical precision, and dependent multi-step workflows, making it a demanding testbed for COM. Beyond CAD, Table 3 already evaluates ComAct across three additional categories (OS Shell, MS Office, and Adobe Suite) on WindowsAgentArena (Bonatti et al., 2024) and ProSoftArena (Ai et al., 2026), showing consistent zero-shot gains over GUI for both frontier and open-source models.
We further evaluated our trained 9B agent on WindowsAgentArena (Table R1). It shows limited transfer to non-CAD tasks, which is expected given our small, CAD-only post-training dataset. While COM unifies how applications are invoked, each application still defines its own objects and methods (e.g., sketches and features in CAD vs. workbooks and cells in Excel), making cross-domain transfer challenging. Still, this 9B result does not reflect the ceiling of COM code generation. We expect larger models trained on broader, high-quality COM data to generalize across domains, and our CAD COM dataset contributes toward that goal.
Table R1. ComAct task success rate (%) on WindowsAgentArena.
Response to W3: Table 2 label suggestion
Thank you for the suggestion. We have updated "Ours" in Table 2 to "Ours (Qwen3.5-9B, trained)" to specify the backbone model and its trained status.
Response to Q1: Success rate vs. number of sequential operations
We grouped tasks by the number of required sequential operations and plotted each model's full-workflow success rate across groups in Appendix E.10 (Figure 11). As the number of operations increases, overall success rate declines for all models, while our trained ComAct agent outperforms all baselines by a large margin on the longest workflows.
Thank you again for your helpful feedback, which has strengthened our paper. We hope our responses address your concerns, and we would greatly appreciate your consideration in updating your score.
Best regards, The Authors