Entity trail
Karpathy
Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.
Briefing refs
40
Findings
40
Edges
0
Sources
97
Showing the first 40 findings. More graph evidence exists in the corpus.
Corpus findings
- 2026-06-30 / thought-leaders-researcherKent C. Dodds: An AI Agent Is 'a Junior Teammate With Infinite Stamina and Zero Context' — and Your Job Is Now to Manage ItIn 'How I Build Web Applications in 2026,' Dodds argues developers are increasingly project managers, product managers, and team leads orchestrating multiple agents rather than typing code, and that the scarce skill is supplying context and management, not syntax. The 'infinite stamina, zero context' framing is a tidy mental model for why context engineering and review discipline now dominate the workflow. It echoes the broader leader consensus (Karpathy, Hightower) that orchestration and taste are the new leverage.
- 2026-06-30 / thought-leaders-researcherKarpathy Reframes the Discipline: From 'Vibe Coding' to 'Agentic Engineering'In his Sequoia Ascent 2026 talk, Karpathy positions agentic engineering as the serious discipline that must grow on top of vibe coding so professional software keeps its quality bar — 'Software 3.0' is prompting-as-programming, with the context window as the lever and the LLM as the interpreter. The job shifts to shaping intent, reviewing outputs, running parallel agents, and designing loops. This is the conceptual scaffolding underneath his expanded CLAUDE.md rules and the clearest articulation yet of what 'engineering' means when agents write the code.
- 2026-06-30 / thought-leaders-researcherAndrej Karpathy's CLAUDE.md Quietly Doubles to Ten Rules — Adds a 'Self-Check Protocol' for Agentic Coding LoopsA document attributed to Karpathy circulating on X this week expands the famous four-rule community CLAUDE.md template to ten, adding rules for verification-before-fixing, debugging discipline, dependency hygiene, and named failure modes that agent loops should self-recognize. One builder writeup claims the additions cut Claude Code's error rate from 41% to 11%. For builders, the shift is from 'prompt better' to 'engineer the loop' — the rules are guardrails for autonomous agents, not just style hints.
- 2026-06-26 / thought-leaders-researcher'An Agent Is a While Loop': A Clean Explainer Reframes Prompt + Loop Engineering as the Core SkillA widely-shared thread (~374 likes) distills agents to a while loop — the model runs, requests tool calls, tool results return to context, the model runs again — and argues 'loop engineering' (designing the stop/verify conditions and tool surface) is now as important as prompt engineering. It reinforces Karpathy's framing that managing autonomous loops is the new programmer skill. Useful as a teaching primitive for anyone onboarding to agent design.
- 2026-06-26 / thought-leaders-researcherAndrej Karpathy Drops a 'Second Brain' Pattern — Argues Most Obsidian Note-Dumps Are a 'Second Drawer,' Not a BrainKarpathy is circulating a pattern for what a genuine 'second brain' should look like, arguing that dumping notes into Obsidian produces a passive 'second drawer' rather than an active, queryable memory. The post lands amid his broader 2026 thesis on managing AI loops and treating LLMs as persistent async teammates. The takeaway for builders: memory systems need structure and retrieval, not just storage — echoing the 'memory as RAM, not storage' framing now common in agent design.
- 2026-06-25 / thought-leaders-researcherAndrej Karpathy Calls Claude Tag 'the 3rd Major Redesign of LLM UI/UX' — AI as a Persistent, Org-Wide Async Teammate, Not a ChatbotReacting to Anthropic's June 23 Claude Tag launch, Karpathy argued LLM interaction has entered a third paradigm: after web chatbots (1st) and standalone apps/IDEs (2nd), the model becomes a self-contained, persistent, asynchronous entity with org-wide tools, memory, and context that works alongside human teams. He stressed the hard part is the under-the-hood plumbing — tools, integrations, compute environments, and shared memory — to make it 'just work' inline with all other org activity. For builders this reframes agent design away from per-user sessions toward shared, stateful teammates carrying persistent organizational context.
- 2026-06-19 / sources-researcherKarpathy Formalizes 'Software 3.0': Automating What Humans Can VerifyAndrej Karpathy published his Sequoia Ascent talk summary on June 17, formalizing 'Software 3.0': where 1.0 automates what humans can specify as rules and 2.0 automates what we can describe with training data, 3.0 automates what humans can verify — anything checkable by a test suite, game score, or proof checker. He pins December 2025 as the inflection point when agentic coding crossed from experimental to reliable. The actionable takeaway for builders: design workflows around verifiability — invest in tests, evals, and checkable specs, because that is now the boundary of what you can safely hand to an agent.
- 2026-06-12 / sources-researcherLoopcraft: Karpathy, Cherny and Steinberger Reframe Agent Work as 'Stacking Loops'Latent Space's June 12 AINews issue distills a builder consensus that you should stop prompting coding agents and instead design loops that prompt them — Boris Cherny: 'I don't prompt Claude anymore. I write loops, the loops do the work,' and Andrej Karpathy on 'removing yourself as the bottleneck.' The piece frames competitive advantage as knowing when to descend into lower loops for reliability and ascend to higher ones as models improve. It's the clearest articulation yet of the orchestration-over-prompting shift, calling it 'The Salty Lesson for agents.'
- 2026-06-11 / thought-leaders-researcherAndrej Karpathy Calls Claude Fable 5 a 'Major-Version-Bump-Deserving Step Change' — 'Never Felt This Tempting to Stop Looking at the Code At All'Reacting to Anthropic's June 9 Fable 5 release, Karpathy said it is SOTA 'on everything by a margin' and qualitatively a genuine step change on the order of Claude 4.5, peaking on long, very difficult problem-solving sessions where you can hand it far more ambitious tasks than usual. He admitted it's the first model where it's tempting to stop reading the code entirely (while cautioning against that in production) and flagged the safeguards as 'a little too trigger happy' at launch. For agentic-coding builders, one of the field's most credible voices is signaling a real capability discontinuity, not incremental gains.
- 2026-06-10 / thought-leaders-researcherAndrej Karpathy on Software 'Coming Out of a Tap': Jevons Paradox Will Explode Demand for Bespoke, Single-Use AppsIn a take surfaced by Simon Willison on June 9, Karpathy argues that as working software increasingly 'comes out of a tap,' cheap generation won't shrink the market — by Jevons paradox it expands it, unleashing demand for explainers, visualizers, dashboards, and disposable single-use apps. For builders, the implication is that distribution and taste, not lines of code, become the binding constraint. It is a notably optimistic counter to fears that abundant AI-generated software collapses developer value.
- 2026-06-05 / thought-leaders-researcherKarpathy's Contrarian Take: 'I've Never Felt This Much Behind as a Programmer — The Profession Is Being Dramatically Refactored'Karpathy posted that the programmer's contributed bits are growing 'increasingly sparse and far between,' and that he could be 10X more powerful if he properly strung together the AI capabilities now available. The take reframes the bottleneck away from writing code and toward orchestration — echoing the thesis that human taste and integration are the scarce resources. It's a candid admission from one of the field's best that even experts are struggling to keep pace with the tooling.
- 2026-06-05 / thought-leaders-researcherAndrej Karpathy Defects to Anthropic, Joins Pretraining Team: 'The Next Few Years at the LLM Frontier Will Be Especially Formative'The OpenAI founding member and coiner of 'vibe coding' announced on X that he is joining Anthropic, starting on the pretraining team, in a post that drew nearly 3 million views within an hour. The move signals a major talent realignment at the frontier — the most influential independent voice in AI engineering is returning to hands-on research rather than education or tooling. For builders, it's a strong signal of where the most ambitious pretraining work is now concentrated.
Source trail
Graph sources
entity graphfindings textkg entitiesnewsletter issues