Skip to content

Podcast

The Debate Over Anthropic’s New Product- Price or Existential Dread?

The AI Daily Brief: Artificial Intelligence News and Analysis

Source ↗ ← All highlights
  • Agentic Workflows Collapse The Software Lifecycle
    • Agentic workflows collapse classical SDLC stages into intent-driven loops led by agents.
    • Boris Tain explains agents iterate across code, tests, and deployment until it works, removing discrete handoffs like code review. Transcript: Nathaniel Whittemore In 2026, the one thing that’s clear to everyone is that things are moving very fast. Even for an industry where it already felt like things were going quickly, we’ve ratcheted it up another notch. As part of that, everyone is grappling with a series of different issues. Everything from the very positive, how do I take advantage of all these new superpowers that I’ve been given, to the exciting but it’s a challenge kind of questions like, how do we redesign Our organization around these new capabilities, to the much more existential questions of, what does it mean that the work that I’ve always done is no longer the work that I will be doing? In many ways, it feels to me like all of those debates came home to roost around a single product this week, which was Anthropik’s new CodeReview feature. Now, this is not a particularly complicated product to explain. Claude writes, when a PR opens, Claude dispatches a team of agents to hunt for bugs. CodeReview is a key part of the development lifecycle, so it stands to reason that AI would be trying to add new efficiency to it. And certainly Anthropic is not the only company thinking in these directions. Cognition recently released DevonReview, which they call a reimagined interface for understanding complex PRs. In their announcement tweet, they wrote, Now they go through a whole bunch of ways in which the product is different, and it got pretty good response. A thousand people bookmarked that tweet, and three-quarters of a million people viewed it. That is, of course, nothing compared to the nearly 14 million who viewed the Claude post, which speaks not only to the relative size of Anthropic, but to the controversy surrounding This new product. So what actually was controversial? On the surface of it, this seems like it would be highly value additive. While they are biased and incentivized to say so, certainly it seems like all the folks inside Anthropic who are using it have had really positive experiences with it. Alex Albert, who does Claude& DevRelations, says this has been a game changer for our internal engine research teams. Rare to see a product get this much praise from some of the top engineers I know. Boris Cherney, the creator of Claude Code, points out, We built it for ourselves first. Code output per Anthropic engineer is up 200% this year, and reviews were the bottleneck. Personally, I’ve been using it for a few weeks and have found it catches many real bugs that I would not have noticed otherwise. Jared Sumner writes, Been using this in Bunn’s repo, Bunn JavaScript being a company that joined Anthropic recently. Jared continues, this in my opinion is the best product in the code review category today. It regularly catches extremely subtle bugs and rarely makes mistakes. CloudCodes Tariq writes, code review is so so good. One of those things I can’t remember how I lived without. What’s more, the discussion of code review and the inevitable changes to it is something that the larger agentic engineering community has been talking about recently irrespective Of this cloud product. Sean Wang slash Swix of Latent Space wrote, This is the final boss of agentic engineering, killing the code review. At this point, multiple people are already weighing how to remove the human code review bottleneck from agents becoming fully productive. I’m not personally there yet, but I tend to be three to six months behind these people, and yeah, it’s definitely coming. Now he points to a guest essay shared on latent space by entrepreneur Ankit-Jane called How to Kill the Code Review. The subheader, which encapsulates the thesis pretty clearly, is human-written code died in 2025, code reviews will die in 2026. I won’t read the whole thing, but a couple of excerpts. Humans already couldn’t keep up with code reviews when humans wrote code at human speed. Every engineering org I’ve talked to has the same dirty secret. PRs sitting for days, rubber stamp approvals, and reviewers skimming 500 line diffs because they have their own work to do. We tell ourselves it is a quality gate, but teams have shipped without line-by review for decades. Code review wasn’t even ubiquitous until around 2012-2014, one veteran engineer told me, there just aren’t enough of us around to remember. And even with reviews, things break. We have learned to build systems that handle failure because we accept that review alone wasn’t enough. This shows in terms of feature flags, rollouts, and instant rollbacks. The next section in the core thrust of Enkit’s argument is called, we have to give up on reading all the code. He continues, teams with high AI adoption complete 21% more tasks and merged 98% more pull requests, but PR review time increases 91% based on data from over 10,000 developers across 1,255 teams. Two things are scaling exponentially, the number of changes and the size of changes. We cannot consume this much code. On top of that, developers keep saying that AI-generated code requires more effort than reviewing code written by their colleagues. Teams produce more code, then spend more time reviewing it. There is no way we win this fight with manual code reviews. Code review is a historical approval gate that no longer matches the shape of the work. Now, Boris Tain wrote something about this as well. His more broadly themed piece from February of this year was called The Software Development Lifecycle is Dead. Boris writes, AI agents didn’t make the SDLC faster. They killed it. I keep hearing people talk about AI as a 10x developer tool. That framing is wrong. It assumes the workflow stays the same and the speed goes up. That’s not what’s happening. The entire lifecycle, the one we’ve built careers around, the one that spawned a multi-billion dollar tooling industry, is collapsing in on itself. And most people haven’t noticed yet. Boris argues that the software development lifecycle, we learned it is a relic. He writes, here is the classic software development lifecycle most of us were taught. And apologies for those of you who are just listening, but basically it’s a circular chart that goes from requirements, to system design, to implementation, to testing, to code review, To deployment, to monitoring, and then back to requirements and through the system again. Boris writes, every stage has its own tools, its own rituals, its own cottage industry. Jira for requirements, Figma for design, VS Code for implementation, JEST for testing, GitHub for code review, AWS for deployment, Datadog for monitoring. Each step is discrete, sequential, handoffs everywhere. Now, here’s what actually happens when an engineer works with a coding agent. In this chart, there is one starting point, which is intent, which moves to the agent, and then the agent works in a circular fashion through code plus test plus deployment to the question Of does it work. If the answer is no, it’s back to the agent for more code, tests, and deployment, back to the question of does it work. And then as soon as the answer to does it work is yes, the code gets shipped. Boris’s point is this, quote, the stages collapsed. They didn’t get faster, they merged. (Time 0:10:56)
  • AI Can Replace Human Code Review Rituals
    • AI code review products like Anthropic’s dispatch specialized agents to hunt for bugs and replace manual review rituals.
    • Nathaniel Whittemore and others report internal usage increased engineer output and that reviewers found subtle bugs missed by humans. Transcript: Nathaniel Whittemore Was Anthropik’s new CodeReview feature. Now, this is not a particularly complicated product to explain. Claude writes, when a PR opens, Claude dispatches a team of agents to hunt for bugs. CodeReview is a key part of the development lifecycle, so it stands to reason that AI would be trying to add new efficiency to it. And certainly Anthropic is not the only company thinking in these directions. Cognition recently released DevonReview, which they call a reimagined interface for understanding complex PRs. In their announcement tweet, they wrote, Now they go through a whole bunch of ways in which the product is different, and it got pretty good response. A thousand people bookmarked that tweet, and three-quarters of a million people viewed it. That is, of course, nothing compared to the nearly 14 million who viewed the Claude post, which speaks not only to the relative size of Anthropic, but to the controversy surrounding This new product. So what actually was controversial? On the surface of it, this seems like it would be highly value additive. While they are biased and incentivized to say so, certainly it seems like all the folks inside Anthropic who are using it have had really positive experiences with it. Alex Albert, who does Claude& DevRelations, says this has been a game changer for our internal engine research teams. Rare to see a product get this much praise from some of the top engineers I know. Boris Cherney, the creator of Claude Code, points out, We built it for ourselves first. Code output per Anthropic engineer is up 200% this year, and reviews were the bottleneck. Personally, I’ve been using it for a few weeks and have found it catches many real bugs that I would not have noticed otherwise. Jared Sumner writes, Been using this in Bunn’s repo, Bunn JavaScript being a company that joined Anthropic recently. Jared continues, this in my opinion is the best product in the code review category today. It regularly catches extremely subtle bugs and rarely makes mistakes. CloudCodes Tariq writes, code review is so so good. One of those things I can’t remember how I lived without. What’s more, the discussion of code review and the inevitable changes to it is something that the larger agentic engineering community has been talking about recently irrespective Of this cloud product. Sean Wang slash Swix of Latent Space wrote, This is the final boss of agentic engineering, killing the code review. At this point, multiple people are already weighing how to remove the human code review bottleneck from agents becoming fully productive. I’m not personally (Time 0:11:30)
  • Anthropic Engineers Say CodeReview Was A Game Changer
    • Anthropic engineers reported a 200% increase in code output using internal CodeReview and praised its bug-catching.
    • Alex Albert and Boris Cherney described it as a game changer for internal research teams. Transcript: Nathaniel Whittemore Alex Albert, who does Claude& DevRelations, says this has been a game changer for our internal engine research teams. Rare to see a product get this much praise from some of the top engineers I know. Boris Cherney, the creator of Claude Code, points out, We built it for ourselves first. Code output per Anthropic engineer is up 200% this year, and reviews were the bottleneck. Personally, I’ve been using it for a few weeks and have found it catches many real bugs that I would not have noticed otherwise. Jared Sumner writes, Been using this in Bunn’s repo, Bunn JavaScript being a company that joined Anthropic recently. Jared continues, this in my opinion is the best product in the code review category today. It regularly catches extremely subtle bugs and rarely makes mistakes. (Time 0:12:35)
  • Budget For Inference Like Labor Not Software
    • Treat inference costs like labor costs and plan organizational headcount adjustments to justify token spend.
    • Sourcegraph CEO Dan Adler warns token budgets will face whiplash if headcount savings don’t materialize. Transcript: Nathaniel Whittemore The big thing that really caught people’s attention was around the pricing. In the pricing section of the Cloud Code Review docs, it says, Code review is billed based on token usage. Reviews average $15 to $25, scaling with PR size, code-based complexity, and how many issues require verification. And boy, were people shocked at this. Var Epsilon writes, The Cloud Code max $200 a month plan is literally infinite tokens. You can just write the one prompt to do a PR review locally, save it as a skill, and you get unlimited reviews. 15 to 25 per review is nuts. Dagster Labs’ Nick Schrock writes, 15 to 25 USD per review, my lord. Alex Kaplan says, $20 for a PR? Headblown emoji, exclamation question mark emoji, devinreview.com is free. So one part of this I think is just a sticker shock argument. If you’ve got most developers used to paying in the tens of dollars for coding tools and seeing review type features bundled into a broader plan, then this amount obviously seems much Larger. What’s more, people are immediately doing the scale math. If a team opens up lots of PRs, 25 per review sounds like it could explode very quickly into hundreds of thousands per developer per month. Now it doesn’t really matter that Anthropic is explicitly targeting a deeper review experience using multiple specialized agents, i.e. Probably not using it for every single time you have to review anything, but still people are just extrapolating out from that number and coming up with some very big numbers on the other Side. Another piece of this though is that I think it shows some chinks in the Anthropic and Opus armor right now. For a very long time, Anthropic was the only game in town when it came to coding. This has been well documented on this show to the point where we don’t really need to discuss it. However, ever since the release of GPT-5, OpenAI has been explicitly attempting to close that gap and even get out ahead, and increasingly there is some evidence that that effort has Been successful. Wes Winder writes, I really don’t understand why you would pay $25 for Claude to review a single PR when Opus 4.6 isn’t even the best model for deep code review. GPT 5.4 is the only model I trust for reviews right now. Shopify product builder Gil writes, imagine spending $15 to $25 onReview and you still have daily downtime and buggy releases. I’d be more confident in this feature if their production quality was higher. Fairmance Tebow writes, In all our benchmarks, Claude reviews are always just the worst. But don’t you worry, now you can pay between $15- $25 per freaking PR and you’ll have good reviews. Are you kidding me? And even some of the first people who are testing it aren’t necessarily coming away all that impressed. Daniel Sand tested Claude Code Review and said, I’m always the first to get excited when Claude ships something new, but in this case, enabling Code Review is just not worth it. Now, none of this is to say that there aren’t people who are taking the other side of this argument. Lindy founder Flow writes, People’s comments on the $15 to $25 per PR price tag remind me of Michael Bloomberg’s answer to people balking at the $2,700 per month cost of the Bloomberg Terminal. If you can’t make $2,700 a month with our product, you’ve got bigger problems to deal with. OpenCode’s Reese Sullivan writes, a $15 to $25 PR review bot that catches an incident that would have cost the company $5 million in breached SLAs and reputation is a no-brainer. I think maybe ultimately the even more interesting dimension of the cost part of the conversation actually has to do with the implications for where things are going. I think increasingly, as AI, and especially AI coding, weaves itself deeper into how we do work, cost profiles which were somewhat ignorable before become not ignorable anymore. Another way of saying it is that AI inference costs start to look a little bit closer to labor costs than to software costs. Sourcegraph CEO Dan Adler writes, 10%. Or even hundreds of millions of dollars in engineering organizations that cost billions in salaries seems reasonable. But if CTOs can’t deliver headcount savings, we’re going to see some real whiplash on token budgets in the next two to four quarters. Another way to put what Dan is saying is that something’s got to give. (Time 0:18:21)
  • Pricing Sparked The Backlash More Than Capability
    • Sticker shock over Anthropic’s $15–$25 per-PR pricing revealed broader anxieties about scaling costs.
    • Developers extrapolated per-review rates into massive monthly bills, fueling intense backlash despite product claims of deeper review. Transcript: Nathaniel Whittemore In the pricing section of the Cloud Code Review docs, it says, Code review is billed based on token usage. Reviews average $15 to $25, scaling with PR size, code-based complexity, and how many issues require verification. And boy, were people shocked at this. Var Epsilon writes, The Cloud Code max $200 a month plan is literally infinite tokens. You can just write the one prompt to do a PR review locally, save it as a skill, and you get unlimited reviews. 15 to 25 per review is nuts. Dagster Labs’ Nick Schrock writes, 15 to 25 USD per review, my lord. Alex Kaplan says, $20 for a PR? Headblown emoji, exclamation question mark emoji, devinreview.com is free. So one part of this I think is just a sticker shock argument. If you’ve got most developers used to paying in the tens of dollars for coding tools and seeing review type features bundled into a broader plan, then this amount obviously seems much Larger. What’s more, people are immediately doing the scale math. If a team opens up lots of PRs, 25 per review sounds like it could explode very quickly into hundreds of thousands per developer per month. Now it doesn’t really matter that Anthropic is explicitly targeting a deeper review experience using multiple specialized agents, i.e. Probably not using it for every single time you have to review anything, but still people are just extrapolating out from that number and coming up with some very big numbers on the other Side. Another piece of this though is that I think it shows some chinks in the Anthropic and Opus armor right now. For a very long time, Anthropic was the only game in town when it came to coding. This has been well documented on this show to the point where we don’t really need to discuss it. However, ever since the release of GPT-5, OpenAI has been explicitly attempting to close that gap and even get out ahead, and increasingly there is some evidence that that effort has Been successful. Wes Winder writes, I really don’t understand why you would pay $25 for Claude to review a single PR when Opus 4.6 isn’t even the best model for deep code review. GPT 5.4 is the only model I trust for reviews right now. Shopify product builder Gil writes, imagine spending $15 to $25 onReview and you still have daily downtime and buggy releases. I’d be more confident in this feature if their production quality was higher. Fairmance Tebow writes, In all our benchmarks, Claude reviews are always just the worst. But don’t you worry, now you can pay between $15- $25 per freaking PR and you’ll have good reviews. (Time 0:18:26)
  • Buy Reviews When They Prevent High Cost Failures
    • Evaluate ROI: pay for AI reviews if they prevent high-cost incidents and breaches.
    • Lindy founder Flow and Reese Sullivan compare $15–$25 per PR to Bloomberg-terminal economics and breach-avoidance savings. Transcript: Nathaniel Whittemore Lindy founder Flow writes, People’s comments on the $15 to $25 per PR price tag remind me of Michael Bloomberg’s answer to people balking at the $2,700 per month cost of the Bloomberg Terminal. If you can’t make $2,700 a month with our product, you’ve got bigger problems to deal with. OpenCode’s Reese Sullivan writes, a $15 to $25 PR review bot that catches an incident that would have cost the company $5 million in breached SLAs and reputation is a no-brainer. (Time 0:21:00)
  • Developers Express Existential Anxiety Over Automation
    • Developers voiced existential anxiety as agent tools erode core identity tasks like reviewing code.
    • Viral posts (e.g., Mo at Mo IO) and essays argue engineers feel their roles being washed away overnight. Transcript: Nathaniel Whittemore I was a 10x engineer, now I’m useless. It’s actually less dramatic than the caption makes it sound, but it’s a real honest exploration of a lot of the feelings that many developers are having right now as the fundamental Nature of what they do as developers has changed underneath their feet almost overnight. And it does feel to me a bit like part of the response to the code review feels a bit like watching the last part of the sandcastle that they’ve spent their whole lives building washed away Into the ocean. (Time 0:23:08)
  • Platform Power Raises Existential Risks For App Builders
    • Fears about platform power and pricing reflect concentration risk: platform providers can observe usage and build competing features.
    • Listeners warned Anthropic could absorb app-layer products after exposing developer usage. Transcript: Nathaniel Whittemore Now, there is one more piece of the negative response to code review that I think is worth tracking as well, which is not just about cost, but about pricing power. And this to me maybe represents another chink in Anthropics armor, although I don’t think it’s limited to Anthropics alone. Garb writes, Feels like the Wild West days of pricing. The general store has you hooked on their supply. They know it, and they’re telling you how much they’re going to fleece you. Because they can. Ejaz writes, Lol, Anthropic just killed a $50 billion industry with a single feature again. Companies pay $50k a year to scan their code for vulnerabilities. Anthropic’s code review does it for you in minutes for a fraction of the cost. Broadloom’s Todd Saunders uses an analogy. Anthropic is the new Amazon. Build on our platform and once you get scale, we will build a basics version of your product and put you out of business instantly. That was a quote to read from this from Varunram Ganesh who wrote, At this point, it’s pretty clear that if you are an app layer company using Cloud Code SDK, it is inevitable that Anthropic Sees your usage and then develops that tool in-house. One of the potential reckonings in the AI space is going to be questions of power and consolidation around the very small number of neutron star companies that are just absorbing everything Around them. (Time 0:24:04)