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].
^[src-088] adds three infrastructure surfaces: local/on-device inference as a model fleet tier, WebMCP/browser affordances as an agent-facing web layer, and evidence-gated harnesses that require agents to prove work before humans review it.
The same update reinforces that agent-native infrastructure is not only APIs for agents; it is the whole operating environment around specs, tools, traces, memory, UI, permissions, and escalation ^[src-088].
^[src-105] adds the latency version of this problem: if models become very fast, the practical limit becomes tools designed for human response times. Agent-native infrastructure therefore needs low-latency, structured, resumable tool surfaces, not only documentation that agents can read.
^[src-111] adds the enterprise architecture version: the Agentic AI Mesh requires agent discovery, workflow discovery, asset registries, observability, access control, evaluations, feedback management, compliance, and risk management.
The same source treats MCP and A2A as interoperability primitives for agent infrastructure, because proprietary point-to-point integrations make large agent estates harder to govern and reuse ^[src-111].
^[src-114] adds Anthropic's managed-runtime version: production agents need a separated harness and execution sandbox, credential Vaults, persistent sessions, visual traces, memory, self-hosted sandboxes, MCP tunnels, and permission policies.
The same source makes a useful enterprise distinction: the differentiating product work is context and domain expertise, while the non-differentiating plumbing is increasingly session, sandbox, credential, observability, and harness infrastructure ^[src-114].
^[src-191] adds the builder-facing infrastructure layer: agent-native systems need CI/CD-like controls, save/resume state, receipts, rendering layers, voice-interruption handling, skills as SDKs, and software-factory orchestration.
The update clarifies that agent-native infrastructure is not just tool access; it is the operational substrate that lets agents be reviewed, recovered, and trusted after they act ^[src-191].

Related entities

Related concepts

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)
^[src-088] AI Engineer late-May 2026 channel update (48 transcripts, 2026-05-15 to 2026-05-31)
^[src-105] Google for Developers – "Gemini co-leads on project origins and what's next" (2026-05-29)
^[src-111] QuantumBlack / McKinsey – "Seizing the agentic AI advantage" (2025-06)
^[src-114] Anthropic – "The evolution of agentic surfaces: building with Claude Managed Agents" (2026-06-10)
^[src-191] AI Engineer World's Fair Online Track 2026 playlist update (47 new transcript captures, 2026-06-22 to 2026-07-02)

Robin Cartier perspective

This page is part of Robin Cartier's working AI knowledge graph: a practical research layer for production AI, recommendation systems, experimentation, GEO, and agentic web readiness.

The useful next step is to connect this concept back to applied product leadership and operating models.

Recommended next

Keep reading from this thread

From 491 indexed pages and articles.