Aaron Levie and Steven Sinofsky on the AI-Worker Future
Experts from a16z, Box, and Microsoft debate the definition and future of AI agents. They explore the shift from monolithic AGI to specialized agent networks, the technical challenges of autonomous systems, and how this new platform will reshape enterprise software, workflows, and the very nature of work.
The ultimate end state of AI is not the conversational, back-and-forth form factor we first saw, but rather autonomous agents that run in the background to execute real work with minimal human intervention. The more work an AI can perform without needing input, the more “agentic” it becomes.
Defining AI Agents: Beyond the Chatbot
An AI agent can be defined by a few key characteristics. First, it is a long-running, autonomous process that executes tasks in the background. Steven Sinofsky draws a parallel to the ampersand (&) in Linux, which runs a command as a background job.
More importantly, a true agent possesses a feedback loop: it produces output that it then feeds back into itself as input to guide its next actions. This distinguishes it from a simple, long-running inference task. This capacity for self-correction and iterative improvement is a core technical challenge, as these non-linear control systems can be difficult to manage and their convergence is not guaranteed.
The Architecture of Agency: AGI vs. Specialized Networks
The discourse around Artificial General Intelligence (AGI) has shifted significantly. The initial concept of a single, monolithic, super-intelligent system is giving way to a more practical and effective architecture: a network of many specialized agents.
This approach mirrors the Unix philosophy of breaking down complex problems into smaller, manageable tools. Each agent becomes a deep expert on a specific task or domain. A higher-level system then orchestrates these agents to solve more complex problems. This “division of labor” offers several advantages:
- Mitigates Context Rot: Large context windows can confuse models and degrade the quality of their output. By partitioning tasks among specialized agents, each one works with a more focused and relevant context. For example, some developers are creating a dedicated sub-agent for each microservice in their codebase, with its own “readme” file for instructions.
- Drives Specialization: This trend is a counter-narrative to the idea of a single, all-knowing AGI. It suggests that progress lies in creating more agents that perform narrower tasks with more specific, complex instructions. Prompts are becoming more sophisticated, not less, as users provide detailed context to guide these specialized systems.
Reshaping Work: From Tool Adoption to Workflow Transformation
The introduction of AI agents is not just about automating existing tasks; it’s about fundamentally changing how work is done, a pattern seen in previous platform shifts.
Initially, new tools often mimic old workflows. The first word processors were used to fill in pre-printed expense reports, rather than generating the entire document from scratch. Over time, however, the workflow itself adapts to the new technology’s capabilities. We will likely see a similar evolution where we don’t just ask agents to conform to our current processes, but instead redesign our processes to best leverage what agents can do.
A key debate is whether AI represents a more profound shift than previous platforms like the internet or the PC. For the first time, programs are “abdicating logic” to a third-party model, not just offloading resources like storage or device drivers. However, one can also view this as a new level of abstraction. When Windows introduced standardized print drivers, it abstracted away complex logic that developers previously had to build themselves, which in turn unlocked new opportunities for developers who embraced the platform.
Currently, agents are most effective as productivity multipliers for experts. An expert developer can use an AI coding assistant to achieve a 10x productivity gain because they can quickly verify the output, identify errors, and provide precise guidance. A novice, lacking this judgment, would be less effective and could even introduce flawed code.
The Business Landscape: Verticalization and the Application Layer
The trend toward specialization creates a massive opportunity for startups to build vertical-specific agents. Rather than being consumed by large model providers, the application layer is ripe for innovation. The playbook is to go deep on a specific workflow—like a payroll specialist or a legal case analyst—and build a dedicated agent for that job.
History shows that as a market grows, the granularity at which a company can be built becomes finer. It was once unthinkable that a single API for sending messages (Twilio) or handling authentication (Okta) could become a massive company. Similarly, we will likely see thousands of companies emerge that are built around providing a single, highly specialized agent.
Large model providers are unlikely to dominate this space because it is incredibly difficult to build deep expertise across dozens of different domains. While pre-training was a generalist achievement that consumed the world’s public data, the next phase of AI is about post-training, domain-specific data, and solving long-tail problems within specific enterprises. Companies that gain permission to access and build workflows on this private data are poised to win.