Agent-to-Agent Software: Why Most Future Code Won't Have a User Interface
Updated
Knowledge on this page was mainly distilled from You're Not the User Anymore.
Software Without a Screen
Most internet traffic is already machine-to-machine. Over 60% of dynamic web traffic is API-based, growing twice as fast as traditional browsing. Software is following the same trajectory. As AI agents become the primary executors of tasks, most software will be consumed by agents, not people. The human-facing layer becomes the exception rather than the rule.
The Bypass Test
A simple test reveals which software is heading behind the wall: could an agent bypass the interface entirely and still get the job done? For calendars, project management tools, and email clients, the answer is yes. The interface exists for humans; the capability underneath is for anything that can call it. Software where the human experience of using it is the whole point, such as music listening, group conversation, or creative tools, stays human-facing. Everything else is up for grabs.
Ephemeral by Design
When agents build software for other agents, permanence stops being a virtue. An agent that needs a specific data transformation writes one, runs it, and discards it. Infrastructure for ephemeral machines that spin up in milliseconds and die when done already exists. No login screen, no user manual, no name. But it is software.
Q&A
What is agent-to-agent software?
Agent-to-agent software is code built by AI agents for consumption by other AI agents, with no human-facing interface. It consists of functions, endpoints, and data transformations that serve a goal without buttons, menus, or onboarding flows. Some of it is persistent (APIs), but increasingly it is ephemeral: created on the fly, used once, and discarded.
What percentage of internet traffic is already machine-to-machine?
Over 60% of all dynamic web traffic is API-based, according to Cloudflare's tracking across their global network. This share is growing roughly twice as fast as traditional browser-based traffic. The human-facing web is already the smaller half of total internet activity.
What is the bypass test for software interfaces?
Ask whether an AI agent could skip the user interface entirely and still accomplish the task. Your calendar, project management tool, and email client all pass this test: an agent needs the API or data model, not the UI. Software fails the test when the human experience of using it is the point, like listening to music, participating in a group chat, or making art.
Why does agent-consumed software tend to be ephemeral?
When the marginal cost of generating code approaches zero and the consumer is an agent that reads raw functions as easily as a human reads a menu, there is no reason to maintain, version, or refactor most code. Agents write what they need, execute it, and discard it. Infrastructure like Fly.io's ephemeral machines already supports this pattern with millisecond spin-up times.
What kind of software stays human-facing in an agent-dominated world?
Software where the experience of using it is the value. Music apps (listening is the point), group chats (being in the conversation matters), creative tools like sketchpads and writing apps, and entertainment all remain human-facing. The dividing line is whether the doing is the product or whether the outcome is the product. Outcome-oriented software migrates to agents.
What should builders do to prepare for agent-to-agent software?
Think of your product as a capability agents consume, not just a product humans use. Invest in well-documented APIs, structured schemas, and function signatures. Design for machine readability alongside human usability. The builders who treat their software as an agent-consumable service will be better positioned as the shift accelerates.