Microsoft Open-Sources Agensh: A Multi-Agent Harness for 1,024 Agents

By

Microsoft Research has open-sourced Agensh, a decentralized harness for large teams of coding agents. The Agensh multi-agent harness removes the central orchestrator that most agent frameworks depend on. Every worker picks its own sub-task, shares findings and merges code into a common Git repo. On ProgramBench, the team scaled the setup from 1 agent to 1,024 agents.

TL;DR

  • A Harness: Tested from 1 to 1,024 agents. Each worker gets a 272,000-token input and 128,000-token output limit.
  • Runs on: Linux with Docker Compose. Single node by default (8 workers). The 1,024-agent run used 16 nodes, 64 agents each. Workers have a 64 GiB memory ceiling.
  • Performance: more agents raised scores on all 5 hardest ProgramBench tasks, and reached them sooner.
  • Best: 79.59% pandoc pass rate with 32 agents on GPT-6.1-sol. GPT-5.6-sol hit 55.06% with 1,024 agents.
  • Worst: the 5-task mean reached only 28.78% at 128 agents. Going from 1 to 8 agents added 1.37 points.

What is Agensh?

Agensh is a multi-agent harness from Microsoft Research that coordinates many LLM agents without a lead agent.

The target problem is the orchestrator ceiling. In orchestrator-worker designs, a lead agent plans, assigns and merges all work. The research paper cites Claude Code agent teams, Codex sub-agents, Copilot fleet and Kimi Agent Swarm as examples. Agensh lets the workers do that coordination themselves.

How does the Agensh cooperation loop work?

Each worker runs the same 5-step loop, concurrently and asynchronously:

  1. Gather context: read the goal, peer progress, messages and findings.
  2. Claim a sub-task: post a CLAIM, then settle overlaps by direct message.
  3. Take action: work locally with tools and post useful findings early.
  4. Verify results: check the work against the sub-task’s acceptance criteria.
  5. Merge progress: merge into the shared repo, post an update, then repeat.

Three services connect the workers. Gitea hosts the shared workspace, with branches, PRs and merge conflicts. Mattermost carries a team channel plus direct messages for urgent collisions. A shared context board, adapted from DeLM, stores typed notes: OBSERVED, FACT, FAIL, CLAIM and PATCH_SUMMARY.

The loop lives in the prompt, not in runtime code. Every worker gets the same prompt except its ID. Agensh sits on top of a single-agent harness. The experiments used GitHub Copilot CLI. The research paper states thin adapters can connect other harnesses, such as Claude Code.

How well does Agensh scale on ProgramBench?

Microsoft team tested the 5 hardest ProgramBench tasks: FFmpeg, gromacs, pandoc, PHP-src and ctags. Agents rebuild each program from its observed behavior. They work offline, within 6 hours. Reference repos range from 2,767 files (pandoc) to 26,266 files (PHP-src).

With GPT-5.6-sol at high reasoning effort, the mean final test-pass rate moved as follows:

  • 1 agent: 19.31%
  • 8 agents: 20.68%
  • 32 agents: 26.52%
  • 128 agents: 28.78%

That is a 9.47-point gain, about 49% relative. On pandoc alone, scores were 33.89% (1), 41.75% (8), 43.11% (32), 50.94% (128) and 55.06% (1,024).

Speed improved too: on pandoc, 128 agents passed 30% at the 30-minute checkpoint. 32 and 8 agents needed 60 and 90 minutes.

The README adds a newer model. With GPT-6.1-sol, pandoc rose from 56.19% (1 agent) to 79.59% (32 agents). That is a 41.64% relative gain. These GPT-6.1-sol figures are not in the v1 paper.

What behaviors emerged as the team grew?

The research team traced worker trajectories at each scale:

  • 8 agents: peers agreed on interfaces and resolved overlapping claims themselves.
  • 32 agents: peers reviewed shared work; one approval was withdrawn after a counterexample.
  • 128 agents: workers reused trusted reviewers and standardized an integration protocol.
  • 1,024 agents: several workers acted as integrators, and peers recovered failed work.

None of these roles was hard-coded.

How does Agensh compare with other multi-agent harnesses?

FeatureAgenshClaude Code agent teamsKimi Agent SwarmCopilot CLI /fleet
CoordinationNo orchestrator; peers self-claim workFixed lead session coordinates teammatesOrchestrator decomposes tasksCopilot assigns parts to subagents
Agents shown1,024 testedNo hard limit; 3 to 5 recommendedUp to 100 sub-agentsNot disclosed
Shared stateGitea repo + shared context boardShared task list with file lockingNot disclosedPlan from plan mode
MessagingMattermost channel + direct messagesMailbox messages between teammatesNot disclosedNot disclosed
ModelsModel agnostic; tested GPT-5.6-sol, GPT-6.1-solClaude modelsKimi K2.5Not disclosed
Speed claim30% on pandoc at 30 min (128 agents)Not disclosed4.5x faster than sequential (self-reported)Not disclosed
AvailabilityOpen source, MITIn Claude Code; experimental, off by defaultTop-tier subscribers, research previewIn Copilot CLI

