- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper separates multi-agent computer-use workflows into a persistent VM-state lineage, called the spine, and disposable branches that return transferable artifacts. This prevents plans from requiring incompatible VM states to be merged. Experiments on Odysseys show improved success and lower API costs, while OSWorld experiments reveal settings where decomposition introduces excessive overhead.
Critical strengths
The distinction between transferable artifacts and persistent execution state is clear and practically motivated. It turns an important deployment constraint into an explicit planning rule.
The main evaluation covers 200 tasks, three worker backbones, and repeated runs. The negative OSWorld results and manager-backbone ablation provide useful evidence about the framework’s limits.
Critical weaknesses
The comparison with MACU changes state handling, artifact routing, and the amount of runtime manager involvement together. The component ablations help, but the full system improves success over spine-only by just 2.2 points on the 45-task subset. A larger paired comparison and a MACU variant with explicit state inheritance would better establish which design choices drive the gains.
The main scores depend on one LLM judge examining trajectories with up to 200 screenshots. The paper does not report a human audit of these judgments. Different coordination methods produce different amounts and distributions of evidence, so the authors should explain how final VM state and branch artifacts are presented consistently to the judge.
The reported financial savings use API-token prices and assign zero cost to the locally hosted worker. VM provisioning, cloning, local inference, and wall-clock execution are outside that comparison. These costs matter for the efficiency claim, particularly given the substantial timeout rate observed on OSWorld.
Questions for authors
How much improvement remains over a state-aware MACU baseline with direct artifact transfer?
Do blinded human judgments confirm the main success-rate differences?
What are the end-to-end latency and resource costs when local inference and VM operations are included?