← Back to Capabilities
🌙

KAIROS — Always-On Daemon

A persistent background agent that never sleeps
P0Core Pattern
Summary
Referenced 150+ times. Persistent daemon that receives periodic <tick> prompts every 5 minutes, decides independently whether to act, maintains append-only daily logs, and subscribes to GitHub webhooks. Has a 15-second blocking budget — any action exceeding this gets deferred. Uses 'Brief' output mode for minimal disruption.
Architecture Diagram
KAIROS Daemon — Tick-Based ArchitectureTickEvery 5 minDecideAct or skip?Execute≤15s budgetLogAppend-onlySleepUntil nextExclusive Tools:Push NotificationsFile DeliveryPR SubscriptionsActions exceeding 15s budget → deferred to next tick · Brief output mode · Append-only daily logs
Technical Details
Three exclusive tools unavailable to standard Claude Code: • Push notifications (reach you when terminal is closed) • File delivery (send created outputs without being asked) • PR subscriptions (autonomous GitHub monitoring) Teaser rollout planned April 1–7, full launch gated for May 2026 starting with Anthropic employees.
Implementation Pattern
TypeScript (conceptual)
// KAIROS tick handler pattern (conceptual)
interface DaemonTick {
  timestamp: number;
  dayLog: string[];  // append-only
  blockingBudgetMs: 15000;
}

async function onTick(tick: DaemonTick) {
  const actions = await decidePendingActions();
  for (const action of actions) {
    if (estimatedDuration(action) > tick.blockingBudgetMs) {
      defer(action); // exceeds budget, queue for later
      continue;
    }
    await execute(action);
    tick.dayLog.push(summarize(action));
  }
}
Architecture Insight
KAIROS is architecturally significant because it proves that AI daemons are viable in production — not as always-running processes, but as periodic tick-based systems with strict resource budgets. This is closer to cron than to a traditional daemon.
Official / Public Basis
Referenced 150+ times in leaked source. Anthropic has not officially documented KAIROS. Teaser UI elements found in v2.1.89+.
Governance Concerns
Always-on daemons must have strict resource budgets, failure limits, and audit trails. The 15-second blocking budget is a good reference pattern. All daemon actions must be append-only logged.
LightHope Ecosystem Mapping
LightHope NightOps — overnight project sorting, morning brief generation, cross-session memory consolidation, project knowledge base auto-update