Yimao Zhou says agent startups optimize humans wrong, and builds an OS for the fix
Emagen AI’s 23-year-old founder argues the industry is fragmenting teams, then proposes an AI-driven operating system.

Yimao Zhou, the 23-year-old founder of Emagen AI, says the agent industry optimizes the wrong unit and proposes an operating system that lets AI drive work and calls on humans. For decision-makers, this is a window into how agent sprawl could either dissolve execution or become coordinated infrastructure.
Every week, another AI agent startup launches. They write code, draft emails, generate slides, analyze data. The pitch is always the same: let specialized agents do “their thing” and humans will supervise. But Yimao Zhou, the 23-year-old founder of Emagen AI, argues the entire agent industry is optimizing the wrong unit. In his view, the current approach makes individuals stronger while fragmenting teams.
Zhou’s answer is not another single-agent product. He is building an operating system where AI drives the work and calls on humans, rather than the other way around. That shift matters because “AI that does tasks” and “AI that runs work” are different categories, and teams feel the difference fast. If every agent is a self-contained helper, coordination becomes human glue. If AI is orchestrating across a workflow, the organization can move like a single system.
To understand why Zhou thinks things are going sideways, zoom out to what “agents” are actually competing on. Most agent startups promise output: a chunk of code, a drafted message, a cleaned dataset, a slide deck. Those deliverables are tangible, easy to demo, and they map well to the buyer’s immediate pain. But the unit of optimization is still the task. A task is local. A team is distributed. When too many local optimizations stack up, you do not get one coordinated outcome, you get a pile of partially compatible actions that need stitching.
Zhou’s framing also reflects incentives that show up in boardrooms and procurement folders. For founders, shipping a new agent is often faster than building platform-grade orchestration. A product that “does X” can find early users quickly. For capital, the story is straightforward: a growing number of agents means a growing number of opportunities. For customers, the attraction is equally clear: try the best tool for each use case instead of waiting for one big system that might do everything. The second-order effect is team fragmentation, and Zhou’s thesis is that the market is already paying that cost.
The operating system idea is essentially an attempt to reverse the dependency chain. In today’s common model, humans initiate work and agents execute. Zhou’s model flips the control loop: AI drives the work and then calls on humans when human judgment is required. That implies the system has a shared model of goals, context, and workflow state. Without that shared operating layer, agents act like independent apps on the same desktop, not like departments under one CEO.
There is also an increasingly important regulatory subtext to this architecture, even if the source does not go into specific regulators. As AI systems take on more operational authority, questions about accountability, auditability, and human oversight move from theoretical to practical. When humans stay in the loop on every step, it is easier to trace decisions back to a person. When AI drives work and selectively calls humans, the organization needs strong governance on when calls happen, what gets logged, and how overrides work. An OS approach can help here, because it creates a single surface for policy enforcement and visibility instead of many separate agents with inconsistent controls.
Second-order implications for executives show up in cost structure and execution speed. Task-based agents can look cheap at the beginning, but orchestration overhead often migrates into human time: aligning outputs, correcting mismatches, reconciling formats, and deciding which agent “wins” when multiple disagree. If an operating system actually coordinates agents end-to-end, it can reduce that human tax. But it also concentrates risk: when the orchestrator is the system, failures and misrouting are systemic rather than localized.
That is why Zhou’s argument about “stronger individuals, more fragmented teams” is more than a product opinion. It is a question of how organizations scale with AI. Individuals can do more when AI helps them at the edges. Teams struggle when coordination becomes a new manual chore. Zhou is positioning Emagen AI as the layer that turns agent output into reliable workflow execution. If he is right, the winners in the agent era will not be the companies that only generate the most impressive artifacts. They will be the companies that coordinate work without tearing teams apart.
For peers deciding what to build, buy, or fund, the strategic stakes are clear. The market will keep producing agent startups every week, and the demos will keep getting smoother. The real question is whether your organization ends up with a chaotic swarm of tools that each optimize their slice, or an operating layer that aligns work to goals and makes human review a deliberate control point, not a constant rescue mission.
This story's Key Insights and Take-aways are locked.
Create a free account to unlock Executive Actions for one credit.
Register to UnlockAlways free for Executives Club members. Join the Club
More in Technology

Propeller finishes Kernel Camp, graduating 5 MENA AI startups from Silicon Valley
Five companies from Tunisia, Morocco, Jordan, and Egypt complete an eight-week Silicon Valley residency with frontier AI mentors and investors.

SteamOS Beta 3.8.20 tackles the Steam Machine's 8GB VRAM bottleneck
A new update promises improved VRAM management and stability, plus Mesa upgrades for better ray tracing performance.

Army signs hyperscale data center deals with private billions, skipping taxpayer construction
Fortune lays out why the Army is shifting national-security infrastructure onto private capital, at speed and scale.

