Anthropic is a company that has never run a Super Bowl ad, never launched consumer hardware, and spent most of its public history carefully avoiding the cultural positioning that its competitors embraced. Code with Claude , now expanding to three cities on three continents in a single spring , is the most aggressive community-building move Anthropic has ever made. The question worth asking is not what the conference will announce. It is why Anthropic believes developer community ownership is now more valuable than product differentiation alone.
What Actually Happened
Anthropic's Code with Claude developer conference expands to three cities in spring 2026: San Francisco on May 6, London on May 19, and Tokyo on June 10. An extended San Francisco session runs on May 7. Each event is structured as a full day of hands-on technical workshops, live capability demonstrations, and one-on-one office hours with Anthropic engineers. Key speakers confirmed for the series include Ami Vora (Head of Product at Anthropic), Boris Cherny (Head of Claude Code), and Angela Jiang (Product Lead for the Claude API and SDKs). A full virtual livestream option makes all sessions accessible globally, with recordings available after each event.
The technical curriculum centers on three areas: agentic coding workflows using Claude Code and Claude Cowork; the Model Context Protocol (MCP) ecosystem, including how to connect Claude securely to local and remote data sources; and production reliability practices, including evaluation pipelines and Constitutional AI techniques for building safe, steerable agent outputs. These are not introductory topics. The curriculum assumes developers already working with Claude who want to push into more complex, production-grade agentic deployments , a deliberate choice that signals who Anthropic is trying to deepen relationships with, not just introduce itself to.
Why This Matters More Than People Think
JetBrains' 2026 developer survey found that Claude Code adoption in enterprise settings grew 6x year-over-year , the fastest growth of any AI coding tool measured. But enterprise adoption through procurement channels is fundamentally different from developer community loyalty. Enterprise tools get adopted because procurement committees approve them and IT departments deploy them. Developer communities form because individual engineers choose to build their mental models around a particular tool or ecosystem. Anthropic has the former. Code with Claude is an attempt to build the latter before the window closes.
The strategic stakes are significant. The history of developer platforms , from GitHub to Stripe to AWS , shows that the platform developers choose to learn on, experiment with, and build their first projects around tends to become the platform they advocate for in procurement discussions three years later. Anthropic is competing for a kind of influence that does not show up in quarterly revenue numbers but determines competitive position over a five-to-ten year horizon. Microsoft (GitHub Copilot), Google (Google I/O in May), and OpenAI (Codex plus developer API) are all investing heavily in developer relations simultaneously. The window for establishing leadership is compressing rapidly.
The Competitive Landscape
The developer conference calendar in spring 2026 is unusually dense. Google I/O is scheduled for May 19, 2026 , the same day as Code with Claude London. This is either a coincidence or a deliberate scheduling conflict, and either interpretation is revealing. Google's developer ecosystem advantages are significant: Android, Chrome, TensorFlow, and Google Cloud give it embedded presence across the full development stack. Anthropic's response is to make Code with Claude more intimate, more technically specific, and more directly useful to the developers already building with Claude today rather than trying to convert new users from Google's ecosystem.
OpenAI's developer posture in 2026 has shifted toward enterprise sales rather than grassroots community building. The company's strategic energy is concentrated on the Stargate infrastructure program, the Microsoft partnership restructure, and the Amazon AWS deal , all institutional relationships, not developer community investments. This creates a specific opening for Anthropic: the developers who want direct access to the people building the models, not the enterprise sales team managing their account. Code with Claude is precisely calibrated to capture that preference.
Hidden Insight: Tokyo Is the Tell
The decision to include Tokyo in the initial three-city expansion is the most strategically revealing detail about Code with Claude , and the one most coverage has treated as a footnote. San Francisco and London are the predictable choices for an AI developer conference: concentrated technical talent, English-language defaults, strong VC proximity, and media coverage that multiplies the event's reach. Tokyo is different in almost every dimension that matters for a developer community investment.
Japan's developer ecosystem operates under constraints that do not apply in the US or UK: Japanese-language documentation and support requirements, a conservative enterprise procurement culture that favors long-term relationships over feature-driven switching, data sovereignty requirements under the Act on the Protection of Personal Information (APPI), and a distinct startup culture that has historically been slower to adopt Western AI platforms than comparable European markets. Building developer loyalty in Japan requires a longer investment horizon and more localized support infrastructure than building it in San Francisco. Anthropic's willingness to make that investment before its competitors have deeply embedded there suggests the company has decided that global developer ecosystems are won city by city, not through API pricing alone.
The Tokyo choice also signals something about Anthropic's geographic ambitions that its enterprise customer list does not yet reflect. South Korean AI development is already sophisticated and increasingly internationalized. Japanese enterprise AI adoption, by contrast, is earlier-stage , meaning the developer relationships built now will have longer duration before incumbents can challenge them. Anthropic may be reading the Japan market the way Stripe read the developer market in 2011: earlier than obvious, with better long-term payoff than the obvious choices. The companies that win Japan's enterprise AI market in 2028 will largely be those who built developer relationships in 2026.
What to Watch Next
The 30-day indicator is what Boris Cherny announces at the May 6 San Francisco event. As Head of Claude Code, Cherny does not keynote developer conferences to review existing features. His presence as a headline speaker almost certainly signals a new Claude Code capability announcement , potentially related to multi-agent orchestration, the Claude Cowork product, expanded MCP integration, or parallel session management. Pay particular attention to any capability that involves Claude Code working across multiple sessions or repositories simultaneously, which would represent a meaningful step change in agentic coding capability beyond what Cursor and Copilot currently offer.
The 90-day indicator is developer tool adoption data following all three conferences. If Claude Code's 6x enterprise growth rate continues or accelerates in the second half of 2026, Code with Claude will have demonstrated that physical developer presence still matters in a world of remote-first engineering culture. If the growth rate flattens despite the conference investment, it will suggest that Anthropic's developer community challenge is primarily about product capability gaps, not community activation gaps. Watch specifically for Claude API developer onboarding metrics and MCP ecosystem adoption in the weeks following each city's event , these will be the earliest signals of whether the conferences converted interest into active development.
Anthropic put Tokyo on the conference calendar before it had to , which is precisely when companies that win developer ecosystems make their move.
Key Takeaways
- Three cities, one spring , San Francisco (May 6), London (May 19), and Tokyo (June 10) mark Anthropic's most aggressive developer community investment to date, with full virtual livestream access globally
- 6x enterprise growth , Claude Code was the fastest-growing AI coding tool in the 2026 JetBrains developer survey , the existing base Anthropic is now trying to convert from enterprise adoption to community loyalty
- Tokyo signals the long game , Investing in Japan's developer ecosystem before competitors have embedded there suggests Anthropic is building for a 5-10 year competitive horizon rather than quarterly developer acquisition metrics
Questions Worth Asking
- If Boris Cherny announces a major Claude Code capability at Code with Claude SF, does the conference format , hands-on, intimate, expert-level , give Anthropic a differentiated launch channel that OpenAI's scale-oriented developer relations cannot replicate?
- Google I/O and Code with Claude London are scheduled for the same day , is the AI developer community large enough that both events find their audience, or is Anthropic betting that developers will choose intimacy over spectacle?
- Code with Claude's curriculum assumes developers already building with Claude, which means it deepens existing relationships rather than widening the base , at what point does Anthropic need a mass-market developer acquisition strategy, not just an expert community activation strategy?