Karpathy: "Claws" Are a New Layer on Top of LLM Agents
Original: Claws are now a new layer on top of LLM agents View original →
Karpathy Names a New AI Stack Layer: Claws
Andrej Karpathy recently bought a Mac Mini to tinker with a new generation of AI agent systems. In a mini-essay on X (Twitter), he introduced terminology that Simon Willison believes will stick: "Claws".
What Are Claws?
According to Karpathy, Claws represent a new architectural layer that sits on top of LLM agents, much like LLM agents themselves were a new layer on top of base LLMs. This layer provides:
- Orchestration: coordinating multiple agents and tasks
- Scheduling: automatically queuing and running tasks
- Context management: maintaining persistent memory across sessions
- Tool calls: integrating external tools and APIs
- Persistence: maintaining long-term state
A Growing Ecosystem
Karpathy notes that an ecosystem is already emerging: NanoClaw (core engine ~4,000 lines of code), nanobot, zeroclaw, ironclaw, and picoclaw. The category's unofficial emoji is 🦞.
Simon Willison observes that "Claw" is becoming a term of art for the entire category of OpenClaw-like systems — AI agents that run on personal hardware, communicate via messaging protocols, and can both respond to direct instructions and schedule tasks autonomously.
Significance
This follows Karpathy's earlier coinage of "vibe coding" and "agentic engineering," both of which achieved widespread adoption. The Hacker News discussion gathered 285 points, reflecting significant developer interest in this evolving layer of the AI stack.
Related Articles
Why it matters: document agents fail when PDF parsing destroys table and column structure. LiteParse uses a monospace grid projection approach instead of heavy layout models, and the code is open source.
r/MachineLearning did not reward this post for frontier performance. It took off because a 7.5M-parameter diffusion LM trained on tiny Shakespeare on an M2 Air made a usually intimidating idea feel buildable.
Hacker News focused on the ambiguity around Claude CLI reuse: even if OpenClaw now treats the path as allowed, developers still want a clearer boundary between subscription, CLI, and API usage.
Comments (0)
No comments yet. Be the first to comment!