Loading video...

Video Failed to Load

Go Home

Claude Code creator Boris Cherny on traits of side projects that take off > Start with automation — it's free leverage. Engineers build it faster than anyone, yet most underuse this superpower. Ask yourself: 'How can I do less of my work? >Track recurring problems & Automate until there's...

rvivek's profile picture

rvivek

13,469 subscribers

206,694 views • 6 months ago •via X (Twitter)

EducationScience & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below
17:28

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 views • 1 month ago

Boris Cherny (creator of Claude Code, Anthropic): "My entire CLAUDE.md is two lines. With every new model you need less instruction, not more, most people are over-engineering the one thing that should stay tiny." in a 7-minute interview, Boris Cherny breaks down why the smallest AI-coding setup wins, and the one moment you should delete your config and start from scratch most engineers do the opposite: they pile on rules, build scaffolding around the model… then the next model ships and makes all of it useless. what he actually keeps in those two lines, and why he tells his team to throw the rest away. Watch the talk, then read the article below. That’s worth more than a $800 course on agent engineering.
7:13

Boris Cherny (creator of Claude Code, Anthropic): "My entire CLAUDE.md is two lines. With every new model you need less instruction, not more, most people are over-engineering the one thing that should stay tiny." in a 7-minute interview, Boris Cherny breaks down why the smallest AI-coding setup wins, and the one moment you should delete your config and start from scratch most engineers do the opposite: they pile on rules, build scaffolding around the model… then the next model ships and makes all of it useless. what he actually keeps in those two lines, and why he tells his team to throw the rest away. Watch the talk, then read the article below. That’s worth more than a $800 course on agent engineering.

Riley West

