Building always-on agents
This post explains that always-on agents are stateful and proactive, running on the same core loop as other agents but surrounded by architecture built from five primitives: an event inbox, timers, memory, permissions, and an outbox. It describes how each primitive works, including inbox best practices, follow-up versus scheduled timers, memory types such as user instructions and task progress, credential proxying and deferred tool calls, and outbox delivery pacing. It concludes with how the primitives form a repeating cycle in which each brief run is triggered by an event and can set timers that wake the agent again later.
Why it matters: Offers a concrete architectural blueprint for teams building proactive, stateful agents, with practical guidance on event handling, memory, permissions, and message pacing.