Apple's own developers had Apple Intelligence waiting in their toolchain. They shipped code with a Claude.md file baked in anyway. This isn't a packaging oversight — it's a verdict from the people closest to the metal.
The incident surfaced when an Apple application was found to contain Claude.md, a configuration file that tells Anthropic's Claude how to behave in a codebase. In developer circles, this is the signature of vibe coding: letting an AI assistant steer significant portions of the implementation. The file went viral on Chinese tech platforms, sparking the predictable wave of schadenfreude. How the mighty have fallen, the commentary went. Even Apple devs are vibe coding now.
But that framing misses the real story. Apple Intelligence exists. Apple's engineers know it exists. They chose Claude anyway.
The gap between what Apple has built and what developers actually want reveals something uncomfortable about the current state of AI-assisted development. Apple Intelligence is deeply integrated into the company's ecosystem — it handles notifications, drafts emails, summarizes pages. But for pure code synthesis, for the kind of iterative back-and-forth that defines modern AI coding workflows, developers are reaching for Claude, for Cursor, for GitHub Copilot. They're not reaching for what Apple shipped.
This isn't unique to Apple. Across the industry, the tools that win developer mindshare aren't the ones with the deepest OS integration. They're the ones that write better code, understand context more precisely, and get out of the way when a developer needs to stay in flow. Claude.md in an Apple app is a data point in a larger pattern: when developers control their own toolchain, Claude wins.
The technical reasons matter. Claude.md allows teams to define project-specific instructions — coding standards, architecture patterns, preferred libraries. It's a configuration that makes the AI a true team member rather than a generic autocomplete engine. Apple Intelligence, for all its polish, doesn't offer this kind of developer-facing customization. It serves the consumer, not the craftsman.
What happens next is straightforward to predict. Apple will either build competitive code-generation capabilities into its developer tools, or it will watch its own engineers continue to route around the official stack. The latter isn't unprecedented — iOS developers have always used third-party tools when Apple's offerings fall short. Xcode's competitors exist for the same reason developers embed Claude.md files: the official path isn't always the best one.
The irony is sharp: Apple positions Apple Intelligence as the future of human-computer interaction, but its own developers are writing that future with someone else's AI. That's not vibe coding. That's preference made visible by an accidental artifact.