Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

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.show more

shmidt

8,702 subscribers

16,085 просмотров • 1 месяц назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." 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. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT

Сreator of Claude Code: BORIS CHERNY, WHO BUILT CLAUDE CODE, SAID IT PLAINLY." 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. "He is not typing anymore. He runs loops that write the code for him. That is the shift most people miss. Not a better prompt. A loop that keeps running while you are gone.People sell $500 courses on this. The person who built the tool said it for free. The exact setup is in the article below.Bookmark this. Follow CyrilXBT

CyrilXBT

38,748 просмотров • 1 месяц назад

"I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops. And this is transition we're going to see for the rest of the year." - Boris Cherny, head of Claude Code at Anthropic.

"I don't prompt Claude anymore. I have loops running that prompt Claude and figuring out what to do. My job is to write loops. And this is transition we're going to see for the rest of the year." - Boris Cherny, head of Claude Code at Anthropic.

Rohan Paul

2,302,968 просмотров • 2 месяцев назад

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,576 просмотров • 22 дней назад

$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 просмотров • 1 месяц назад

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 просмотров • 1 месяц назад

Claude Code creator: "I don't prompt Claude anymore. I write loops - and the loops do the work. My job is to write loops." in 30 minutes Boris reveals his actual daily Claude Code setup. Claude Code + loops + dynamic workflow Worth more than a $500 vibe-coding course

Claude Code creator: "I don't prompt Claude anymore. I write loops - and the loops do the work. My job is to write loops." in 30 minutes Boris reveals his actual daily Claude Code setup. Claude Code + loops + dynamic workflow Worth more than a $500 vibe-coding course

Codez

872,815 просмотров • 2 месяцев назад

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 просмотров • 2 месяцев назад

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Dep

20,909 просмотров • 1 месяц назад

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

The creator of Claude Code deleted his IDE in November 2024. In the last 30 days, 100% of his contributions were written by Claude Code. 259 PRs. His job is not prompting anymore. His job is writing loops that prompt Claude for him. Here is what that progression actually looks like: → stage 1: write code by hand with autocomplete → stage 2: run 5-10 claude sessions in parallel, prompt each one yourself → stage 3: write loops that prompt claude — you become the author, the model becomes a subroutine → the ralph loop (2025): bash one-liner, fixed anchor files, built a programming language for $297 → the 2026 loop: loops supervising loops, scheduling on infrastructure time, git-backed durable state → five building blocks: automations, durable state, validator split, loop orchestration, crash recovery Most developers are still in stage 2, prompting sessions by hand. The ones at stage 3 are writing the loops that do the prompting for them. Read this article to be ahead of the curve! Follow NeilXbt for more AI engineering intelligence that shows you exactly where the leverage moved and what building at that level actually looks like.

NeilXbt

11,556 просмотров • 2 месяцев назад

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,041 просмотров • 2 месяцев назад

Anthropic's Boris Cherny says coding is moving to a higher level of abstraction A year ago, the workflow was writing code in an IDE, then prompting multiple Claude instances in parallel. Now, it is writing loops that prompt Claude and figure out what to do "the next transition is coming this year"

Anthropic's Boris Cherny says coding is moving to a higher level of abstraction A year ago, the workflow was writing code in an IDE, then prompting multiple Claude instances in parallel. Now, it is writing loops that prompt Claude and figure out what to do "the next transition is coming this year"

Haider.

526,682 просмотров • 2 месяцев назад

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

412,046 просмотров • 2 месяцев назад

Creator of Claude Code : "I don't prompt Claude anymore. I create loops - and the loops do the work. My job is to create loops." In 30 minutes, Boris breaks down his real daily Claude Code setup. Claude + loops + routines + dynamic workflow Worth more than a $500 vibe-coding course

Creator of Claude Code : "I don't prompt Claude anymore. I create loops - and the loops do the work. My job is to create loops." In 30 minutes, Boris breaks down his real daily Claude Code setup. Claude + loops + routines + dynamic workflow Worth more than a $500 vibe-coding course

Codez

148,147 просмотров • 2 месяцев назад

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 again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below

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 again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below

kiosa

16,808 просмотров • 1 месяц назад

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 просмотров • 3 месяцев назад

Borris Cherny the creator of Claude Code doesn't write code. He doesn't even talk to Claude. He runs one Claude that prompts the rest. He drops it like a throwaway, but that's the whole game now. You stop being the worker and become the one who runs them. ↓read this today to master multi-agent system

Borris Cherny the creator of Claude Code doesn't write code. He doesn't even talk to Claude. He runs one Claude that prompts the rest. He drops it like a throwaway, but that's the whole game now. You stop being the worker and become the one who runs them. ↓read this today to master multi-agent system

Rohit

205,067 просмотров • 2 месяцев назад

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Alpha Batcher

141,110 просмотров • 2 месяцев назад

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 просмотров • 1 месяц назад

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.

Rohit

30,233 просмотров • 2 месяцев назад

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 просмотров • 2 месяцев назад