Agent-Native Infrastructure
Agent-native infrastructure is the redesign of tools, docs, services, and deployment surfaces so agents can sense, act, configure, and verify work directly instead of following human-centric click instructions.
Key points
- Karpathy says most frameworks and services still publish docs for humans, but the useful artifact is increasingly the exact thing to copy-paste to an agent [src-055].
- He frames future infrastructure as sensors over the world, actuators over the world, and data structures that are legible to LLMs [src-055].
- The MenuGen deployment story is his negative example: much of the work was not building the app but manually configuring Vercel, DNS, service settings, and accounts [src-055].
- A good test for agent-native infrastructure is whether a user can prompt an LLM to build and deploy a working app without manually touching the service configuration path [src-055].
- The direction points toward agent representation for people and organizations, where one agent can negotiate or coordinate with another agent over meetings, settings, or operational details [src-055].
- Richardson adds the production architecture angle: once agents look like microservices and MCP servers look like gateway infrastructure, agent-native systems need hardened interfaces, governance, verification, and operational structure [src-057].
- The AI Engineer corpus adds concrete infrastructure categories: agent identity, OAuth, sandboxes, MCP servers, stateful environments, durable workflows, eval platforms, observability, agent fleets, browser/computer-use surfaces, and codebase readiness for coding agents [src-077].
- This shifts agent-native infrastructure from "make tools easy for agents" toward "make agents operable": permissioned, observable, recoverable, measurable, and deployable inside real products and enterprises [src-077].
- OpenAI's Codex discussion adds the consumer/knowledge-worker surface: plugins for documents, calendars, email, Notion, dashboards, and local files make the agent more useful because it can act where the user's work already lives [src-081].
- Computer use is the fallback for non-programmatic surfaces: Sio cites shopping, OS settings, slide/image editing, and QA as cases where the agent can click through interfaces when direct APIs are not enough [src-081].
Related entities
Related concepts
- Software 3.0
- Model Context Protocol (MCP)
- Claude Code Computer Use
- Agentic Engineering
- AI-Native Organizational Process
- Agents As Microservices
- Model Context Protocol (MCP)
- Enterprise Agent Governance
- Agent Security Boundaries
- Continuous Agent Evaluation
- LLM Observability
- AI Engineering Discipline
- Everyday Agentic Work
Source references
- [src-055] Sequoia Capital — "Andrej Karpathy: From Vibe Coding to Agentic Engineering" (2026-04-29)
- [src-057] Amazon Web Services — "The Future of Agentic AI with Rory Richardson | AWS Humans In The Loop Podcast" (2026-05-01)
- [src-077] AI Engineer channel transcript cluster (678 saved transcripts, 2023-10-20 to 2026-05-15)
- [src-081] OpenAI — "Codex for Everyday Work: AI Agents Beyond Coding" (2026-05-14)