Glean 拾遗
Recent picks

1pick · chronological

11-14

The five primitives behind always-on agents

Always-on agents are mostly asleep: an event wakes a worker, a short run executes, state is written back, and the agent sleeps again. The post decomposes the surrounding architecture into five primitives. An event inbox (durable table + handler + worker) replaces letting each event source call the agent directly, avoiding competing runs and lost events on crash. Timers split into agent-set follow-ups and recurring schedules, stored separately and fired by a polling scheduler that writes into the inbox. Memory is a directory of files for user instructions, user notes, past messages and task progress, with the rule that memory only holds what cannot be looked up elsewhere. Permissions rely on a credential-injecting proxy, classifier-based auto mode, and deferred tool calls that end a run mid-call and resume it from a new event. An outbox with a dispatcher paces delivery and enables retries. The only hard number is a 78% per-task cost drop on a long-horizon coding benchmark versus 40% on typical workloads.

claude.com · 15 min · Agent Architecture · Agent Infrastructure · Agent-Memory