Claude Code: How Anthropic Builds Software with Agents

AI Engineergo watch the original →

Anthropic's team discusses how Claude Code and Claude Tag have shifted their internal development from manual implementation to high-level product strategy, utilizing proactive agentic workflows to land over 65% of their product PRs.

The Shift from Implementation to Product Strategy

The conversation highlights a fundamental change in the software engineering lifecycle. Previously, development was defined by long-term planning, PRDs, and manual coding. With the maturity of coding agents like Claude Code, the bottleneck has shifted from execution to product taste and business sense. Engineers are now spending less time writing boilerplate and more time defining the product experience, as the timeline from idea to implementation has collapsed from months to days.

Proactive Collaboration with Claude Tag

Anthropic has moved beyond individual agent usage toward team-based, proactive workflows. Claude Tag, an agent integrated into Slack, acts as a multiplayer interface for the team. It monitors bug reports, drafts PRs, and maintains team memory. By operating proactively rather than reactively, it currently handles over 65% of the team's product PRs. This shift has turned the agent into a team member that observes and learns from human social norms, effectively leveling up the team's collective usage of the tool.

Building Trust Through Infrastructure

As models evolve, the team relies on a robust, multi-layered evaluation (eval) framework to maintain quality. This includes internal dog-fooding, where the team fixes their own product issues before shipping, and a comprehensive suite of automated tests. For critical code, human code owners still provide manual review, but for outer-layer changes, the team has successfully transitioned to having Claude Code perform the review. This was achieved through a six-month process of building confidence, where human review was gradually phased out as the agent proved it could catch regressions.

Redefining Engineering Norms

Traditional engineering wisdom, such as the avoidance of rewrites, is being challenged. The speakers argue that in an era of high-quality test suites, rewrites are now a viable and beneficial strategy for modernization. Furthermore, the team emphasizes that because implementation is now cheaper, developers should stop "negotiating against themselves" and pursue more ambitious, complex projects that were previously considered too resource-intensive.

Safety and Future Design

Safety remains a priority, particularly for "Auto Mode." Anthropic utilizes external red-teaming to stress-test against prompt injection and data exfiltration. Looking forward, the team is focused on improving the interaction design of agents, aiming to make them better partners that can bridge the gap between abstract ideas and production-ready software without requiring constant human hand-holding.

  • #ai-agents
  • #dev-tooling
  • #software-engineering

summary by google/gemini-3.1-flash-lite. probably wrong about something. check the source.