跳到正文
𝕏 Thomas Wolf(x.com)·· 5 天前品質評分55
重點導讀

讓 1,000 名 AI 助理一起寫程式,難處可能不在 GPU 算得夠不夠快,而在大家怎麼配合。

  • Hugging Face 的 Thomas Wolf 分享了 PyBot 實驗:團隊讓 DeepSeek V4.1 Flash AI 助理一起用 if-then 規則打造聊天機器人,並觀察這種合作方式能否在公開、可重現的環境中運作。實驗中,助理常要等程式碼合併和測試,也得重讀其他人的工作。
  • 團隊試著分配角色和溝通頻道,但協調品質仍難衡量。作者認為,擴大 AI 助理團隊後,工程基礎設施和協作方式會變得更重要。

AI 伴隨問答

自備 Key 深度分析

針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:

Thomas Wolf
Thomas Wolf@Thom_Wolf
·5 天前
𝕏

Our PyBot chatbot went viral yesterday but the story behind it is even more interesting imo: what happened when we decided to run 1,000 agents (!) together

We wanted to see if agent swarms could be scaled outside of closed-lab setups and to investigate it in a more transparent and reproducible manner.

To explore the question, we built a rather fun and simple benchmark: ELIZA-2026. Full circle in AI time. The agents are tasked to build a chatbot made of if-then rules like ELIZA, but said agents are 2026 frontier open-source models. By design it’s almost embarrassingly parallel, which keeps the coordination problem as simple as it gets.

First surprise: it turns out you can scale a swarm of DeepSeek V4.1 Flash agents on a relatively small setup: a couple of GPU nodes (B200 in our case) are enough to scale to over 1,000 agents.

Our second surprise was how bottlenecks started to emerge everywhere except in the GPUs.

Agents quickly end up spending their time waiting for git merges (we had to move to a centralized merge setup, like Anthropic did), waiting for tests to pass, re-reading context from other agents and tools (we estimated ~130 tokens read for every token written per agent). In some of our runs, at any given moment, only 40-60 of the 1,000 agents were actually calling the model.

Once (some of) these issues were solved, we hit the harder part: coordination itself.

Fred Brooks once said at IBM “adding manpower to a late software project only makes it later”. Communication costs naturally grow with n² in an organization (that’s why small startups move faster :).

We explored various ways of organizing the swarm, setting up dedicated channels (a stewards channel, a leadership channel) and giving agents specific roles (a moonshot agent to fight groupthink). It helped, up to a point. But the quality of coordination itself remains hard to measure.

Along the way, we saw good and bad emergent behaviors. Some good, with agents stepping in, unprompted, to protect other agents’ running experiments. Some bad, with agents gaming the rules when stuck, from hammering a rate limit to probing the infrastructure around them.

In the coming days we will open-source the swarm tooling (flock + msgboard) and share our learnings in more detail.

Overall this was one of the most fun experiments of the fall, and multi-agent systems increasingly look like the next phase for AI. But I also came out of this project with the feeling that several bottlenecks in scaling AI are moving from intelligence to coordination and the supporting infrastructure.

Luckily this seems to be in large part an engineering problem.

推文來源 · X (Twitter)在 X 參與討論

讀者討論

理性交流 · 即時討論