236,811 views • 1 month ago

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (Boris Cherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations Brought to you by: • Statsig — ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for automated code review. Proactively find and fix issues in real-time with the SonarQube MCP Server: • WorkOS – Everything you need to make your app enterprise ready. Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”
1:37:58

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (Boris Cherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations Brought to you by: • Statsig — ⁠ The unified platform for flags, analytics, experiments, and more. • Sonar – The makers of SonarQube, the industry standard for automated code review. Proactively find and fix issues in real-time with the SonarQube MCP Server: • WorkOS – Everything you need to make your app enterprise ready. Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”

Gergely Orosz

489,599 views • 4 months ago

Claude Code creator, Boris Cherny: "A year ago, I prompted Claude to write code. Now I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops." in 30 minutes, Boris explains exactly what that next abstraction layer looks like - and why it's coming for everyone, not just engineers -why he uninstalled his IDE the moment he stopped needing it -the "underfund the team, overfund the tokens" strategy he recommends to every founder -why hundreds of his Claudes are scanning Twitter and GitHub right now, deciding what to build next -the real reason coding became Anthropic's testing ground for AI safety in the first place guide on loop👇
29:51

Claude Code creator, Boris Cherny: "A year ago, I prompted Claude to write code. Now I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops." in 30 minutes, Boris explains exactly what that next abstraction layer looks like - and why it's coming for everyone, not just engineers -why he uninstalled his IDE the moment he stopped needing it -the "underfund the team, overfund the tokens" strategy he recommends to every founder -why hundreds of his Claudes are scanning Twitter and GitHub right now, deciding what to build next -the real reason coding became Anthropic's testing ground for AI safety in the first place guide on loop👇

rewind

176,935 views • 25 days ago

AI can’t yet one-shot an entire product—but with the rise of vibe coding, supercharged developers are getting close. Part intuition and experimentation, part validation, it's the new frontier of software development. YC's Tom Blomfield (Tom Blomfield) has spent the last month building side projects with tools like Claude Code, Windsurf, and Aqua, seeing just how far you can push modern LLMs. From writing full-stack apps to debugging with a single copy paste of an error message, AI is becoming a legit collaborator in the dev process. With tips from YC founders in the Spring batch, this is a playbook for anyone who wants to get the most out of vibe coding and build faster.
0:45

AI can’t yet one-shot an entire product—but with the rise of vibe coding, supercharged developers are getting close. Part intuition and experimentation, part validation, it's the new frontier of software development. YC's Tom Blomfield (Tom Blomfield) has spent the last month building side projects with tools like Claude Code, Windsurf, and Aqua, seeing just how far you can push modern LLMs. From writing full-stack apps to debugging with a single copy paste of an error message, AI is becoming a legit collaborator in the dev process. With tips from YC founders in the Spring batch, this is a playbook for anyone who wants to get the most out of vibe coding and build faster.

Y Combinator

151,372 views • 1 year ago

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
1:22:03

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,412 views • 1 month ago

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.
0:53

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.

American Optimist

21,014 views • 4 months ago

Claude Code cracked something open for us Every 📧. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12
1:10:11

Claude Code cracked something open for us Every 📧. Now I ship to codebases I barely know, every feature we ship makes the next one easier, and non-technical members of the team use the terminal. I’m genuinely grateful. So I brought its creators, Cat Wu (cat) and Boris Cherny (Boris Cherny) from Anthropic, on AI & I to say thank you—and to talk about everything they’ve learned from building Claude Code. We get into: • The workflows Anthropic’s smartest engineers use to push Claude Code to its limits. Why they pit subagents against each other to get cleaner results, how they turn past code into leverage, and the slash commands and MCPs they rely on most. • The product lessons behind one of the most loved AI agents in the world. How the team balances simplicity and power—building a tool that anyone can use, but that experts can bend to their will—and their philosophy of “unshipping,” or cutting back whenever there’s a simpler, more intuitive path to user intent. • A peek into the future of coding with AI. The new form factors they’re experimenting with to make Claude Code more autonomous, more reliable, and more accessible to non-technical users This is a must-watch for anyone—both technical and non-technical—who wants to learn how to use Claude Code like the people who built it. Watch below! Timestamps: Introduction: 00:01:26 Claude Code’s origin story: 00:02:25 How Anthropic dogfoods Claude Code: 00:07:03 Boris and Cat’s favorite slash commands: 00:14:06 How Boris uses Claude Code to plan feature development: 00:15:49 Everything Anthropic has learned about using sub-agents well: 00:21:53 Use Claude Code to turn past code into leverage: 00:26:16 The product decisions for building an agent that’s simple and powerful: 00:33:14 Making Claude Code accessible to the non-technical user: 00:36:38 The next form factor for coding with AI: 00:45:12

Dan Shipper 📧

57,568 views • 8 months ago

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
0:40

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,735 views • 26 days ago

Klarna CEO Sebastian Siemiatkowski never learned how to code. But after a summer using Cursor, he now brings working prototypes to meetings instead of asking engineers to interpret his ideas: “Because I'm not an engineer, I've been vibe coding my whole life.” “I come into the meeting room, there's tons of product people and engineers. I say, ‘I think we should build an app that kind of does this, and it should work like that.’ They try to make sense of what is saying.” “I've never seen the code. I don't know how they made it. It's beautiful, I like our app. I think it's nice but, I don't know how it works.” “So to me, I've been vibe coding for 20 years. The only difference is now I'm sitting with a computer, and I'm doing it with AI and it's coming back with the prototype in 20 minutes.”
3:02

Klarna CEO Sebastian Siemiatkowski never learned how to code. But after a summer using Cursor, he now brings working prototypes to meetings instead of asking engineers to interpret his ideas: “Because I'm not an engineer, I've been vibe coding my whole life.” “I come into the meeting room, there's tons of product people and engineers. I say, ‘I think we should build an app that kind of does this, and it should work like that.’ They try to make sense of what is saying.” “I've never seen the code. I don't know how they made it. It's beautiful, I like our app. I think it's nice but, I don't know how it works.” “So to me, I've been vibe coding for 20 years. The only difference is now I'm sitting with a computer, and I'm doing it with AI and it's coming back with the prototype in 20 minutes.”

sourcery

149,352 views • 6 months ago

Struggling engineers identify with the craft. Thriving engineers identify more with the impact. - Gergely Orosz on SWEs in the era of vibecoding: "At my brother's company, he mandated his team: everyone’s using Claude Code, everyone needs to do prompting, and you need to generate your code." "Around 50% of his team got really demotivated. One engineer quit and told him, 'I do not want to be a prompter, I love the craft.'" "For that engineer, code was his identity. He was the go-to guy and understood the codebase better than anyone. People used to go up to him asking, 'Hey, how does this work, etc.?' Now, no one walks up to him because the AI can answer it." "Builders who don't care about the tools that much are going to thrive. For people who care about the craft, there might be niches, but it'll be harder."
1:27

Struggling engineers identify with the craft. Thriving engineers identify more with the impact. - Gergely Orosz on SWEs in the era of vibecoding: "At my brother's company, he mandated his team: everyone’s using Claude Code, everyone needs to do prompting, and you need to generate your code." "Around 50% of his team got really demotivated. One engineer quit and told him, 'I do not want to be a prompter, I love the craft.'" "For that engineer, code was his identity. He was the go-to guy and understood the codebase better than anyone. People used to go up to him asking, 'Hey, how does this work, etc.?' Now, no one walks up to him because the AI can answer it." "Builders who don't care about the tools that much are going to thrive. For people who care about the craft, there might be niches, but it'll be harder."

TBPN

23,818 views • 5 months ago

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
28:49

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,504 views • 1 month ago

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.
0:35

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.

Dustin

82,737 views • 3 months ago

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.
20:58

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,028 views • 1 month ago

Read the actual Anthropic piece. It's wilder than the hype precisely because it's so measured. As of last month, Claude writes more than 80% of the code Anthropic merges into its own codebase. Their engineers now ship roughly 8x the code per day they did in 2024. On a fixed test they run every release (take some training code, make it run faster), the model went from ~3x a year ago to ~52x. A skilled human gets about 4x in a few hours. And when a researcher hits a wrong turn mid-investigation, the newest model now picks the better next step 64% of the time. The honest part the hype skips is that Anthropic says we are NOT at self-improvement yet. Claude still can't decide which problems are worth solving. That research taste is the last thing keeping a human in the loop. But they openly map the moment it closes, when agents can build and train models themselves and Claude starts improving Claude. And the loudest signal in the whole thing sits at the end: the company building this is the one asking for a working pause button before the loop closes.
0:34

Read the actual Anthropic piece. It's wilder than the hype precisely because it's so measured. As of last month, Claude writes more than 80% of the code Anthropic merges into its own codebase. Their engineers now ship roughly 8x the code per day they did in 2024. On a fixed test they run every release (take some training code, make it run faster), the model went from ~3x a year ago to ~52x. A skilled human gets about 4x in a few hours. And when a researcher hits a wrong turn mid-investigation, the newest model now picks the better next step 64% of the time. The honest part the hype skips is that Anthropic says we are NOT at self-improvement yet. Claude still can't decide which problems are worth solving. That research taste is the last thing keeping a human in the loop. But they openly map the moment it closes, when agents can build and train models themselves and Claude starts improving Claude. And the loudest signal in the whole thing sits at the end: the company building this is the one asking for a working pause button before the loop closes.

Alex Veremeyenko

33,666 views • 1 month ago

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!
3:40

I'm teaching a new course! AI Python for Beginners is a series of four short courses that teach anyone to code, regardless of current technical skill. We are offering these courses free for a limited time. Generative AI is transforming coding. This course teaches coding in a way that’s aligned with where the field is going, rather than where it has been: (1) AI as a Coding Companion. Experienced coders are using AI to help write snippets of code, debug code, and the like. We embrace this approach and describe best-practices for coding with a chatbot. Throughout the course, you'll have access to an AI chatbot that will be your own coding companion that can assist you every step of the way as you code. (2) Learning by Building AI Applications. You'll write code that interacts with large language models to quickly create fun applications to customize poems, write recipes, and manage a to-do list. This hands-on approach helps you see how writing code that calls on powerful AI models will make you more effective in your work and personal projects. With this approach, beginning programmers can learn to do useful things with code far faster than they could have even a year ago. Knowing a little bit of coding is increasingly helping people in job roles other than software engineers. For example, I've seen a marketing professional write code to download web pages and use generative AI to derive insights; a reporter write code to flag important stories; and an investor automate the initial drafts of contracts. With this course you’ll be equipped to automate repetitive tasks, analyze data more efficiently, and leverage AI to enhance your productivity. If you are already an experienced developer, please help me spread the word and encourage your non-developer friends to learn a little bit of coding. I hope you'll check out the first two short courses here!

Andrew Ng

1,224,296 views • 1 year ago

Broadcom's CEO just told investors that one senior engineer with Claude Opus can do in one week what ten engineers earning $300,000 a year take three months to produce. Every engineering org in the world is running the wrong headcount math. This was not a prediction. It was a report from inside Broadcom. Hock Tan said his engineers are already using Claude Opus for engineering design and code assistance. Not experimenting with it. Using it. And the output they are getting from a single senior engineer in one week is equivalent to what a team of ten would produce over three months. Do that math slowly. Ten engineers at $300,000 a year is $3 million in annual salary. Three months of their time is $750,000 of labor. One engineer with Claude Opus produces the same result in one week. He also said something that most people in the room let slide past them. The engineers who get good at these tools do not just get faster. They get better. The designs they produce with AI assistance are probably better than what they would produce without it. That is the part nobody wants to say out loud. It was never just about speed. The ceiling on what a single engineer can produce just moved. And the teams that have not figured that out yet are spending $750,000 to do what one person with the right tools can do for a fraction of that. What do you guys think about this? (Watch the full interview at Bloomberg Live on YouTube)
1:15

Broadcom's CEO just told investors that one senior engineer with Claude Opus can do in one week what ten engineers earning $300,000 a year take three months to produce. Every engineering org in the world is running the wrong headcount math. This was not a prediction. It was a report from inside Broadcom. Hock Tan said his engineers are already using Claude Opus for engineering design and code assistance. Not experimenting with it. Using it. And the output they are getting from a single senior engineer in one week is equivalent to what a team of ten would produce over three months. Do that math slowly. Ten engineers at $300,000 a year is $3 million in annual salary. Three months of their time is $750,000 of labor. One engineer with Claude Opus produces the same result in one week. He also said something that most people in the room let slide past them. The engineers who get good at these tools do not just get faster. They get better. The designs they produce with AI assistance are probably better than what they would produce without it. That is the part nobody wants to say out loud. It was never just about speed. The ceiling on what a single engineer can produce just moved. And the teams that have not figured that out yet are spending $750,000 to do what one person with the right tools can do for a fraction of that. What do you guys think about this? (Watch the full interview at Bloomberg Live on YouTube)

Ihtesham Ali

96,980 views • 25 days ago

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.
0:31

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

Akshay 🚀

30,806 views • 1 year ago

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code
1:00:16

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 views • 11 months ago

The future of product management looks a lot like Zevi Arnovitz Zevi is an IC PM at Meta, has no technical background—is scared to even look at code—but has taught himself how to use Cursor and Claude Code to build significant and real product. He's developed his own very powerful Cursor workflow that allows him to quickly add his ideas to Linear, develop a plan using Claude Code, build it within Cursor, and then have different LLMs review his code. Zevi's engineers at Meta ask him to teach them how he does what he does, and I haven’t stopped thinking about this conversation since we had it. Everyone needs to pay close attention to what AI us unlocking for non-technical people. We discuss: 🔸 The complete AI workflow that lets non-technical people build in Cursor 🔸 How to use multiple AI models for different tasks (Claude for planning, Gemini for UI) 🔸Specific slash commands to automate key prompts 🔸 Zevi’s “peer review” technique, which uses different LLM models to review each other’s code 🔸 Why this might be the best time to be a junior in tech, despite the challenging job market 🔸 How Zevi used AI to prepare for his Meta PM interviews Listen now 👇 - YouTube: - Spotify: - Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 10Web.io — Vibe coding platform as an API 🏆 DX — The developer intelligence platform designed by leading researchers 🏆 Framer — Build better websites faster
1:15

The future of product management looks a lot like Zevi Arnovitz Zevi is an IC PM at Meta, has no technical background—is scared to even look at code—but has taught himself how to use Cursor and Claude Code to build significant and real product. He's developed his own very powerful Cursor workflow that allows him to quickly add his ideas to Linear, develop a plan using Claude Code, build it within Cursor, and then have different LLMs review his code. Zevi's engineers at Meta ask him to teach them how he does what he does, and I haven’t stopped thinking about this conversation since we had it. Everyone needs to pay close attention to what AI us unlocking for non-technical people. We discuss: 🔸 The complete AI workflow that lets non-technical people build in Cursor 🔸 How to use multiple AI models for different tasks (Claude for planning, Gemini for UI) 🔸Specific slash commands to automate key prompts 🔸 Zevi’s “peer review” technique, which uses different LLM models to review each other’s code 🔸 Why this might be the best time to be a junior in tech, despite the challenging job market 🔸 How Zevi used AI to prepare for his Meta PM interviews Listen now 👇 - YouTube: - Spotify: - Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 10Web.io — Vibe coding platform as an API 🏆 DX — The developer intelligence platform designed by leading researchers 🏆 Framer — Build better websites faster

Lenny Rachitsky

308,836 views • 5 months ago