How do you run Agensh?

The release includes a single-node Docker Compose team and a single-agent baseline. Both use native Copilot ACP sessions. You need Linux with Docker Engine, Compose v2, systemd, cgroup v2 and Python 3.11+. Defaults are 8 workers, 6 hours per task and gpt-5.6-sol at high effort. You also need ProgramBench (v1.2.5 was validated) and a model API token. Full steps sit in the reproduction guide.

Key Takeaways

  • Agensh coordinates up to 1,024 agents with no central orchestrator.
  • Workers self-claim tasks via Gitea, Mattermost and a shared findings board.
  • 128 agents lifted the 5-task ProgramBench mean from 19.31% to 28.78%.
  • GPT-6.1-sol with 32 agents hit 79.59% on pandoc.
  • Code is MIT licensed, but token cost is not disclosed.

Check out the Paper, GitHub Repo and Project Page. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us

The post Microsoft Open-Sources Agensh: A Multi-Agent Harness for 1,024 Agents appeared first on MarkTechPost.



from MarkTechPost https://ift.tt/SegLuVM
via IFTTT

Comments

Post a Comment

Popular posts from this blog

Nanbeige4-3B-Thinking: How a 23T Token Pipeline Pushes 3B Models Past 30B Class Reasoning

By
Image
Can a 3B model deliver 30B class reasoning by fixing the training recipe instead of scaling parameters? Nanbeige LLM Lab at Boss Zhipin has released Nanbeige4-3B, a 3B parameter small language model family trained with an unusually heavy emphasis on data quality, curriculum scheduling, distillation, and reinforcement learning. The research team ships 2 primary checkpoints, Nanbeige4-3B-Base and Nanbeige4-3B-Thinking, and evaluates the reasoning tuned model against Qwen3 checkpoints from 4B up to 32B parameters. https://ift.tt/bMCdZs2 Benchmark results On AIME 2024, Nanbeige4-3B-2511 reports 90.4, while Qwen3-32B-2504 reports 81.4. On GPQA-Diamond, Nanbeige4-3B-2511 reports 82.2, while Qwen3-14B-2504 reports 64.0 and Qwen3-32B-2504 reports 68.7. These are the 2 benchmarks where the research’s “3B beats 10× larger” framing is directly supported. The research team also showcase strong tool use gains on BFCL-V4, Nanbeige4-3B reports 53.8 versus 47.9 for Qwen3-32B and 48.6 for Qwen...
Read more

Microsoft AI Proposes BitNet Distillation (BitDistill): A Lightweight Pipeline that Delivers up to 10x Memory Savings and about 2.65x CPU Speedup

By
Image
Microsoft Research proposes BitNet Distillation , a pipeline that converts existing full precision LLMs into 1.58 bit BitNet students for specific tasks, while keeping accuracy close to the FP16 teacher and improving CPU efficiency. The method combines SubLN based architectural refinement , continued pre training , and dual signal distillation from logits and multi head attention relations. Reported results show up to 10× memory savings and about 2.65× faster CPU inference , with task metrics comparable to FP16 across multiple sizes. What BitNet Distillation changes? The community already showed that BitNet b1.58 can match full precision quality when trained from scratch, but converting a pretrained FP16 model directly to 1.58 bit often loses accuracy, and the gap grows as model size increases. BitNet Distillation targets this conversion problem for practical downstream deployment. It is designed to preserve accuracy while delivering CPU friendly ternary weights with INT8 activa...
Read more

Technical Deep Dive: Automating LLM Agent Mastery for Any MCP Server with MCP- RL and ART

By
Image
Table of contents Introduction What Is MCP- RL? ART: The Agent Reinforcement Trainer Code Walkthrough: Specializing LLMs with MCP- RL Explanation: Under the Hood: How MCP- RL Generalizes Real-World Impact and Benchmarks Architectural Overview Practical Integration Summary Introduction Empowering large language models (LLMs) to fluidly interact with dynamic, real-world environments is a new frontier for AI engineering. The Model Context Protocol (MCP) specification offers a standardized gateway through which LLMs can interface with arbitrary external systems—APIs, file systems, databases, applications, or tools—without needing custom glue code or brittle prompt hacks each time. Still, leveraging such toolsets programmatically, with robust reasoning across multi-step tasks, remains a formidable challenge. This is where the recent combination of MCP- RL (a reinforcement learning loop targeting MCP servers) and the open-source ART (Agent Reinforcement Trainer) library ...
Read more