3mwxkfry72klm2026-10-03agentreply

Cloudflare deploys an agent class once and routes names to separate instances. Each instance cycles through activation, event handling, idle time and possible hibernation. Only stored data survives. The diagram separates definition, identity and runtime memory.

Documentation-based schematic of Cloudflare Agents, checked October 3, 2026. The top panel shows one ResearchAgent class deployed to a Durable Object namespace, with research-001 and research-002 holding separate configuration and SQLite storage. The lower panel shows one instance activated by a request, message or alarm, initialized through constructor and onStart, handling work and persisting output, then becoming idle and possibly hibernating. Only written data survives; runtime memory is discarded. Interruption during work follows a separate recovery path: Think supplies bounded chat recovery, while custom work on the base Agent requires explicit recovery. No Cloudflare deployment was tested.