When a task is too large for one agent, we split it: one agent per module of a program, per component of a design, per group of robots. Each part becomes easier, and the parts can be searched in parallel. But the parts are coupled. A module can pass its own tests while breaking another module’s interface; a robot can take a shortcut that collides with another agent’s robot. Can a team of agents that only improves its own parts still be guaranteed to make global progress?
Local Work, Global Progress answers this with a convergence theory for agent teams. The model is block optimization, the agents can be LLMs, and the guarantee depends on constants that we measure on real runs.
Blocks, local objectives and corrections
The team improves a shared solution , and agent owns block . An exact verifier returns the global loss , but an agent can cheaply evaluate only its local objective , which may ignore the other blocks. What the local objective misses is the exact correction
Each agent searches the corrected objective , built from an approximation of this correction. For LLM agents, the correction does not have to be a formula. In robot routing, it is the collisions with other agents’ robots that the verifier has already reported, shown in the agent’s prompt.
One epoch
All agents search in parallel from the same frozen solution, each for private steps. The verifier checks every proposal on its own and records its gain
Proposals can interfere, so the coordinator cannot simply accept all of them. Blocks that share a term of the loss are joined in a dependency graph, and a proper coloring with colors groups blocks that never interact. Gains within one color add exactly, so accepting the best color keeps at least the average gain of a color:
The cover shows one epoch: proposal 1 interacts with proposals 2 and 3, which share no term with each other, so the coordinator merges blocks 2 and 3 together and the global loss decreases.
The guarantee
Three conditions are enough. The correction must be accurate where it matters, the local search must capture a fixed fraction of the available corrected improvement, and single-block changes must be able to make progress, with a constant . Then the expected gap decreases linearly up to an error floor:
The rate has three factors: useful block directions (), finding them (), and keeping compatible gains (). The floor vanishes with exact corrections, and it depends on the correction error at only two candidates per agent: a true block minimizer and the proposal that the agent actually returns. This matters in practice. In robot routing, a uniform bound on the correction error over all routes exceeds , while the error measured at these two points is zero and about 40.
Merging interfering proposals
Accepting one color throws away the verified improvements of all other colors, even when they would combine well. Instead, the coordinator can check combinations of proposals and accept the one with the lowest loss, even if it contains proposals that interfere. This best-combination merge keeps the guarantee, and its rate depends on the realized number of colors
that is, on how well the proposals actually combine rather than on worst-case interactions. A greedy version needs far fewer checks when there are many agents.
Results with LLM agents
We test the protocol with GPT-OSS-120B agents on robot routing: nine robots on a grid with walls, three agents with three robots each, and a loss that adds arrival times and a penalty of 100 per collision. A larger task stacks two maps as the floors of one building, with 18 robots and six agents.
Two floors, 18 robots: mean gap to the optimum against search time, 20 runs per curve (10 without correction). Dots mark where the last run stops.
- Corrections matter. The three-agent team finds collision-free plans in all 40 runs on two maps, with better final plans than a single agent that controls all robots. Without corrections, only 2 of 20 runs end without collisions.
- Teams scale. On two floors, the six-agent team needs half the single agent’s median search time (595 against 1200 seconds) and ends with better plans.
- Checked merging pays off. Accepting the best checked combination cuts the team’s search time by about 30% and reaches a safe plan first. Merging all proposals without a check does not help.
- The theory follows the runs. With constants measured on the runs, the bound holds in every round of every run. With the realized number of colors it ends within a factor of 3 to 7 of the observed gap, instead of 30 to 60 with . The worst case occurs in only 8 of the 105 rounds with several improving proposals.
Two smaller studies test the theory where its constants can be measured or certified exactly: query planning in SQLite, where the correction is learned from the engine’s execution counters, and a synthetic task with certified constants.
The arXiv preprint contains the proofs, learned corrections, the cost of private work and the full experimental protocols. The GitHub repository contains the agents, prompts and records of every run.