← All IntelClip / EntertainmentMake infrastructure agent-native
From Andrej Karpathy on Vibe Coding & Agentic Engineering (AI Ascent 2026) · ≈25:40
“Everything is still fundamentally written for humans and has to be moved around.”
“Why are people still telling me what to do? Like I don't want to do anything. What is the thing I should copy paste to my agent?”
“How do we make it agent native? Basically describe it to agents first.”
What’s in it
- Why docs written for humans frustrate agent-driven workflows
- The case for agent-native tooling and copy-paste-ready instructions
- Decomposing workloads into sensors and actuators for LLMs
Clip transcript
you know, native agentic environment looks like and everything has to be rewritten. Everything is still fundamentally written for humans and has to be moved around. I still use most of the time when I use different frameworks or libraries or things like that. They still have docs that are fundamentally written for humans. This is my favorite pet peeve. Like I don't Why are people still telling me what to do? Like I don't want to do anything. What is the thing I should copy paste to my agent? >> [laughter] >> So it's just every time I'm told, you know, go to this URL or something like that. It's just like ah. >> [laughter] >> You know. >> [snorts] >> So um everyone is I think excited about how do we decompose the workloads that need to happen into fundamentally sensors over the world, actuators over the world. How do we make it agent native? Basically describe it to agents first. Um and then I have a lot of automation around you know, the Yeah, around data structures that are very legible to the LLMs. So I think
Comments
Sign in to comment.
Loading comments…