Effective Strategies for Asynchronous Software Engineering Agents
- Published
- Source
- arXiv
- Paper number
- 130
- Field
- Code Agents
- arXiv ID
- 2603.21489
Key points
- The core method is this: a manager builds a task dependency graph, delegates only qualified nodes, and updates the state when engineer agents complete sub-tasks.
- The execution model is this: engineers edit in isolated git worktrees, run local tests before committing, and return changes through a structured branch-and-merge pipeline.
- Empirically, CAID improves PaperBench by 26.7 percentage points and Commit0-Lite by 14.3 percentage points over the single-agent baseline, suggesting gains in both accuracy and long-horizon coordination.
- A key takeaway is that parallelism has an optimum. Two to four engineers help, but with eight engineers results can worsen as merge conflicts, dependency waits, and verification overhead outweigh the added headcount.
Paper links
External research summaries. These are not HDATF publications or measured product results.