Back
The VergeProductThe Verge2026-04-02

Claude Code Leak Reveals AI Pet and Always-On Background Agent

A source map file accidentally bundled with Claude Code 2.1.88 exposed Anthropic's full TypeScript codebase, revealing two unannounced features: a Tamagotchi-style AI companion and an always-on background agent mode.

Original source

Anthropic had an unintentional product reveal this week. A source map file shipped inside Claude Code version 2.1.88 left the company's full TypeScript codebase readable to anyone who looked closely enough. The exposed code surfaced two notable unreleased features: a persistent, Tamagotchi-style "pet" companion tied to Claude, and an always-on background agent capable of running tasks autonomously without explicit user prompting.

The Tamagotchi-style feature appears to be a persistent AI persona with some form of state or relationship model — implying Claude could develop a simulated ongoing "relationship" with users over time. The always-on agent, meanwhile, points toward an ambient computing model where Claude monitors context and acts proactively in the background, rather than waiting to be invoked. Neither feature has been officially announced or documented by Anthropic.

Source map leaks of this kind are a known risk in modern JavaScript and TypeScript development, where build tooling can inadvertently bundle human-readable source alongside compiled output. It's an operational security slip rather than a breach, but the result is the same: a detailed, unfiltered look at what a major AI lab is building before it's ready to show the world. Anthropic has not issued a public statement at the time of writing.

The leak raises genuine questions about both the product direction and the safety considerations of an always-on agent. Background agents that act without explicit triggers represent a meaningful shift in how AI systems interact with user environments — and they're likely to attract scrutiny from regulators and privacy advocates alike, regardless of how polished the final feature turns out to be.

Panel Takes

The Builder

The Builder

Developer Perspective

Source map leaks are the kind of thing that keeps DevOps engineers up at night — this is a basic build pipeline hygiene failure, not a sophisticated attack. That said, the always-on agent architecture buried in that code is genuinely interesting; running persistent background tasks without user invocation is a hard problem and I want to know how they're handling context windows and permissions. The Tamagotchi bit feels like a UX experiment, but the agent infra is the real story here.

The Skeptic

The Skeptic

Reality Check

Let's pump the brakes on the excitement — leaked source code shows what engineers are *experimenting with*, not what ships. Half the features buried in any company's codebase never see the light of day, and calling something 'Tamagotchi-style' based on variable names is a big interpretive leap. More concerning to me is that a company handling sensitive user data just accidentally published its own source code; that's the headline, not the feature speculation.

The Futurist

The Futurist

Big Picture

An always-on ambient agent is the clearest signal yet that AI labs are moving from tools you invoke to systems that live alongside you — this is the shift from calculator to operating system. The Tamagotchi framing is easy to mock, but persistent relational state between a user and an AI model is a foundational UX primitive that will matter enormously at scale. Anthropic didn't mean to show their hand, but what they revealed confirms the next battleground is ambient presence, not just chat quality.

The Creator

The Creator

Content & Design

A Tamagotchi-style companion from a company known for safety-first messaging is a genuinely surprising design swing — someone on that team is thinking about emotional engagement in a way that goes well beyond a chat interface. The risk is that 'relationship simulation' features tend to get either cringey or manipulative fast, and design execution will make or break it. I'm curious whether this is a bold UX bet or something that quietly disappears before launch.