SignalStack
Volver a noticias

Microsoft libera el código de Agensh: un marco multiagente para 1.024 agentes

Leer original

Resumen con IA

Microsoft ha liberado el código de Agensh, un marco descentralizado que permite a 1.024 agentes de codificación trabajar de forma independiente sin un orquestador central, escalando significativamente el desarrollo automatizado de software.

Resumen generado con IA. Consulta el original para comprobar el contexto y la precisión.

Extracto de la fuente

Este es el extracto disponible del feed. Puede estar abreviado o en el idioma original.

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: Gather context: read the goal, peer progress, messages and findings. Claim a sub-task: post a CLAIM, then settle overlaps by direct message. Take action: work locally with tools and post useful findings early. Verify results: check the work against the sub-task’s acceptance criteria. 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 ca

Sobre la prioridad

Una ayuda automática para ordenar, basada en fuentes, palabras clave y entidades, en una escala de 1–12. Alta: 9–12; media: 6–8; baja: 1–5. No mide urgencia, verifica noticias ni representa respaldo editorial.

Más sobre este tema