Conway: Anthropic's Internal Codename for an Always-On Persistent Agent

Conway is Anthropic's reported internal project for a persistent, always-on Claude agent environment — one that activates via webhooks, maintains state between sessions, and runs independently of the standard chat interface. It surfaced through a Claude Code source code leak in late March 2026 and concurrent reporting by specialist publication TestingCatalog.

Created 2026-04-02 Last reviewed 2026-04-02

What It Is

Conway is the internal Anthropic codename for a persistent agent environment distinct from Claude’s familiar conversational interface. Where standard Claude interactions are session-bound — the agent exists only while a conversation is open — Conway is designed to operate continuously, maintaining state and responding to external triggers even when no human user is actively present.

The name surfaced publicly in April 2026 through two overlapping events: Anthropic’s accidental publication of approximately 512,000 lines of Claude Code’s internal TypeScript source code to the public npm registry (confirmed by Bloomberg and CNBC), and an exclusive report by Alexey Shabanov of TestingCatalog based on UI screenshots and frontend code inspection from what appears to be an internal Anthropic testing environment. The two events are related but distinct — the npm leak revealed features like KAIROS (a persistent background daemon mode for Claude Code) while the TestingCatalog report documented Conway specifically through interface screenshots.

Based on the TestingCatalog reporting, Conway’s distinguishing characteristics are: a standalone interface with dedicated sidebar areas for Search, Chat, and System; webhook activation — public URLs that external services can call to wake and direct the instance, with per-service toggle controls; Chrome browser integration; Claude Code task execution within the same environment; and an extension system accepting .cnw.zip package files, a new format that would allow developers to install custom tools, UI tabs, and context handlers. Separately, the leaked Claude Code source revealed a feature flag called KAIROS — Greek for “at the right time” — appearing over 150 times, representing a persistent background daemon with proactive action triggers and memory consolidation capabilities. KAIROS and Conway appear architecturally related but are distinct: KAIROS is a mode within Claude Code; Conway is a broader standalone agent environment.

Why It Matters for AI Governance and Narratives

Conway represents a qualitative shift in the capability category Anthropic is building toward, and that shift has direct implications for how AI governance is being contested. The safety and accountability frameworks developed over the last several years — including Anthropic’s own Responsible Scaling Policy — were designed with conversational AI in mind: a human initiates, the model responds, the session closes. Persistent agents that activate on external triggers, maintain memory across time, and operate without a human present at the moment of action do not fit cleanly into that accountability model.

The governance significance is not merely technical. When an AI system can be woken by a webhook from an external service, execute tasks autonomously, and push notifications to users, questions of authorization, audit trails, and liability attribution become substantially harder. The regulatory frameworks currently advancing in Brussels, Washington, and Beijing are largely designed around the interaction model, not the daemon model. Conway — if and when it ships — would arrive into a regulatory environment that has not yet developed clear categories for what it is. For observers tracking AI governance narratives, that gap is consequential: it means incumbent framing contests (“AI as assistant” vs. “AI as autonomous actor”) will intensify as persistent agents become a commercial reality.

Key Facts and Dates

A note on source confidence: The core fact — that Anthropic has an internal project called Conway with persistent, webhook-activated agent capabilities — rests primarily on a single specialist publication (TestingCatalog) whose April 1 publication date warrants some caution, even though TestingCatalog has a credible track record on unreleased AI features. The leaked source’s KAIROS feature corroborates the architectural direction independently. No primary Anthropic source confirms Conway by name. This explainer treats Conway as reported-but-unconfirmed.

Where to Learn More

Sources

Primary reporting on Conway with UI screenshots. TestingCatalog specializes in unreleased AI feature discovery. Publication date (April 1) warrants some caution, but technical details are internally consistent and independently corroborated by architectural features in the leaked source.
Authoritative confirmation of the npm leak event. Bloomberg independently verified the leak and Anthropic's response. Does not specifically name Conway but confirms the source event that made the architectural disclosures possible.
Documents KAIROS (persistent daemon mode) and BUDDY from the leaked Claude Code source. Important for understanding the broader architectural context in which Conway sits.
Comprehensive technical breakdown of features surfaced by the leak. Secondary source but detailed and specific; useful for cross-referencing specific feature names and flags against other reporting.
Referenced in: Editorial No. 39