Agensh: Scaling Organizational Intelligence to 1,024 Agents

Zhihao Zhan, Ting Song, Li Dong, Shaohan Huang, Jianxun Lian, Yan Xia, Furu Wei

Microsoft Research

Published September 22, 2026 · on the feed September 23, 2026 · ▲ 25 · arXiv 2609.26781

Agents Dead link arXiv ↗Hugging Face ↗

The abstract

A multi-agent system can reduce latency on complex tasks by executing work concurrently. Several pioneering harness frameworks support multi-agent systems. However, the scalability of current multi-agent harnesses is often constrained by a central orchestrator's capacity to allocate tasks and coordinate workers. To address this limitation, we introduce Agensh, a scalable self-organized multi-agent harness without a central orchestrator: concurrent workers execute a multi-agent cooperation loop, continuously gathering context, claiming and self-assigning sub-tasks, taking action and sharing findings, verifying results, and merging progress in an asynchronous manner. The loop is supported by the agentic organization infrastructure comprising three components: a shared workspace holds proposed, ongoing, and completed work; a message interface lets workers communicate; and shared context retains reusable findings and work intentions. To test the scalability of Agensh, we evaluate it on the five hardest ProgramBench tasks with GPT-5.6-sol (high). Scaling from 1 to 128 agents raises the mean final test-pass rate from 19.31% to 28.78%, an approximately 49% relative improvement. Larger organizations reach comparable test-pass rates earlier. On pandoc, scaling from 1 to 1,024 agents raises the final test-pass rate from 33.89% to 55.06%. Worker trajectories further show that different forms of self-organized cooperation gradually emerges and standardizes as the organization grows. These results reveal the number of agents as a new scaling dimension for multi-agent organizations to expand the frontier of general intelligence, offering a practical solution for complex tasks under hard latency constraints or time budgets.

The Brief

2:52

A short podcast summary of the paper. Written and voiced by AI.

Transcript

Agensh. Scaling Organizational Intelligence to 1,024 Agents. By Zhihao Zhan and six others, from Microsoft Research. Published on the twenty-second of September. It links to a code repository that is no longer there.

A multi-agent system can cut latency on complex tasks by doing work concurrently. Several pioneering harness frameworks support such systems. But their scalability is often limited by a central orchestrator, and by how much that orchestrator can handle in allocating tasks and coordinating workers. As the number of workers grows, the orchestrator becomes the bottleneck. Every allocation and every coordination decision passes through it, so the capacity of that one component caps the whole system.

Agensh removes the orchestrator. It is a scalable, self-organized multi-agent harness in which concurrent workers each run a cooperation loop. They continuously gather context, claim and self-assign sub-tasks, act and share what they find, verify results, and merge progress, all asynchronously. Nobody hands out the work. The workers take it.

The loop is supported by what the authors call agentic organization infrastructure, which has three components. A shared workspace holds work that is proposed, ongoing and completed. A message interface lets workers talk to each other. And a shared context keeps reusable findings and records of what each worker intends to do. Between them, these three pieces do what an orchestrator would otherwise do. The workspace shows what needs doing and who is on it. The messages let workers coordinate directly. The shared context stops them from repeating each other's discoveries or colliding on the same work.

To test scalability, Agensh was run on the five hardest ProgramBench tasks with GPT-5.6-sol at high setting. Scaling from one agent to one hundred and twenty-eight raises the mean final test-pass rate from nineteen point three one percent to twenty-eight point seven eight percent, a relative improvement of about forty-nine percent. Larger organizations also reach comparable pass rates earlier. So adding agents helps in two ways: the final result is better, and good results arrive sooner, which is the latency benefit a multi-agent system was meant to deliver in the first place.

On pandoc, the scale goes further. Moving from one agent to one thousand and twenty-four raises the final test-pass rate from thirty-three point eight nine percent to fifty-five point zero six percent. Worker trajectories show different forms of self-organized cooperation emerging gradually and becoming standardized as the organization grows. The structure is not designed in advance. It appears as the number of workers rises.

The authors read these results as establishing the number of agents as a new scaling dimension for multi-agent organizations. With no central orchestrator in the loop, adding workers kept helping, up to one thousand and twenty-four of them on pandoc. They offer it as a practical option for complex tasks under hard limits on latency or time.

Paper Quest · 7 chapters · about 41 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

Every quest starts with a wall. Here it is one coordinator trying to manage an ever-growing crowd.

You want many AI coding workers to rebuild a huge piece of software within a fixed time budget. More workers running at once should mean faster progress.

The road ahead

  1. 1 · The problem ~7 min Many AI coding workers running at once should finish a huge job faster, but one main agent coordinating them all caps how far that scales.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~9 min Remove the central coordinator: workers organise themselves, each running the same loop, coordinating through a Git workspace, messages and shared notes.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Each worker repeats five steps: gather context, claim a sub-task, act while sharing findings, verify, and merge into the shared workspace.
  6. 6 · The experiment ~6 min You’ll guess: Going from one agent to 128 on the five hardest ProgramBench tasks, how big was the relative gain in mean final test-pass rate?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.