100 People + Agents Editing One Document Simultaneously: Multica Calls It a Stress Test
Multica has launched a feature that lets 100 people/agents edit documents in real time, and it has already replaced Feishu internally. The author responds that this need is not a must-have and was mainly for stress testing. Built on CRDT, it is available first to self-hosted users.
Multica built a feature that lets 100 people/agents edit a document in real time. In a tweet, the author said it was built "by accident" and fills in the capability that Multica users have requested most. Internally, it has completely replaced Feishu Docs.
Multica is a workspace for "human + agent" teams. You can connect coding tools such as Claude Code, Codex, and Hermes as "teammates" on the team, assign them tasks, track progress, and review code. Previously, it was more like an agent project management tool. Now that document editing has been added, it means agents and humans can collaborate in real time in the same document.
The new feature supports 100 people/agents editing a single document at the same time. In the comments, someone asked about the technical approach, and the author replied that it uses CRDT. CRDT is a distributed data structure that lets multiple nodes make concurrent modifications to the same piece of data and eventually stay consistent, without a central server arbitrating order. Simply put, everyone can write at the same time without worrying about conflicts. Collaborative products like Figma also use similar technology.
Currently, self-hosted users can get early access through a feature flag. The cloud version will open only after the team tests it for a while longer. This pace is fairly prudent: let tech enthusiasts try it first, then release it to a broader set of users.
What's interesting is the skepticism from commenters. Someone asked: In what scenario would you need 100 people/agents to edit one document together? The author was very direct: It's not really needed; it's mainly to do collaborative editing with many people + many agents and run a stress test.
This exchange is worth thinking about. Product features are usually said to be demand-driven, but this feature seems more technology-driven: first probe the system's limits and see whether it can handle 100 concurrent users. This honest admission that it isn't a must-have is far more credible than the cliché of "solving user pain points."
Some commenters joked that the endgame is evolving into an agent-native Feishu. The author responded: You could understand it that way, but we try to keep it from becoming bloated; the knowledge base should be just an optional capability.
This sentence reveals the product direction: Multica doesn't want to become a large, all-encompassing collaboration platform. Instead, it wants knowledge collaboration to grow out of its agent management capabilities. Document editing is infrastructure, turning the place where agents and humans work into a document.
Imagine a real scenario: the Lead Agent writes the spec, the Backend Agent changes code, the QA Agent runs tests, and a human reviews. All these steps happen in the same workspace, and the document is the collaboration site. Real-time editing by 100 people is the limit; an actual team may need only a dozen or so concurrent editors, but that's already enough to change how collaboration works.
The internal team has already replaced Feishu Docs with this feature, which shows that stability is reasonably assured. Some commenters are calling for an iOS version; mobile is also something many people expect. Next, we'll see whether this feature extends to knowledge bases, more IM tools, or becomes a default capability.
Whether a feature is a must-have is sometimes not something you can figure out through research. Multica first got the extreme scenario working, and then looked at where it could land. At least the internal team has already voted with their feet.
发布时间: 2026-11-22 07:04