← Wiki

Software Design for the Agent Era

ai-agentssoftware-evolutionenterprise-aifuture-of-work

The Shift

For decades, software design centered on one question: how does a human user interact with the system? Aaron Levie argues this is breaking: “Almost everything about how we’re building enterprise software products is changing right now. Now many of the core design challenges are more about how the user will work with AI Agents to do this task.”

The new design questions are different:

  • How does the user set up, deploy, and orchestrate AI agents?
  • How does the user provide context to agents?
  • How does the user review and incorporate agent output?
  • Does this happen through an existing UI, chat, a task queue, a workflow builder?

The UI Inversion

In a world of AI agents, the user-facing interface gets simpler while the machine-facing interface gets richer. Levie observes: “The knobs, toggles, switches, and components needed for people to execute tasks are less necessary in a world of AI Agents. The APIs to these capabilities still matter for the AI Agents to use — but they’re primarily leveraged in the background.”

This creates a design inversion:

ElementPre-agent eraAgent era
Primary interfaceComplex GUI for humansAPI for agents
Human interfaceFeature-rich, multi-stepSimplified: setup, review, exceptions
Interaction modelHuman executes tasksHuman orchestrates agents
Design surfaceScreens, forms, dashboardsPrompts, task queues, review flows

Building for Trillions of Agents

Levie projects a future where “there will be trillions of agents executing every type of task for us imaginable.” This creates infrastructure demands that current software was never designed for:

  • Identity: Agents need verifiable identities across platforms
  • Storage: File systems and databases for agent work products, sessions, and shared data
  • Collaboration: Tools for agents to work with humans (and other agents)
  • Finance: Safe mechanisms for agents to spend or manage money
  • Compute: Sandboxed environments for agents to execute code

“CLIs/APIs are their native tongue” — software designed for agents must be API-first, not UI-first with an API bolted on.

New Design Challenges

Building for agents introduces challenges that don’t exist when building for humans:

  1. Oversight requirements. Agents require far more oversight than human users. They cannot self-correct the way a human notices they’re going down the wrong path.
  2. Accountability gap. Agents can’t be held responsible for their work. The person who launches the agent bears responsibility.
  3. Privacy asymmetry. Agents don’t get the same privacy rights as humans — their work must be auditable.
  4. Failure detection. Agents “don’t quite know when they’ve run astray and can’t execute the task at hand.”

Proactive vs. Reactive Software

Elvis argues: “Proactive agents are going to fundamentally change how we interact with software.” Traditional software waits for user input. Agent-era software anticipates needs, monitors conditions, and takes action before the user asks — shifting the interaction model from pull (user requests action) to push (system initiates action).

The Two-Track Split

Levie predicts “a split between two types of teams or companies for the foreseeable future” — those designing for the agent paradigm and those still building traditional user-centric software. This parallels every prior platform shift: companies that built for mobile early gained structural advantages over those that treated it as a feature of their desktop product.

The same dynamic applies at the startup level: “We’re at a fascinating point where there’s a decent thesis for starting new companies in literally every established software category.” The thesis is that incumbents built their UX for humans; challengers can build from scratch for the agent-and-human paradigm.

Connection to the Two Machine Ages

This shift mirrors the pattern in The Two Machine Ages. The steam engine (first machine age) augmented physical power but required factory redesign to capture its value. AI (second machine age) augments cognitive power but requires software redesign. The electric motor wasn’t transformative until manufacturers redesigned the factory floor. AI agents won’t be transformative until software is redesigned around agent-first architecture.