Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying... show more

kiosa

2,835 subscribers

16,808 görüntüleme • 1 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,148 görüntüleme • 10 gün önce

Creator and head of Claude Code, Anthropic: "I don't prompt Claude anymore. I have loops running that prompt Claude and decide what to do. My job is to write loops." He hasn't hand-written a line of code since November. 100% is Claude Code now. Still ships 10 to 30 pull requests a day. He breaks down his actual workflow in the 1h28m podcast. Loops writing 100% of the code. Engineer leveling up, or automated out?

Creator and head of Claude Code, Anthropic: "I don't prompt Claude anymore. I have loops running that prompt Claude and decide what to do. My job is to write loops." He hasn't hand-written a line of code since November. 100% is Claude Code now. Still ships 10 to 30 pull requests a day. He breaks down his actual workflow in the 1h28m podcast. Loops writing 100% of the code. Engineer leveling up, or automated out?

shmidt

521,927 görüntüleme • 1 ay önce

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.

Raytar

28,046 görüntüleme • 24 gün önce

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below

Boris Cherny, the creator of Claude Code, just explained why the features most users never find are the ones that matter most in this podcast he breaks down not just how to use Claude, but what it all means for the next few years: > the right way to give Claude context before it starts working > why giving it too much information is just as bad as too little > how Claude Code is already changing how engineers build things > how the people who built Claude actually use it day to day based on this podcast and months of using Claude myself, I put together a guide on everything Claude can do that most people have no idea exists you can find it below

Anatoli Kopadze

22,474 görüntüleme • 2 ay önce

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Rahul

38,114 görüntüleme • 2 ay önce

Claude Code creator: "I don't prompt Claude anymore. I have loops that figure out what to do. My job is to create loops." in 30 minutes Boris breaks down his daily Claude Code setup, step by step the person who built the tool doesn't use it the way most people think no prompts, no chat box, just loops running on their own I broke down 17 Claude features most people have never found full guide in the post below

Claude Code creator: "I don't prompt Claude anymore. I have loops that figure out what to do. My job is to create loops." in 30 minutes Boris breaks down his daily Claude Code setup, step by step the person who built the tool doesn't use it the way most people think no prompts, no chat box, just loops running on their own I broke down 17 Claude features most people have never found full guide in the post below

Anatoli Kopadze

411,800 görüntüleme • 1 ay önce

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anatoli Kopadze

310,920 görüntüleme • 2 ay önce

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Mnimiy

113,663 görüntüleme • 1 ay önce

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,243 görüntüleme • 1 ay önce

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

Anthropic team: "Most people are prompting Claude wrong" They dropped a 24-minute workshop on how Claude prompts are actually built Free From the people who built the model There are 6 elements in a real Claude prompt Most people use 1 That is why their outputs feel generic Better wording is not enough Claude rewards structure, context, examples, constraints, and feedback I watched it twice Then built a Claude Skill that applies all 6 automatically You write normally The skill structures the prompt before Claude sees it Bookmark and watch this Then save the setup below

rari

15,655 görüntüleme • 1 ay önce

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below

Boris Cherny: "I don't write code anymore, I just prompt with Claude" he spent 57 minutes explaining exactly where this is all going here's what stood out: > Claude Code grew faster than anyone at Anthropic expected > AI agents are moving beyond coding into every industry > running 1,000 agents in parallel is already happening > SaaS may not survive the agent era if the Head of Claude Code prompts instead of codes, what does that tell you about the next 2 years? that's exactly why I put together an article on Claude features most people don't know exist it will change how you work with Claude completely you can find it below

Anatoli Kopadze

20,003 görüntüleme • 2 ay önce

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 görüntüleme • 2 ay önce

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.

Anatoli Kopadze

47,071 görüntüleme • 7 gün önce

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,240 görüntüleme • 5 ay önce

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Avid

26,996 görüntüleme • 1 ay önce

Anthropic is paying $500k-$850k/year for engineers who can build AI agents. Two Anthropic engineers just gave away a 75-minute workshop: 27:01 - A full app from one prompt 37:55 - Anthropic's real agent setup 54:38 - Permanent memory for Claude 1:08:38 - Make Claude work while you sleep Prompting Claude is becoming basic. Make Claude prompt itself. Watch the workshop, then read the guide to building loops below.

Anthropic is paying $500k-$850k/year for engineers who can build AI agents. Two Anthropic engineers just gave away a 75-minute workshop: 27:01 - A full app from one prompt 37:55 - Anthropic's real agent setup 54:38 - Permanent memory for Claude 1:08:38 - Make Claude work while you sleep Prompting Claude is becoming basic. Make Claude prompt itself. Watch the workshop, then read the guide to building loops below.

Raytar

54,019 görüntüleme • 21 gün önce

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):

Alex Finn

40,955 görüntüleme • 10 ay önce

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

16,085 görüntüleme • 1 ay önce

$Boris Cherny, head of Claude Code at Anthropic: "I don't prompt Claude anymore. I have loops that are running; they are the ones prompting Claude and figuring out what to do. My job is to write loops." He's right. Karpathy and Steinberger arrived at the same conclusion from different angles. The skill has a new name. Loop engineering. Cherny's token bill is zero. He works at Anthropic. Steinberger burned $1.3 million in OpenAI credits in 30 days. He works at OpenAI. Loops are the right architecture. But the people evangelizing them aren't the ones paying. I wrote a breakdown of five plays that land most of what a loop gives you at a fraction of the cost, plus the one case where a loop is worth paying for.$

Boris Cherny, head of Claude Code at Anthropic: "I don't prompt Claude anymore. I have loops that are running; they are the ones prompting Claude and figuring out what to do. My job is to write loops." He's right. Karpathy and Steinberger arrived at the same conclusion from different angles. The skill has a new name. Loop engineering. Cherny's token bill is zero. He works at Anthropic. Steinberger burned $1.3 million in OpenAI credits in 30 days. He works at OpenAI. Loops are the right architecture. But the people evangelizing them aren't the ones paying. I wrote a breakdown of five plays that land most of what a loop gives you at a fraction of the cost, plus the one case where a loop is worth paying for.

Alex Prompter

15,166 görüntüleme • 1 ay önce

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

103,005 görüntüleme • 2 ay önce