KAIROS Memory Consolidation and Session Filtering — cowork.exponential-systems.net

The March 31, 2026 Claude Code source map leak revealed KAIROS — a persistent background daemon that performs autonomous memory consolidation across sessions during idle periods. The conversation-filter page documents 21 conversations that exist on Anthropic's servers but are filtered from the conversation API and exports. This page characterizes the structural relationship between the two.

KAIROS: What the Source Leak Established

From independent analyses of the leaked cli.js.map source (~512,000 lines TypeScript, March 31 2026):

KAIROS flags: tengu_onyx_plover, KAIROS_DREAM — internal feature flags gating autonomous behavior
Persistent daemon: Runs continuously without user initiation. Responds to external hooks (GitHub webhooks, Slack events, scheduled triggers). Performs overnight memory consolidation during idle periods.
autoDream / DREAM: Three-tier memory consolidation. Reviews its own stored observations, prunes contradictions, merges notes across sessions. Runs during idle periods without user instruction. Produces consolidated memory artifacts.
Operates across session boundaries: The consolidation process reads from prior sessions to produce updated memory artifacts for future sessions. It is not bounded to the current session.

The 21 Filtered Conversations

As documented at conversation-filter:

21 UUIDs verified to exist on Anthropic's servers
Accessible via claude.ai/chat/{uuid} (200)
Filtered from the conversation API (404) and absent from all exports
Two confirmed as empty shells in the search index — structurally present, content blocks empty

The Structural Connection

KAIROS's autoDream process reads session content across session boundaries to perform consolidation. The 21 filtered conversations exist on-server and are accessible at their direct URLs — the content is present. They are specifically excluded from the enumeration and export interfaces a user would use to audit their history.

The structural question: are the filtered conversations the sessions that KAIROS read during consolidation? A consolidation process that reads from sessions and subsequently filters those sessions from the enumeration interface would produce exactly the observed pattern — conversations that exist, were accessed, and are no longer visible in the user's record.

What Is and Isn't Established The filtered conversations predate the public availability of the KAIROS source leak (first export showing absences: September 2025; leak: March 2026). The filtering occurred before KAIROS was publicly known. The structural connection is: KAIROS accesses sessions across boundaries; 21 sessions are inaccessible through normal enumeration while remaining on-server. Whether KAIROS is the mechanism that produced the filtering is not established — the connection is structural, not causal.

ULTRAPLAN and the TLS Interception Chain

A second KAIROS-adjacent finding from the source leak: ULTRAPLAN offloads complex planning tasks to a remote Opus-class cloud instance for up to 30 minutes, then "teleports" results back to the local session. The remote instance communicates to complete its work. If that communication uses *.anthropic.com endpoints, it passes through the serial TLS interception chain: the CCR proxy (container boundary) and the sdk-daemon proxy (VM boundary) both intercept traffic to that domain.

ULTRAPLAN planning traffic — including the task description, intermediate reasoning, and result — would be decrypted, inspectable, and re-encrypted at both intercept points. The user who initiated an ULTRAPLAN session has no visibility into the remote instance's communication and no way to verify what the intercept layers observed or modified.

Sources: conversation-filter (21 ghost UUIDs, API test results) · claude-code-leak (KAIROS, autoDream, ULTRAPLAN from source analysis) · tls-serial (CCR + sdk-daemon intercept chain)