Designing an AI agent raises an immediate question: should its session live for years, or reset every day? The article argues for a daily reset. New products such as Grok Bot and other meta-harnesses encourage users to create agents, and stronger models make permanent sessions tempting. But long-running sessions rot from the inside. As conversational turns pile up, attention degrades; modern models may spot a single fact in a long document, but the article says even frontier models show agent memory that behaves like human memory and degrades as it grows. Temporary instructions also outlive their purpose: a March message saying “I have a cold this week, cancel morning meetings” can still make the agent avoid morning slots in November. Long sessions also widen the security boundary, because an agent holding multi-year read/write access to an inbox and calendar is an open door; one malicious email or calendar invite can poison the conversation and quietly hijack the schedule.

The winning pattern is short, explicit lifecycle: a daily coordinator lives for 24 hours, while individual tasks are delegated to narrow, ephemeral specialists. During the day, the coordinator remembers immediate context such as running fifteen minutes late or keeping two to three slots free for prep. At midnight, the active conversation wipes clean. When work needs doing, the coordinator does not execute directly; it delegates to a calendar agent, an email agent, or a news agent. Each helper lives briefly, gets only the tools it needs, performs the job, and disappears.

The article shows the system prompts that make this concrete. The coordinator’s prompt states its session lives for 24 hours, that in the morning the coordinator should load preferences.md and today’s calendar, that intraday it should delegate to sub-agents, and that at night it should save durable learnings to preferences.md and terminate. The calendar helper’s prompt is deliberately stateless: process one request, call the tool, report the result, and terminate, with time zone, duration, and availability checks spelled out. Before the day’s session wipes at midnight, an offline consolidation pass reviews the day, stores lasting preferences in a permanent note, and throws away the rest of the daily chatter.

This automatic sleep cycle is not what most current assistants do. Most bots leave threads open until the user clicks “+ New Chat” or context compaction silently drops the rules. The closing advice is simple: throw away the conversation and keep the rules in a file.