Can AI Models Direct Each Other? Organizational Structure as a Probe into Training Limitations

TL;DR

This paper investigates the effectiveness and limitations of using a hierarchical multi-agent AI system, with a manager directing a worker, for software engineering tasks, highlighting the importance of organizational structure and training gaps.

Contribution

It introduces a two-agent pipeline with a manager and worker, analyzing how organizational structure impacts performance and revealing training gaps in current models.

Findings

A strong manager directing a weak worker matches a strong single agent in performance.

A weak manager directing a weak worker performs worse than a weak agent alone.

Active direction and structured exploration significantly improve task success.

Abstract

Can an expensive AI model effectively direct a cheap one to solve software engineering tasks? We study this question by introducing ManagerWorker, a two-agent pipeline where an expensive "manager" model (text-only, no code execution) analyzes issues, dispatches exploration tasks, and reviews implementations, while a cheap "worker" model (with full repo access) executes code changes. We evaluate on 200 instances from SWE-bench Lite across five configurations that vary the manager-worker relationship, pipeline complexity, and model pairing. Our findings reveal both the promise and the limits of multi-agent direction: (1) a strong manager directing a weak worker (62%) matches a strong single agent (60%) at a fraction of the strong-model token usage, showing that expensive reasoning can substitute for expensive execution; (2) a weak manager directing a weak worker (42%) performs worse than the weak agent alone (44%), demonstrating that the directing relationship requires a genuine capability gap--structure without substance is pure overhead; (3) the manager's value lies in directing, not merely reviewing--a minimal review-only loop adds just 2pp over the baseline, while structured exploration and planning add 11pp, showing that active direction is what makes the capability gap productive; and (4) these behaviors trace to a single root cause: current models are trained as monolithic agents, and splitting them into director/worker roles fights their training distribution. The pipeline succeeds by designing around this mismatch--keeping each model close to its trained mode (text generation for the manager, tool use for the worker) and externalizing organizational structure to code. This diagnosis points to concrete training gaps: delegation, scoped execution, and mode switching are skills absent from current training data.