跪拜 Guibai
← All articles
Interview · GitHub · Algorithms

Super-Agent Architecture Converges: Five Labs, Six Weeks, One Baseline

By 怕浪猫 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Any developer building agent workflows now inherits an emerging industry baseline: cloud VMs, persistent memory, MCP, and mandatory human sign-offs on irreversible actions. Ignoring those defaults means shipping agents that die with a closed laptop, forget context, or get blocked by payment and security teams.

Summary

The super-agent boom broke in autumn 2026. Starting September 8, Meta launched Muse; OpenAI followed with dots at DevDay (Sept 29), Google with Gemini agent (Oct 8), Anthropic with Claude Duet (Oct 21), and DeepSeek with an open-sourced prototype (Oct 31). The five products share a de facto architecture: a persistent coordinator, independent sub-agents, a cloud sandbox that survives a closed laptop, cross-session memory, and MCP as the tool connector. The differences are mostly naming.

Two things stand out. First, every vendor treats cost as a design constraint, not an afterthought: Duet only checks in a few times a day to spare quota, Google adds smart routing and spending caps, Meta promises a 10x cost-efficiency increase. Second, permission boundaries are nearly identical across the board: reading, drafting, preparing are autonomous; sending, paying, signing, deleting require human approval; securities trading and cross-account transfers are prohibited even when approved. That convergence is a settlement, not a coincidence.

Divergences remain around proactivity timing, permission granularity, and whether agents should talk to other vendors' agents. OpenAI's product head said he personally would never attend a meeting with someone else's AI. Meanwhile Chinese vendors are splitting along product lines: Alibaba's super-app integration, ByteDance's OS-level phone assistant, Tencent's WeChat ecosystem, and more. The U.S. leans enterprise integration and governance; China leans consumer super-apps.

Takeaways
— Five vendors shipped in six weeks: Meta Muse (Sept 8), OpenAI dots (Sept 29), Google Gemini agent (Oct 8), Anthropic Claude Duet (Oct 21), DeepSeek Super-agent (Oct 31).
— Muse reached 10M+ users with ~25% daily usage and >$200 average purchase among active shoppers.
— dots runs 7×24 with a cloud browser and 4,000+ app connections, but proactive research only gets read-only tools.
— Google's coworker agents get an @agents.company.com email and persistent storage; they can call Anthropic's Claude as a model option.
— Duet only checks in a few times a day; sending, paying, signing, and deleting require approval, and securities trading or inter-account transfers are banned outright.
— Microsoft Agent 365 is a control plane for governance, not an agent itself.
— DeepSeek open-sourced a prototype with a Router/Worker split where workers have isolated contexts and subscribe to the same thread.
— Common red lines: send/pay/sign/delete require human approval; securities trading and inter-account transfers are off-limits for every vendor.
— MCP is the de facto tool connection standard; A2A is just starting (Coze already supports it).
— Chinese vendors emphasize consumer super-app ecosystems; US vendors emphasize enterprise integration and governance.
— Cost is a hard constraint: Duet avoids continuous patrols to save quota, Google uses smart routing and spending caps, Meta wants 10x cost efficiency in a year.
— Unresolved disagreements include proactive timing (dots alerts 3 minutes before a meeting), permission granularity, whether agents should talk to each other, and merchant-side acceptance.
Conclusions

The six-week cluster points to a shared threshold: model capability is no longer the limiting factor, so attention and session management became the bottleneck and every vendor independently shipped the same skeleton.

Google's coworker agents with corporate email addresses and persistent storage turn agents into organizational actors, which forces governance onto the same rails as human employees.

The near-identical red lines on sending, paying, signing, and deleting show the industry settling on risk boundaries before any technical mechanism makes them safe.

OpenAI's dots accepting only read-only tools for proactive research reveals how quickly autonomy collides with accidental writes; the official admission that granular controls are needed is a concession to that reality.

DeepSeek's Router/Worker pattern directly offloads coordination from a heavyweight main agent, addressing the inference cost that bogs down sub-agent orchestration in mainstream designs.

The split between US enterprise-governance focus and Chinese consumer-super-app focus is not just a regional taste; it sets different cost and privacy trade-offs for agents that Western developers will either adopt or work around.

Concepts & terms
MCP (Model Context Protocol)
An open protocol that standardizes how agents connect to external tools and data sources. In this article, MCP is cited as the de facto standard for tool connections across all major vendors, replacing per-vendor proprietary integrations.
A2A (Agent-to-Agent)
A protocol for agents to communicate and coordinate with each other directly. The article notes it is just starting, with ByteDance's Coze already supporting it, while other vendors are still debating whether agents should even be allowed to talk to other vendors' agents.
Router/Worker architecture
A design pattern used by DeepSeek's super-agent prototype. A lightweight Router handles routing decisions and never executes tasks; multiple Workers run independently with isolated contexts, and they subscribe to a shared thread to detect conflicts. This avoids the inference overhead of a main agent coordinating many sub-agents.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