How Claude Code Claude Codes

What It Covers

The Vergecast marks Claude Code's one-year anniversary with Boris Cherny, the tool's creator at Anthropic, examining how AI coding shifted from developer niche to mainstream productivity tool. A second segment with Verge reporter Hayden Field addresses data privacy frameworks for AI tools, covering what users actually surrender when connecting Gmail, calendars, and files to AI systems.

Key Questions Answered

• •AI coding adoption curve: Claude Code's coding contribution jumped from roughly 10% at launch to 100% for its own creator by November 2025, when Sonnet 4.5 released. The shift happened overnight rather than gradually — the model began autonomously running tests, opening browsers to verify visual output, and correcting pixel-level UI errors without human review, eliminating the need to open a text editor at all.
• •Non-developer adoption signal: Sales teams, product managers, and data scientists at enterprise companies including Spotify, Netflix, Nvidia, and Ramp now use Claude Code weekly — not just engineers. When Anthropic's own sales staff reached roughly 50% weekly usage, the team recognized the terminal interface was a barrier and built Cowork, a sandboxed virtual machine version with deletion protection designed for non-technical users.
• •AI feedback loop for product development: Approximately 30% of Claude Code's own shipped code now originates from the model autonomously scanning user feedback channels on Slack and GitHub, identifying reported bugs, and generating fixes without human assignment. This workflow became viable only with Opus 4.5 and 4.6 — earlier model versions lacked sufficient judgment to prioritize and act on unstructured feedback independently.
• •Privacy risk framework for AI tools: Treat AI data permissions with sharper scrutiny than standard apps because these companies are newer, less regulated, and operating under voluntary compliance frameworks they can revise without notice. If a company gets acquired, data policies can shift entirely. A practical rule: avoid sharing anything with a free AI product that you would not want public, since free products monetize user data by definition.
• •Training data ambiguity in terms of service: Even when AI companies explicitly state they do not train on connected Gmail or calendar data, separate clauses can permit training on any content a user copies, pastes, or receives as a response from those integrations. Consumer-tier accounts at Anthropic carry this caveat; enterprise accounts carry stronger protections. Reading privacy policies as living, frequently revised documents rather than fixed contracts is the practical approach.
• •Gemini's structural privacy advantage: Connecting Gmail to Google's Gemini involves one company accessing data it already holds, whereas connecting Gmail to Claude or ChatGPT creates a second corporate entity with a full data profile. Security principles favor fewer organizations holding complete data sets. For users already embedded in Google's ecosystem, Gemini presents a narrower attack surface for sensitive personal data than cross-platform AI integrations.